[JBoss Seam] - making custom user-object available to Seam context
by axismundi
I am struggling a little bit with the logic of the Seam context.
Currently we get "RequiredException: @In attribute requires non-null value" messages after the user has logged in.
Requirement:
on authentication, an ApplicationUser object should be made available to Seam-context for later usage.
Current solution:
our authenticator-class is supposed to outject a property to the Seam-context:
@Out
private ApplicationUser applicationUser;
or, alternatively, make itself available :
@Name("authenticator")
public class Authenticator {....
However, none of both is available in the Seam-context after the user has logged in!
I suppose, the reason is that once Authenticator.authenticate() returns true indicating successfull authentication, Seams Identity-class expires the current context and creates a new context. Hence, both objects, applicationUser and authenticator, are LOST.
So, what is best practise to make our custom user-object available to the session?
org.jboss.seam.security.Identity doesn't offer something like "setAttribute".
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095507#4095507
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095507
18Â years, 9Â months
[Installation, Configuration & DEPLOYMENT] - Re: 5.0.0 beta 2 and virtual hosts
by david.wade
JBoss by default has an application deployed on the root context "/" which I believe will be visible across all virtual hosts as it is not bound to any particular virtual host.
That root application (look for ROOT.war in the deploy directory) doesn't really provide any critical functionality, just links to the jmx-console, the web-console and tomcat status etc.
Your options are to remove the application -just delete the entire directory or to edit the web.xml to move it off the root context.
Have always thought it rather inconvenient/awkward that the root context is already used in JBoss. It would be much better if both that root application and the jmx and web consoles were under an appropriate context like /jboss-admin. Having them under a single context not only gets them out of the way, it makes it simpler to restrict access at a network dispatcher or apache level.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095500#4095500
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095500
18Â years, 9Â months
[JBoss Tools (users)] - Re: Update to JBoss IDE beta3 -> lots of problems ...
by max.andersenï¼ jboss.com
The packaging was changed because it was slow (e.g. not incremental,dependent on ant, no exploded packaging option) and cumbersome to setup (I personally could not figure out the old packaging without docs)
If you find the old packaging easy to setup then please tell us what is broken with the new one.
e.g. I just went back and retried archiving and I could only find one issue that was trivial to work around.
Here are the steps I did:
Select project
Open Archives View
Click WAR
complete wizard/Press Finish
The generated war has one issue, lib has a folder called lib with jars instead of in root so I just changed the **/*.jar filter to look in lib folder directly instead of root project.
And if i change the war to be exploded I can browse it easily and the war is constantly uptodate; i don't have to cnostantly press archive/packaging.
Please tell me what is wrong with that.
Is it the ant integration you are missing the docs for or ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095487#4095487
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095487
18Â years, 9Â months