RE: I'm sorry, but your browser is not supported

2013-05-25T00:53:00Z

网络是一条ADSL，然后一个tp-link带拨号和路由功能的“共享上网一体机”（TD-W89541G），设置很简单，没有发现里面有什么特别的配制。有没有什么办法解决？

RE: ListBuilder Add-On

2013-05-25T00:29:12Z

Is this working in Vaadin 7.0.6?

I am not sure, but I tried converting a TwinColSelect to a ListBuilder, changed the Sets to Lists, but somehow my values are not showing up in the right side. I build the list by adding in all of the IDs using addItem(), then use setItemCaption() to specify the labels to appear with each ID. The left side list appears to show all elements, with nothing in the right side. I am assuming that my ID (it's a class we use called EsfUUID that encapsulates a UUID) is somehow not matching.

Also, when I do not set a width, the left/right selection lists are narrower than the labels shown inside.

When I set to 100% width, it would sometimes appear and then shrink, and another time each of the left and ride sides appeared to be 100% (so it was twice as wide as my screen). Because these are inside a Disclosure (the Animator add-on), it's possible they are not working well together.

Does Vaadin 7 have a scheme for blocking navigation if a form is "dirty" (m

2013-05-24T23:28:17Z

Thought I read about some new confirmation dialog in Vaadin 7, but now cannot find it. We have our own scheme using Vaadin 6, but wondered if there was now support for closing windows or otherwise navigating away when changes have been made but not committed? Thanks!

RE: FilteringTable add-on

2013-05-24T23:15:53Z

What I had to do, that I'm not happy with, is pull the FilterFieldGenerator into my project and modify it.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

private Filter generateFilter(Property field, Object propertyId,
         Object value) {
      if (field instanceof DateFilterPopup) {
         return generateDateFilter(field, propertyId, value);
      } else if (field instanceof NumberFilterPopup) {
         return generateNumberFilter(field, propertyId, value);
      } else if (field instanceof OptionGroupPopup) {
         return generateGenericFilter(field, propertyId,
                  ((OptionGroupPopup) field).getFilterValue());
      } else if (value != null && !value.equals("")) {
         return generateGenericFilter(field, propertyId, value);
      }
      return null;
}

I test for the instance of OptionGroupPopup (my widget), then I send the generateGenricFilter() a value that the class itself composes. If there is a better way to do this, please tell me.

RE: RegexpValidator failing for all of my Vaadin 6-style form fields using

2013-05-24T22:23:34Z

Maybe I'm going about this the wrong way. Perhaps I don't need to use a Validator for the field anymore, but can rely on the Converter to throw an exception if it's not in the valid format. Is that the new way?

It seems that if I add an error message to the ConversionException, that does not get displayed to the user. They just get a "Could not convert value to EsfName" which is meaningless to the user. I'd like the conversion exception to be thrown and show it's message, or when I throw it, it still calls my validator so that message can be shown as the reason for the invalid field.

But I don't see how it can call my validator using an object rather than the string entered since an object cannot be created using an invalid value to begin with.

RE: RegexpValidator failing for all of my Vaadin 6-style form fields using

2013-05-24T22:12:23Z

I guess I'm a bit confused on how to proceed with this. My object has a perfectly good String representation, and the Converter handles this well (though automatic in Vaadin 6 via toString() and a constructor that takes a string).

But the validator is attempting to convert the string to my object type BEFORE it's been validated, and if the value entered into the TextField is not valid, it cannot even create my model object. I need to check the string version held in the TextField first. This is particularly an issue because of my object can only hold values 0 and 1, for example, and the user enters 2, the object cannot be created, and then on validation failure it then attempts to take the bad object and convert it to a string for the text field. I must be missing something about how this is done in Vaadin 7 since this worked like a charm in Vaadin 6.

RE: HEARTBEAT not found

2013-05-24T22:00:42Z

Apparently, I had the same problem, I repeated that twice and it worked:

Arnold Somogyi:

I am a little bit confused. Could you tell me why I need to map twice the VaadinServlet?
I mapped it once and everything is working very well except the HEARTBEAT.

And if the HEARTBEAT uses /VAADIN and I mapped the vaadinServlet to /VAADIN why HEARTBEAT is not working?

1
2
3
4
5
6
7
8
9

<servlet-mapping>
      <servlet-name>Vaadin Application Servlet</servlet-name>
      <url-pattern>/check/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
      <servlet-name>Vaadin Application Servlet</servlet-name>
      <url-pattern>/VAADIN/*</url-pattern>
</servlet-mapping>

RE: RegexpValidator failing for all of my Vaadin 6-style form fields using

2013-05-24T21:43:28Z

Thomas Mattsson:

That does sound correct. The whole point of the converters was to convert the data to a more 'real' format before validations/storage..

Perhaps, but it's not as easy as under Vaadin 6 where I needed no converter AND I could subclass the RegexpValidator to validate my own objects.

RE: Refresher

2013-05-24T21:08:37Z

Henrik Paul:

How did you recompile the widgetset? You could try running "mvn vaadin:clean vaadin:compile"

Henrik, I tried your suggestion (running mvn vaadin:clean vaadin:compile). The goals completed successfully, but the message still appears when the application is run.

RE: Component extensions, building widgetset.

2013-05-24T20:29:12Z

Thanks a lot!
I will give that a try as soon as possible.

RE: RegexpValidator failing for all of my Vaadin 6-style form fields using

2013-05-24T20:08:42Z

That does sound correct. The whole point of the converters was to convert the data to a more 'real' format before validations/storage..

RE: RegexpValidator failing for all of my Vaadin 6-style form fields using

2013-05-24T18:43:22Z

Further checking seems to indicate that my EsfName class which is tied to a TextField and has a Converter to go between String/EsfName displays fine in the form, but when it comes time to run my Validator, it receives an EsfName object which the regular expression validator cannot handle. So the validator appears to be getting directly from the data source without being converted to a string, which is only a bit confusing because if the user types in the TextField, it will be just a String until it's validated and can be converted to my EsfName type.

It seems I can no longer just extend RegexpValidator regardless of the Converter.

RE: Size of a component?

2013-05-24T18:20:43Z

Peter Walzer:

without using any vaadin addons?

That's an interesting requirement. I guess you could always write yourself a client side widget or extension to report this.

Just out of curiosity, where do you need the width of a component?

RE: FilteringTable add-on

2013-05-24T17:56:29Z

I am trying to move from an older version of Filter Table to 0.8.6. I have a custom popup widget that gets filled with all the possibilities on the column and displays them as an option group so the user can check as many as they wish. Then it also has a "wildcard" text field where they can enter wildcards.

I need a way to send

FilterGenerator.generateFilter()

these two sources, or a way to combine the option group and the wildcard input before generateFilter is called. So for instance, if two options are checked, Baseball and Basketball, and a wildcard of Foot, I might send generateFilter "Baseball, Basketball, Foot".

How would I do this? How do I "get between" the custom widget and generateFilter()?

RE: Vaadin 7 OSGi bridge - status quo

2013-05-24T17:41:18Z

We are getting progress.

See https://github.com/Atmosphere/atmosphere/issues/1100. Waiting for changes in atmosphere 1.0.14-SNAPSHOT to become part of maven repo. Then i hope that things work fine again.

RE: RegexpValidator failing for all of my Vaadin 6-style form fields using

2013-05-24T17:13:03Z

Thomas Mattsson:

The chain is Field->Converter->Validator->DataSource, so if you convert the value from a String to something else, then you need to use that something else in your validator.

Thanks, Thomas. I'm not sure what is different then. I mean, my validator always worked on a String, and I'm getting a String as expected in my Validator, but one issue I'm facing is that the field is optional (not required), so it can be blank. It's as if under Vaadin 6, a blank/null value in a TextField that was optional didn't call the validator, but now it does. Is that possible?

RE: Component extensions, building widgetset.

2013-05-24T17:12:28Z

So what the text that you pasted is trying to say, is, that the code you have at hand (the extension) needs to be compiled from Java into JavaScript. This is how Vaadin works in the browser. First of you have to get a widget set definition. That widgetset definition tells where GWT can find all the relevant files that should be compiled into Javascript. Explanation on how widget sets works can be found here. What you need on top of the example in that page is a row defining a package named 'client' to indicate that it has more files there is more files that needs to be compiled.
So basically this:

1
2
3
4
5
6
7

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE module PUBLIC "-//Google Inc.//DTD Google Web Toolkit 1.7.0//EN"
"http://google-web-toolkit.googlecode.com/svn/tags/1.7.0/distro-source/core/src/gwt-module.dtd">
<module>
<inherits name="com.vaadin.DefaultWidgetSet" />
<source path="client" />
</module>

Then you put that file somewhere in you src folder. Within the package where that file is, you create a new package named 'client'. Into that package, you put your extension's connector. Then you have to compile your custom widget set. Lastly, you have to inform your web.xml to use your newly compiled widget set. Now you are good to go.

RE: Recompile widgetset in Vaadin 7 with maven fails

2013-05-24T17:02:23Z

Unfortunately I'm still stuck on this. If anybody has a suggestion I would be most thankful!

mike

RE: Difference between JPAContainer and SQLContainer

2013-05-24T16:53:35Z

Two different techonoliges. SQLContainer uses, well, SQL to query a database directly. JPA stands for Java Persistance API and uses entities more directly. JPA is an abstraction of the database. For example the frameworks EclipseLink and Hibernate provide JPA support.

Compare SQL

SELECT * FROM Employee WHERE pay>3000;

with JPA

1
2
3
4
5

CriteriaQuery cq = cb.createQuery();
Root e = cq.from(Employee.class);
cq.where(cb.greaterThan(e.get("pay"), 3000));
Query query = em.createQuery(cq);
List<Employee> result = query.getResultList();

JPA has also JPQL which is quite close to SQL, and it can also be queried directly with SQL.

RE: SCSS compilation work-around

2013-05-24T16:21:55Z

Henri Sara:

If you compile the theme and place the generated .css file alongside with the SCSS file, no on-the-fly compilation of the theme is performed.

The easiest way to compile the theme is from the command line (see this tutorial), but copying the file from the browser should also work.

The tickets to support theme compilation in plugins are #10291 (Maven) and #10712 (Eclipse).

Perfect! Thanks, Henri. I'll just use the browser version for now until the Eclipse plugin compiler is working.

It would be nice, perhaps, when the VaadinServlet is not in production to use the styles.scss file -- if present -- even if styles.css is present, and when in production, to use styles.css directly without the compilation. Then we could store the final compiled styles.css in our project for version control and ease of release. Now we need to generate and keep styles.css somewhere in our version control so it goes to production, though not with its related theme files. (I know Ivy is the new way, but that tool produces the same issue in that our release structure doesn't include the files that need to be released without manually copying them over and hoping we have them all. Couldn't Ivy put the files it needs into WEB-INF/lib so when we release that, too, we already have the correct tools?)

Recent Posts

RE: I'm sorry, but your browser is not supported

RE: ListBuilder Add-On

Does Vaadin 7 have a scheme for blocking navigation if a form is "dirty" (m

RE: FilteringTable add-on

RE: RegexpValidator failing for all of my Vaadin 6-style form fields using

RE: RegexpValidator failing for all of my Vaadin 6-style form fields using

RE: HEARTBEAT not found

RE: RegexpValidator failing for all of my Vaadin 6-style form fields using

RE: Refresher

RE: Component extensions, building widgetset.

RE: RegexpValidator failing for all of my Vaadin 6-style form fields using

RE: RegexpValidator failing for all of my Vaadin 6-style form fields using

RE: Size of a component?

RE: FilteringTable add-on

RE: Vaadin 7 OSGi bridge - status quo

RE: RegexpValidator failing for all of my Vaadin 6-style form fields using

RE: Component extensions, building widgetset.

RE: Recompile widgetset in Vaadin 7 with maven fails

RE: Difference between JPAContainer and SQLContainer

RE: SCSS compilation work-around