[JBossWS] - Re: How to configure <application-policy name=
by joncmuniz
It's very very easy!!!!!!!!!!!!!
| <!--
| A template configuration for the JBossWS security domain.
| This defaults to the UsersRolesLoginModule the same as other and should be
| changed to a stronger authentication mechanism as required.
|
| <application-policy name="JBossWS">
| <authentication>
| <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule"
| flag="required">
| <module-option name="usersProperties">props/jbossws-users.properties</module-option>
| <module-option name="rolesProperties">props/jbossws-roles.properties</module-option>
| <module-option name="unauthenticatedIdentity">anonymous</module-option>
| </login-module>
| </authentication>
| </application-policy>
| -->
|
CHANGE FOR THIS ----------
| <application-policy name="JBossWS">
| <authentication>
| <login-module code="org.jboss.security.auth.spi.LdapLoginModule"
| flag="required">
| <module-option name="java.naming.factory.initial">
| com.sun.jndi.ldap.LdapCtxFactory
| </module-option>
| <module-option name="java.naming.provider.url">
| ldap://YOUR IP:PORT LDAP/
| </module-option>
| <module-option name="java.naming.security.authentication">
| simple
| </module-option>
| <module-option name="principalDNPrefix">uid=</module-option>
| <module-option name="principalDNSuffix">
| ,ou=users,dc=cds,dc=com
| </module-option>
|
| <module-option name="rolesCtxDN">
| ou=groups,dc=cds,dc=com
| </module-option>
| <module-option name="uidAttributeID">member</module-option>
| <module-option name="matchOnUserDN">true</module-option>
|
| <module-option name="roleAttributeID">cn</module-option>
| <module-option name="roleAttributeIsDN">false </module-option>
| </login-module>
| </authentication>
| </application-policy>
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225646#4225646
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225646
17 years
[Clustering/JBoss] - Re: Load balancer to wit till the jboss server started
by tosaravananm
We use JAAS Authentication policy.
To explain the problem clearly,
We have a rich client developed on eclipse rcp, login to the application will be done using this rich client. And we use client side interceptor as a load balancer and RoundRobin as a load balancing policy.
RoundRobin load balancing algorithm will select the targets(JBoss servers) in a circular fashion.
We get the problem in the following sequence
1. Start the target1 (JBoss server1)
2. Login to the application (After server1 started fully)
3. Start the target2(JBoss server2)
The calls are hitting the server2 before it started fully, and the method invocation end up in a failure because the call was for the service which is to be deployed( because the server is in the process of starting and some of the services needed are not deployed yet).
Is there a way we can notify the load balancing algorithm(RoundRobin) to choose the target(JBoss server for invocation) which is fully started with all the services deployed(meaning that the server is fully started with the attribute change notification org.jboss.system.server.started).
And to discard the targets for invocation if the target is in the process of starting.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225642#4225642
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225642
17 years
[JBoss Tools (users)] - birt intergration param tag
by sjikkebats2
<b:birt designType="embed" designName="test.rptdesign" embeddable="true" masterpage="false">
<b:param name="sample" value="#{revenueParameterSelector.query}"/>
</b:birt>
gives a NPE:
org.jboss.seam.birt.ui.UIParameter.restoreState(UIParameter.java:151)
javax.faces.component.UIComponentBase.processRestoreState(UIComponentBase.java:1141)
javax.faces.component.UIComponentBase.processRestoreState(UIComponentBase.java:1157)
javax.faces.component.UIComponentBase.processRestoreState(UIComponentBase.java:1157)
javax.faces.component.UIComponentBase.processRestoreState(UIComponentBase.java:1157)
org.ajax4jsf.application.AjaxStateManager.restoreView(AjaxStateManager.java:414)
com.sun.faces.application.ViewHandlerImpl.restoreView(ViewHandlerImpl.java:290)
org.jboss.seam.jsf.SeamViewHandler.restoreView(SeamViewHandler.java:93)
com.sun.facelets.FaceletViewHandler.restoreView(FaceletViewHandler.java:316)
org.ajax4jsf.application.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:116)
com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:141)
com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251)
com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177)
org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267)
org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380)
org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507)
org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
java.lang.Thread.run(Thread.java:595)
what can be the problem?
I use:
jboss-seam-2.1.1.GA
jboss-eap-4.2
BIRT Reporting Runtime Component 2.3.0
Seam Tools for Eclipse Version: 3.0.0.GA-R200903141626-H5
Eclipse Platform Version: 3.4.2
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225637#4225637
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225637
17 years