Thanks. Our customer says they will not upgrade Axis on their end and
required that we write this particular web service using JAX-RPC.
NetBeans won't let me create a new JAX-RPC web service inside an EJB 3.0
project which is a real shame. All of the problems I have with NetBeans
over the last few years are centered around bugs or limitations in web
service features.
Thanks,
Ryan
glassfish_at_javadesktop.org wrote:
> From a spec perspective there's no limitation that all components in a module or application have to be one or the other. Each stateless session bean can be implemented as either a JAX-WS or JAX-RPC endpoint. Of course, JAX-WS is the recommended approach going forward. JAX-RPC will be a candidate for pruning from a future version of the Java EE platform and will not be available as an option for the new EJB 3.1 Singleton component.
> [Message sent by forum member 'ksak' (ksak)]
>
> http://forums.java.net/jive/thread.jspa?messageID=295440
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
>