[Installation, Configuration & Deployment] - Isolated ClassLoading in JBoss 4.0.4.GA
by skidvd
Hello,
I'm not sure if this is the right forum for this question ... I also tried the Tomcat forum without success ... please let me know if there is a better forum for this question.
Anyway, I'm attemtping to achieve isolated classloading for individual war based applications (without much success) in a JBoss 4.0.4GA environment. I understand that these issues have changed since at least the 3.x days as well as perhaps yet again since the 4.0.2 days from what I have found in the wiki at http://wiki.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration.
Anyway, I am hoping to have entirely self sufficient (they use ONLY the classes they contain in WEB-INF/classes and WEB-INF/lib and do not or conflict with anything else on the parent classloaders) war applications that do not use anything such as the MyFaces and log4j libs from the parent classloaders. From the wiki, I have tried the following. Here is what I have in my:
jbossweb-tomcat55.sar/META-INF/jboss-service.xml:
false
false
<attribute "FilteredPackages">org.apache.commons.logging
In each war I have added a WEB-INF/jboss-web.xml with the following content:
<jboss-web>
<class-loading java2ClassLoadingCompliance="false">
<loader-repository>
dot.com:loader=unique-archive-name
<loader-repository-config>java2ParentDelegation=false</loader-repository-config>
</loader-repository>
</class-loading>
</jboss-web>
However, this is not providing isolation for me (as adding MyFaces and/or log4j jars of different versions to my WEB-INF/lib causes conflicts symptomatic of non-isolated class loading).
Am I missing something unique in 4.0.4 or otherwise missing something? How can this desired behavior be achieved?
TIA!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3966995#3966995
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3966995
19 years, 8 months
[JBoss Portal] - Authentication-strength for access control
by falke2006
Hello,
I have been searching information about the possibility to use the information about the authentication method a client has used to authenticate against the server... to use this information for a decision about the redirect to e.g. a Portlet Page.
Example:
There is a Portlet instance within a Portal Page that is accessed by the user that requires at least a client-certificate. But when the user has been challenged for authentication before, he was logged in using form-based authentication.
Now the user should be challenged again, due to the fact of his low authentication strength.
===
Is there any possibility to set (and read at runtime) a required auth-strength for Portal resources? I could not find such a thing in the documentation but I know that it exists e.g. in the Apache WebServer.
Furthermore, is there maybe an extension to handle the described scenario?
Many thanks for any contribution!!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3966991#3966991
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3966991
19 years, 8 months
[Clustering/JBoss] - Re: Does clustering require traffic over 1098 as well as 118
by bstansberry@jboss.com
The traffic will go over whatever interface the HA-JNDI service is configured to use (which is typically an external interface, as HA-JNDI is used by clients).
I wouldn't say this was by design; it's more a side effect of using RMI. To make it go away you would need to:
1) Configure HA-JNDI to use the internal interface (set the BindAddress attribute in the HA-JNDI section of cluster-service.xml.) Obviously this is only an option if you don't have external clients that need HA-JNDI.
2) Prevent exchange of internal interface RMI stubs for clustered EJBs:
a) Use the PooledInvokerHA instead of the JRMPInvokerHA for clustered EJBs. Simplest is to edit conf/standardjboss.xml looking for occurences of
<invoker-mbean>jboss:service=invoker,type=jrmpha</invoker-mbean>
and replacing them with <invoker-mbean>jboss:service=invoker,type=pooledha</invoker-mbean>
OR b) Configure the JRMPInvokerHA (in cluster-service.xml) to use the internal address (set the "ServerAddress" attribute.) Again, this is only an option if you don't have external clients that need the EJBs.
There is a JIRA for 5.0 to convert HA-JNDI to use Remoting, which will remove the RMI issue for that service. For 5.0 clsutered EJBs already use Remoting.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3966990#3966990
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3966990
19 years, 8 months