It looks like we can add to the Christmas cheer by announcing that Seam 2.1.1 is now out. Seam 2.1.1 is largely a bug-fix release, with a number of notable performance improvements, especially around hot deploy. We've added support for PDF forms to the iText integration as well as OpenID support. Seam-gen now generates IntelliJ IDEA projects. And, I should also point out that we've changed a few of the URLs on examples to match up better with the example names. If you are developing on Seam 2.1, you should consider upgrading quickly to get the latest fixes.
[Download] [Reference Documentation] [JIRA] [Release Notes] [Migration Guide]
Created: 23. Dec 2008, 00:45 CET (Norman Richards)
Last Modified: 23. Dec 2008, 22:15 CET (Dan Allen)
Great job! Thanks a lot!
---- one world, one seam:)
I found this site from the great article for setting up Ivy for use with Seam. Is there a similar article to getting SeamTest running? I've been trying to get SeamTest working for awhile and I never quite get there.
It's nice that seam-gen now supports IntelliJ. Are there any plans to support generating maven2 pom.xml files? Preferable following the maven2 standard directory structure. It would be nice to able to do things like
Is it mandatory to use new CacheProvider from Seam in order to use jboss cache ?
Upgrading from seam 2.0.0CR2 to 2.1.1GA would appear to have broken previous jboss configuration , which started jboss cache by have treecache.xml in root of ear
Sinc eseam upgrade JBoss cache not starting. Can see it missing from jmx console
JBoss Cache should be auto-installed if you have a treecache.xml installed, through the cache providers. Please start a topic on the forums.
Hello!
There are points to be improved regarding validation with Hibernate Validator, right?
I'm having lots of trouble with validation against an annotated POJO. It's not only define your POJO and annotate it with your validation and in the presentation use the s:validate tag to validate your data against the POJO.
It seems that there are some conceptual problems with this. For example, if I only annotate a POJO attribute with @NotNull and I give it a nice message to display, and add the s:validate tag, as I submit the form I get an ugly Hibernate InvalidState message.
And if I set the attribute 'required true' in the inputText, my beautiful message is replaced by an ugly one from JSF. So it looks like a problem, right? Why do not rely only on annotations and s:validate tags for validation?
The idea seems to be so nice and clean, but it is not working yet. I'm needing to validate forms manually, since I can't have it done only with annotations and s:validate, which is annoying! Are JBoss Seam guys seeing this problem?
I like things to be simple and clean, and so like it lots of people in this area, and I appreciate so much the work of JBoss guys with Seam, but I pity this problem because I was so excited about using Seam and it being nice and clean and all, but I'm having a really hard time with this validation stuff.
Does someone knows if there is a fix for it in upcoming releases?
did anyone tried Web Beans 1.0.0.BETA1? it looks promising..
-Jani Syed
Hello Rodrigo,
I'd say that you have a configuration-issue in your project. I'm using Hibernate-Validators without the described problems since a year or so...
Cheers, Jan
shouldn't you use internationalization to put some to JSF or Hibernate ones instead of having then in your annotations? Ressources files are easier to change then recompiling your code to change your pretty messages.
Yes, this is a missing feature in JSF 1.2, which we added to JSF 2.
Yes, you should :-) Hibernate validator and JSF both support this.