Back- and forward-navigation between 'secure' pages will only be restricted
after logging out if you have specify the page property login-required="true"
for those pages you do not want the browser to cache in memory.
For example (in pages.xml):
|
| ...
|
|
If you log-out from a pag
This is an example of an approach I have used for drop-down lists. Each
constant is instantiated with the key defined in the messages properties file:
| public enum Salutation {
|
| MR("salutation-mr-label"),
| MRS("salutation-mrs-label"),
| MS("salutation-ms-label");
Tim, thanks for the feedback.
anonymous wrote :
| This is going to be *slow*. I'm assuming this is not what you intended to
do.
No, it was not intentional but an oversight on my part due to my limited
experience with messaging.
I have changed over to the JmsXA connection factory and this a
Hi Ron,
Thanks for your response. I have spent a bit of time investigating the
circumstances that trigger the WARN message, and can advise that it only seems
to be triggered after a call to the connection close() method.
If you run the following code snippet in a session bean you ought to be ab
Apologies, forgot to mention - I'm running jboss-messaging-1.2.0.SP1 on
jboss-4.0.5.GA
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040193#4040193
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4040193
__
I've migrated a MDB from JBossMQ to JBoss Messaging which works as expected,
however I am getting 'unrecognised listener ID' warning each time it fires, and
also when the JBoss server instance shuts down. Here's an excerpt from the
server output:
| ...
| 14:26:40,328 WARN [BisocketServerI
Pete, I have come across this same problem using the EJB @Timeout annotation on
a bean method. In my case the seam injected component was null within the scope
of the annotated method only (the injected component worked perfectly in the
other methods within the same bean!).
By trial and error I
Thanks for quick response.
Presumably the page attribute login-required, as in
anonymous wrote :
|
|
performs the same function as the empty page element so only one
needs to be specified?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=401871
I have also noticed my log filing up with NotLoggedInException stake traces
even though redirection is working fine.
Shane also commented on this in Jira JBSEAM-752 so could someone advise if this
is going to be looked into. Thanks.
View the original post :
http://www.jboss.com/index.html?mod
P.S. Components.xml remains unchanged i.e.
|
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4017807#4017807
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4017807
___
I've tried to apply the settings via the 'class' and 'precedence' attributes of
the element but to no avail.
My implementation of Identity does work however with the following annotation -
@Install(precedence = DEPLOYMENT). According to the javadocs this is the
"precedence to use for component
Pete, I had overlooked the extra attributes on the tag
that provide for a bespoke Identity so thank you for making me revisit this -
I will amend my configuration.
Mike, thanks for your pointers. I actually got my Identity working by changing
the precedence as per your suggestion.
Thank you
Thanks for response Pete.
One problem I have run up against is the annotation
@Name("org.jboss.seam.security.identity") is not unique - trying to use this in
the derived class as per your code snippet throws
"java.lang.IllegalStateException: Two components with the same name and
precedence: or
I've had no problems implementing the latest authentication/authorisation
security features thanks to the contributors to this thread :)
I now need to roll my own implementation of org.jboss.seam.security.Identity to
include a third log-in form attribute called 'organisation'. This identifies
t
14 matches
Mail list logo
