Koshuke,
Thanks for the reply and great work with with updating the maven repo.
Yes, I did look at the documentation. It appears that uses Spring IoC and
xml
schema extension capability to replace sun-jaxws.xml, which I definitely
like.
My question was really how do I get access to the wac in the SEI? I guess I
could
get it in a roundabout way by using @Resource -> webServiceContext.
It would be nice if the WSSpringServlet supported it's own IoC which would
be a child
of wac (from the contextLoader Listener) and the jax-ws.http bean be
retrieved from it.
Otherwise I do really like the way it is heading with the schema extension.
Great work.
Thanks
Mohan
On 12/6/06, Kohsuke Kawaguchi <Kohsuke.Kawaguchi_at_sun.com> wrote:
>
> Mohan K R wrote:
> > Hello,
> > I am very much interested in the Spring Support in the jax-ws.commons
> > package.
>
> Cool!
>
> > I wanted to try it out
> > so I checked it our from the subversion repository. It appears one of
> the
> > dependency (I don't have it
> > handy, I think it was saaj-api) has a transitive dependency to
> > javax.activation 1.0.2 which is not available
> > anywhere (well, the pom are available but they point back to java.netrepos
> > and java.net has only 1.1).
>
> Indeed it looks like SAAJ.
>
> I'll update the dependency to activation 1.1, which is available on
> java.net maven repo. I think the added convenience wins over depending
> on an unnecessary new version.
>
> > Currently, my use-case for spring is that I need to bootstrap by SEI
> with
> > some spring injected beans,
> > is that possible? Thanks
>
> The goal includes making that possible, yes.
>
> Have you looked at https://jax-ws-commons.dev.java.net/nonav/spring/ ?
> Does this make sense to you as a spring user?
>
> --
> Kohsuke Kawaguchi
> Sun Microsystems kohsuke.kawaguchi_at_sun.com
>
>
>