You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by James Green <ja...@gmail.com> on 2013/11/19 18:38:57 UTC
WARNING: Injection data not found in JNDI context
This is causing an NPE accessing a WebServiceContext annotated with
@Resource.
To detail, I've been refactoring my Maven project into sub-projects to
facilitate versioning of interfaces. Previously the entire web interface
was held in a single war file project and it all worked.
The above field is in a base class I use for SOAP services. The base class
was moved into a jar project and depended upon by two others - both war
packaging.
In each case I have a beans.xml file which I thought might fix it. The
exact message as output by the latest TomEE-Plus 1.6-SNAPSHOT:
WARNING: Injection data not found in JNDI context:
jndiName='comp/env/com.mycompany.saas.jaxws.SoapBase/context',
target=com.mycompany.saas.jaxws.SoapBase/context
I have also tried making a getter and setter for the field and placing the
@Resource on the setter to no effect.
Any ideas?
Thanks,
James
Re: WARNING: Injection data not found in JNDI context
Posted by James Green <ja...@gmail.com>.
That works. Do you have a JIRA ticket I can watch?
Thanks for your time on this - we appreciate it!
On 20 November 2013 10:51, Romain Manni-Bucau <rm...@gmail.com> wrote:
> Hi
>
> I'll fix the pojo issue but you can configure urls in openejb-jar.xml:
>
> http://svn.apache.org/repos/asf/tomee/tomee/trunk/examples/change-jaxws-url/src/main/resources/META-INF/openejb-jar.xml
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
>
> 2013/11/20 James Green <ja...@gmail.com>:
> > I added @Stateless to the web service and indeed warning solved.
> >
> > So I added it to web.xml to resolve my original (business) problem of
> > wanting versioned urls - and the warning comes back.
> >
> > What do I need to do then?
> >
> > I have updated the source project on github to reflect this.
> >
> >
> > On 20 November 2013 09:50, Romain Manni-Bucau <rm...@gmail.com>
> wrote:
> >
> >> Hi
> >>
> >> just debugged a bit and it only works for ejb ATM
> >> Romain Manni-Bucau
> >> Twitter: @rmannibucau
> >> Blog: http://rmannibucau.wordpress.com/
> >> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> >> Github: https://github.com/rmannibucau
> >>
> >>
> >>
> >> 2013/11/20 James Green <ja...@gmail.com>:
> >> > Right, it really does not get any simpler than this:
> >> >
> >> > https://github.com/jmkgreen/test-multi-module
> >> >
> >> > I even accept it may not actually have met minimum requirements yet!
> >> >
> >> > The log:
> >> >
> >> > INFO: Deployed
> >> >
> >>
> Application(path=C:\Users\jgreen\Downloads\apache-tomee-plus-1.6.0-SNAPSHOT-NOV13\webapps\webapp)
> >> > Nov 20, 2013 9:18:54 AM org.apache.openejb.InjectionProcessor
> >> > fillInjectionProperties
> >> > WARNING: Injection data not found in JNDI context:
> >> > jndiName='comp/env/com.example.webapp.SoapBaseClass/context',
> >> > target=com.example.webapp.SoapBaseClass/context
> >> > Nov 20, 2013 9:18:54 AM
> org.apache.openejb.server.webservices.WsService
> >> > afterApplicationCreated
> >> > INFO: Webservice(wsdl=http://localhost:8080//webapp/SoapService,
> qname={
> >> > http://www.example.net/2013-11-20}SoapService) -->
> >> > Pojo(id=webapp.com.example.webapp.SoapService)
> >> >
> >> >
> >> >
> >> > On 20 November 2013 05:49, Romain Manni-Bucau <rm...@gmail.com>
> >> wrote:
> >> >
> >> >> Hmm
> >> >>
> >> >> Can you redo a project like it repeoducing it? Uber*ar are often
> >> breaking
> >> >> things...
> >> >> Le 19 nov. 2013 23:09, "James Green" <ja...@gmail.com> a
> >> écrit :
> >> >>
> >> >> > I am able to trigger this by adding the webservice class to
> web.xml.
> >> >> >
> >> >> > I took an existing (working) WebService class that was annotated
> >> >> > @Stateless. I removed @Stateless and instead added a servlet entry
> in
> >> >> > web.xml to route specific URL requests to it. That class is now
> >> listed as
> >> >> > suffering the injection problem (it too extends this base class
> having
> >> >> > @Resource WebServiceContext inside). I added @Stateless back on
> but no
> >> >> > change.
> >> >> >
> >> >> > The only other matter worthy of mentioning is that since I now have
> >> two
> >> >> web
> >> >> > archive projects within the parent project, I created a third to
> hold
> >> >> both
> >> >> > web archives as dependencies, this one an 'uberwar'
> >> >> > using org.codehaus.cargo:cargo-maven2-plugin. The default
> >> configuration
> >> >> > descriptor from their web site is being used, apparently fine.
> >> >> >
> >> >> >
> >> >> > On 19 November 2013 21:29, Romain Manni-Bucau <
> rmannibucau@gmail.com>
> >> >> > wrote:
> >> >> >
> >> >> > > Hmm, beans.xml is useless for @Resource, that sthg else i fear
> >> >> > > Le 19 nov. 2013 22:27, "James Green" <ja...@gmail.com>
> a
> >> >> écrit
> >> >> > :
> >> >> > >
> >> >> > > > Would the project with the base class also require a beans.xml
> >> file?
> >> >> > It's
> >> >> > > > not something covered in the examples we all see...
> >> >> > > >
> >> >> > > > I would expect subclasses annotated @WebService and having in
> the
> >> >> > object
> >> >> > > a
> >> >> > > > field annotated @Resource to be scanned by reflection and
> >> injected.
> >> >> > Just
> >> >> > > > wanting to confirm my thinking that the packages with the
> >> subclasses
> >> >> > > need a
> >> >> > > > beans.xml declaration but nothing further for this stuff to
> work.
> >> >> > > >
> >> >> > > >
> >> >> > > > On 19 November 2013 21:18, Romain Manni-Bucau <
> >> rmannibucau@gmail.com
> >> >> >
> >> >> > > > wrote:
> >> >> > > >
> >> >> > > > > No, just as prefix. Hmm, try to share something to reproduce
> >> >> > otherwise
> >> >> > > > > thats hard to help you :s
> >> >> > > > >
> >> >> > > > > Ps: is it an ear?
> >> >> > > > > Le 19 nov. 2013 22:16, "James Green" <
> james.mk.green@gmail.com>
> >> a
> >> >> > > écrit
> >> >> > > > :
> >> >> > > > >
> >> >> > > > > > I renamed to mycompany-jaxws-core and it made no
> difference.
> >> >> Unless
> >> >> > > you
> >> >> > > > > are
> >> >> > > > > > suggesting anything with jaxws in it's name will be
> >> excluded..?
> >> >> > > > > >
> >> >> > > > > >
> >> >> > > > > > On 19 November 2013 21:02, Romain Manni-Bucau <
> >> >> > rmannibucau@gmail.com
> >> >> > > >
> >> >> > > > > > wrote:
> >> >> > > > > >
> >> >> > > > > > > Try to rename it foo.jar, we exclude few jars from
> scanning
> >> >> using
> >> >> > > > > > > prefixes...jaxws can be one (i dont recall atm to be
> fully
> >> >> > honest)
> >> >> > > > > > > Le 19 nov. 2013 21:47, "James Green" <
> >> james.mk.green@gmail.com
> >> >> >
> >> >> > a
> >> >> > > > > écrit
> >> >> > > > > > :
> >> >> > > > > > >
> >> >> > > > > > > > The name is something like jaxws-core. Why would you
> >> think it
> >> >> > is
> >> >> > > > > being
> >> >> > > > > > > > excluded?
> >> >> > > > > > > >
> >> >> > > > > > > > It's a commercial project I am afraid so best I can do
> is
> >> >> try a
> >> >> > > > test
> >> >> > > > > > case
> >> >> > > > > > > > if I get desperate.
> >> >> > > > > > > >
> >> >> > > > > > > > I could collapse the code back into a single war
> archive
> >> >> again
> >> >> > > but
> >> >> > > > > I'd
> >> >> > > > > > be
> >> >> > > > > > > > disappointed :(.
> >> >> > > > > > > >
> >> >> > > > > > > >
> >> >> > > > > > > > On 19 November 2013 19:18, Romain Manni-Bucau <
> >> >> > > > rmannibucau@gmail.com
> >> >> > > > > >
> >> >> > > > > > > > wrote:
> >> >> > > > > > > >
> >> >> > > > > > > > > Hi
> >> >> > > > > > > > >
> >> >> > > > > > > > > What s the jar name (isnt it an exclusion?)? Can you
> >> >> > reproduce
> >> >> > > it
> >> >> > > > > and
> >> >> > > > > > > > share
> >> >> > > > > > > > > a project?
> >> >> > > > > > > > > Le 19 nov. 2013 20:02, "James Green" <
> >> >> > james.mk.green@gmail.com
> >> >> > > >
> >> >> > > > a
> >> >> > > > > > > écrit
> >> >> > > > > > > > :
> >> >> > > > > > > > >
> >> >> > > > > > > > > > I just moved the setter of the WebServiceContext
> (with
> >> >> > > > @Resource)
> >> >> > > > > > to
> >> >> > > > > > > > the
> >> >> > > > > > > > > > @WebService implementation classes in the
> dependency
> >> .war
> >> >> > > > package
> >> >> > > > > > > and I
> >> >> > > > > > > > > > still get the error.
> >> >> > > > > > > > > >
> >> >> > > > > > > > > > I was hoping the container took issue with the
> >> annotation
> >> >> > > being
> >> >> > > > > in
> >> >> > > > > > a
> >> >> > > > > > > > > class
> >> >> > > > > > > > > > within a .jar library but whatever the problem is,
> it
> >> >> isn't
> >> >> > > > that.
> >> >> > > > > > > > > >
> >> >> > > > > > > > > > Suggestions welcomed.
> >> >> > > > > > > > > >
> >> >> > > > > > > > > >
> >> >> > > > > > > > > > On 19 November 2013 17:38, James Green <
> >> >> > > > james.mk.green@gmail.com
> >> >> > > > > >
> >> >> > > > > > > > wrote:
> >> >> > > > > > > > > >
> >> >> > > > > > > > > > > This is causing an NPE accessing a
> WebServiceContext
> >> >> > > > annotated
> >> >> > > > > > with
> >> >> > > > > > > > > > > @Resource.
> >> >> > > > > > > > > > >
> >> >> > > > > > > > > > > To detail, I've been refactoring my Maven project
> >> into
> >> >> > > > > > sub-projects
> >> >> > > > > > > > to
> >> >> > > > > > > > > > > facilitate versioning of interfaces. Previously
> the
> >> >> > entire
> >> >> > > > web
> >> >> > > > > > > > > interface
> >> >> > > > > > > > > > > was held in a single war file project and it all
> >> >> worked.
> >> >> > > > > > > > > > >
> >> >> > > > > > > > > > > The above field is in a base class I use for SOAP
> >> >> > services.
> >> >> > > > The
> >> >> > > > > > > base
> >> >> > > > > > > > > > class
> >> >> > > > > > > > > > > was moved into a jar project and depended upon by
> >> two
> >> >> > > others
> >> >> > > > -
> >> >> > > > > > both
> >> >> > > > > > > > war
> >> >> > > > > > > > > > > packaging.
> >> >> > > > > > > > > > >
> >> >> > > > > > > > > > > In each case I have a beans.xml file which I
> thought
> >> >> > might
> >> >> > > > fix
> >> >> > > > > > it.
> >> >> > > > > > > > The
> >> >> > > > > > > > > > > exact message as output by the latest TomEE-Plus
> >> >> > > > 1.6-SNAPSHOT:
> >> >> > > > > > > > > > >
> >> >> > > > > > > > > > > WARNING: Injection data not found in JNDI
> context:
> >> >> > > > > > > > > > >
> >> >> > > > jndiName='comp/env/com.mycompany.saas.jaxws.SoapBase/context',
> >> >> > > > > > > > > > > target=com.mycompany.saas.jaxws.SoapBase/context
> >> >> > > > > > > > > > >
> >> >> > > > > > > > > > > I have also tried making a getter and setter for
> the
> >> >> > field
> >> >> > > > and
> >> >> > > > > > > > placing
> >> >> > > > > > > > > > the
> >> >> > > > > > > > > > > @Resource on the setter to no effect.
> >> >> > > > > > > > > > >
> >> >> > > > > > > > > > > Any ideas?
> >> >> > > > > > > > > > >
> >> >> > > > > > > > > > > Thanks,
> >> >> > > > > > > > > > >
> >> >> > > > > > > > > > > James
> >> >> > > > > > > > > > >
> >> >> > > > > > > > > > >
> >> >> > > > > > > > > >
> >> >> > > > > > > > >
> >> >> > > > > > > >
> >> >> > > > > > >
> >> >> > > > > >
> >> >> > > > >
> >> >> > > >
> >> >> > >
> >> >> >
> >> >>
> >>
>
Re: WARNING: Injection data not found in JNDI context
Posted by James Green <ja...@gmail.com>.
Actually it's now uberwar creating problems - ignore me :)
On 20 November 2013 11:45, James Green <ja...@gmail.com> wrote:
> How should I write the config for multiple EJBs? Adding extra <session>
> elements results in none applying and I cannot spot an example.
>
>
> On 20 November 2013 11:11, James Green <ja...@gmail.com> wrote:
>
>> Is there an issue covering the lack of support when exposed via web.xml?
>>
>>
>> On 20 November 2013 11:06, Romain Manni-Bucau <rm...@gmail.com>wrote:
>>
>>> FYI https://issues.apache.org/jira/browse/TOMEE-1081
>>> Romain Manni-Bucau
>>> Twitter: @rmannibucau
>>> Blog: http://rmannibucau.wordpress.com/
>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>> Github: https://github.com/rmannibucau
>>>
>>>
>>>
>>> 2013/11/20 Romain Manni-Bucau <rm...@gmail.com>:
>>> > Hi
>>> >
>>> > I'll fix the pojo issue but you can configure urls in openejb-jar.xml:
>>> >
>>> http://svn.apache.org/repos/asf/tomee/tomee/trunk/examples/change-jaxws-url/src/main/resources/META-INF/openejb-jar.xml
>>> > Romain Manni-Bucau
>>> > Twitter: @rmannibucau
>>> > Blog: http://rmannibucau.wordpress.com/
>>> > LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>> > Github: https://github.com/rmannibucau
>>> >
>>> >
>>> >
>>> > 2013/11/20 James Green <ja...@gmail.com>:
>>> >> I added @Stateless to the web service and indeed warning solved.
>>> >>
>>> >> So I added it to web.xml to resolve my original (business) problem of
>>> >> wanting versioned urls - and the warning comes back.
>>> >>
>>> >> What do I need to do then?
>>> >>
>>> >> I have updated the source project on github to reflect this.
>>> >>
>>> >>
>>> >> On 20 November 2013 09:50, Romain Manni-Bucau <rm...@gmail.com>
>>> wrote:
>>> >>
>>> >>> Hi
>>> >>>
>>> >>> just debugged a bit and it only works for ejb ATM
>>> >>> Romain Manni-Bucau
>>> >>> Twitter: @rmannibucau
>>> >>> Blog: http://rmannibucau.wordpress.com/
>>> >>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>> >>> Github: https://github.com/rmannibucau
>>> >>>
>>> >>>
>>> >>>
>>> >>> 2013/11/20 James Green <ja...@gmail.com>:
>>> >>> > Right, it really does not get any simpler than this:
>>> >>> >
>>> >>> > https://github.com/jmkgreen/test-multi-module
>>> >>> >
>>> >>> > I even accept it may not actually have met minimum requirements
>>> yet!
>>> >>> >
>>> >>> > The log:
>>> >>> >
>>> >>> > INFO: Deployed
>>> >>> >
>>> >>>
>>> Application(path=C:\Users\jgreen\Downloads\apache-tomee-plus-1.6.0-SNAPSHOT-NOV13\webapps\webapp)
>>> >>> > Nov 20, 2013 9:18:54 AM org.apache.openejb.InjectionProcessor
>>> >>> > fillInjectionProperties
>>> >>> > WARNING: Injection data not found in JNDI context:
>>> >>> > jndiName='comp/env/com.example.webapp.SoapBaseClass/context',
>>> >>> > target=com.example.webapp.SoapBaseClass/context
>>> >>> > Nov 20, 2013 9:18:54 AM
>>> org.apache.openejb.server.webservices.WsService
>>> >>> > afterApplicationCreated
>>> >>> > INFO: Webservice(wsdl=http://localhost:8080//webapp/SoapService,
>>> qname={
>>> >>> > http://www.example.net/2013-11-20}SoapService) -->
>>> >>> > Pojo(id=webapp.com.example.webapp.SoapService)
>>> >>> >
>>> >>> >
>>> >>> >
>>> >>> > On 20 November 2013 05:49, Romain Manni-Bucau <
>>> rmannibucau@gmail.com>
>>> >>> wrote:
>>> >>> >
>>> >>> >> Hmm
>>> >>> >>
>>> >>> >> Can you redo a project like it repeoducing it? Uber*ar are often
>>> >>> breaking
>>> >>> >> things...
>>> >>> >> Le 19 nov. 2013 23:09, "James Green" <ja...@gmail.com> a
>>> >>> écrit :
>>> >>> >>
>>> >>> >> > I am able to trigger this by adding the webservice class to
>>> web.xml.
>>> >>> >> >
>>> >>> >> > I took an existing (working) WebService class that was annotated
>>> >>> >> > @Stateless. I removed @Stateless and instead added a servlet
>>> entry in
>>> >>> >> > web.xml to route specific URL requests to it. That class is now
>>> >>> listed as
>>> >>> >> > suffering the injection problem (it too extends this base class
>>> having
>>> >>> >> > @Resource WebServiceContext inside). I added @Stateless back on
>>> but no
>>> >>> >> > change.
>>> >>> >> >
>>> >>> >> > The only other matter worthy of mentioning is that since I now
>>> have
>>> >>> two
>>> >>> >> web
>>> >>> >> > archive projects within the parent project, I created a third
>>> to hold
>>> >>> >> both
>>> >>> >> > web archives as dependencies, this one an 'uberwar'
>>> >>> >> > using org.codehaus.cargo:cargo-maven2-plugin. The default
>>> >>> configuration
>>> >>> >> > descriptor from their web site is being used, apparently fine.
>>> >>> >> >
>>> >>> >> >
>>> >>> >> > On 19 November 2013 21:29, Romain Manni-Bucau <
>>> rmannibucau@gmail.com>
>>> >>> >> > wrote:
>>> >>> >> >
>>> >>> >> > > Hmm, beans.xml is useless for @Resource, that sthg else i fear
>>> >>> >> > > Le 19 nov. 2013 22:27, "James Green" <
>>> james.mk.green@gmail.com> a
>>> >>> >> écrit
>>> >>> >> > :
>>> >>> >> > >
>>> >>> >> > > > Would the project with the base class also require a
>>> beans.xml
>>> >>> file?
>>> >>> >> > It's
>>> >>> >> > > > not something covered in the examples we all see...
>>> >>> >> > > >
>>> >>> >> > > > I would expect subclasses annotated @WebService and having
>>> in the
>>> >>> >> > object
>>> >>> >> > > a
>>> >>> >> > > > field annotated @Resource to be scanned by reflection and
>>> >>> injected.
>>> >>> >> > Just
>>> >>> >> > > > wanting to confirm my thinking that the packages with the
>>> >>> subclasses
>>> >>> >> > > need a
>>> >>> >> > > > beans.xml declaration but nothing further for this stuff to
>>> work.
>>> >>> >> > > >
>>> >>> >> > > >
>>> >>> >> > > > On 19 November 2013 21:18, Romain Manni-Bucau <
>>> >>> rmannibucau@gmail.com
>>> >>> >> >
>>> >>> >> > > > wrote:
>>> >>> >> > > >
>>> >>> >> > > > > No, just as prefix. Hmm, try to share something to
>>> reproduce
>>> >>> >> > otherwise
>>> >>> >> > > > > thats hard to help you :s
>>> >>> >> > > > >
>>> >>> >> > > > > Ps: is it an ear?
>>> >>> >> > > > > Le 19 nov. 2013 22:16, "James Green" <
>>> james.mk.green@gmail.com>
>>> >>> a
>>> >>> >> > > écrit
>>> >>> >> > > > :
>>> >>> >> > > > >
>>> >>> >> > > > > > I renamed to mycompany-jaxws-core and it made no
>>> difference.
>>> >>> >> Unless
>>> >>> >> > > you
>>> >>> >> > > > > are
>>> >>> >> > > > > > suggesting anything with jaxws in it's name will be
>>> >>> excluded..?
>>> >>> >> > > > > >
>>> >>> >> > > > > >
>>> >>> >> > > > > > On 19 November 2013 21:02, Romain Manni-Bucau <
>>> >>> >> > rmannibucau@gmail.com
>>> >>> >> > > >
>>> >>> >> > > > > > wrote:
>>> >>> >> > > > > >
>>> >>> >> > > > > > > Try to rename it foo.jar, we exclude few jars from
>>> scanning
>>> >>> >> using
>>> >>> >> > > > > > > prefixes...jaxws can be one (i dont recall atm to be
>>> fully
>>> >>> >> > honest)
>>> >>> >> > > > > > > Le 19 nov. 2013 21:47, "James Green" <
>>> >>> james.mk.green@gmail.com
>>> >>> >> >
>>> >>> >> > a
>>> >>> >> > > > > écrit
>>> >>> >> > > > > > :
>>> >>> >> > > > > > >
>>> >>> >> > > > > > > > The name is something like jaxws-core. Why would you
>>> >>> think it
>>> >>> >> > is
>>> >>> >> > > > > being
>>> >>> >> > > > > > > > excluded?
>>> >>> >> > > > > > > >
>>> >>> >> > > > > > > > It's a commercial project I am afraid so best I can
>>> do is
>>> >>> >> try a
>>> >>> >> > > > test
>>> >>> >> > > > > > case
>>> >>> >> > > > > > > > if I get desperate.
>>> >>> >> > > > > > > >
>>> >>> >> > > > > > > > I could collapse the code back into a single war
>>> archive
>>> >>> >> again
>>> >>> >> > > but
>>> >>> >> > > > > I'd
>>> >>> >> > > > > > be
>>> >>> >> > > > > > > > disappointed :(.
>>> >>> >> > > > > > > >
>>> >>> >> > > > > > > >
>>> >>> >> > > > > > > > On 19 November 2013 19:18, Romain Manni-Bucau <
>>> >>> >> > > > rmannibucau@gmail.com
>>> >>> >> > > > > >
>>> >>> >> > > > > > > > wrote:
>>> >>> >> > > > > > > >
>>> >>> >> > > > > > > > > Hi
>>> >>> >> > > > > > > > >
>>> >>> >> > > > > > > > > What s the jar name (isnt it an exclusion?)? Can
>>> you
>>> >>> >> > reproduce
>>> >>> >> > > it
>>> >>> >> > > > > and
>>> >>> >> > > > > > > > share
>>> >>> >> > > > > > > > > a project?
>>> >>> >> > > > > > > > > Le 19 nov. 2013 20:02, "James Green" <
>>> >>> >> > james.mk.green@gmail.com
>>> >>> >> > > >
>>> >>> >> > > > a
>>> >>> >> > > > > > > écrit
>>> >>> >> > > > > > > > :
>>> >>> >> > > > > > > > >
>>> >>> >> > > > > > > > > > I just moved the setter of the
>>> WebServiceContext (with
>>> >>> >> > > > @Resource)
>>> >>> >> > > > > > to
>>> >>> >> > > > > > > > the
>>> >>> >> > > > > > > > > > @WebService implementation classes in the
>>> dependency
>>> >>> .war
>>> >>> >> > > > package
>>> >>> >> > > > > > > and I
>>> >>> >> > > > > > > > > > still get the error.
>>> >>> >> > > > > > > > > >
>>> >>> >> > > > > > > > > > I was hoping the container took issue with the
>>> >>> annotation
>>> >>> >> > > being
>>> >>> >> > > > > in
>>> >>> >> > > > > > a
>>> >>> >> > > > > > > > > class
>>> >>> >> > > > > > > > > > within a .jar library but whatever the problem
>>> is, it
>>> >>> >> isn't
>>> >>> >> > > > that.
>>> >>> >> > > > > > > > > >
>>> >>> >> > > > > > > > > > Suggestions welcomed.
>>> >>> >> > > > > > > > > >
>>> >>> >> > > > > > > > > >
>>> >>> >> > > > > > > > > > On 19 November 2013 17:38, James Green <
>>> >>> >> > > > james.mk.green@gmail.com
>>> >>> >> > > > > >
>>> >>> >> > > > > > > > wrote:
>>> >>> >> > > > > > > > > >
>>> >>> >> > > > > > > > > > > This is causing an NPE accessing a
>>> WebServiceContext
>>> >>> >> > > > annotated
>>> >>> >> > > > > > with
>>> >>> >> > > > > > > > > > > @Resource.
>>> >>> >> > > > > > > > > > >
>>> >>> >> > > > > > > > > > > To detail, I've been refactoring my Maven
>>> project
>>> >>> into
>>> >>> >> > > > > > sub-projects
>>> >>> >> > > > > > > > to
>>> >>> >> > > > > > > > > > > facilitate versioning of interfaces.
>>> Previously the
>>> >>> >> > entire
>>> >>> >> > > > web
>>> >>> >> > > > > > > > > interface
>>> >>> >> > > > > > > > > > > was held in a single war file project and it
>>> all
>>> >>> >> worked.
>>> >>> >> > > > > > > > > > >
>>> >>> >> > > > > > > > > > > The above field is in a base class I use for
>>> SOAP
>>> >>> >> > services.
>>> >>> >> > > > The
>>> >>> >> > > > > > > base
>>> >>> >> > > > > > > > > > class
>>> >>> >> > > > > > > > > > > was moved into a jar project and depended
>>> upon by
>>> >>> two
>>> >>> >> > > others
>>> >>> >> > > > -
>>> >>> >> > > > > > both
>>> >>> >> > > > > > > > war
>>> >>> >> > > > > > > > > > > packaging.
>>> >>> >> > > > > > > > > > >
>>> >>> >> > > > > > > > > > > In each case I have a beans.xml file which I
>>> thought
>>> >>> >> > might
>>> >>> >> > > > fix
>>> >>> >> > > > > > it.
>>> >>> >> > > > > > > > The
>>> >>> >> > > > > > > > > > > exact message as output by the latest
>>> TomEE-Plus
>>> >>> >> > > > 1.6-SNAPSHOT:
>>> >>> >> > > > > > > > > > >
>>> >>> >> > > > > > > > > > > WARNING: Injection data not found in JNDI
>>> context:
>>> >>> >> > > > > > > > > > >
>>> >>> >> > > >
>>> jndiName='comp/env/com.mycompany.saas.jaxws.SoapBase/context',
>>> >>> >> > > > > > > > > > >
>>> target=com.mycompany.saas.jaxws.SoapBase/context
>>> >>> >> > > > > > > > > > >
>>> >>> >> > > > > > > > > > > I have also tried making a getter and setter
>>> for the
>>> >>> >> > field
>>> >>> >> > > > and
>>> >>> >> > > > > > > > placing
>>> >>> >> > > > > > > > > > the
>>> >>> >> > > > > > > > > > > @Resource on the setter to no effect.
>>> >>> >> > > > > > > > > > >
>>> >>> >> > > > > > > > > > > Any ideas?
>>> >>> >> > > > > > > > > > >
>>> >>> >> > > > > > > > > > > Thanks,
>>> >>> >> > > > > > > > > > >
>>> >>> >> > > > > > > > > > > James
>>> >>> >> > > > > > > > > > >
>>> >>> >> > > > > > > > > > >
>>> >>> >> > > > > > > > > >
>>> >>> >> > > > > > > > >
>>> >>> >> > > > > > > >
>>> >>> >> > > > > > >
>>> >>> >> > > > > >
>>> >>> >> > > > >
>>> >>> >> > > >
>>> >>> >> > >
>>> >>> >> >
>>> >>> >>
>>> >>>
>>>
>>
>>
>
Re: WARNING: Injection data not found in JNDI context
Posted by James Green <ja...@gmail.com>.
How should I write the config for multiple EJBs? Adding extra <session>
elements results in none applying and I cannot spot an example.
On 20 November 2013 11:11, James Green <ja...@gmail.com> wrote:
> Is there an issue covering the lack of support when exposed via web.xml?
>
>
> On 20 November 2013 11:06, Romain Manni-Bucau <rm...@gmail.com>wrote:
>
>> FYI https://issues.apache.org/jira/browse/TOMEE-1081
>> Romain Manni-Bucau
>> Twitter: @rmannibucau
>> Blog: http://rmannibucau.wordpress.com/
>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>> Github: https://github.com/rmannibucau
>>
>>
>>
>> 2013/11/20 Romain Manni-Bucau <rm...@gmail.com>:
>> > Hi
>> >
>> > I'll fix the pojo issue but you can configure urls in openejb-jar.xml:
>> >
>> http://svn.apache.org/repos/asf/tomee/tomee/trunk/examples/change-jaxws-url/src/main/resources/META-INF/openejb-jar.xml
>> > Romain Manni-Bucau
>> > Twitter: @rmannibucau
>> > Blog: http://rmannibucau.wordpress.com/
>> > LinkedIn: http://fr.linkedin.com/in/rmannibucau
>> > Github: https://github.com/rmannibucau
>> >
>> >
>> >
>> > 2013/11/20 James Green <ja...@gmail.com>:
>> >> I added @Stateless to the web service and indeed warning solved.
>> >>
>> >> So I added it to web.xml to resolve my original (business) problem of
>> >> wanting versioned urls - and the warning comes back.
>> >>
>> >> What do I need to do then?
>> >>
>> >> I have updated the source project on github to reflect this.
>> >>
>> >>
>> >> On 20 November 2013 09:50, Romain Manni-Bucau <rm...@gmail.com>
>> wrote:
>> >>
>> >>> Hi
>> >>>
>> >>> just debugged a bit and it only works for ejb ATM
>> >>> Romain Manni-Bucau
>> >>> Twitter: @rmannibucau
>> >>> Blog: http://rmannibucau.wordpress.com/
>> >>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>> >>> Github: https://github.com/rmannibucau
>> >>>
>> >>>
>> >>>
>> >>> 2013/11/20 James Green <ja...@gmail.com>:
>> >>> > Right, it really does not get any simpler than this:
>> >>> >
>> >>> > https://github.com/jmkgreen/test-multi-module
>> >>> >
>> >>> > I even accept it may not actually have met minimum requirements yet!
>> >>> >
>> >>> > The log:
>> >>> >
>> >>> > INFO: Deployed
>> >>> >
>> >>>
>> Application(path=C:\Users\jgreen\Downloads\apache-tomee-plus-1.6.0-SNAPSHOT-NOV13\webapps\webapp)
>> >>> > Nov 20, 2013 9:18:54 AM org.apache.openejb.InjectionProcessor
>> >>> > fillInjectionProperties
>> >>> > WARNING: Injection data not found in JNDI context:
>> >>> > jndiName='comp/env/com.example.webapp.SoapBaseClass/context',
>> >>> > target=com.example.webapp.SoapBaseClass/context
>> >>> > Nov 20, 2013 9:18:54 AM
>> org.apache.openejb.server.webservices.WsService
>> >>> > afterApplicationCreated
>> >>> > INFO: Webservice(wsdl=http://localhost:8080//webapp/SoapService,
>> qname={
>> >>> > http://www.example.net/2013-11-20}SoapService) -->
>> >>> > Pojo(id=webapp.com.example.webapp.SoapService)
>> >>> >
>> >>> >
>> >>> >
>> >>> > On 20 November 2013 05:49, Romain Manni-Bucau <
>> rmannibucau@gmail.com>
>> >>> wrote:
>> >>> >
>> >>> >> Hmm
>> >>> >>
>> >>> >> Can you redo a project like it repeoducing it? Uber*ar are often
>> >>> breaking
>> >>> >> things...
>> >>> >> Le 19 nov. 2013 23:09, "James Green" <ja...@gmail.com> a
>> >>> écrit :
>> >>> >>
>> >>> >> > I am able to trigger this by adding the webservice class to
>> web.xml.
>> >>> >> >
>> >>> >> > I took an existing (working) WebService class that was annotated
>> >>> >> > @Stateless. I removed @Stateless and instead added a servlet
>> entry in
>> >>> >> > web.xml to route specific URL requests to it. That class is now
>> >>> listed as
>> >>> >> > suffering the injection problem (it too extends this base class
>> having
>> >>> >> > @Resource WebServiceContext inside). I added @Stateless back on
>> but no
>> >>> >> > change.
>> >>> >> >
>> >>> >> > The only other matter worthy of mentioning is that since I now
>> have
>> >>> two
>> >>> >> web
>> >>> >> > archive projects within the parent project, I created a third to
>> hold
>> >>> >> both
>> >>> >> > web archives as dependencies, this one an 'uberwar'
>> >>> >> > using org.codehaus.cargo:cargo-maven2-plugin. The default
>> >>> configuration
>> >>> >> > descriptor from their web site is being used, apparently fine.
>> >>> >> >
>> >>> >> >
>> >>> >> > On 19 November 2013 21:29, Romain Manni-Bucau <
>> rmannibucau@gmail.com>
>> >>> >> > wrote:
>> >>> >> >
>> >>> >> > > Hmm, beans.xml is useless for @Resource, that sthg else i fear
>> >>> >> > > Le 19 nov. 2013 22:27, "James Green" <ja...@gmail.com>
>> a
>> >>> >> écrit
>> >>> >> > :
>> >>> >> > >
>> >>> >> > > > Would the project with the base class also require a
>> beans.xml
>> >>> file?
>> >>> >> > It's
>> >>> >> > > > not something covered in the examples we all see...
>> >>> >> > > >
>> >>> >> > > > I would expect subclasses annotated @WebService and having
>> in the
>> >>> >> > object
>> >>> >> > > a
>> >>> >> > > > field annotated @Resource to be scanned by reflection and
>> >>> injected.
>> >>> >> > Just
>> >>> >> > > > wanting to confirm my thinking that the packages with the
>> >>> subclasses
>> >>> >> > > need a
>> >>> >> > > > beans.xml declaration but nothing further for this stuff to
>> work.
>> >>> >> > > >
>> >>> >> > > >
>> >>> >> > > > On 19 November 2013 21:18, Romain Manni-Bucau <
>> >>> rmannibucau@gmail.com
>> >>> >> >
>> >>> >> > > > wrote:
>> >>> >> > > >
>> >>> >> > > > > No, just as prefix. Hmm, try to share something to
>> reproduce
>> >>> >> > otherwise
>> >>> >> > > > > thats hard to help you :s
>> >>> >> > > > >
>> >>> >> > > > > Ps: is it an ear?
>> >>> >> > > > > Le 19 nov. 2013 22:16, "James Green" <
>> james.mk.green@gmail.com>
>> >>> a
>> >>> >> > > écrit
>> >>> >> > > > :
>> >>> >> > > > >
>> >>> >> > > > > > I renamed to mycompany-jaxws-core and it made no
>> difference.
>> >>> >> Unless
>> >>> >> > > you
>> >>> >> > > > > are
>> >>> >> > > > > > suggesting anything with jaxws in it's name will be
>> >>> excluded..?
>> >>> >> > > > > >
>> >>> >> > > > > >
>> >>> >> > > > > > On 19 November 2013 21:02, Romain Manni-Bucau <
>> >>> >> > rmannibucau@gmail.com
>> >>> >> > > >
>> >>> >> > > > > > wrote:
>> >>> >> > > > > >
>> >>> >> > > > > > > Try to rename it foo.jar, we exclude few jars from
>> scanning
>> >>> >> using
>> >>> >> > > > > > > prefixes...jaxws can be one (i dont recall atm to be
>> fully
>> >>> >> > honest)
>> >>> >> > > > > > > Le 19 nov. 2013 21:47, "James Green" <
>> >>> james.mk.green@gmail.com
>> >>> >> >
>> >>> >> > a
>> >>> >> > > > > écrit
>> >>> >> > > > > > :
>> >>> >> > > > > > >
>> >>> >> > > > > > > > The name is something like jaxws-core. Why would you
>> >>> think it
>> >>> >> > is
>> >>> >> > > > > being
>> >>> >> > > > > > > > excluded?
>> >>> >> > > > > > > >
>> >>> >> > > > > > > > It's a commercial project I am afraid so best I can
>> do is
>> >>> >> try a
>> >>> >> > > > test
>> >>> >> > > > > > case
>> >>> >> > > > > > > > if I get desperate.
>> >>> >> > > > > > > >
>> >>> >> > > > > > > > I could collapse the code back into a single war
>> archive
>> >>> >> again
>> >>> >> > > but
>> >>> >> > > > > I'd
>> >>> >> > > > > > be
>> >>> >> > > > > > > > disappointed :(.
>> >>> >> > > > > > > >
>> >>> >> > > > > > > >
>> >>> >> > > > > > > > On 19 November 2013 19:18, Romain Manni-Bucau <
>> >>> >> > > > rmannibucau@gmail.com
>> >>> >> > > > > >
>> >>> >> > > > > > > > wrote:
>> >>> >> > > > > > > >
>> >>> >> > > > > > > > > Hi
>> >>> >> > > > > > > > >
>> >>> >> > > > > > > > > What s the jar name (isnt it an exclusion?)? Can
>> you
>> >>> >> > reproduce
>> >>> >> > > it
>> >>> >> > > > > and
>> >>> >> > > > > > > > share
>> >>> >> > > > > > > > > a project?
>> >>> >> > > > > > > > > Le 19 nov. 2013 20:02, "James Green" <
>> >>> >> > james.mk.green@gmail.com
>> >>> >> > > >
>> >>> >> > > > a
>> >>> >> > > > > > > écrit
>> >>> >> > > > > > > > :
>> >>> >> > > > > > > > >
>> >>> >> > > > > > > > > > I just moved the setter of the WebServiceContext
>> (with
>> >>> >> > > > @Resource)
>> >>> >> > > > > > to
>> >>> >> > > > > > > > the
>> >>> >> > > > > > > > > > @WebService implementation classes in the
>> dependency
>> >>> .war
>> >>> >> > > > package
>> >>> >> > > > > > > and I
>> >>> >> > > > > > > > > > still get the error.
>> >>> >> > > > > > > > > >
>> >>> >> > > > > > > > > > I was hoping the container took issue with the
>> >>> annotation
>> >>> >> > > being
>> >>> >> > > > > in
>> >>> >> > > > > > a
>> >>> >> > > > > > > > > class
>> >>> >> > > > > > > > > > within a .jar library but whatever the problem
>> is, it
>> >>> >> isn't
>> >>> >> > > > that.
>> >>> >> > > > > > > > > >
>> >>> >> > > > > > > > > > Suggestions welcomed.
>> >>> >> > > > > > > > > >
>> >>> >> > > > > > > > > >
>> >>> >> > > > > > > > > > On 19 November 2013 17:38, James Green <
>> >>> >> > > > james.mk.green@gmail.com
>> >>> >> > > > > >
>> >>> >> > > > > > > > wrote:
>> >>> >> > > > > > > > > >
>> >>> >> > > > > > > > > > > This is causing an NPE accessing a
>> WebServiceContext
>> >>> >> > > > annotated
>> >>> >> > > > > > with
>> >>> >> > > > > > > > > > > @Resource.
>> >>> >> > > > > > > > > > >
>> >>> >> > > > > > > > > > > To detail, I've been refactoring my Maven
>> project
>> >>> into
>> >>> >> > > > > > sub-projects
>> >>> >> > > > > > > > to
>> >>> >> > > > > > > > > > > facilitate versioning of interfaces.
>> Previously the
>> >>> >> > entire
>> >>> >> > > > web
>> >>> >> > > > > > > > > interface
>> >>> >> > > > > > > > > > > was held in a single war file project and it
>> all
>> >>> >> worked.
>> >>> >> > > > > > > > > > >
>> >>> >> > > > > > > > > > > The above field is in a base class I use for
>> SOAP
>> >>> >> > services.
>> >>> >> > > > The
>> >>> >> > > > > > > base
>> >>> >> > > > > > > > > > class
>> >>> >> > > > > > > > > > > was moved into a jar project and depended upon
>> by
>> >>> two
>> >>> >> > > others
>> >>> >> > > > -
>> >>> >> > > > > > both
>> >>> >> > > > > > > > war
>> >>> >> > > > > > > > > > > packaging.
>> >>> >> > > > > > > > > > >
>> >>> >> > > > > > > > > > > In each case I have a beans.xml file which I
>> thought
>> >>> >> > might
>> >>> >> > > > fix
>> >>> >> > > > > > it.
>> >>> >> > > > > > > > The
>> >>> >> > > > > > > > > > > exact message as output by the latest
>> TomEE-Plus
>> >>> >> > > > 1.6-SNAPSHOT:
>> >>> >> > > > > > > > > > >
>> >>> >> > > > > > > > > > > WARNING: Injection data not found in JNDI
>> context:
>> >>> >> > > > > > > > > > >
>> >>> >> > > >
>> jndiName='comp/env/com.mycompany.saas.jaxws.SoapBase/context',
>> >>> >> > > > > > > > > > >
>> target=com.mycompany.saas.jaxws.SoapBase/context
>> >>> >> > > > > > > > > > >
>> >>> >> > > > > > > > > > > I have also tried making a getter and setter
>> for the
>> >>> >> > field
>> >>> >> > > > and
>> >>> >> > > > > > > > placing
>> >>> >> > > > > > > > > > the
>> >>> >> > > > > > > > > > > @Resource on the setter to no effect.
>> >>> >> > > > > > > > > > >
>> >>> >> > > > > > > > > > > Any ideas?
>> >>> >> > > > > > > > > > >
>> >>> >> > > > > > > > > > > Thanks,
>> >>> >> > > > > > > > > > >
>> >>> >> > > > > > > > > > > James
>> >>> >> > > > > > > > > > >
>> >>> >> > > > > > > > > > >
>> >>> >> > > > > > > > > >
>> >>> >> > > > > > > > >
>> >>> >> > > > > > > >
>> >>> >> > > > > > >
>> >>> >> > > > > >
>> >>> >> > > > >
>> >>> >> > > >
>> >>> >> > >
>> >>> >> >
>> >>> >>
>> >>>
>>
>
>
Re: WARNING: Injection data not found in JNDI context
Posted by James Green <ja...@gmail.com>.
Is there an issue covering the lack of support when exposed via web.xml?
On 20 November 2013 11:06, Romain Manni-Bucau <rm...@gmail.com> wrote:
> FYI https://issues.apache.org/jira/browse/TOMEE-1081
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
>
> 2013/11/20 Romain Manni-Bucau <rm...@gmail.com>:
> > Hi
> >
> > I'll fix the pojo issue but you can configure urls in openejb-jar.xml:
> >
> http://svn.apache.org/repos/asf/tomee/tomee/trunk/examples/change-jaxws-url/src/main/resources/META-INF/openejb-jar.xml
> > Romain Manni-Bucau
> > Twitter: @rmannibucau
> > Blog: http://rmannibucau.wordpress.com/
> > LinkedIn: http://fr.linkedin.com/in/rmannibucau
> > Github: https://github.com/rmannibucau
> >
> >
> >
> > 2013/11/20 James Green <ja...@gmail.com>:
> >> I added @Stateless to the web service and indeed warning solved.
> >>
> >> So I added it to web.xml to resolve my original (business) problem of
> >> wanting versioned urls - and the warning comes back.
> >>
> >> What do I need to do then?
> >>
> >> I have updated the source project on github to reflect this.
> >>
> >>
> >> On 20 November 2013 09:50, Romain Manni-Bucau <rm...@gmail.com>
> wrote:
> >>
> >>> Hi
> >>>
> >>> just debugged a bit and it only works for ejb ATM
> >>> Romain Manni-Bucau
> >>> Twitter: @rmannibucau
> >>> Blog: http://rmannibucau.wordpress.com/
> >>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> >>> Github: https://github.com/rmannibucau
> >>>
> >>>
> >>>
> >>> 2013/11/20 James Green <ja...@gmail.com>:
> >>> > Right, it really does not get any simpler than this:
> >>> >
> >>> > https://github.com/jmkgreen/test-multi-module
> >>> >
> >>> > I even accept it may not actually have met minimum requirements yet!
> >>> >
> >>> > The log:
> >>> >
> >>> > INFO: Deployed
> >>> >
> >>>
> Application(path=C:\Users\jgreen\Downloads\apache-tomee-plus-1.6.0-SNAPSHOT-NOV13\webapps\webapp)
> >>> > Nov 20, 2013 9:18:54 AM org.apache.openejb.InjectionProcessor
> >>> > fillInjectionProperties
> >>> > WARNING: Injection data not found in JNDI context:
> >>> > jndiName='comp/env/com.example.webapp.SoapBaseClass/context',
> >>> > target=com.example.webapp.SoapBaseClass/context
> >>> > Nov 20, 2013 9:18:54 AM
> org.apache.openejb.server.webservices.WsService
> >>> > afterApplicationCreated
> >>> > INFO: Webservice(wsdl=http://localhost:8080//webapp/SoapService,
> qname={
> >>> > http://www.example.net/2013-11-20}SoapService) -->
> >>> > Pojo(id=webapp.com.example.webapp.SoapService)
> >>> >
> >>> >
> >>> >
> >>> > On 20 November 2013 05:49, Romain Manni-Bucau <rmannibucau@gmail.com
> >
> >>> wrote:
> >>> >
> >>> >> Hmm
> >>> >>
> >>> >> Can you redo a project like it repeoducing it? Uber*ar are often
> >>> breaking
> >>> >> things...
> >>> >> Le 19 nov. 2013 23:09, "James Green" <ja...@gmail.com> a
> >>> écrit :
> >>> >>
> >>> >> > I am able to trigger this by adding the webservice class to
> web.xml.
> >>> >> >
> >>> >> > I took an existing (working) WebService class that was annotated
> >>> >> > @Stateless. I removed @Stateless and instead added a servlet
> entry in
> >>> >> > web.xml to route specific URL requests to it. That class is now
> >>> listed as
> >>> >> > suffering the injection problem (it too extends this base class
> having
> >>> >> > @Resource WebServiceContext inside). I added @Stateless back on
> but no
> >>> >> > change.
> >>> >> >
> >>> >> > The only other matter worthy of mentioning is that since I now
> have
> >>> two
> >>> >> web
> >>> >> > archive projects within the parent project, I created a third to
> hold
> >>> >> both
> >>> >> > web archives as dependencies, this one an 'uberwar'
> >>> >> > using org.codehaus.cargo:cargo-maven2-plugin. The default
> >>> configuration
> >>> >> > descriptor from their web site is being used, apparently fine.
> >>> >> >
> >>> >> >
> >>> >> > On 19 November 2013 21:29, Romain Manni-Bucau <
> rmannibucau@gmail.com>
> >>> >> > wrote:
> >>> >> >
> >>> >> > > Hmm, beans.xml is useless for @Resource, that sthg else i fear
> >>> >> > > Le 19 nov. 2013 22:27, "James Green" <ja...@gmail.com>
> a
> >>> >> écrit
> >>> >> > :
> >>> >> > >
> >>> >> > > > Would the project with the base class also require a beans.xml
> >>> file?
> >>> >> > It's
> >>> >> > > > not something covered in the examples we all see...
> >>> >> > > >
> >>> >> > > > I would expect subclasses annotated @WebService and having in
> the
> >>> >> > object
> >>> >> > > a
> >>> >> > > > field annotated @Resource to be scanned by reflection and
> >>> injected.
> >>> >> > Just
> >>> >> > > > wanting to confirm my thinking that the packages with the
> >>> subclasses
> >>> >> > > need a
> >>> >> > > > beans.xml declaration but nothing further for this stuff to
> work.
> >>> >> > > >
> >>> >> > > >
> >>> >> > > > On 19 November 2013 21:18, Romain Manni-Bucau <
> >>> rmannibucau@gmail.com
> >>> >> >
> >>> >> > > > wrote:
> >>> >> > > >
> >>> >> > > > > No, just as prefix. Hmm, try to share something to reproduce
> >>> >> > otherwise
> >>> >> > > > > thats hard to help you :s
> >>> >> > > > >
> >>> >> > > > > Ps: is it an ear?
> >>> >> > > > > Le 19 nov. 2013 22:16, "James Green" <
> james.mk.green@gmail.com>
> >>> a
> >>> >> > > écrit
> >>> >> > > > :
> >>> >> > > > >
> >>> >> > > > > > I renamed to mycompany-jaxws-core and it made no
> difference.
> >>> >> Unless
> >>> >> > > you
> >>> >> > > > > are
> >>> >> > > > > > suggesting anything with jaxws in it's name will be
> >>> excluded..?
> >>> >> > > > > >
> >>> >> > > > > >
> >>> >> > > > > > On 19 November 2013 21:02, Romain Manni-Bucau <
> >>> >> > rmannibucau@gmail.com
> >>> >> > > >
> >>> >> > > > > > wrote:
> >>> >> > > > > >
> >>> >> > > > > > > Try to rename it foo.jar, we exclude few jars from
> scanning
> >>> >> using
> >>> >> > > > > > > prefixes...jaxws can be one (i dont recall atm to be
> fully
> >>> >> > honest)
> >>> >> > > > > > > Le 19 nov. 2013 21:47, "James Green" <
> >>> james.mk.green@gmail.com
> >>> >> >
> >>> >> > a
> >>> >> > > > > écrit
> >>> >> > > > > > :
> >>> >> > > > > > >
> >>> >> > > > > > > > The name is something like jaxws-core. Why would you
> >>> think it
> >>> >> > is
> >>> >> > > > > being
> >>> >> > > > > > > > excluded?
> >>> >> > > > > > > >
> >>> >> > > > > > > > It's a commercial project I am afraid so best I can
> do is
> >>> >> try a
> >>> >> > > > test
> >>> >> > > > > > case
> >>> >> > > > > > > > if I get desperate.
> >>> >> > > > > > > >
> >>> >> > > > > > > > I could collapse the code back into a single war
> archive
> >>> >> again
> >>> >> > > but
> >>> >> > > > > I'd
> >>> >> > > > > > be
> >>> >> > > > > > > > disappointed :(.
> >>> >> > > > > > > >
> >>> >> > > > > > > >
> >>> >> > > > > > > > On 19 November 2013 19:18, Romain Manni-Bucau <
> >>> >> > > > rmannibucau@gmail.com
> >>> >> > > > > >
> >>> >> > > > > > > > wrote:
> >>> >> > > > > > > >
> >>> >> > > > > > > > > Hi
> >>> >> > > > > > > > >
> >>> >> > > > > > > > > What s the jar name (isnt it an exclusion?)? Can you
> >>> >> > reproduce
> >>> >> > > it
> >>> >> > > > > and
> >>> >> > > > > > > > share
> >>> >> > > > > > > > > a project?
> >>> >> > > > > > > > > Le 19 nov. 2013 20:02, "James Green" <
> >>> >> > james.mk.green@gmail.com
> >>> >> > > >
> >>> >> > > > a
> >>> >> > > > > > > écrit
> >>> >> > > > > > > > :
> >>> >> > > > > > > > >
> >>> >> > > > > > > > > > I just moved the setter of the WebServiceContext
> (with
> >>> >> > > > @Resource)
> >>> >> > > > > > to
> >>> >> > > > > > > > the
> >>> >> > > > > > > > > > @WebService implementation classes in the
> dependency
> >>> .war
> >>> >> > > > package
> >>> >> > > > > > > and I
> >>> >> > > > > > > > > > still get the error.
> >>> >> > > > > > > > > >
> >>> >> > > > > > > > > > I was hoping the container took issue with the
> >>> annotation
> >>> >> > > being
> >>> >> > > > > in
> >>> >> > > > > > a
> >>> >> > > > > > > > > class
> >>> >> > > > > > > > > > within a .jar library but whatever the problem
> is, it
> >>> >> isn't
> >>> >> > > > that.
> >>> >> > > > > > > > > >
> >>> >> > > > > > > > > > Suggestions welcomed.
> >>> >> > > > > > > > > >
> >>> >> > > > > > > > > >
> >>> >> > > > > > > > > > On 19 November 2013 17:38, James Green <
> >>> >> > > > james.mk.green@gmail.com
> >>> >> > > > > >
> >>> >> > > > > > > > wrote:
> >>> >> > > > > > > > > >
> >>> >> > > > > > > > > > > This is causing an NPE accessing a
> WebServiceContext
> >>> >> > > > annotated
> >>> >> > > > > > with
> >>> >> > > > > > > > > > > @Resource.
> >>> >> > > > > > > > > > >
> >>> >> > > > > > > > > > > To detail, I've been refactoring my Maven
> project
> >>> into
> >>> >> > > > > > sub-projects
> >>> >> > > > > > > > to
> >>> >> > > > > > > > > > > facilitate versioning of interfaces. Previously
> the
> >>> >> > entire
> >>> >> > > > web
> >>> >> > > > > > > > > interface
> >>> >> > > > > > > > > > > was held in a single war file project and it all
> >>> >> worked.
> >>> >> > > > > > > > > > >
> >>> >> > > > > > > > > > > The above field is in a base class I use for
> SOAP
> >>> >> > services.
> >>> >> > > > The
> >>> >> > > > > > > base
> >>> >> > > > > > > > > > class
> >>> >> > > > > > > > > > > was moved into a jar project and depended upon
> by
> >>> two
> >>> >> > > others
> >>> >> > > > -
> >>> >> > > > > > both
> >>> >> > > > > > > > war
> >>> >> > > > > > > > > > > packaging.
> >>> >> > > > > > > > > > >
> >>> >> > > > > > > > > > > In each case I have a beans.xml file which I
> thought
> >>> >> > might
> >>> >> > > > fix
> >>> >> > > > > > it.
> >>> >> > > > > > > > The
> >>> >> > > > > > > > > > > exact message as output by the latest TomEE-Plus
> >>> >> > > > 1.6-SNAPSHOT:
> >>> >> > > > > > > > > > >
> >>> >> > > > > > > > > > > WARNING: Injection data not found in JNDI
> context:
> >>> >> > > > > > > > > > >
> >>> >> > > > jndiName='comp/env/com.mycompany.saas.jaxws.SoapBase/context',
> >>> >> > > > > > > > > > > target=com.mycompany.saas.jaxws.SoapBase/context
> >>> >> > > > > > > > > > >
> >>> >> > > > > > > > > > > I have also tried making a getter and setter
> for the
> >>> >> > field
> >>> >> > > > and
> >>> >> > > > > > > > placing
> >>> >> > > > > > > > > > the
> >>> >> > > > > > > > > > > @Resource on the setter to no effect.
> >>> >> > > > > > > > > > >
> >>> >> > > > > > > > > > > Any ideas?
> >>> >> > > > > > > > > > >
> >>> >> > > > > > > > > > > Thanks,
> >>> >> > > > > > > > > > >
> >>> >> > > > > > > > > > > James
> >>> >> > > > > > > > > > >
> >>> >> > > > > > > > > > >
> >>> >> > > > > > > > > >
> >>> >> > > > > > > > >
> >>> >> > > > > > > >
> >>> >> > > > > > >
> >>> >> > > > > >
> >>> >> > > > >
> >>> >> > > >
> >>> >> > >
> >>> >> >
> >>> >>
> >>>
>
Re: WARNING: Injection data not found in JNDI context
Posted by Romain Manni-Bucau <rm...@gmail.com>.
FYI https://issues.apache.org/jira/browse/TOMEE-1081
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2013/11/20 Romain Manni-Bucau <rm...@gmail.com>:
> Hi
>
> I'll fix the pojo issue but you can configure urls in openejb-jar.xml:
> http://svn.apache.org/repos/asf/tomee/tomee/trunk/examples/change-jaxws-url/src/main/resources/META-INF/openejb-jar.xml
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
>
> 2013/11/20 James Green <ja...@gmail.com>:
>> I added @Stateless to the web service and indeed warning solved.
>>
>> So I added it to web.xml to resolve my original (business) problem of
>> wanting versioned urls - and the warning comes back.
>>
>> What do I need to do then?
>>
>> I have updated the source project on github to reflect this.
>>
>>
>> On 20 November 2013 09:50, Romain Manni-Bucau <rm...@gmail.com> wrote:
>>
>>> Hi
>>>
>>> just debugged a bit and it only works for ejb ATM
>>> Romain Manni-Bucau
>>> Twitter: @rmannibucau
>>> Blog: http://rmannibucau.wordpress.com/
>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>> Github: https://github.com/rmannibucau
>>>
>>>
>>>
>>> 2013/11/20 James Green <ja...@gmail.com>:
>>> > Right, it really does not get any simpler than this:
>>> >
>>> > https://github.com/jmkgreen/test-multi-module
>>> >
>>> > I even accept it may not actually have met minimum requirements yet!
>>> >
>>> > The log:
>>> >
>>> > INFO: Deployed
>>> >
>>> Application(path=C:\Users\jgreen\Downloads\apache-tomee-plus-1.6.0-SNAPSHOT-NOV13\webapps\webapp)
>>> > Nov 20, 2013 9:18:54 AM org.apache.openejb.InjectionProcessor
>>> > fillInjectionProperties
>>> > WARNING: Injection data not found in JNDI context:
>>> > jndiName='comp/env/com.example.webapp.SoapBaseClass/context',
>>> > target=com.example.webapp.SoapBaseClass/context
>>> > Nov 20, 2013 9:18:54 AM org.apache.openejb.server.webservices.WsService
>>> > afterApplicationCreated
>>> > INFO: Webservice(wsdl=http://localhost:8080//webapp/SoapService, qname={
>>> > http://www.example.net/2013-11-20}SoapService) -->
>>> > Pojo(id=webapp.com.example.webapp.SoapService)
>>> >
>>> >
>>> >
>>> > On 20 November 2013 05:49, Romain Manni-Bucau <rm...@gmail.com>
>>> wrote:
>>> >
>>> >> Hmm
>>> >>
>>> >> Can you redo a project like it repeoducing it? Uber*ar are often
>>> breaking
>>> >> things...
>>> >> Le 19 nov. 2013 23:09, "James Green" <ja...@gmail.com> a
>>> écrit :
>>> >>
>>> >> > I am able to trigger this by adding the webservice class to web.xml.
>>> >> >
>>> >> > I took an existing (working) WebService class that was annotated
>>> >> > @Stateless. I removed @Stateless and instead added a servlet entry in
>>> >> > web.xml to route specific URL requests to it. That class is now
>>> listed as
>>> >> > suffering the injection problem (it too extends this base class having
>>> >> > @Resource WebServiceContext inside). I added @Stateless back on but no
>>> >> > change.
>>> >> >
>>> >> > The only other matter worthy of mentioning is that since I now have
>>> two
>>> >> web
>>> >> > archive projects within the parent project, I created a third to hold
>>> >> both
>>> >> > web archives as dependencies, this one an 'uberwar'
>>> >> > using org.codehaus.cargo:cargo-maven2-plugin. The default
>>> configuration
>>> >> > descriptor from their web site is being used, apparently fine.
>>> >> >
>>> >> >
>>> >> > On 19 November 2013 21:29, Romain Manni-Bucau <rm...@gmail.com>
>>> >> > wrote:
>>> >> >
>>> >> > > Hmm, beans.xml is useless for @Resource, that sthg else i fear
>>> >> > > Le 19 nov. 2013 22:27, "James Green" <ja...@gmail.com> a
>>> >> écrit
>>> >> > :
>>> >> > >
>>> >> > > > Would the project with the base class also require a beans.xml
>>> file?
>>> >> > It's
>>> >> > > > not something covered in the examples we all see...
>>> >> > > >
>>> >> > > > I would expect subclasses annotated @WebService and having in the
>>> >> > object
>>> >> > > a
>>> >> > > > field annotated @Resource to be scanned by reflection and
>>> injected.
>>> >> > Just
>>> >> > > > wanting to confirm my thinking that the packages with the
>>> subclasses
>>> >> > > need a
>>> >> > > > beans.xml declaration but nothing further for this stuff to work.
>>> >> > > >
>>> >> > > >
>>> >> > > > On 19 November 2013 21:18, Romain Manni-Bucau <
>>> rmannibucau@gmail.com
>>> >> >
>>> >> > > > wrote:
>>> >> > > >
>>> >> > > > > No, just as prefix. Hmm, try to share something to reproduce
>>> >> > otherwise
>>> >> > > > > thats hard to help you :s
>>> >> > > > >
>>> >> > > > > Ps: is it an ear?
>>> >> > > > > Le 19 nov. 2013 22:16, "James Green" <ja...@gmail.com>
>>> a
>>> >> > > écrit
>>> >> > > > :
>>> >> > > > >
>>> >> > > > > > I renamed to mycompany-jaxws-core and it made no difference.
>>> >> Unless
>>> >> > > you
>>> >> > > > > are
>>> >> > > > > > suggesting anything with jaxws in it's name will be
>>> excluded..?
>>> >> > > > > >
>>> >> > > > > >
>>> >> > > > > > On 19 November 2013 21:02, Romain Manni-Bucau <
>>> >> > rmannibucau@gmail.com
>>> >> > > >
>>> >> > > > > > wrote:
>>> >> > > > > >
>>> >> > > > > > > Try to rename it foo.jar, we exclude few jars from scanning
>>> >> using
>>> >> > > > > > > prefixes...jaxws can be one (i dont recall atm to be fully
>>> >> > honest)
>>> >> > > > > > > Le 19 nov. 2013 21:47, "James Green" <
>>> james.mk.green@gmail.com
>>> >> >
>>> >> > a
>>> >> > > > > écrit
>>> >> > > > > > :
>>> >> > > > > > >
>>> >> > > > > > > > The name is something like jaxws-core. Why would you
>>> think it
>>> >> > is
>>> >> > > > > being
>>> >> > > > > > > > excluded?
>>> >> > > > > > > >
>>> >> > > > > > > > It's a commercial project I am afraid so best I can do is
>>> >> try a
>>> >> > > > test
>>> >> > > > > > case
>>> >> > > > > > > > if I get desperate.
>>> >> > > > > > > >
>>> >> > > > > > > > I could collapse the code back into a single war archive
>>> >> again
>>> >> > > but
>>> >> > > > > I'd
>>> >> > > > > > be
>>> >> > > > > > > > disappointed :(.
>>> >> > > > > > > >
>>> >> > > > > > > >
>>> >> > > > > > > > On 19 November 2013 19:18, Romain Manni-Bucau <
>>> >> > > > rmannibucau@gmail.com
>>> >> > > > > >
>>> >> > > > > > > > wrote:
>>> >> > > > > > > >
>>> >> > > > > > > > > Hi
>>> >> > > > > > > > >
>>> >> > > > > > > > > What s the jar name (isnt it an exclusion?)? Can you
>>> >> > reproduce
>>> >> > > it
>>> >> > > > > and
>>> >> > > > > > > > share
>>> >> > > > > > > > > a project?
>>> >> > > > > > > > > Le 19 nov. 2013 20:02, "James Green" <
>>> >> > james.mk.green@gmail.com
>>> >> > > >
>>> >> > > > a
>>> >> > > > > > > écrit
>>> >> > > > > > > > :
>>> >> > > > > > > > >
>>> >> > > > > > > > > > I just moved the setter of the WebServiceContext (with
>>> >> > > > @Resource)
>>> >> > > > > > to
>>> >> > > > > > > > the
>>> >> > > > > > > > > > @WebService implementation classes in the dependency
>>> .war
>>> >> > > > package
>>> >> > > > > > > and I
>>> >> > > > > > > > > > still get the error.
>>> >> > > > > > > > > >
>>> >> > > > > > > > > > I was hoping the container took issue with the
>>> annotation
>>> >> > > being
>>> >> > > > > in
>>> >> > > > > > a
>>> >> > > > > > > > > class
>>> >> > > > > > > > > > within a .jar library but whatever the problem is, it
>>> >> isn't
>>> >> > > > that.
>>> >> > > > > > > > > >
>>> >> > > > > > > > > > Suggestions welcomed.
>>> >> > > > > > > > > >
>>> >> > > > > > > > > >
>>> >> > > > > > > > > > On 19 November 2013 17:38, James Green <
>>> >> > > > james.mk.green@gmail.com
>>> >> > > > > >
>>> >> > > > > > > > wrote:
>>> >> > > > > > > > > >
>>> >> > > > > > > > > > > This is causing an NPE accessing a WebServiceContext
>>> >> > > > annotated
>>> >> > > > > > with
>>> >> > > > > > > > > > > @Resource.
>>> >> > > > > > > > > > >
>>> >> > > > > > > > > > > To detail, I've been refactoring my Maven project
>>> into
>>> >> > > > > > sub-projects
>>> >> > > > > > > > to
>>> >> > > > > > > > > > > facilitate versioning of interfaces. Previously the
>>> >> > entire
>>> >> > > > web
>>> >> > > > > > > > > interface
>>> >> > > > > > > > > > > was held in a single war file project and it all
>>> >> worked.
>>> >> > > > > > > > > > >
>>> >> > > > > > > > > > > The above field is in a base class I use for SOAP
>>> >> > services.
>>> >> > > > The
>>> >> > > > > > > base
>>> >> > > > > > > > > > class
>>> >> > > > > > > > > > > was moved into a jar project and depended upon by
>>> two
>>> >> > > others
>>> >> > > > -
>>> >> > > > > > both
>>> >> > > > > > > > war
>>> >> > > > > > > > > > > packaging.
>>> >> > > > > > > > > > >
>>> >> > > > > > > > > > > In each case I have a beans.xml file which I thought
>>> >> > might
>>> >> > > > fix
>>> >> > > > > > it.
>>> >> > > > > > > > The
>>> >> > > > > > > > > > > exact message as output by the latest TomEE-Plus
>>> >> > > > 1.6-SNAPSHOT:
>>> >> > > > > > > > > > >
>>> >> > > > > > > > > > > WARNING: Injection data not found in JNDI context:
>>> >> > > > > > > > > > >
>>> >> > > > jndiName='comp/env/com.mycompany.saas.jaxws.SoapBase/context',
>>> >> > > > > > > > > > > target=com.mycompany.saas.jaxws.SoapBase/context
>>> >> > > > > > > > > > >
>>> >> > > > > > > > > > > I have also tried making a getter and setter for the
>>> >> > field
>>> >> > > > and
>>> >> > > > > > > > placing
>>> >> > > > > > > > > > the
>>> >> > > > > > > > > > > @Resource on the setter to no effect.
>>> >> > > > > > > > > > >
>>> >> > > > > > > > > > > Any ideas?
>>> >> > > > > > > > > > >
>>> >> > > > > > > > > > > Thanks,
>>> >> > > > > > > > > > >
>>> >> > > > > > > > > > > James
>>> >> > > > > > > > > > >
>>> >> > > > > > > > > > >
>>> >> > > > > > > > > >
>>> >> > > > > > > > >
>>> >> > > > > > > >
>>> >> > > > > > >
>>> >> > > > > >
>>> >> > > > >
>>> >> > > >
>>> >> > >
>>> >> >
>>> >>
>>>
Re: WARNING: Injection data not found in JNDI context
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi
I'll fix the pojo issue but you can configure urls in openejb-jar.xml:
http://svn.apache.org/repos/asf/tomee/tomee/trunk/examples/change-jaxws-url/src/main/resources/META-INF/openejb-jar.xml
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2013/11/20 James Green <ja...@gmail.com>:
> I added @Stateless to the web service and indeed warning solved.
>
> So I added it to web.xml to resolve my original (business) problem of
> wanting versioned urls - and the warning comes back.
>
> What do I need to do then?
>
> I have updated the source project on github to reflect this.
>
>
> On 20 November 2013 09:50, Romain Manni-Bucau <rm...@gmail.com> wrote:
>
>> Hi
>>
>> just debugged a bit and it only works for ejb ATM
>> Romain Manni-Bucau
>> Twitter: @rmannibucau
>> Blog: http://rmannibucau.wordpress.com/
>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>> Github: https://github.com/rmannibucau
>>
>>
>>
>> 2013/11/20 James Green <ja...@gmail.com>:
>> > Right, it really does not get any simpler than this:
>> >
>> > https://github.com/jmkgreen/test-multi-module
>> >
>> > I even accept it may not actually have met minimum requirements yet!
>> >
>> > The log:
>> >
>> > INFO: Deployed
>> >
>> Application(path=C:\Users\jgreen\Downloads\apache-tomee-plus-1.6.0-SNAPSHOT-NOV13\webapps\webapp)
>> > Nov 20, 2013 9:18:54 AM org.apache.openejb.InjectionProcessor
>> > fillInjectionProperties
>> > WARNING: Injection data not found in JNDI context:
>> > jndiName='comp/env/com.example.webapp.SoapBaseClass/context',
>> > target=com.example.webapp.SoapBaseClass/context
>> > Nov 20, 2013 9:18:54 AM org.apache.openejb.server.webservices.WsService
>> > afterApplicationCreated
>> > INFO: Webservice(wsdl=http://localhost:8080//webapp/SoapService, qname={
>> > http://www.example.net/2013-11-20}SoapService) -->
>> > Pojo(id=webapp.com.example.webapp.SoapService)
>> >
>> >
>> >
>> > On 20 November 2013 05:49, Romain Manni-Bucau <rm...@gmail.com>
>> wrote:
>> >
>> >> Hmm
>> >>
>> >> Can you redo a project like it repeoducing it? Uber*ar are often
>> breaking
>> >> things...
>> >> Le 19 nov. 2013 23:09, "James Green" <ja...@gmail.com> a
>> écrit :
>> >>
>> >> > I am able to trigger this by adding the webservice class to web.xml.
>> >> >
>> >> > I took an existing (working) WebService class that was annotated
>> >> > @Stateless. I removed @Stateless and instead added a servlet entry in
>> >> > web.xml to route specific URL requests to it. That class is now
>> listed as
>> >> > suffering the injection problem (it too extends this base class having
>> >> > @Resource WebServiceContext inside). I added @Stateless back on but no
>> >> > change.
>> >> >
>> >> > The only other matter worthy of mentioning is that since I now have
>> two
>> >> web
>> >> > archive projects within the parent project, I created a third to hold
>> >> both
>> >> > web archives as dependencies, this one an 'uberwar'
>> >> > using org.codehaus.cargo:cargo-maven2-plugin. The default
>> configuration
>> >> > descriptor from their web site is being used, apparently fine.
>> >> >
>> >> >
>> >> > On 19 November 2013 21:29, Romain Manni-Bucau <rm...@gmail.com>
>> >> > wrote:
>> >> >
>> >> > > Hmm, beans.xml is useless for @Resource, that sthg else i fear
>> >> > > Le 19 nov. 2013 22:27, "James Green" <ja...@gmail.com> a
>> >> écrit
>> >> > :
>> >> > >
>> >> > > > Would the project with the base class also require a beans.xml
>> file?
>> >> > It's
>> >> > > > not something covered in the examples we all see...
>> >> > > >
>> >> > > > I would expect subclasses annotated @WebService and having in the
>> >> > object
>> >> > > a
>> >> > > > field annotated @Resource to be scanned by reflection and
>> injected.
>> >> > Just
>> >> > > > wanting to confirm my thinking that the packages with the
>> subclasses
>> >> > > need a
>> >> > > > beans.xml declaration but nothing further for this stuff to work.
>> >> > > >
>> >> > > >
>> >> > > > On 19 November 2013 21:18, Romain Manni-Bucau <
>> rmannibucau@gmail.com
>> >> >
>> >> > > > wrote:
>> >> > > >
>> >> > > > > No, just as prefix. Hmm, try to share something to reproduce
>> >> > otherwise
>> >> > > > > thats hard to help you :s
>> >> > > > >
>> >> > > > > Ps: is it an ear?
>> >> > > > > Le 19 nov. 2013 22:16, "James Green" <ja...@gmail.com>
>> a
>> >> > > écrit
>> >> > > > :
>> >> > > > >
>> >> > > > > > I renamed to mycompany-jaxws-core and it made no difference.
>> >> Unless
>> >> > > you
>> >> > > > > are
>> >> > > > > > suggesting anything with jaxws in it's name will be
>> excluded..?
>> >> > > > > >
>> >> > > > > >
>> >> > > > > > On 19 November 2013 21:02, Romain Manni-Bucau <
>> >> > rmannibucau@gmail.com
>> >> > > >
>> >> > > > > > wrote:
>> >> > > > > >
>> >> > > > > > > Try to rename it foo.jar, we exclude few jars from scanning
>> >> using
>> >> > > > > > > prefixes...jaxws can be one (i dont recall atm to be fully
>> >> > honest)
>> >> > > > > > > Le 19 nov. 2013 21:47, "James Green" <
>> james.mk.green@gmail.com
>> >> >
>> >> > a
>> >> > > > > écrit
>> >> > > > > > :
>> >> > > > > > >
>> >> > > > > > > > The name is something like jaxws-core. Why would you
>> think it
>> >> > is
>> >> > > > > being
>> >> > > > > > > > excluded?
>> >> > > > > > > >
>> >> > > > > > > > It's a commercial project I am afraid so best I can do is
>> >> try a
>> >> > > > test
>> >> > > > > > case
>> >> > > > > > > > if I get desperate.
>> >> > > > > > > >
>> >> > > > > > > > I could collapse the code back into a single war archive
>> >> again
>> >> > > but
>> >> > > > > I'd
>> >> > > > > > be
>> >> > > > > > > > disappointed :(.
>> >> > > > > > > >
>> >> > > > > > > >
>> >> > > > > > > > On 19 November 2013 19:18, Romain Manni-Bucau <
>> >> > > > rmannibucau@gmail.com
>> >> > > > > >
>> >> > > > > > > > wrote:
>> >> > > > > > > >
>> >> > > > > > > > > Hi
>> >> > > > > > > > >
>> >> > > > > > > > > What s the jar name (isnt it an exclusion?)? Can you
>> >> > reproduce
>> >> > > it
>> >> > > > > and
>> >> > > > > > > > share
>> >> > > > > > > > > a project?
>> >> > > > > > > > > Le 19 nov. 2013 20:02, "James Green" <
>> >> > james.mk.green@gmail.com
>> >> > > >
>> >> > > > a
>> >> > > > > > > écrit
>> >> > > > > > > > :
>> >> > > > > > > > >
>> >> > > > > > > > > > I just moved the setter of the WebServiceContext (with
>> >> > > > @Resource)
>> >> > > > > > to
>> >> > > > > > > > the
>> >> > > > > > > > > > @WebService implementation classes in the dependency
>> .war
>> >> > > > package
>> >> > > > > > > and I
>> >> > > > > > > > > > still get the error.
>> >> > > > > > > > > >
>> >> > > > > > > > > > I was hoping the container took issue with the
>> annotation
>> >> > > being
>> >> > > > > in
>> >> > > > > > a
>> >> > > > > > > > > class
>> >> > > > > > > > > > within a .jar library but whatever the problem is, it
>> >> isn't
>> >> > > > that.
>> >> > > > > > > > > >
>> >> > > > > > > > > > Suggestions welcomed.
>> >> > > > > > > > > >
>> >> > > > > > > > > >
>> >> > > > > > > > > > On 19 November 2013 17:38, James Green <
>> >> > > > james.mk.green@gmail.com
>> >> > > > > >
>> >> > > > > > > > wrote:
>> >> > > > > > > > > >
>> >> > > > > > > > > > > This is causing an NPE accessing a WebServiceContext
>> >> > > > annotated
>> >> > > > > > with
>> >> > > > > > > > > > > @Resource.
>> >> > > > > > > > > > >
>> >> > > > > > > > > > > To detail, I've been refactoring my Maven project
>> into
>> >> > > > > > sub-projects
>> >> > > > > > > > to
>> >> > > > > > > > > > > facilitate versioning of interfaces. Previously the
>> >> > entire
>> >> > > > web
>> >> > > > > > > > > interface
>> >> > > > > > > > > > > was held in a single war file project and it all
>> >> worked.
>> >> > > > > > > > > > >
>> >> > > > > > > > > > > The above field is in a base class I use for SOAP
>> >> > services.
>> >> > > > The
>> >> > > > > > > base
>> >> > > > > > > > > > class
>> >> > > > > > > > > > > was moved into a jar project and depended upon by
>> two
>> >> > > others
>> >> > > > -
>> >> > > > > > both
>> >> > > > > > > > war
>> >> > > > > > > > > > > packaging.
>> >> > > > > > > > > > >
>> >> > > > > > > > > > > In each case I have a beans.xml file which I thought
>> >> > might
>> >> > > > fix
>> >> > > > > > it.
>> >> > > > > > > > The
>> >> > > > > > > > > > > exact message as output by the latest TomEE-Plus
>> >> > > > 1.6-SNAPSHOT:
>> >> > > > > > > > > > >
>> >> > > > > > > > > > > WARNING: Injection data not found in JNDI context:
>> >> > > > > > > > > > >
>> >> > > > jndiName='comp/env/com.mycompany.saas.jaxws.SoapBase/context',
>> >> > > > > > > > > > > target=com.mycompany.saas.jaxws.SoapBase/context
>> >> > > > > > > > > > >
>> >> > > > > > > > > > > I have also tried making a getter and setter for the
>> >> > field
>> >> > > > and
>> >> > > > > > > > placing
>> >> > > > > > > > > > the
>> >> > > > > > > > > > > @Resource on the setter to no effect.
>> >> > > > > > > > > > >
>> >> > > > > > > > > > > Any ideas?
>> >> > > > > > > > > > >
>> >> > > > > > > > > > > Thanks,
>> >> > > > > > > > > > >
>> >> > > > > > > > > > > James
>> >> > > > > > > > > > >
>> >> > > > > > > > > > >
>> >> > > > > > > > > >
>> >> > > > > > > > >
>> >> > > > > > > >
>> >> > > > > > >
>> >> > > > > >
>> >> > > > >
>> >> > > >
>> >> > >
>> >> >
>> >>
>>
Re: WARNING: Injection data not found in JNDI context
Posted by James Green <ja...@gmail.com>.
I added @Stateless to the web service and indeed warning solved.
So I added it to web.xml to resolve my original (business) problem of
wanting versioned urls - and the warning comes back.
What do I need to do then?
I have updated the source project on github to reflect this.
On 20 November 2013 09:50, Romain Manni-Bucau <rm...@gmail.com> wrote:
> Hi
>
> just debugged a bit and it only works for ejb ATM
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
>
> 2013/11/20 James Green <ja...@gmail.com>:
> > Right, it really does not get any simpler than this:
> >
> > https://github.com/jmkgreen/test-multi-module
> >
> > I even accept it may not actually have met minimum requirements yet!
> >
> > The log:
> >
> > INFO: Deployed
> >
> Application(path=C:\Users\jgreen\Downloads\apache-tomee-plus-1.6.0-SNAPSHOT-NOV13\webapps\webapp)
> > Nov 20, 2013 9:18:54 AM org.apache.openejb.InjectionProcessor
> > fillInjectionProperties
> > WARNING: Injection data not found in JNDI context:
> > jndiName='comp/env/com.example.webapp.SoapBaseClass/context',
> > target=com.example.webapp.SoapBaseClass/context
> > Nov 20, 2013 9:18:54 AM org.apache.openejb.server.webservices.WsService
> > afterApplicationCreated
> > INFO: Webservice(wsdl=http://localhost:8080//webapp/SoapService, qname={
> > http://www.example.net/2013-11-20}SoapService) -->
> > Pojo(id=webapp.com.example.webapp.SoapService)
> >
> >
> >
> > On 20 November 2013 05:49, Romain Manni-Bucau <rm...@gmail.com>
> wrote:
> >
> >> Hmm
> >>
> >> Can you redo a project like it repeoducing it? Uber*ar are often
> breaking
> >> things...
> >> Le 19 nov. 2013 23:09, "James Green" <ja...@gmail.com> a
> écrit :
> >>
> >> > I am able to trigger this by adding the webservice class to web.xml.
> >> >
> >> > I took an existing (working) WebService class that was annotated
> >> > @Stateless. I removed @Stateless and instead added a servlet entry in
> >> > web.xml to route specific URL requests to it. That class is now
> listed as
> >> > suffering the injection problem (it too extends this base class having
> >> > @Resource WebServiceContext inside). I added @Stateless back on but no
> >> > change.
> >> >
> >> > The only other matter worthy of mentioning is that since I now have
> two
> >> web
> >> > archive projects within the parent project, I created a third to hold
> >> both
> >> > web archives as dependencies, this one an 'uberwar'
> >> > using org.codehaus.cargo:cargo-maven2-plugin. The default
> configuration
> >> > descriptor from their web site is being used, apparently fine.
> >> >
> >> >
> >> > On 19 November 2013 21:29, Romain Manni-Bucau <rm...@gmail.com>
> >> > wrote:
> >> >
> >> > > Hmm, beans.xml is useless for @Resource, that sthg else i fear
> >> > > Le 19 nov. 2013 22:27, "James Green" <ja...@gmail.com> a
> >> écrit
> >> > :
> >> > >
> >> > > > Would the project with the base class also require a beans.xml
> file?
> >> > It's
> >> > > > not something covered in the examples we all see...
> >> > > >
> >> > > > I would expect subclasses annotated @WebService and having in the
> >> > object
> >> > > a
> >> > > > field annotated @Resource to be scanned by reflection and
> injected.
> >> > Just
> >> > > > wanting to confirm my thinking that the packages with the
> subclasses
> >> > > need a
> >> > > > beans.xml declaration but nothing further for this stuff to work.
> >> > > >
> >> > > >
> >> > > > On 19 November 2013 21:18, Romain Manni-Bucau <
> rmannibucau@gmail.com
> >> >
> >> > > > wrote:
> >> > > >
> >> > > > > No, just as prefix. Hmm, try to share something to reproduce
> >> > otherwise
> >> > > > > thats hard to help you :s
> >> > > > >
> >> > > > > Ps: is it an ear?
> >> > > > > Le 19 nov. 2013 22:16, "James Green" <ja...@gmail.com>
> a
> >> > > écrit
> >> > > > :
> >> > > > >
> >> > > > > > I renamed to mycompany-jaxws-core and it made no difference.
> >> Unless
> >> > > you
> >> > > > > are
> >> > > > > > suggesting anything with jaxws in it's name will be
> excluded..?
> >> > > > > >
> >> > > > > >
> >> > > > > > On 19 November 2013 21:02, Romain Manni-Bucau <
> >> > rmannibucau@gmail.com
> >> > > >
> >> > > > > > wrote:
> >> > > > > >
> >> > > > > > > Try to rename it foo.jar, we exclude few jars from scanning
> >> using
> >> > > > > > > prefixes...jaxws can be one (i dont recall atm to be fully
> >> > honest)
> >> > > > > > > Le 19 nov. 2013 21:47, "James Green" <
> james.mk.green@gmail.com
> >> >
> >> > a
> >> > > > > écrit
> >> > > > > > :
> >> > > > > > >
> >> > > > > > > > The name is something like jaxws-core. Why would you
> think it
> >> > is
> >> > > > > being
> >> > > > > > > > excluded?
> >> > > > > > > >
> >> > > > > > > > It's a commercial project I am afraid so best I can do is
> >> try a
> >> > > > test
> >> > > > > > case
> >> > > > > > > > if I get desperate.
> >> > > > > > > >
> >> > > > > > > > I could collapse the code back into a single war archive
> >> again
> >> > > but
> >> > > > > I'd
> >> > > > > > be
> >> > > > > > > > disappointed :(.
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > On 19 November 2013 19:18, Romain Manni-Bucau <
> >> > > > rmannibucau@gmail.com
> >> > > > > >
> >> > > > > > > > wrote:
> >> > > > > > > >
> >> > > > > > > > > Hi
> >> > > > > > > > >
> >> > > > > > > > > What s the jar name (isnt it an exclusion?)? Can you
> >> > reproduce
> >> > > it
> >> > > > > and
> >> > > > > > > > share
> >> > > > > > > > > a project?
> >> > > > > > > > > Le 19 nov. 2013 20:02, "James Green" <
> >> > james.mk.green@gmail.com
> >> > > >
> >> > > > a
> >> > > > > > > écrit
> >> > > > > > > > :
> >> > > > > > > > >
> >> > > > > > > > > > I just moved the setter of the WebServiceContext (with
> >> > > > @Resource)
> >> > > > > > to
> >> > > > > > > > the
> >> > > > > > > > > > @WebService implementation classes in the dependency
> .war
> >> > > > package
> >> > > > > > > and I
> >> > > > > > > > > > still get the error.
> >> > > > > > > > > >
> >> > > > > > > > > > I was hoping the container took issue with the
> annotation
> >> > > being
> >> > > > > in
> >> > > > > > a
> >> > > > > > > > > class
> >> > > > > > > > > > within a .jar library but whatever the problem is, it
> >> isn't
> >> > > > that.
> >> > > > > > > > > >
> >> > > > > > > > > > Suggestions welcomed.
> >> > > > > > > > > >
> >> > > > > > > > > >
> >> > > > > > > > > > On 19 November 2013 17:38, James Green <
> >> > > > james.mk.green@gmail.com
> >> > > > > >
> >> > > > > > > > wrote:
> >> > > > > > > > > >
> >> > > > > > > > > > > This is causing an NPE accessing a WebServiceContext
> >> > > > annotated
> >> > > > > > with
> >> > > > > > > > > > > @Resource.
> >> > > > > > > > > > >
> >> > > > > > > > > > > To detail, I've been refactoring my Maven project
> into
> >> > > > > > sub-projects
> >> > > > > > > > to
> >> > > > > > > > > > > facilitate versioning of interfaces. Previously the
> >> > entire
> >> > > > web
> >> > > > > > > > > interface
> >> > > > > > > > > > > was held in a single war file project and it all
> >> worked.
> >> > > > > > > > > > >
> >> > > > > > > > > > > The above field is in a base class I use for SOAP
> >> > services.
> >> > > > The
> >> > > > > > > base
> >> > > > > > > > > > class
> >> > > > > > > > > > > was moved into a jar project and depended upon by
> two
> >> > > others
> >> > > > -
> >> > > > > > both
> >> > > > > > > > war
> >> > > > > > > > > > > packaging.
> >> > > > > > > > > > >
> >> > > > > > > > > > > In each case I have a beans.xml file which I thought
> >> > might
> >> > > > fix
> >> > > > > > it.
> >> > > > > > > > The
> >> > > > > > > > > > > exact message as output by the latest TomEE-Plus
> >> > > > 1.6-SNAPSHOT:
> >> > > > > > > > > > >
> >> > > > > > > > > > > WARNING: Injection data not found in JNDI context:
> >> > > > > > > > > > >
> >> > > > jndiName='comp/env/com.mycompany.saas.jaxws.SoapBase/context',
> >> > > > > > > > > > > target=com.mycompany.saas.jaxws.SoapBase/context
> >> > > > > > > > > > >
> >> > > > > > > > > > > I have also tried making a getter and setter for the
> >> > field
> >> > > > and
> >> > > > > > > > placing
> >> > > > > > > > > > the
> >> > > > > > > > > > > @Resource on the setter to no effect.
> >> > > > > > > > > > >
> >> > > > > > > > > > > Any ideas?
> >> > > > > > > > > > >
> >> > > > > > > > > > > Thanks,
> >> > > > > > > > > > >
> >> > > > > > > > > > > James
> >> > > > > > > > > > >
> >> > > > > > > > > > >
> >> > > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
>
Re: WARNING: Injection data not found in JNDI context
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi
just debugged a bit and it only works for ejb ATM
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2013/11/20 James Green <ja...@gmail.com>:
> Right, it really does not get any simpler than this:
>
> https://github.com/jmkgreen/test-multi-module
>
> I even accept it may not actually have met minimum requirements yet!
>
> The log:
>
> INFO: Deployed
> Application(path=C:\Users\jgreen\Downloads\apache-tomee-plus-1.6.0-SNAPSHOT-NOV13\webapps\webapp)
> Nov 20, 2013 9:18:54 AM org.apache.openejb.InjectionProcessor
> fillInjectionProperties
> WARNING: Injection data not found in JNDI context:
> jndiName='comp/env/com.example.webapp.SoapBaseClass/context',
> target=com.example.webapp.SoapBaseClass/context
> Nov 20, 2013 9:18:54 AM org.apache.openejb.server.webservices.WsService
> afterApplicationCreated
> INFO: Webservice(wsdl=http://localhost:8080//webapp/SoapService, qname={
> http://www.example.net/2013-11-20}SoapService) -->
> Pojo(id=webapp.com.example.webapp.SoapService)
>
>
>
> On 20 November 2013 05:49, Romain Manni-Bucau <rm...@gmail.com> wrote:
>
>> Hmm
>>
>> Can you redo a project like it repeoducing it? Uber*ar are often breaking
>> things...
>> Le 19 nov. 2013 23:09, "James Green" <ja...@gmail.com> a écrit :
>>
>> > I am able to trigger this by adding the webservice class to web.xml.
>> >
>> > I took an existing (working) WebService class that was annotated
>> > @Stateless. I removed @Stateless and instead added a servlet entry in
>> > web.xml to route specific URL requests to it. That class is now listed as
>> > suffering the injection problem (it too extends this base class having
>> > @Resource WebServiceContext inside). I added @Stateless back on but no
>> > change.
>> >
>> > The only other matter worthy of mentioning is that since I now have two
>> web
>> > archive projects within the parent project, I created a third to hold
>> both
>> > web archives as dependencies, this one an 'uberwar'
>> > using org.codehaus.cargo:cargo-maven2-plugin. The default configuration
>> > descriptor from their web site is being used, apparently fine.
>> >
>> >
>> > On 19 November 2013 21:29, Romain Manni-Bucau <rm...@gmail.com>
>> > wrote:
>> >
>> > > Hmm, beans.xml is useless for @Resource, that sthg else i fear
>> > > Le 19 nov. 2013 22:27, "James Green" <ja...@gmail.com> a
>> écrit
>> > :
>> > >
>> > > > Would the project with the base class also require a beans.xml file?
>> > It's
>> > > > not something covered in the examples we all see...
>> > > >
>> > > > I would expect subclasses annotated @WebService and having in the
>> > object
>> > > a
>> > > > field annotated @Resource to be scanned by reflection and injected.
>> > Just
>> > > > wanting to confirm my thinking that the packages with the subclasses
>> > > need a
>> > > > beans.xml declaration but nothing further for this stuff to work.
>> > > >
>> > > >
>> > > > On 19 November 2013 21:18, Romain Manni-Bucau <rmannibucau@gmail.com
>> >
>> > > > wrote:
>> > > >
>> > > > > No, just as prefix. Hmm, try to share something to reproduce
>> > otherwise
>> > > > > thats hard to help you :s
>> > > > >
>> > > > > Ps: is it an ear?
>> > > > > Le 19 nov. 2013 22:16, "James Green" <ja...@gmail.com> a
>> > > écrit
>> > > > :
>> > > > >
>> > > > > > I renamed to mycompany-jaxws-core and it made no difference.
>> Unless
>> > > you
>> > > > > are
>> > > > > > suggesting anything with jaxws in it's name will be excluded..?
>> > > > > >
>> > > > > >
>> > > > > > On 19 November 2013 21:02, Romain Manni-Bucau <
>> > rmannibucau@gmail.com
>> > > >
>> > > > > > wrote:
>> > > > > >
>> > > > > > > Try to rename it foo.jar, we exclude few jars from scanning
>> using
>> > > > > > > prefixes...jaxws can be one (i dont recall atm to be fully
>> > honest)
>> > > > > > > Le 19 nov. 2013 21:47, "James Green" <james.mk.green@gmail.com
>> >
>> > a
>> > > > > écrit
>> > > > > > :
>> > > > > > >
>> > > > > > > > The name is something like jaxws-core. Why would you think it
>> > is
>> > > > > being
>> > > > > > > > excluded?
>> > > > > > > >
>> > > > > > > > It's a commercial project I am afraid so best I can do is
>> try a
>> > > > test
>> > > > > > case
>> > > > > > > > if I get desperate.
>> > > > > > > >
>> > > > > > > > I could collapse the code back into a single war archive
>> again
>> > > but
>> > > > > I'd
>> > > > > > be
>> > > > > > > > disappointed :(.
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > On 19 November 2013 19:18, Romain Manni-Bucau <
>> > > > rmannibucau@gmail.com
>> > > > > >
>> > > > > > > > wrote:
>> > > > > > > >
>> > > > > > > > > Hi
>> > > > > > > > >
>> > > > > > > > > What s the jar name (isnt it an exclusion?)? Can you
>> > reproduce
>> > > it
>> > > > > and
>> > > > > > > > share
>> > > > > > > > > a project?
>> > > > > > > > > Le 19 nov. 2013 20:02, "James Green" <
>> > james.mk.green@gmail.com
>> > > >
>> > > > a
>> > > > > > > écrit
>> > > > > > > > :
>> > > > > > > > >
>> > > > > > > > > > I just moved the setter of the WebServiceContext (with
>> > > > @Resource)
>> > > > > > to
>> > > > > > > > the
>> > > > > > > > > > @WebService implementation classes in the dependency .war
>> > > > package
>> > > > > > > and I
>> > > > > > > > > > still get the error.
>> > > > > > > > > >
>> > > > > > > > > > I was hoping the container took issue with the annotation
>> > > being
>> > > > > in
>> > > > > > a
>> > > > > > > > > class
>> > > > > > > > > > within a .jar library but whatever the problem is, it
>> isn't
>> > > > that.
>> > > > > > > > > >
>> > > > > > > > > > Suggestions welcomed.
>> > > > > > > > > >
>> > > > > > > > > >
>> > > > > > > > > > On 19 November 2013 17:38, James Green <
>> > > > james.mk.green@gmail.com
>> > > > > >
>> > > > > > > > wrote:
>> > > > > > > > > >
>> > > > > > > > > > > This is causing an NPE accessing a WebServiceContext
>> > > > annotated
>> > > > > > with
>> > > > > > > > > > > @Resource.
>> > > > > > > > > > >
>> > > > > > > > > > > To detail, I've been refactoring my Maven project into
>> > > > > > sub-projects
>> > > > > > > > to
>> > > > > > > > > > > facilitate versioning of interfaces. Previously the
>> > entire
>> > > > web
>> > > > > > > > > interface
>> > > > > > > > > > > was held in a single war file project and it all
>> worked.
>> > > > > > > > > > >
>> > > > > > > > > > > The above field is in a base class I use for SOAP
>> > services.
>> > > > The
>> > > > > > > base
>> > > > > > > > > > class
>> > > > > > > > > > > was moved into a jar project and depended upon by two
>> > > others
>> > > > -
>> > > > > > both
>> > > > > > > > war
>> > > > > > > > > > > packaging.
>> > > > > > > > > > >
>> > > > > > > > > > > In each case I have a beans.xml file which I thought
>> > might
>> > > > fix
>> > > > > > it.
>> > > > > > > > The
>> > > > > > > > > > > exact message as output by the latest TomEE-Plus
>> > > > 1.6-SNAPSHOT:
>> > > > > > > > > > >
>> > > > > > > > > > > WARNING: Injection data not found in JNDI context:
>> > > > > > > > > > >
>> > > > jndiName='comp/env/com.mycompany.saas.jaxws.SoapBase/context',
>> > > > > > > > > > > target=com.mycompany.saas.jaxws.SoapBase/context
>> > > > > > > > > > >
>> > > > > > > > > > > I have also tried making a getter and setter for the
>> > field
>> > > > and
>> > > > > > > > placing
>> > > > > > > > > > the
>> > > > > > > > > > > @Resource on the setter to no effect.
>> > > > > > > > > > >
>> > > > > > > > > > > Any ideas?
>> > > > > > > > > > >
>> > > > > > > > > > > Thanks,
>> > > > > > > > > > >
>> > > > > > > > > > > James
>> > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
Re: WARNING: Injection data not found in JNDI context
Posted by James Green <ja...@gmail.com>.
Right, it really does not get any simpler than this:
https://github.com/jmkgreen/test-multi-module
I even accept it may not actually have met minimum requirements yet!
The log:
INFO: Deployed
Application(path=C:\Users\jgreen\Downloads\apache-tomee-plus-1.6.0-SNAPSHOT-NOV13\webapps\webapp)
Nov 20, 2013 9:18:54 AM org.apache.openejb.InjectionProcessor
fillInjectionProperties
WARNING: Injection data not found in JNDI context:
jndiName='comp/env/com.example.webapp.SoapBaseClass/context',
target=com.example.webapp.SoapBaseClass/context
Nov 20, 2013 9:18:54 AM org.apache.openejb.server.webservices.WsService
afterApplicationCreated
INFO: Webservice(wsdl=http://localhost:8080//webapp/SoapService, qname={
http://www.example.net/2013-11-20}SoapService) -->
Pojo(id=webapp.com.example.webapp.SoapService)
On 20 November 2013 05:49, Romain Manni-Bucau <rm...@gmail.com> wrote:
> Hmm
>
> Can you redo a project like it repeoducing it? Uber*ar are often breaking
> things...
> Le 19 nov. 2013 23:09, "James Green" <ja...@gmail.com> a écrit :
>
> > I am able to trigger this by adding the webservice class to web.xml.
> >
> > I took an existing (working) WebService class that was annotated
> > @Stateless. I removed @Stateless and instead added a servlet entry in
> > web.xml to route specific URL requests to it. That class is now listed as
> > suffering the injection problem (it too extends this base class having
> > @Resource WebServiceContext inside). I added @Stateless back on but no
> > change.
> >
> > The only other matter worthy of mentioning is that since I now have two
> web
> > archive projects within the parent project, I created a third to hold
> both
> > web archives as dependencies, this one an 'uberwar'
> > using org.codehaus.cargo:cargo-maven2-plugin. The default configuration
> > descriptor from their web site is being used, apparently fine.
> >
> >
> > On 19 November 2013 21:29, Romain Manni-Bucau <rm...@gmail.com>
> > wrote:
> >
> > > Hmm, beans.xml is useless for @Resource, that sthg else i fear
> > > Le 19 nov. 2013 22:27, "James Green" <ja...@gmail.com> a
> écrit
> > :
> > >
> > > > Would the project with the base class also require a beans.xml file?
> > It's
> > > > not something covered in the examples we all see...
> > > >
> > > > I would expect subclasses annotated @WebService and having in the
> > object
> > > a
> > > > field annotated @Resource to be scanned by reflection and injected.
> > Just
> > > > wanting to confirm my thinking that the packages with the subclasses
> > > need a
> > > > beans.xml declaration but nothing further for this stuff to work.
> > > >
> > > >
> > > > On 19 November 2013 21:18, Romain Manni-Bucau <rmannibucau@gmail.com
> >
> > > > wrote:
> > > >
> > > > > No, just as prefix. Hmm, try to share something to reproduce
> > otherwise
> > > > > thats hard to help you :s
> > > > >
> > > > > Ps: is it an ear?
> > > > > Le 19 nov. 2013 22:16, "James Green" <ja...@gmail.com> a
> > > écrit
> > > > :
> > > > >
> > > > > > I renamed to mycompany-jaxws-core and it made no difference.
> Unless
> > > you
> > > > > are
> > > > > > suggesting anything with jaxws in it's name will be excluded..?
> > > > > >
> > > > > >
> > > > > > On 19 November 2013 21:02, Romain Manni-Bucau <
> > rmannibucau@gmail.com
> > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Try to rename it foo.jar, we exclude few jars from scanning
> using
> > > > > > > prefixes...jaxws can be one (i dont recall atm to be fully
> > honest)
> > > > > > > Le 19 nov. 2013 21:47, "James Green" <james.mk.green@gmail.com
> >
> > a
> > > > > écrit
> > > > > > :
> > > > > > >
> > > > > > > > The name is something like jaxws-core. Why would you think it
> > is
> > > > > being
> > > > > > > > excluded?
> > > > > > > >
> > > > > > > > It's a commercial project I am afraid so best I can do is
> try a
> > > > test
> > > > > > case
> > > > > > > > if I get desperate.
> > > > > > > >
> > > > > > > > I could collapse the code back into a single war archive
> again
> > > but
> > > > > I'd
> > > > > > be
> > > > > > > > disappointed :(.
> > > > > > > >
> > > > > > > >
> > > > > > > > On 19 November 2013 19:18, Romain Manni-Bucau <
> > > > rmannibucau@gmail.com
> > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hi
> > > > > > > > >
> > > > > > > > > What s the jar name (isnt it an exclusion?)? Can you
> > reproduce
> > > it
> > > > > and
> > > > > > > > share
> > > > > > > > > a project?
> > > > > > > > > Le 19 nov. 2013 20:02, "James Green" <
> > james.mk.green@gmail.com
> > > >
> > > > a
> > > > > > > écrit
> > > > > > > > :
> > > > > > > > >
> > > > > > > > > > I just moved the setter of the WebServiceContext (with
> > > > @Resource)
> > > > > > to
> > > > > > > > the
> > > > > > > > > > @WebService implementation classes in the dependency .war
> > > > package
> > > > > > > and I
> > > > > > > > > > still get the error.
> > > > > > > > > >
> > > > > > > > > > I was hoping the container took issue with the annotation
> > > being
> > > > > in
> > > > > > a
> > > > > > > > > class
> > > > > > > > > > within a .jar library but whatever the problem is, it
> isn't
> > > > that.
> > > > > > > > > >
> > > > > > > > > > Suggestions welcomed.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On 19 November 2013 17:38, James Green <
> > > > james.mk.green@gmail.com
> > > > > >
> > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > This is causing an NPE accessing a WebServiceContext
> > > > annotated
> > > > > > with
> > > > > > > > > > > @Resource.
> > > > > > > > > > >
> > > > > > > > > > > To detail, I've been refactoring my Maven project into
> > > > > > sub-projects
> > > > > > > > to
> > > > > > > > > > > facilitate versioning of interfaces. Previously the
> > entire
> > > > web
> > > > > > > > > interface
> > > > > > > > > > > was held in a single war file project and it all
> worked.
> > > > > > > > > > >
> > > > > > > > > > > The above field is in a base class I use for SOAP
> > services.
> > > > The
> > > > > > > base
> > > > > > > > > > class
> > > > > > > > > > > was moved into a jar project and depended upon by two
> > > others
> > > > -
> > > > > > both
> > > > > > > > war
> > > > > > > > > > > packaging.
> > > > > > > > > > >
> > > > > > > > > > > In each case I have a beans.xml file which I thought
> > might
> > > > fix
> > > > > > it.
> > > > > > > > The
> > > > > > > > > > > exact message as output by the latest TomEE-Plus
> > > > 1.6-SNAPSHOT:
> > > > > > > > > > >
> > > > > > > > > > > WARNING: Injection data not found in JNDI context:
> > > > > > > > > > >
> > > > jndiName='comp/env/com.mycompany.saas.jaxws.SoapBase/context',
> > > > > > > > > > > target=com.mycompany.saas.jaxws.SoapBase/context
> > > > > > > > > > >
> > > > > > > > > > > I have also tried making a getter and setter for the
> > field
> > > > and
> > > > > > > > placing
> > > > > > > > > > the
> > > > > > > > > > > @Resource on the setter to no effect.
> > > > > > > > > > >
> > > > > > > > > > > Any ideas?
> > > > > > > > > > >
> > > > > > > > > > > Thanks,
> > > > > > > > > > >
> > > > > > > > > > > James
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: WARNING: Injection data not found in JNDI context
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hmm
Can you redo a project like it repeoducing it? Uber*ar are often breaking
things...
Le 19 nov. 2013 23:09, "James Green" <ja...@gmail.com> a écrit :
> I am able to trigger this by adding the webservice class to web.xml.
>
> I took an existing (working) WebService class that was annotated
> @Stateless. I removed @Stateless and instead added a servlet entry in
> web.xml to route specific URL requests to it. That class is now listed as
> suffering the injection problem (it too extends this base class having
> @Resource WebServiceContext inside). I added @Stateless back on but no
> change.
>
> The only other matter worthy of mentioning is that since I now have two web
> archive projects within the parent project, I created a third to hold both
> web archives as dependencies, this one an 'uberwar'
> using org.codehaus.cargo:cargo-maven2-plugin. The default configuration
> descriptor from their web site is being used, apparently fine.
>
>
> On 19 November 2013 21:29, Romain Manni-Bucau <rm...@gmail.com>
> wrote:
>
> > Hmm, beans.xml is useless for @Resource, that sthg else i fear
> > Le 19 nov. 2013 22:27, "James Green" <ja...@gmail.com> a écrit
> :
> >
> > > Would the project with the base class also require a beans.xml file?
> It's
> > > not something covered in the examples we all see...
> > >
> > > I would expect subclasses annotated @WebService and having in the
> object
> > a
> > > field annotated @Resource to be scanned by reflection and injected.
> Just
> > > wanting to confirm my thinking that the packages with the subclasses
> > need a
> > > beans.xml declaration but nothing further for this stuff to work.
> > >
> > >
> > > On 19 November 2013 21:18, Romain Manni-Bucau <rm...@gmail.com>
> > > wrote:
> > >
> > > > No, just as prefix. Hmm, try to share something to reproduce
> otherwise
> > > > thats hard to help you :s
> > > >
> > > > Ps: is it an ear?
> > > > Le 19 nov. 2013 22:16, "James Green" <ja...@gmail.com> a
> > écrit
> > > :
> > > >
> > > > > I renamed to mycompany-jaxws-core and it made no difference. Unless
> > you
> > > > are
> > > > > suggesting anything with jaxws in it's name will be excluded..?
> > > > >
> > > > >
> > > > > On 19 November 2013 21:02, Romain Manni-Bucau <
> rmannibucau@gmail.com
> > >
> > > > > wrote:
> > > > >
> > > > > > Try to rename it foo.jar, we exclude few jars from scanning using
> > > > > > prefixes...jaxws can be one (i dont recall atm to be fully
> honest)
> > > > > > Le 19 nov. 2013 21:47, "James Green" <ja...@gmail.com>
> a
> > > > écrit
> > > > > :
> > > > > >
> > > > > > > The name is something like jaxws-core. Why would you think it
> is
> > > > being
> > > > > > > excluded?
> > > > > > >
> > > > > > > It's a commercial project I am afraid so best I can do is try a
> > > test
> > > > > case
> > > > > > > if I get desperate.
> > > > > > >
> > > > > > > I could collapse the code back into a single war archive again
> > but
> > > > I'd
> > > > > be
> > > > > > > disappointed :(.
> > > > > > >
> > > > > > >
> > > > > > > On 19 November 2013 19:18, Romain Manni-Bucau <
> > > rmannibucau@gmail.com
> > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hi
> > > > > > > >
> > > > > > > > What s the jar name (isnt it an exclusion?)? Can you
> reproduce
> > it
> > > > and
> > > > > > > share
> > > > > > > > a project?
> > > > > > > > Le 19 nov. 2013 20:02, "James Green" <
> james.mk.green@gmail.com
> > >
> > > a
> > > > > > écrit
> > > > > > > :
> > > > > > > >
> > > > > > > > > I just moved the setter of the WebServiceContext (with
> > > @Resource)
> > > > > to
> > > > > > > the
> > > > > > > > > @WebService implementation classes in the dependency .war
> > > package
> > > > > > and I
> > > > > > > > > still get the error.
> > > > > > > > >
> > > > > > > > > I was hoping the container took issue with the annotation
> > being
> > > > in
> > > > > a
> > > > > > > > class
> > > > > > > > > within a .jar library but whatever the problem is, it isn't
> > > that.
> > > > > > > > >
> > > > > > > > > Suggestions welcomed.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On 19 November 2013 17:38, James Green <
> > > james.mk.green@gmail.com
> > > > >
> > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > This is causing an NPE accessing a WebServiceContext
> > > annotated
> > > > > with
> > > > > > > > > > @Resource.
> > > > > > > > > >
> > > > > > > > > > To detail, I've been refactoring my Maven project into
> > > > > sub-projects
> > > > > > > to
> > > > > > > > > > facilitate versioning of interfaces. Previously the
> entire
> > > web
> > > > > > > > interface
> > > > > > > > > > was held in a single war file project and it all worked.
> > > > > > > > > >
> > > > > > > > > > The above field is in a base class I use for SOAP
> services.
> > > The
> > > > > > base
> > > > > > > > > class
> > > > > > > > > > was moved into a jar project and depended upon by two
> > others
> > > -
> > > > > both
> > > > > > > war
> > > > > > > > > > packaging.
> > > > > > > > > >
> > > > > > > > > > In each case I have a beans.xml file which I thought
> might
> > > fix
> > > > > it.
> > > > > > > The
> > > > > > > > > > exact message as output by the latest TomEE-Plus
> > > 1.6-SNAPSHOT:
> > > > > > > > > >
> > > > > > > > > > WARNING: Injection data not found in JNDI context:
> > > > > > > > > >
> > > jndiName='comp/env/com.mycompany.saas.jaxws.SoapBase/context',
> > > > > > > > > > target=com.mycompany.saas.jaxws.SoapBase/context
> > > > > > > > > >
> > > > > > > > > > I have also tried making a getter and setter for the
> field
> > > and
> > > > > > > placing
> > > > > > > > > the
> > > > > > > > > > @Resource on the setter to no effect.
> > > > > > > > > >
> > > > > > > > > > Any ideas?
> > > > > > > > > >
> > > > > > > > > > Thanks,
> > > > > > > > > >
> > > > > > > > > > James
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: WARNING: Injection data not found in JNDI context
Posted by James Green <ja...@gmail.com>.
I am able to trigger this by adding the webservice class to web.xml.
I took an existing (working) WebService class that was annotated
@Stateless. I removed @Stateless and instead added a servlet entry in
web.xml to route specific URL requests to it. That class is now listed as
suffering the injection problem (it too extends this base class having
@Resource WebServiceContext inside). I added @Stateless back on but no
change.
The only other matter worthy of mentioning is that since I now have two web
archive projects within the parent project, I created a third to hold both
web archives as dependencies, this one an 'uberwar'
using org.codehaus.cargo:cargo-maven2-plugin. The default configuration
descriptor from their web site is being used, apparently fine.
On 19 November 2013 21:29, Romain Manni-Bucau <rm...@gmail.com> wrote:
> Hmm, beans.xml is useless for @Resource, that sthg else i fear
> Le 19 nov. 2013 22:27, "James Green" <ja...@gmail.com> a écrit :
>
> > Would the project with the base class also require a beans.xml file? It's
> > not something covered in the examples we all see...
> >
> > I would expect subclasses annotated @WebService and having in the object
> a
> > field annotated @Resource to be scanned by reflection and injected. Just
> > wanting to confirm my thinking that the packages with the subclasses
> need a
> > beans.xml declaration but nothing further for this stuff to work.
> >
> >
> > On 19 November 2013 21:18, Romain Manni-Bucau <rm...@gmail.com>
> > wrote:
> >
> > > No, just as prefix. Hmm, try to share something to reproduce otherwise
> > > thats hard to help you :s
> > >
> > > Ps: is it an ear?
> > > Le 19 nov. 2013 22:16, "James Green" <ja...@gmail.com> a
> écrit
> > :
> > >
> > > > I renamed to mycompany-jaxws-core and it made no difference. Unless
> you
> > > are
> > > > suggesting anything with jaxws in it's name will be excluded..?
> > > >
> > > >
> > > > On 19 November 2013 21:02, Romain Manni-Bucau <rmannibucau@gmail.com
> >
> > > > wrote:
> > > >
> > > > > Try to rename it foo.jar, we exclude few jars from scanning using
> > > > > prefixes...jaxws can be one (i dont recall atm to be fully honest)
> > > > > Le 19 nov. 2013 21:47, "James Green" <ja...@gmail.com> a
> > > écrit
> > > > :
> > > > >
> > > > > > The name is something like jaxws-core. Why would you think it is
> > > being
> > > > > > excluded?
> > > > > >
> > > > > > It's a commercial project I am afraid so best I can do is try a
> > test
> > > > case
> > > > > > if I get desperate.
> > > > > >
> > > > > > I could collapse the code back into a single war archive again
> but
> > > I'd
> > > > be
> > > > > > disappointed :(.
> > > > > >
> > > > > >
> > > > > > On 19 November 2013 19:18, Romain Manni-Bucau <
> > rmannibucau@gmail.com
> > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Hi
> > > > > > >
> > > > > > > What s the jar name (isnt it an exclusion?)? Can you reproduce
> it
> > > and
> > > > > > share
> > > > > > > a project?
> > > > > > > Le 19 nov. 2013 20:02, "James Green" <james.mk.green@gmail.com
> >
> > a
> > > > > écrit
> > > > > > :
> > > > > > >
> > > > > > > > I just moved the setter of the WebServiceContext (with
> > @Resource)
> > > > to
> > > > > > the
> > > > > > > > @WebService implementation classes in the dependency .war
> > package
> > > > > and I
> > > > > > > > still get the error.
> > > > > > > >
> > > > > > > > I was hoping the container took issue with the annotation
> being
> > > in
> > > > a
> > > > > > > class
> > > > > > > > within a .jar library but whatever the problem is, it isn't
> > that.
> > > > > > > >
> > > > > > > > Suggestions welcomed.
> > > > > > > >
> > > > > > > >
> > > > > > > > On 19 November 2013 17:38, James Green <
> > james.mk.green@gmail.com
> > > >
> > > > > > wrote:
> > > > > > > >
> > > > > > > > > This is causing an NPE accessing a WebServiceContext
> > annotated
> > > > with
> > > > > > > > > @Resource.
> > > > > > > > >
> > > > > > > > > To detail, I've been refactoring my Maven project into
> > > > sub-projects
> > > > > > to
> > > > > > > > > facilitate versioning of interfaces. Previously the entire
> > web
> > > > > > > interface
> > > > > > > > > was held in a single war file project and it all worked.
> > > > > > > > >
> > > > > > > > > The above field is in a base class I use for SOAP services.
> > The
> > > > > base
> > > > > > > > class
> > > > > > > > > was moved into a jar project and depended upon by two
> others
> > -
> > > > both
> > > > > > war
> > > > > > > > > packaging.
> > > > > > > > >
> > > > > > > > > In each case I have a beans.xml file which I thought might
> > fix
> > > > it.
> > > > > > The
> > > > > > > > > exact message as output by the latest TomEE-Plus
> > 1.6-SNAPSHOT:
> > > > > > > > >
> > > > > > > > > WARNING: Injection data not found in JNDI context:
> > > > > > > > >
> > jndiName='comp/env/com.mycompany.saas.jaxws.SoapBase/context',
> > > > > > > > > target=com.mycompany.saas.jaxws.SoapBase/context
> > > > > > > > >
> > > > > > > > > I have also tried making a getter and setter for the field
> > and
> > > > > > placing
> > > > > > > > the
> > > > > > > > > @Resource on the setter to no effect.
> > > > > > > > >
> > > > > > > > > Any ideas?
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > >
> > > > > > > > > James
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: WARNING: Injection data not found in JNDI context
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hmm, beans.xml is useless for @Resource, that sthg else i fear
Le 19 nov. 2013 22:27, "James Green" <ja...@gmail.com> a écrit :
> Would the project with the base class also require a beans.xml file? It's
> not something covered in the examples we all see...
>
> I would expect subclasses annotated @WebService and having in the object a
> field annotated @Resource to be scanned by reflection and injected. Just
> wanting to confirm my thinking that the packages with the subclasses need a
> beans.xml declaration but nothing further for this stuff to work.
>
>
> On 19 November 2013 21:18, Romain Manni-Bucau <rm...@gmail.com>
> wrote:
>
> > No, just as prefix. Hmm, try to share something to reproduce otherwise
> > thats hard to help you :s
> >
> > Ps: is it an ear?
> > Le 19 nov. 2013 22:16, "James Green" <ja...@gmail.com> a écrit
> :
> >
> > > I renamed to mycompany-jaxws-core and it made no difference. Unless you
> > are
> > > suggesting anything with jaxws in it's name will be excluded..?
> > >
> > >
> > > On 19 November 2013 21:02, Romain Manni-Bucau <rm...@gmail.com>
> > > wrote:
> > >
> > > > Try to rename it foo.jar, we exclude few jars from scanning using
> > > > prefixes...jaxws can be one (i dont recall atm to be fully honest)
> > > > Le 19 nov. 2013 21:47, "James Green" <ja...@gmail.com> a
> > écrit
> > > :
> > > >
> > > > > The name is something like jaxws-core. Why would you think it is
> > being
> > > > > excluded?
> > > > >
> > > > > It's a commercial project I am afraid so best I can do is try a
> test
> > > case
> > > > > if I get desperate.
> > > > >
> > > > > I could collapse the code back into a single war archive again but
> > I'd
> > > be
> > > > > disappointed :(.
> > > > >
> > > > >
> > > > > On 19 November 2013 19:18, Romain Manni-Bucau <
> rmannibucau@gmail.com
> > >
> > > > > wrote:
> > > > >
> > > > > > Hi
> > > > > >
> > > > > > What s the jar name (isnt it an exclusion?)? Can you reproduce it
> > and
> > > > > share
> > > > > > a project?
> > > > > > Le 19 nov. 2013 20:02, "James Green" <ja...@gmail.com>
> a
> > > > écrit
> > > > > :
> > > > > >
> > > > > > > I just moved the setter of the WebServiceContext (with
> @Resource)
> > > to
> > > > > the
> > > > > > > @WebService implementation classes in the dependency .war
> package
> > > > and I
> > > > > > > still get the error.
> > > > > > >
> > > > > > > I was hoping the container took issue with the annotation being
> > in
> > > a
> > > > > > class
> > > > > > > within a .jar library but whatever the problem is, it isn't
> that.
> > > > > > >
> > > > > > > Suggestions welcomed.
> > > > > > >
> > > > > > >
> > > > > > > On 19 November 2013 17:38, James Green <
> james.mk.green@gmail.com
> > >
> > > > > wrote:
> > > > > > >
> > > > > > > > This is causing an NPE accessing a WebServiceContext
> annotated
> > > with
> > > > > > > > @Resource.
> > > > > > > >
> > > > > > > > To detail, I've been refactoring my Maven project into
> > > sub-projects
> > > > > to
> > > > > > > > facilitate versioning of interfaces. Previously the entire
> web
> > > > > > interface
> > > > > > > > was held in a single war file project and it all worked.
> > > > > > > >
> > > > > > > > The above field is in a base class I use for SOAP services.
> The
> > > > base
> > > > > > > class
> > > > > > > > was moved into a jar project and depended upon by two others
> -
> > > both
> > > > > war
> > > > > > > > packaging.
> > > > > > > >
> > > > > > > > In each case I have a beans.xml file which I thought might
> fix
> > > it.
> > > > > The
> > > > > > > > exact message as output by the latest TomEE-Plus
> 1.6-SNAPSHOT:
> > > > > > > >
> > > > > > > > WARNING: Injection data not found in JNDI context:
> > > > > > > >
> jndiName='comp/env/com.mycompany.saas.jaxws.SoapBase/context',
> > > > > > > > target=com.mycompany.saas.jaxws.SoapBase/context
> > > > > > > >
> > > > > > > > I have also tried making a getter and setter for the field
> and
> > > > > placing
> > > > > > > the
> > > > > > > > @Resource on the setter to no effect.
> > > > > > > >
> > > > > > > > Any ideas?
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > >
> > > > > > > > James
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: WARNING: Injection data not found in JNDI context
Posted by James Green <ja...@gmail.com>.
Would the project with the base class also require a beans.xml file? It's
not something covered in the examples we all see...
I would expect subclasses annotated @WebService and having in the object a
field annotated @Resource to be scanned by reflection and injected. Just
wanting to confirm my thinking that the packages with the subclasses need a
beans.xml declaration but nothing further for this stuff to work.
On 19 November 2013 21:18, Romain Manni-Bucau <rm...@gmail.com> wrote:
> No, just as prefix. Hmm, try to share something to reproduce otherwise
> thats hard to help you :s
>
> Ps: is it an ear?
> Le 19 nov. 2013 22:16, "James Green" <ja...@gmail.com> a écrit :
>
> > I renamed to mycompany-jaxws-core and it made no difference. Unless you
> are
> > suggesting anything with jaxws in it's name will be excluded..?
> >
> >
> > On 19 November 2013 21:02, Romain Manni-Bucau <rm...@gmail.com>
> > wrote:
> >
> > > Try to rename it foo.jar, we exclude few jars from scanning using
> > > prefixes...jaxws can be one (i dont recall atm to be fully honest)
> > > Le 19 nov. 2013 21:47, "James Green" <ja...@gmail.com> a
> écrit
> > :
> > >
> > > > The name is something like jaxws-core. Why would you think it is
> being
> > > > excluded?
> > > >
> > > > It's a commercial project I am afraid so best I can do is try a test
> > case
> > > > if I get desperate.
> > > >
> > > > I could collapse the code back into a single war archive again but
> I'd
> > be
> > > > disappointed :(.
> > > >
> > > >
> > > > On 19 November 2013 19:18, Romain Manni-Bucau <rmannibucau@gmail.com
> >
> > > > wrote:
> > > >
> > > > > Hi
> > > > >
> > > > > What s the jar name (isnt it an exclusion?)? Can you reproduce it
> and
> > > > share
> > > > > a project?
> > > > > Le 19 nov. 2013 20:02, "James Green" <ja...@gmail.com> a
> > > écrit
> > > > :
> > > > >
> > > > > > I just moved the setter of the WebServiceContext (with @Resource)
> > to
> > > > the
> > > > > > @WebService implementation classes in the dependency .war package
> > > and I
> > > > > > still get the error.
> > > > > >
> > > > > > I was hoping the container took issue with the annotation being
> in
> > a
> > > > > class
> > > > > > within a .jar library but whatever the problem is, it isn't that.
> > > > > >
> > > > > > Suggestions welcomed.
> > > > > >
> > > > > >
> > > > > > On 19 November 2013 17:38, James Green <james.mk.green@gmail.com
> >
> > > > wrote:
> > > > > >
> > > > > > > This is causing an NPE accessing a WebServiceContext annotated
> > with
> > > > > > > @Resource.
> > > > > > >
> > > > > > > To detail, I've been refactoring my Maven project into
> > sub-projects
> > > > to
> > > > > > > facilitate versioning of interfaces. Previously the entire web
> > > > > interface
> > > > > > > was held in a single war file project and it all worked.
> > > > > > >
> > > > > > > The above field is in a base class I use for SOAP services. The
> > > base
> > > > > > class
> > > > > > > was moved into a jar project and depended upon by two others -
> > both
> > > > war
> > > > > > > packaging.
> > > > > > >
> > > > > > > In each case I have a beans.xml file which I thought might fix
> > it.
> > > > The
> > > > > > > exact message as output by the latest TomEE-Plus 1.6-SNAPSHOT:
> > > > > > >
> > > > > > > WARNING: Injection data not found in JNDI context:
> > > > > > > jndiName='comp/env/com.mycompany.saas.jaxws.SoapBase/context',
> > > > > > > target=com.mycompany.saas.jaxws.SoapBase/context
> > > > > > >
> > > > > > > I have also tried making a getter and setter for the field and
> > > > placing
> > > > > > the
> > > > > > > @Resource on the setter to no effect.
> > > > > > >
> > > > > > > Any ideas?
> > > > > > >
> > > > > > > Thanks,
> > > > > > >
> > > > > > > James
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: WARNING: Injection data not found in JNDI context
Posted by Romain Manni-Bucau <rm...@gmail.com>.
No, just as prefix. Hmm, try to share something to reproduce otherwise
thats hard to help you :s
Ps: is it an ear?
Le 19 nov. 2013 22:16, "James Green" <ja...@gmail.com> a écrit :
> I renamed to mycompany-jaxws-core and it made no difference. Unless you are
> suggesting anything with jaxws in it's name will be excluded..?
>
>
> On 19 November 2013 21:02, Romain Manni-Bucau <rm...@gmail.com>
> wrote:
>
> > Try to rename it foo.jar, we exclude few jars from scanning using
> > prefixes...jaxws can be one (i dont recall atm to be fully honest)
> > Le 19 nov. 2013 21:47, "James Green" <ja...@gmail.com> a écrit
> :
> >
> > > The name is something like jaxws-core. Why would you think it is being
> > > excluded?
> > >
> > > It's a commercial project I am afraid so best I can do is try a test
> case
> > > if I get desperate.
> > >
> > > I could collapse the code back into a single war archive again but I'd
> be
> > > disappointed :(.
> > >
> > >
> > > On 19 November 2013 19:18, Romain Manni-Bucau <rm...@gmail.com>
> > > wrote:
> > >
> > > > Hi
> > > >
> > > > What s the jar name (isnt it an exclusion?)? Can you reproduce it and
> > > share
> > > > a project?
> > > > Le 19 nov. 2013 20:02, "James Green" <ja...@gmail.com> a
> > écrit
> > > :
> > > >
> > > > > I just moved the setter of the WebServiceContext (with @Resource)
> to
> > > the
> > > > > @WebService implementation classes in the dependency .war package
> > and I
> > > > > still get the error.
> > > > >
> > > > > I was hoping the container took issue with the annotation being in
> a
> > > > class
> > > > > within a .jar library but whatever the problem is, it isn't that.
> > > > >
> > > > > Suggestions welcomed.
> > > > >
> > > > >
> > > > > On 19 November 2013 17:38, James Green <ja...@gmail.com>
> > > wrote:
> > > > >
> > > > > > This is causing an NPE accessing a WebServiceContext annotated
> with
> > > > > > @Resource.
> > > > > >
> > > > > > To detail, I've been refactoring my Maven project into
> sub-projects
> > > to
> > > > > > facilitate versioning of interfaces. Previously the entire web
> > > > interface
> > > > > > was held in a single war file project and it all worked.
> > > > > >
> > > > > > The above field is in a base class I use for SOAP services. The
> > base
> > > > > class
> > > > > > was moved into a jar project and depended upon by two others -
> both
> > > war
> > > > > > packaging.
> > > > > >
> > > > > > In each case I have a beans.xml file which I thought might fix
> it.
> > > The
> > > > > > exact message as output by the latest TomEE-Plus 1.6-SNAPSHOT:
> > > > > >
> > > > > > WARNING: Injection data not found in JNDI context:
> > > > > > jndiName='comp/env/com.mycompany.saas.jaxws.SoapBase/context',
> > > > > > target=com.mycompany.saas.jaxws.SoapBase/context
> > > > > >
> > > > > > I have also tried making a getter and setter for the field and
> > > placing
> > > > > the
> > > > > > @Resource on the setter to no effect.
> > > > > >
> > > > > > Any ideas?
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > James
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: WARNING: Injection data not found in JNDI context
Posted by James Green <ja...@gmail.com>.
I renamed to mycompany-jaxws-core and it made no difference. Unless you are
suggesting anything with jaxws in it's name will be excluded..?
On 19 November 2013 21:02, Romain Manni-Bucau <rm...@gmail.com> wrote:
> Try to rename it foo.jar, we exclude few jars from scanning using
> prefixes...jaxws can be one (i dont recall atm to be fully honest)
> Le 19 nov. 2013 21:47, "James Green" <ja...@gmail.com> a écrit :
>
> > The name is something like jaxws-core. Why would you think it is being
> > excluded?
> >
> > It's a commercial project I am afraid so best I can do is try a test case
> > if I get desperate.
> >
> > I could collapse the code back into a single war archive again but I'd be
> > disappointed :(.
> >
> >
> > On 19 November 2013 19:18, Romain Manni-Bucau <rm...@gmail.com>
> > wrote:
> >
> > > Hi
> > >
> > > What s the jar name (isnt it an exclusion?)? Can you reproduce it and
> > share
> > > a project?
> > > Le 19 nov. 2013 20:02, "James Green" <ja...@gmail.com> a
> écrit
> > :
> > >
> > > > I just moved the setter of the WebServiceContext (with @Resource) to
> > the
> > > > @WebService implementation classes in the dependency .war package
> and I
> > > > still get the error.
> > > >
> > > > I was hoping the container took issue with the annotation being in a
> > > class
> > > > within a .jar library but whatever the problem is, it isn't that.
> > > >
> > > > Suggestions welcomed.
> > > >
> > > >
> > > > On 19 November 2013 17:38, James Green <ja...@gmail.com>
> > wrote:
> > > >
> > > > > This is causing an NPE accessing a WebServiceContext annotated with
> > > > > @Resource.
> > > > >
> > > > > To detail, I've been refactoring my Maven project into sub-projects
> > to
> > > > > facilitate versioning of interfaces. Previously the entire web
> > > interface
> > > > > was held in a single war file project and it all worked.
> > > > >
> > > > > The above field is in a base class I use for SOAP services. The
> base
> > > > class
> > > > > was moved into a jar project and depended upon by two others - both
> > war
> > > > > packaging.
> > > > >
> > > > > In each case I have a beans.xml file which I thought might fix it.
> > The
> > > > > exact message as output by the latest TomEE-Plus 1.6-SNAPSHOT:
> > > > >
> > > > > WARNING: Injection data not found in JNDI context:
> > > > > jndiName='comp/env/com.mycompany.saas.jaxws.SoapBase/context',
> > > > > target=com.mycompany.saas.jaxws.SoapBase/context
> > > > >
> > > > > I have also tried making a getter and setter for the field and
> > placing
> > > > the
> > > > > @Resource on the setter to no effect.
> > > > >
> > > > > Any ideas?
> > > > >
> > > > > Thanks,
> > > > >
> > > > > James
> > > > >
> > > > >
> > > >
> > >
> >
>
Re: WARNING: Injection data not found in JNDI context
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Try to rename it foo.jar, we exclude few jars from scanning using
prefixes...jaxws can be one (i dont recall atm to be fully honest)
Le 19 nov. 2013 21:47, "James Green" <ja...@gmail.com> a écrit :
> The name is something like jaxws-core. Why would you think it is being
> excluded?
>
> It's a commercial project I am afraid so best I can do is try a test case
> if I get desperate.
>
> I could collapse the code back into a single war archive again but I'd be
> disappointed :(.
>
>
> On 19 November 2013 19:18, Romain Manni-Bucau <rm...@gmail.com>
> wrote:
>
> > Hi
> >
> > What s the jar name (isnt it an exclusion?)? Can you reproduce it and
> share
> > a project?
> > Le 19 nov. 2013 20:02, "James Green" <ja...@gmail.com> a écrit
> :
> >
> > > I just moved the setter of the WebServiceContext (with @Resource) to
> the
> > > @WebService implementation classes in the dependency .war package and I
> > > still get the error.
> > >
> > > I was hoping the container took issue with the annotation being in a
> > class
> > > within a .jar library but whatever the problem is, it isn't that.
> > >
> > > Suggestions welcomed.
> > >
> > >
> > > On 19 November 2013 17:38, James Green <ja...@gmail.com>
> wrote:
> > >
> > > > This is causing an NPE accessing a WebServiceContext annotated with
> > > > @Resource.
> > > >
> > > > To detail, I've been refactoring my Maven project into sub-projects
> to
> > > > facilitate versioning of interfaces. Previously the entire web
> > interface
> > > > was held in a single war file project and it all worked.
> > > >
> > > > The above field is in a base class I use for SOAP services. The base
> > > class
> > > > was moved into a jar project and depended upon by two others - both
> war
> > > > packaging.
> > > >
> > > > In each case I have a beans.xml file which I thought might fix it.
> The
> > > > exact message as output by the latest TomEE-Plus 1.6-SNAPSHOT:
> > > >
> > > > WARNING: Injection data not found in JNDI context:
> > > > jndiName='comp/env/com.mycompany.saas.jaxws.SoapBase/context',
> > > > target=com.mycompany.saas.jaxws.SoapBase/context
> > > >
> > > > I have also tried making a getter and setter for the field and
> placing
> > > the
> > > > @Resource on the setter to no effect.
> > > >
> > > > Any ideas?
> > > >
> > > > Thanks,
> > > >
> > > > James
> > > >
> > > >
> > >
> >
>
Re: WARNING: Injection data not found in JNDI context
Posted by James Green <ja...@gmail.com>.
The name is something like jaxws-core. Why would you think it is being
excluded?
It's a commercial project I am afraid so best I can do is try a test case
if I get desperate.
I could collapse the code back into a single war archive again but I'd be
disappointed :(.
On 19 November 2013 19:18, Romain Manni-Bucau <rm...@gmail.com> wrote:
> Hi
>
> What s the jar name (isnt it an exclusion?)? Can you reproduce it and share
> a project?
> Le 19 nov. 2013 20:02, "James Green" <ja...@gmail.com> a écrit :
>
> > I just moved the setter of the WebServiceContext (with @Resource) to the
> > @WebService implementation classes in the dependency .war package and I
> > still get the error.
> >
> > I was hoping the container took issue with the annotation being in a
> class
> > within a .jar library but whatever the problem is, it isn't that.
> >
> > Suggestions welcomed.
> >
> >
> > On 19 November 2013 17:38, James Green <ja...@gmail.com> wrote:
> >
> > > This is causing an NPE accessing a WebServiceContext annotated with
> > > @Resource.
> > >
> > > To detail, I've been refactoring my Maven project into sub-projects to
> > > facilitate versioning of interfaces. Previously the entire web
> interface
> > > was held in a single war file project and it all worked.
> > >
> > > The above field is in a base class I use for SOAP services. The base
> > class
> > > was moved into a jar project and depended upon by two others - both war
> > > packaging.
> > >
> > > In each case I have a beans.xml file which I thought might fix it. The
> > > exact message as output by the latest TomEE-Plus 1.6-SNAPSHOT:
> > >
> > > WARNING: Injection data not found in JNDI context:
> > > jndiName='comp/env/com.mycompany.saas.jaxws.SoapBase/context',
> > > target=com.mycompany.saas.jaxws.SoapBase/context
> > >
> > > I have also tried making a getter and setter for the field and placing
> > the
> > > @Resource on the setter to no effect.
> > >
> > > Any ideas?
> > >
> > > Thanks,
> > >
> > > James
> > >
> > >
> >
>
Re: WARNING: Injection data not found in JNDI context
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi
What s the jar name (isnt it an exclusion?)? Can you reproduce it and share
a project?
Le 19 nov. 2013 20:02, "James Green" <ja...@gmail.com> a écrit :
> I just moved the setter of the WebServiceContext (with @Resource) to the
> @WebService implementation classes in the dependency .war package and I
> still get the error.
>
> I was hoping the container took issue with the annotation being in a class
> within a .jar library but whatever the problem is, it isn't that.
>
> Suggestions welcomed.
>
>
> On 19 November 2013 17:38, James Green <ja...@gmail.com> wrote:
>
> > This is causing an NPE accessing a WebServiceContext annotated with
> > @Resource.
> >
> > To detail, I've been refactoring my Maven project into sub-projects to
> > facilitate versioning of interfaces. Previously the entire web interface
> > was held in a single war file project and it all worked.
> >
> > The above field is in a base class I use for SOAP services. The base
> class
> > was moved into a jar project and depended upon by two others - both war
> > packaging.
> >
> > In each case I have a beans.xml file which I thought might fix it. The
> > exact message as output by the latest TomEE-Plus 1.6-SNAPSHOT:
> >
> > WARNING: Injection data not found in JNDI context:
> > jndiName='comp/env/com.mycompany.saas.jaxws.SoapBase/context',
> > target=com.mycompany.saas.jaxws.SoapBase/context
> >
> > I have also tried making a getter and setter for the field and placing
> the
> > @Resource on the setter to no effect.
> >
> > Any ideas?
> >
> > Thanks,
> >
> > James
> >
> >
>
Re: WARNING: Injection data not found in JNDI context
Posted by James Green <ja...@gmail.com>.
I just moved the setter of the WebServiceContext (with @Resource) to the
@WebService implementation classes in the dependency .war package and I
still get the error.
I was hoping the container took issue with the annotation being in a class
within a .jar library but whatever the problem is, it isn't that.
Suggestions welcomed.
On 19 November 2013 17:38, James Green <ja...@gmail.com> wrote:
> This is causing an NPE accessing a WebServiceContext annotated with
> @Resource.
>
> To detail, I've been refactoring my Maven project into sub-projects to
> facilitate versioning of interfaces. Previously the entire web interface
> was held in a single war file project and it all worked.
>
> The above field is in a base class I use for SOAP services. The base class
> was moved into a jar project and depended upon by two others - both war
> packaging.
>
> In each case I have a beans.xml file which I thought might fix it. The
> exact message as output by the latest TomEE-Plus 1.6-SNAPSHOT:
>
> WARNING: Injection data not found in JNDI context:
> jndiName='comp/env/com.mycompany.saas.jaxws.SoapBase/context',
> target=com.mycompany.saas.jaxws.SoapBase/context
>
> I have also tried making a getter and setter for the field and placing the
> @Resource on the setter to no effect.
>
> Any ideas?
>
> Thanks,
>
> James
>
>