[JBoss Seam] - Re: Trinidad 1.0.0, Seam and JBoss 4.0.5
by petemuir
"stephen.friedrich" wrote : Thanks a million, Pete.
| Maybe I will just update JBoss and JSF versions at the same time as switching from ADF Faces to Trinidad.
| Seemed like a good idea to take the smallest step possible and update one after the other and check that nothing gets broken along the way.
It's probably worth it if you can - you will need to if you want to remain current with releases of Seam, as to run Seam 1.3 (and later) on JBoss 4.0.5.GA would need significant work! Generally the JSF 1.2 RI seems "better" than myfaces (partly as its a newer spec!) e.g. better reporting of errors.
anonymous wrote : I noticed that seamdiscs puts the myfaces api jar in the ear and only the impl jar in the web module. That's a combination I have not yet tried. Will check if that works this evening.anonymous wrote :
| |
| | I take it you mean trinidad? Thats needed so that you can get at the trinidad model classes (such as TreeModel) from your business layer)
| |
| | anonymous wrote : I don't (yet) need jboss-seam-trinidad.jar if I don't need the special handling of Trinidad's data model, right?
| |
| | Exactly. It will only ever be optional - containing enhancements and possibly making configuration easier.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042777#4042777
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042777
17 years, 4 months
[Beginners Corner] - Re: Seam Deployment Error
by jeffowen
OK, I've cracked what the cause is. Perhaps someone who understands the annotations could now explain why it happens:
It goes wrong if the code has @Stateful commented out (or I use @Stateless instead):
package org.jboss.seam.example.booking;
//imports ......
//@Stateful
@Name("myAction")
@Scope(EVENT)
@Restrict("#{identity.loggedIn}")
....
// other code
...
@Destroy @Remove
public void destroy() {}
but, not if I don't comment out the @Stateful
package org.jboss.seam.example.booking;
//imports ......
@Stateful
@Name("schoolList")
@Scope(EVENT)
@Restrict("#{identity.loggedIn}")
....
// other code
...
@Destroy @Remove
public void destroy() {}
It seems to be associated with the presence of the @Destroy and @Remove tags. If these are present and the bean is not @Stateful then I get this deployment error. I sort of understand from the tutorial that you need @Destroy @Remove if the bean is stateful. I didn't get that you couldn't have them if it wasn't.
I supposed (perhaps naively) that this type of error would be picked up at compile time.
Is there some kind of checker that can be run to look for this sort of thing?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042776#4042776
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042776
17 years, 4 months