[JBoss Seam] - Re: Seam configuration questions
by lightbulb432
Thanks for that information about the jmx-console...I'm playing around with it right now and it seems very useful!
A few questions about these classloading issues that have come up by me reading the JBoss ClassLoading wikis:
1) What is the relationship between UnifiedClassLoaders and EARs, WARs, EJB-JARs, and regular JARs deployed in the application server? The following link doesn't explicitly say whether every archive has one and only one UCL:
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossClassLoadingUseCases.
What about an archive with sub-archives (e.g. an EAR containing WARs, JARs, and EJB-JARs)? Do they ALL share the same UCL? (My question asks more about this one...)
2) From http://www.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration :
"There are two levels of scoping, isolation from other deployments, and isolation that overrides the loading of JBoss server classes. With nested modules, only the top level file may specify class loader scoping. If you have a .ear file containing other modules, only scoping specified in the .ear's META-INF/jboss-app.xml is used. This also applies for any other deployment which contains sub-deployments. For example, if a .sar contains a .war deployment, only the .sar META-INF/jboss-service.xml scoping has effect."
Does this mean that every class in a given top-level archive (or sub-archive of it) has been loaded by the same classloader, and therefore absolutely any class can see any other class within the top-level archive (or sub-archive)?
3) How does the exception with classes in the WAR file occur (where things in the WAR file can't be seen elsewhere in the archive by default)? Is the WAR's jboss-***.xml file ignored? (i.e. The equivalent of it always turning ON scoped classloading for that WAR?) Why is it treated different from other archive types?
4) Is saying that an archive has scoped classloading the exact same as saying that the archive has its own UCL?
Thanks a lot for your help.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991844#3991844
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991844
19 years, 4 months
[Security & JAAS/JBoss] - Re: How to implement Federated SSO using our own custom logo
by sohil.shah＠jboss.com
njw-
here is a possible solution using Federated SSO:
JBoss Federated SSO stack fits on top of any arbitrary web application regardless of their network location.
All the web apps that need to be federated (termed form a federation of partner sites), need to integrate this stack as per the instructions provided on the project's wiki.
Now, once the user is authenticated using the central login application that you are talking about, a SAML token will be circulated through the federation and processed by the Federated SSO stack in each web application.
anonymous wrote :
| I've downloaded JBoss Federated SSO but failed at the first hurdle because we're not using LDAP. I can see that I need to implement my own LoginProvider but cant work out what form this should take (war, ear etc), how to deploy it, or how it relates to the logon app we need to build, or how our 'business' apps understand which user they are dealing with
|
You are correct, you need to implement the LoginProvider which integrates with your Identity Store which I believe is an Oracle database. You can package this up in a jar file and drop it into the jboss-sso.sar file deployed with each one of your web applications
Hope this helps
Thanks
Sohil
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991841#3991841
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991841
19 years, 4 months