[EJB 3.0] - Re: Is there an equivalent of @RemoteBindings in jboss.xml
by ALRubinger
I think my previous posts weren't as to-the-point as they could have been; sorry for that. And I've never invoked EJB3 over SSL, so everything in this post is just stuff I've come across while doing other related dev.
"sbivol" wrote : I'm not familiar with the Binding Manager, so I'd like to make sure I got it right. So you're saying that, if I:
| a) deploy the ssl-service.xml within the ejb jar just like in the ejb3 ssl tutorial for example
Nope...that file should go under your "deploy" directory...
"sbivol" wrote : b) not use any @RemoteBinding annotation or its equivalent jboss.xml constructs
Well, you'll need @RemoteBinding (or XML equiv) to override the "clientBindUrl" property, specifying a protocol of "sslsocket" in place of the default "socket". Something like:
@RemoteBindings({
| @RemoteBinding(clientBindUrl="sslsocket://0.0.0.0:3843", jndiBinding="StatefulSSL"),
| @RemoteBinding(jndiBinding="StatefulNormal")
| })
..which is from the Transport documentation http://docs.jboss.org/ejb3/app-server/reference/build/reference/en/html/t.... The above example binds the EJB both on SSL and non-SSL sockets, placing the proxy stubs in JNDI.
"sbivol" wrote : If I now DO NOT use this annotation, how would a client state that it needs to use a service over ssl or non-ssl?
The client may differentiate which transport to use by looking up the appropriate JNDI address.
I couldn't yet find documentation for the corresponding XML for jboss.xml - overriding these properties for @RemoteBinding was new in RC9 (http://jira.jboss.com/jira/browse/EJBTHREE-571) and I'm not sure if the docs are out there yet.
S,
ALR
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982581#3982581
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982581
19Â years, 6Â months
[JBoss Eclipse IDE (users)] - Re: JBossIDE-2.0.0.Beta2 enhancements to support complex Jbo
by garu
Ok, i know it may sound complicated, but that kind of configuration, ie keeping well separated the installation from the configuration/customization part was the only way to obtain that Jboss was accepted in the production environment and i'm really sorry that with eclipse and Jboss in 2006 i'm not yet able to do what was possible with Jbuilder and Tomcat back in 2002. Having a single installation/runtime and multiple instances/configurations.
Believe me, keeping that kind of configuration also in the pc has its advantages. Instead of spreading all the configuration changes in the various files i have all the customizations in a single place different from the installation and, for example, migrating from 4.0.4 to 4.0.5, which i did recently, costed me just the time to download and unpack the zip file.
Unfortunately it's since webtools was born that from time to time i try to see if i'm able to obtain what i need, with no luck and i guess this is another time i'll have to throw in the trash can all the JbossIDE/webtools again and resort back to the old ant way.
Are you really sure you cannot do anything in this direction?
In any case be sure i appreciate what you have done up to now with your ide.
Thanks, Gabriele
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982576#3982576
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982576
19Â years, 6Â months