AW: [JBoss-dev] JNDI binding for J2EE1.4 compliant webservices
> -Ursprüngliche Nachricht- > Von: Scott M Stark [mailto:[EMAIL PROTECTED] > Gesendet: Donnerstag, 20. November 2003 16:07 > An: [EMAIL PROTECTED] > Betreff: Re: [JBoss-dev] JNDI binding for J2EE1.4 compliant > webservices > > > I agree with that, so what is the confusion? >From my reading, I was seeing the relation between server and client programming more analogously to the existing EJB/J2EE specification bits. I was proposing to bind the service references into (global) JNDI by the JSR109Deployer regardless of whether a client app is present (as we do with the ejb stubs). The JSR109ClientDeployer would then only live in client processes and just dealing with generating link-refs into the local client JNDI. Furthermore, there is IMHO the possibility (requirement) to use service-endpoint references in the server programming model just as ejb-ref and servlet-ref. CGJ ### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: AW: [JBoss-dev] JNDI binding for J2EE1.4 compliant webservices
I don't see a problem with doing that, and in fact, if the behavior of the deployer is more consistent with existing, can reuse existing logic, etc. if this is the mode of operation then this is fine. Its really an implementation detail that the spec is not going to define. It would also probably simplify the j2ee application client because without the server side setup of the jax-rpc binding the app client deployer has to do this. -- Scott Stark Chief Technology Officer JBoss Group, LLC Jung , Dr. Christoph wrote: From my reading, I was seeing the relation between server and client programming more analogously to the existing EJB/J2EE specification bits. I was proposing to bind the service references into (global) JNDI by the JSR109Deployer regardless of whether a client app is present (as we do with the ejb stubs). The JSR109ClientDeployer would then only live in client processes and just dealing with generating link-refs into the local client JNDI. Furthermore, there is IMHO the possibility (requirement) to use service-endpoint references in the server programming model just as ejb-ref and servlet-ref. CGJ --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
