This is not a seam question at all, is it?
Anyway, read the following pdf, especially the sections about type erasure.
http://java.sun.com/j2se/1.5/pdf/generics-tutorial.pdf
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4002155#4002155
Reply to the post :
http://docs.jboss.com/seam/1.1GA/reference/en/html/concepts.html#d0e2489
anonymous wrote :
| 3.2.3. Entity beans
| Entity bean components do not support bijection or context demarcation. Nor
does invocation of an entity bean trigger validation.
View the original post :
Interesting indeed: I was running JDK 6.
Changed JDK for JBoss to 1.5 and it deployed fine.
As a double check I changed back to 6 (simply restarting the server with the
ear still in the deploy directory): The error reappeared
So I guess you should change the import.sql anyway. It's an easy
Seam 1.1.0 GA
Built registration example with ant, deployed to JBoss AS 4.0.5.
When I leave the password field empty I get a message Validation Error as
expected.
However if I enter one to four characters, I get a nasty exception:
01:48:04,593 ERROR [[Faces Servlet]] Servlet.service() for
Seam 1.1.0.GA, JBoss 4.0.5.GA
Currently deployment fails with this exception:
Caused by: java.sql.SQLException: Wrong data type: Timestamp format must be
-mm-dd hh:mm:ss[.f]
| at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
| at
Huh? That's exactly what I meant: The value of embeddedEjb is jardcoded to
false in this snippet:
[EMAIL PROTECTED] wrote : Here is a quote from the ant build:
|
| filter token=embeddedEjb value=false/
| |
In another place in the build file it's hardcoded to true.
So the value defined
For the benefit of others searching the forum:
http://jira.jboss.com/jira/browse/JBSEAM-501
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3994919#3994919
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3994919
I think you should use @Length(min=1) instead.
Empty fields give zero length strings rather than null strings.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3994920#3994920
Reply to the post :
It's quite confusing: The ant build never uses this setting at all, but has the
values hardcoded in the targets.
When I use my IDE to build (so that ant filter tokens are not replaced in
component.xml), then the resulting ear is not deployable to JBoss because it
wants to use an embedded ejb3
The docs say at several places that you have to download/use the installer to
be able to use EJB3, but where is that darn thing?
I can see the installer download for 4.0.4, 4.0.3, ... but where is the 4.0.5
version?
View the original post :
I haven't found it in the reference:
Does bijection, context demarcation, and validation work on SLSBs and SFSBs
even if those beans are not Seam components (i.e. have no @Name annotation)?
My understanding is that it could work, because the seam interceptor defined in
ejb-jar.xml applies to
Oops, I can answer my own question :-(
A look into the SeamInterceptor source shows that it explicitly ignores
everything that isn't a seam component.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3972965#3972965
Reply to the post :
Seam reference:
anonymous wrote :
|10.9 Annotations for use with JSF dataTable
| They appear on attributes.
|
|@DataModel - exposes an attribute of type List, Map, Set or Object[]
|
Annotation sources:
anonymous wrote :
|Annotations targets are both
Also it does not only work for Object[] but also for arrays with specific
component type, e.g. Hotel[]
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3972300#3972300
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3972300
I think the only way to do this is to create a getter that returns the already
wrapped field and then use the parent components name , something like
|public DataModel getListModel() {
| return new ListDataModel(list);
|
then #{component1.listModel} and #{component2.listModel}
Me too :-(
You've beat me by one minute, so now there are JBSEAM-345 and JBSEAM-346.
BTW: JetBrains already resolved there Jira Issue and even have a new EAP
version out that includes the fix:
http://www.jetbrains.net/jira/browse/IDEADEV-9090
View the original post :
Currently ejb-jar.xml files in seam examples (1.0.1 GA) use just ejb-jar.
How about adding full, standard-compliant declaration?
ejb-jar xmlns=http://java.sun.com/xml/ns/javaee;
| xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
|
17 matches
Mail list logo
