I'm having a few difficulties understanding the observed behaviour of my
conversations.
I have an application which starts 2 conversations one after the other. Both
conversations are defined on stateful EJBs with methods annotated with @Begin.
Both of these 'begin' methods are called, so at
We've implemented a captcha test which works well when saving state on the
client. However, if the state is set in web.xml to be saved server side:
context-param
| param-namejavax.faces.STATE_SAVING_METHOD/param-name
| param-valueserver/param-value
| /context-param
Then the
Okay, that makes sense. Thanks for the speedy response.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4069899#4069899
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4069899
___
Hi,
Following the Seam reference, I've setup a login page using the identity
management facilities. The log in works fine, and in my Facelets I can use the
following successfully:
s:div rendered=#{identity.loggedIn}
| YOU ARE LOGGED IN
| /s:div
I've also setup the JBoss Rules engine,
A Facelet is referencing the name property of the authenticator, as follows:
h2name = #{authenticator.name}/h2
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4069864#4069864
Reply to the post :
I've now tried invoking the tryRulesEngine() from a command button (rather than
via the property accessor) and it works.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4069868#4069868
Reply to the post :
The Seam homepage states:
you can use Seam in any J2EE application server, with one caveat: you will not
be able to use EJB 3.0 session beans. However, you can use either Hibernate or
JPA for persistence, and you can use Seam JavaBean components instead of
session beans
