No, I am not able to follow you. AFAIK, in Java EE, you can either
develop an EJB or Servlet based web service end point. Now, there is a
third option: which is JAX-RS. When you designate your Java class with
one of those component types, an appropriate container manages their
life cycle and hence will perform necessary dependency management. So
far, I don't see any need for Spring. You can then package the
components into an archive (e.g., a war file) and deploy it. If you add
necessary OSGi metadata, then you can deploy as an OSGi bundle.
Thanks,
Sahoo
glassfish_at_javadesktop.org wrote:
> Hi Sahoo,
>
> Thanks for the reply.
>
> I would like Spring to wire my webservice (kindly refer to my configuration, applicationContext.xml).
> These configurations wire the beans fine but do not initialize the beans. So whenever I try to invoke the web method, the runnable bean does not run.
>
> Am I in the wrong direction for using spring for wiring the classes?
>
> As for the osgi bundles, I was hoping I can "get bean" from a factory from the apache felix to be used by my web service.
>
> (Sorry if I not able to say it as clearly as it should be :) )
>
> Thanks,
> [Message sent by forum member 'carloliwanag']
>
> http://forums.java.net/jive/thread.jspa?messageID=395438
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>