Hi, we have configured our EJB 2.1 SLSB with a stateless-ssl-invoker as 
described in 
http://docs.jboss.org/jbossas/jboss4guide/r3/html/ch8.chapter.html. Works fine 
:-)

But how can we do this with our new EJB3-Beans in  Jbos 4.0.3? I have tested it 
with a standard jboss.xml file:


  |   <enterprise-beans>
  |     <session>
  |       
<ejb-name>com.camunda.toolkit.jbpm.service.AdminServicesImpl</ejb-name>
  |       <jndi-name>com.camunda.toolkit.jbpm.service.AdminServices</jndi-name>
  |       <invoker-bindings>
  |                 <invoker>
  |                     
<invoker-proxy-binding-name>stateless-ssl-invoker</invoker-proxy-binding-name>
  |                 </invoker>
  |       </invoker-bindings>
  |     </session>
  |   </enterprise-beans>
  | 
  | 
  |     <invoker-proxy-bindings>
  |         <invoker-proxy-binding>
  |             <name>stateless-ssl-invoker</name>
  |             
<invoker-mbean>jboss:service=invoker,type=jrmp,socketType=SSL</invoker-mbean>
  |             <proxy-factory>org.jboss.proxy.ejb.ProxyFactory</proxy-factory>
  |             <proxy-factory-config>
  |             <client-interceptors>
  |                 <home>
  |                     
<interceptor>org.jboss.proxy.ejb.HomeInterceptor</interceptor>
  |                     
<interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
  |                     
<interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
  |                     
<interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
  |                 </home>
  |                 <bean>
  |                     
<interceptor>org.jboss.proxy.ejb.StatelessSessionInterceptor</interceptor>
  |                     
<interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
  |                     
<interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
  |                     
<interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
  |                 </bean>
  |             </client-interceptors>
  |             </proxy-factory-config>
  |         </invoker-proxy-binding>
  |     </invoker-proxy-bindings>  
  | 


But it has no effect, we can continue to connect without SSL after this...

The application is deployed as .ejb3 archive.

Any ideas?

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3914145#3914145

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3914145


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to