Re: JNDI lookup help
On Nov 13, 2007, at 12:10 PM, Casey Rayman wrote: This is great. It's working just how I expect it to with my simple test case. Now that it's working I'll try some more complicated tests. This is so cool! I can't thank you enough! No problem. Just tell everyone you know the same thing and we'll call it even ;) Strictly speaking this is probably a different request, but I'm still using a shell of an openejb-jar to specify what physical table the abstract schema. Like this: http://www.openejb.org/xml/ns/openejb-jar-2.2";> AuxGenderRO AuxGender If the table-name could get picked up from the weblogic-cmp-rdbms- jar.xml then it really would be totally seamless. Yea, getting the cmp conversion in there would be great. I've started hacking on it, but I'm not the CMP guy typically (that'd be Dain), so it'll take me a bit longer. We fully support the glassfish descriptors so people using glassfish can do what you're trying to do. We really want OpenEJB to be usable by anyone who'd like a boost in productivity regardless of who they deploy to in production. Anyway, going to copy from the glassfish conversion code and see how far I get. Our CMP container is actually a thin layer on top of JPA (big advantage to users) so conversion is actually a matter of converting the weblogic cmp beans to JPA, which is doable just a bit trickier. -David On Nov 12, 2007, at 11:19 PM, David Blevins wrote: To make sure everything is absolutely perfect, I've hacked up an example of using the weblogic descriptors. And for the first time ever, I hacked up an Ant build.xml to run the example as I know that's what you're using. You can get the example via: svn export http://svn.apache.org/repos/asf/openejb/trunk/openejb3/examples/helloworld-weblogic Then run with: ant -lib maven-ant-tasks-2.0.7.jar I've incorporated the maven-ant-tasks-2.0.7.jar AntLib just to make downloading all the dependencies and building the classpaths easier. It can be downloaded here: http://www.apache.org/dist/maven/binaries/maven-ant-tasks-2.0.7.jar Unfortunately, there was one last oversight on my part in r593658 which I posted yesterday. Hopefully the above example which shows things working end-to-end (and now runs with our build) will get you back on the fast track. Here's another binary build for non- maven usage: http://people.apache.org/~dblevins/openejb-594438 Thanks for hanging in there. This is a great feature to have, we definitely appreciate the requests. -David
Re: JNDI lookup help
This is great. It's working just how I expect it to with my simple test case. Now that it's working I'll try some more complicated tests. This is so cool! I can't thank you enough! Strictly speaking this is probably a different request, but I'm still using a shell of an openejb-jar to specify what physical table the abstract schema. Like this: http://www.openejb.org/xml/ns/openejb-jar-2.2";> AuxGenderRO AuxGender If the table-name could get picked up from the weblogic-cmp-rdbms- jar.xml then it really would be totally seamless. Casey On Nov 12, 2007, at 11:19 PM, David Blevins wrote: To make sure everything is absolutely perfect, I've hacked up an example of using the weblogic descriptors. And for the first time ever, I hacked up an Ant build.xml to run the example as I know that's what you're using. You can get the example via: svn export http://svn.apache.org/repos/asf/openejb/trunk/openejb3/examples/helloworld-weblogic Then run with: ant -lib maven-ant-tasks-2.0.7.jar I've incorporated the maven-ant-tasks-2.0.7.jar AntLib just to make downloading all the dependencies and building the classpaths easier. It can be downloaded here: http://www.apache.org/dist/maven/binaries/maven-ant-tasks-2.0.7.jar Unfortunately, there was one last oversight on my part in r593658 which I posted yesterday. Hopefully the above example which shows things working end-to-end (and now runs with our build) will get you back on the fast track. Here's another binary build for non-maven usage: http://people.apache.org/~dblevins/openejb-594438 Thanks for hanging in there. This is a great feature to have, we definitely appreciate the requests. -David
Re: JNDI lookup help
To make sure everything is absolutely perfect, I've hacked up an example of using the weblogic descriptors. And for the first time ever, I hacked up an Ant build.xml to run the example as I know that's what you're using. You can get the example via: svn export http://svn.apache.org/repos/asf/openejb/trunk/openejb3/examples/helloworld-weblogic Then run with: ant -lib maven-ant-tasks-2.0.7.jar I've incorporated the maven-ant-tasks-2.0.7.jar AntLib just to make downloading all the dependencies and building the classpaths easier. It can be downloaded here: http://www.apache.org/dist/maven/binaries/maven-ant-tasks-2.0.7.jar Unfortunately, there was one last oversight on my part in r593658 which I posted yesterday. Hopefully the above example which shows things working end-to-end (and now runs with our build) will get you back on the fast track. Here's another binary build for non-maven usage: http://people.apache.org/~dblevins/openejb-594438 Thanks for hanging in there. This is a great feature to have, we definitely appreciate the requests. -David
Re: JNDI lookup help
On Nov 9, 2007, at 2:47 PM, Casey Rayman wrote:
This fixed the error. One hopefully last question for a while: The
bean get's deployed, but it is still being deployed by the
{deploymentId}{interfaceType.annotationName} format. Do I need to
force openejb.jndiname.format to something other than the default so
it takes the value from the weblogic config file?
Nope, the new per/ejb jndi name feature wasn't getting picked up quite
right. Added some better unit tests and fixed it up. This should do
the trick:
http://people.apache.org/~dblevins/openejb-594005
-David
Casey
On Nov 9, 2007, at 4:09 PM, David Blevins wrote:
On Nov 9, 2007, at 1:01 PM, Casey Rayman wrote:
Unfortunately my Weblogic experience is clearly boxed in at
version 7, and I wouldn't say that my experience runs real deep
there either. I've only been tinkering with this application a
few months now.
No worries. I think i've figured it out. From the docs seems like
reference-descriptor was the only deprecated and removed element.
It also seems like it was just a wrapper element for the various
resource-description, resource-env-description, ejb-reference-
description, etc which are still there -- just no containing
'reference-descriptor' tag.
So I've added all the necessary bits and it should work now:
http://people.apache.org/~dblevins/openejb-593658/
Give the above binary a try and let's cross our fingers :) Let me
know how it goes.
-David
Re: JNDI lookup help
This fixed the error. One hopefully last question for a while: The
bean get's deployed, but it is still being deployed by the
{deploymentId}{interfaceType.annotationName} format. Do I need to
force openejb.jndiname.format to something other than the default so
it takes the value from the weblogic config file?
Casey
On Nov 9, 2007, at 4:09 PM, David Blevins wrote:
On Nov 9, 2007, at 1:01 PM, Casey Rayman wrote:
Unfortunately my Weblogic experience is clearly boxed in at version
7, and I wouldn't say that my experience runs real deep there
either. I've only been tinkering with this application a few
months now.
No worries. I think i've figured it out. From the docs seems like
reference-descriptor was the only deprecated and removed element.
It also seems like it was just a wrapper element for the various
resource-description, resource-env-description, ejb-reference-
description, etc which are still there -- just no containing
'reference-descriptor' tag.
So I've added all the necessary bits and it should work now:
http://people.apache.org/~dblevins/openejb-593658/
Give the above binary a try and let's cross our fingers :) Let me
know how it goes.
-David
Re: JNDI lookup help
On Nov 9, 2007, at 1:01 PM, Casey Rayman wrote: Unfortunately my Weblogic experience is clearly boxed in at version 7, and I wouldn't say that my experience runs real deep there either. I've only been tinkering with this application a few months now. No worries. I think i've figured it out. From the docs seems like reference-descriptor was the only deprecated and removed element. It also seems like it was just a wrapper element for the various resource- description, resource-env-description, ejb-reference-description, etc which are still there -- just no containing 'reference-descriptor' tag. So I've added all the necessary bits and it should work now: http://people.apache.org/~dblevins/openejb-593658/ Give the above binary a try and let's cross our fingers :) Let me know how it goes. -David
Re: JNDI lookup help
On Nov 9, 2007, at 1:01 PM, Casey Rayman wrote: Unfortunately my Weblogic experience is clearly boxed in at version 7, and I wouldn't say that my experience runs real deep there either. I've only been tinkering with this application a few months now. No worries. I think i've figured it out. From the docs seems like reference-descriptor was the only deprecated and removed element. It also seems like it was just a wrapper element for the various resource- description, resource-env-description, ejb-reference-description, etc which are still there -- just no containing 'reference-descriptor' tag. So I've added all the necessary bits and it should work now: http://people.apache.org/~dblevins/openejb-593658/ Give the above binary a try and let's cross our fingers :) Let me know how it goes. -David
Re: JNDI lookup help
Unfortunately my Weblogic experience is clearly boxed in at version 7,
and I wouldn't say that my experience runs real deep there either.
I've only been tinkering with this application a few months now.
Casey
On Nov 9, 2007, at 2:50 PM, David Blevins wrote:
Looks like reference-descriptor is an element that was cut out of
the schema somewhere along the line. Do you know if there is a more
current element that replaces this one? We could add the old
element to our jaxb tree then move the data over into the right
place of the new tree.
I suppose I should pull down the v7 descriptors and generate a
sample xml doc with all the elements to see what else might have
disappeared between then and the v9 descriptors.
-David
On Nov 8, 2007, at 1:41 PM, Casey Rayman wrote:
We use Ant here. I'll download a copy of Maven to see if I can't
get a little more self sufficient with my own builds and perhaps
even contribute.
I've been busy this week with production problems, but I gave it a
quick try and this is the error I got so far. I'll see if I can't
dig into it a bit further this evening. It's probably something
I'm doing wrong though.
[severity=ERROR,message=unexpected element (uri:"http://www.bea.com/ns/weblogic/90
", local:"reference-descriptor"). Expected elements are <{http://www.bea.com/ns/weblogic/90
}resource-description>,<{http://www.bea.com/ns/weblogic/90}network-
access-point>,<{http://www.bea.com/ns/weblogic/90}entity-
descriptor>,<{http://www.bea.com/ns/weblogic/90}enable-call-by-
reference>,<{http://www.bea.com/ns/weblogic/90}create-as-principal-
name>,<{http://www.bea.com/ns/weblogic/90}stateful-session-
descriptor>,<{http://www.bea.com/ns/weblogic/90}local-jndi-name>,<{http://www.bea.com/ns/weblogic/90
}ejb-name>,<{http://www.bea.com/ns/weblogic/90}dispatch-policy>,<{http://www.bea.com/ns/weblogic/90
}message-driven-descriptor>,<{http://www.bea.com/ns/weblogic/
90}clients-on-same-server>,<{http://www.bea.com/ns/weblogic/90}run-
as-principal-name>,<{http://www.bea.com/ns/weblogic/90}iiop-
security-descriptor>,<{http://www.bea.com/ns/weblogic/90}jndi-
name>,<{http://www.bea.com/ns/weblogic/90}service-reference-
description>,<{http://www.bea.com/ns/weblogic/90}ejb-reference-
description>,<{http://www.bea.com/ns/weblogic/90}remove-as-
principal-name>,<{http://www.bea.com/ns/weblogic/90}passivate-as-
principal-name>,<{http://www.bea.com/ns/weblogic/90}resource-env-
description>,<{http://www.bea.com/ns/weblogic/90}transaction-
descriptor>,<{http://www.bea.com/ns/weblogic/90}remote-client-
timeout>,<{http://www.bea.com/ns/weblogic/90}stateless-session-
descriptor
>,locator=[node=null,object=null,url=null,line=11,col=29,offset=-1]]
javax.xml.bind.UnmarshalException: unexpected element (uri:"http://www.bea.com/ns/weblogic/90
", local:"reference-descriptor"). Expected elements are <{http://www.bea.com/ns/weblogic/90
}resource-description>,<{http://www.bea.com/ns/weblogic/90}network-
access-point>,<{http://www.bea.com/ns/weblogic/90}entity-
descriptor>,<{http://www.bea.com/ns/weblogic/90}enable-call-by-
reference>,<{http://www.bea.com/ns/weblogic/90}create-as-principal-
name>,<{http://www.bea.com/ns/weblogic/90}stateful-session-
descriptor>,<{http://www.bea.com/ns/weblogic/90}local-jndi-name>,<{http://www.bea.com/ns/weblogic/90
}ejb-name>,<{http://www.bea.com/ns/weblogic/90}dispatch-policy>,<{http://www.bea.com/ns/weblogic/90
}message-driven-descriptor>,<{http://www.bea.com/ns/weblogic/
90}clients-on-same-server>,<{http://www.bea.com/ns/weblogic/90}run-
as-principal-name>,<{http://www.bea.com/ns/weblogic/90}iiop-
security-descriptor>,<{http://www.bea.com/ns/weblogic/90}jndi-
name>,<{http://www.bea.com/ns/weblogic/90}service-reference-
description>,<{http://www.bea.com/ns/weblogic/90}ejb-reference-
description>,<{http://www.bea.com/ns/weblogic/90}remove-as-
principal-name>,<{http://www.bea.com/ns/weblogic/90}passivate-as-
principal-name>,<{http://www.bea.com/ns/weblogic/90}resource-env-
description>,<{http://www.bea.com/ns/weblogic/90}transaction-
descriptor>,<{http://www.bea.com/ns/weblogic/90}remote-client-
timeout>,<{http://www.bea.com/ns/weblogic/90}stateless-session-
descriptor>
at
com
.sun
.xml
.bind
.v2
.runtime
.unmarshaller
.UnmarshallingContext.handleEvent(UnmarshallingContext.java:523)
at
com
.sun
.xml.bind.v2.runtime.unmarshaller.Loader.reportError(Loader.java:199)
at
com
.sun
.xml.bind.v2.runtime.unmarshaller.Loader.reportError(Loader.java:194)
at
com
.sun
.xml
.bind
.v2
.runtime
.unmarshaller.Loader.reportUnexpectedChildElement(Loader.java:71)
at
com
.sun
.xml.bind.v2.runtime.unmarshaller.Loader.childElement(Loader.java:65)
at
com
.sun
.xml
.bind
.v2
.runtime
.unmarshaller.StructureLoader.childElement(StructureLoader.java:209)
at
com
.sun
.xml
.bind
.v2
.runtime
.unmarshaller
.UnmarshallingContext._startElement(UnmarshallingContext.java:366)
at
com
.sun
.xml
Re: JNDI lookup help
Looks like reference-descriptor is an element that was cut out of the
schema somewhere along the line. Do you know if there is a more
current element that replaces this one? We could add the old element
to our jaxb tree then move the data over into the right place of the
new tree.
I suppose I should pull down the v7 descriptors and generate a sample
xml doc with all the elements to see what else might have disappeared
between then and the v9 descriptors.
-David
On Nov 8, 2007, at 1:41 PM, Casey Rayman wrote:
We use Ant here. I'll download a copy of Maven to see if I can't
get a little more self sufficient with my own builds and perhaps
even contribute.
I've been busy this week with production problems, but I gave it a
quick try and this is the error I got so far. I'll see if I can't
dig into it a bit further this evening. It's probably something I'm
doing wrong though.
[severity=ERROR,message=unexpected element (uri:"http://www.bea.com/ns/weblogic/90
", local:"reference-descriptor"). Expected elements are <{http://www.bea.com/ns/weblogic/90
}resource-description>,<{http://www.bea.com/ns/weblogic/90}network-
access-point>,<{http://www.bea.com/ns/weblogic/90}entity-
descriptor>,<{http://www.bea.com/ns/weblogic/90}enable-call-by-
reference>,<{http://www.bea.com/ns/weblogic/90}create-as-principal-
name>,<{http://www.bea.com/ns/weblogic/90}stateful-session-
descriptor>,<{http://www.bea.com/ns/weblogic/90}local-jndi-name>,<{http://www.bea.com/ns/weblogic/90
}ejb-name>,<{http://www.bea.com/ns/weblogic/90}dispatch-policy>,<{http://www.bea.com/ns/weblogic/90
}message-driven-descriptor>,<{http://www.bea.com/ns/weblogic/
90}clients-on-same-server>,<{http://www.bea.com/ns/weblogic/90}run-
as-principal-name>,<{http://www.bea.com/ns/weblogic/90}iiop-security-
descriptor>,<{http://www.bea.com/ns/weblogic/90}jndi-name>,<{http://www.bea.com/ns/weblogic/90
}service-reference-description>,<{http://www.bea.com/ns/weblogic/
90}ejb-reference-description>,<{http://www.bea.com/ns/weblogic/
90}remove-as-principal-name>,<{http://www.bea.com/ns/weblogic/
90}passivate-as-principal-name>,<{http://www.bea.com/ns/weblogic/
90}resource-env-description>,<{http://www.bea.com/ns/weblogic/
90}transaction-descriptor>,<{http://www.bea.com/ns/weblogic/
90}remote-client-timeout>,<{http://www.bea.com/ns/weblogic/
90}stateless-session-
descriptor
>,locator=[node=null,object=null,url=null,line=11,col=29,offset=-1]]
javax.xml.bind.UnmarshalException: unexpected element (uri:"http://www.bea.com/ns/weblogic/90
", local:"reference-descriptor"). Expected elements are <{http://www.bea.com/ns/weblogic/90
}resource-description>,<{http://www.bea.com/ns/weblogic/90}network-
access-point>,<{http://www.bea.com/ns/weblogic/90}entity-
descriptor>,<{http://www.bea.com/ns/weblogic/90}enable-call-by-
reference>,<{http://www.bea.com/ns/weblogic/90}create-as-principal-
name>,<{http://www.bea.com/ns/weblogic/90}stateful-session-
descriptor>,<{http://www.bea.com/ns/weblogic/90}local-jndi-name>,<{http://www.bea.com/ns/weblogic/90
}ejb-name>,<{http://www.bea.com/ns/weblogic/90}dispatch-policy>,<{http://www.bea.com/ns/weblogic/90
}message-driven-descriptor>,<{http://www.bea.com/ns/weblogic/
90}clients-on-same-server>,<{http://www.bea.com/ns/weblogic/90}run-
as-principal-name>,<{http://www.bea.com/ns/weblogic/90}iiop-security-
descriptor>,<{http://www.bea.com/ns/weblogic/90}jndi-name>,<{http://www.bea.com/ns/weblogic/90
}service-reference-description>,<{http://www.bea.com/ns/weblogic/
90}ejb-reference-description>,<{http://www.bea.com/ns/weblogic/
90}remove-as-principal-name>,<{http://www.bea.com/ns/weblogic/
90}passivate-as-principal-name>,<{http://www.bea.com/ns/weblogic/
90}resource-env-description>,<{http://www.bea.com/ns/weblogic/
90}transaction-descriptor>,<{http://www.bea.com/ns/weblogic/
90}remote-client-timeout>,<{http://www.bea.com/ns/weblogic/
90}stateless-session-descriptor>
at
com
.sun
.xml
.bind
.v2
.runtime
.unmarshaller
.UnmarshallingContext.handleEvent(UnmarshallingContext.java:523)
at
com
.sun.xml.bind.v2.runtime.unmarshaller.Loader.reportError(Loader.java:
199)
at
com
.sun.xml.bind.v2.runtime.unmarshaller.Loader.reportError(Loader.java:
194)
at
com
.sun
.xml
.bind
.v2
.runtime
.unmarshaller.Loader.reportUnexpectedChildElement(Loader.java:71)
at
com
.sun
.xml.bind.v2.runtime.unmarshaller.Loader.childElement(Loader.java:65)
at
com
.sun
.xml
.bind
.v2
.runtime
.unmarshaller.StructureLoader.childElement(StructureLoader.java:209)
at
com
.sun
.xml
.bind
.v2
.runtime
.unmarshaller
.UnmarshallingContext._startElement(UnmarshallingContext.java:366)
at
com
.sun
.xml
.bind
.v2
.runtime
.unmarshaller
.UnmarshallingContext.startElement(UnmarshallingContext.java:347)
at
com
.sun
.xml
.bind
.v2.runtime.unmarshaller.SAXConnector.startElement(SAXConnector.java:
101)
at
org.xml.sax.helpers.XMLFilterImpl.startElement(XMLFi
Re: JNDI lookup help
This looks like something I did wrong. Digging in now.
-David
On Nov 8, 2007, at 1:41 PM, Casey Rayman wrote:
We use Ant here. I'll download a copy of Maven to see if I can't
get a little more self sufficient with my own builds and perhaps
even contribute.
I've been busy this week with production problems, but I gave it a
quick try and this is the error I got so far. I'll see if I can't
dig into it a bit further this evening. It's probably something I'm
doing wrong though.
[severity=ERROR,message=unexpected element (uri:"http://www.bea.com/ns/weblogic/90
", local:"reference-descriptor"). Expected elements are <{http://www.bea.com/ns/weblogic/90
}resource-description>,<{http://www.bea.com/ns/weblogic/90}network-
access-point>,<{http://www.bea.com/ns/weblogic/90}entity-
descriptor>,<{http://www.bea.com/ns/weblogic/90}enable-call-by-
reference>,<{http://www.bea.com/ns/weblogic/90}create-as-principal-
name>,<{http://www.bea.com/ns/weblogic/90}stateful-session-
descriptor>,<{http://www.bea.com/ns/weblogic/90}local-jndi-name>,<{http://www.bea.com/ns/weblogic/90
}ejb-name>,<{http://www.bea.com/ns/weblogic/90}dispatch-policy>,<{http://www.bea.com/ns/weblogic/90
}message-driven-descriptor>,<{http://www.bea.com/ns/weblogic/
90}clients-on-same-server>,<{http://www.bea.com/ns/weblogic/90}run-
as-principal-name>,<{http://www.bea.com/ns/weblogic/90}iiop-security-
descriptor>,<{http://www.bea.com/ns/weblogic/90}jndi-name>,<{http://www.bea.com/ns/weblogic/90
}service-reference-description>,<{http://www.bea.com/ns/weblogic/
90}ejb-reference-description>,<{http://www.bea.com/ns/weblogic/
90}remove-as-principal-name>,<{http://www.bea.com/ns/weblogic/
90}passivate-as-principal-name>,<{http://www.bea.com/ns/weblogic/
90}resource-env-description>,<{http://www.bea.com/ns/weblogic/
90}transaction-descriptor>,<{http://www.bea.com/ns/weblogic/
90}remote-client-timeout>,<{http://www.bea.com/ns/weblogic/
90}stateless-session-
descriptor
>,locator=[node=null,object=null,url=null,line=11,col=29,offset=-1]]
javax.xml.bind.UnmarshalException: unexpected element (uri:"http://www.bea.com/ns/weblogic/90
", local:"reference-descriptor"). Expected elements are <{http://www.bea.com/ns/weblogic/90
}resource-description>,<{http://www.bea.com/ns/weblogic/90}network-
access-point>,<{http://www.bea.com/ns/weblogic/90}entity-
descriptor>,<{http://www.bea.com/ns/weblogic/90}enable-call-by-
reference>,<{http://www.bea.com/ns/weblogic/90}create-as-principal-
name>,<{http://www.bea.com/ns/weblogic/90}stateful-session-
descriptor>,<{http://www.bea.com/ns/weblogic/90}local-jndi-name>,<{http://www.bea.com/ns/weblogic/90
}ejb-name>,<{http://www.bea.com/ns/weblogic/90}dispatch-policy>,<{http://www.bea.com/ns/weblogic/90
}message-driven-descriptor>,<{http://www.bea.com/ns/weblogic/
90}clients-on-same-server>,<{http://www.bea.com/ns/weblogic/90}run-
as-principal-name>,<{http://www.bea.com/ns/weblogic/90}iiop-security-
descriptor>,<{http://www.bea.com/ns/weblogic/90}jndi-name>,<{http://www.bea.com/ns/weblogic/90
}service-reference-description>,<{http://www.bea.com/ns/weblogic/
90}ejb-reference-description>,<{http://www.bea.com/ns/weblogic/
90}remove-as-principal-name>,<{http://www.bea.com/ns/weblogic/
90}passivate-as-principal-name>,<{http://www.bea.com/ns/weblogic/
90}resource-env-description>,<{http://www.bea.com/ns/weblogic/
90}transaction-descriptor>,<{http://www.bea.com/ns/weblogic/
90}remote-client-timeout>,<{http://www.bea.com/ns/weblogic/
90}stateless-session-descriptor>
at
com
.sun
.xml
.bind
.v2
.runtime
.unmarshaller
.UnmarshallingContext.handleEvent(UnmarshallingContext.java:523)
at
com
.sun.xml.bind.v2.runtime.unmarshaller.Loader.reportError(Loader.java:
199)
at
com
.sun.xml.bind.v2.runtime.unmarshaller.Loader.reportError(Loader.java:
194)
at
com
.sun
.xml
.bind
.v2
.runtime
.unmarshaller.Loader.reportUnexpectedChildElement(Loader.java:71)
at
com
.sun
.xml.bind.v2.runtime.unmarshaller.Loader.childElement(Loader.java:65)
at
com
.sun
.xml
.bind
.v2
.runtime
.unmarshaller.StructureLoader.childElement(StructureLoader.java:209)
at
com
.sun
.xml
.bind
.v2
.runtime
.unmarshaller
.UnmarshallingContext._startElement(UnmarshallingContext.java:366)
at
com
.sun
.xml
.bind
.v2
.runtime
.unmarshaller
.UnmarshallingContext.startElement(UnmarshallingContext.java:347)
at
com
.sun
.xml
.bind
.v2.runtime.unmarshaller.SAXConnector.startElement(SAXConnector.java:
101)
at
org.xml.sax.helpers.XMLFilterImpl.startElement(XMLFilterImpl.java:527)
at org.apache.openejb.jee.wls.JaxbWls
$NamespaceFilter.startElement(JaxbWls.java:127)
at
com
.sun
.org
.apache
.xerces
.internal
.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:533)
at
com
.sun
.org
.apache
.xerces
.internal.impl.dtd.XMLDTDValidator.startElement(XMLDTDValidator.java:
798)
at
com
.sun
.org
.apache
.xerces
.internal
.impl
.XMLNSDocumentSc
Re: JNDI lookup help
We use Ant here. I'll download a copy of Maven to see if I can't get
a little more self sufficient with my own builds and perhaps even
contribute.
I've been busy this week with production problems, but I gave it a
quick try and this is the error I got so far. I'll see if I can't dig
into it a bit further this evening. It's probably something I'm doing
wrong though.
[severity=ERROR,message=unexpected element (uri:"http://www.bea.com/ns/weblogic/90
", local:"reference-descriptor"). Expected elements are <{http://www.bea.com/ns/weblogic/90
}resource-description>,<{http://www.bea.com/ns/weblogic/90}network-
access-point>,<{http://www.bea.com/ns/weblogic/90}entity-descriptor>,<{http://www.bea.com/ns/weblogic/90
}enable-call-by-reference>,<{http://www.bea.com/ns/weblogic/90}create-
as-principal-name>,<{http://www.bea.com/ns/weblogic/90}stateful-
session-descriptor>,<{http://www.bea.com/ns/weblogic/90}local-jndi-
name>,<{http://www.bea.com/ns/weblogic/90}ejb-name>,<{http://www.bea.com/ns/weblogic/90
}dispatch-policy>,<{http://www.bea.com/ns/weblogic/90}message-driven-
descriptor>,<{http://www.bea.com/ns/weblogic/90}clients-on-same-
server>,<{http://www.bea.com/ns/weblogic/90}run-as-principal-name>,<{http://www.bea.com/ns/weblogic/90
}iiop-security-descriptor>,<{http://www.bea.com/ns/weblogic/90}jndi-
name>,<{http://www.bea.com/ns/weblogic/90}service-reference-
description>,<{http://www.bea.com/ns/weblogic/90}ejb-reference-
description>,<{http://www.bea.com/ns/weblogic/90}remove-as-principal-
name>,<{http://www.bea.com/ns/weblogic/90}passivate-as-principal-
name>,<{http://www.bea.com/ns/weblogic/90}resource-env-description>,<{http://www.bea.com/ns/weblogic/90
}transaction-descriptor>,<{http://www.bea.com/ns/weblogic/90}remote-
client-timeout>,<{http://www.bea.com/ns/weblogic/90}stateless-session-
descriptor
>,locator=[node=null,object=null,url=null,line=11,col=29,offset=-1]]
javax.xml.bind.UnmarshalException: unexpected element (uri:"http://www.bea.com/ns/weblogic/90
", local:"reference-descriptor"). Expected elements are <{http://www.bea.com/ns/weblogic/90
}resource-description>,<{http://www.bea.com/ns/weblogic/90}network-
access-point>,<{http://www.bea.com/ns/weblogic/90}entity-descriptor>,<{http://www.bea.com/ns/weblogic/90
}enable-call-by-reference>,<{http://www.bea.com/ns/weblogic/90}create-
as-principal-name>,<{http://www.bea.com/ns/weblogic/90}stateful-
session-descriptor>,<{http://www.bea.com/ns/weblogic/90}local-jndi-
name>,<{http://www.bea.com/ns/weblogic/90}ejb-name>,<{http://www.bea.com/ns/weblogic/90
}dispatch-policy>,<{http://www.bea.com/ns/weblogic/90}message-driven-
descriptor>,<{http://www.bea.com/ns/weblogic/90}clients-on-same-
server>,<{http://www.bea.com/ns/weblogic/90}run-as-principal-name>,<{http://www.bea.com/ns/weblogic/90
}iiop-security-descriptor>,<{http://www.bea.com/ns/weblogic/90}jndi-
name>,<{http://www.bea.com/ns/weblogic/90}service-reference-
description>,<{http://www.bea.com/ns/weblogic/90}ejb-reference-
description>,<{http://www.bea.com/ns/weblogic/90}remove-as-principal-
name>,<{http://www.bea.com/ns/weblogic/90}passivate-as-principal-
name>,<{http://www.bea.com/ns/weblogic/90}resource-env-description>,<{http://www.bea.com/ns/weblogic/90
}transaction-descriptor>,<{http://www.bea.com/ns/weblogic/90}remote-
client-timeout>,<{http://www.bea.com/ns/weblogic/90}stateless-session-
descriptor>
at
com
.sun
.xml
.bind
.v2
.runtime
.unmarshaller
.UnmarshallingContext.handleEvent(UnmarshallingContext.java:523)
at
com
.sun.xml.bind.v2.runtime.unmarshaller.Loader.reportError(Loader.java:
199)
at
com
.sun.xml.bind.v2.runtime.unmarshaller.Loader.reportError(Loader.java:
194)
at
com
.sun
.xml
.bind
.v2
.runtime.unmarshaller.Loader.reportUnexpectedChildElement(Loader.java:
71)
at
com
.sun.xml.bind.v2.runtime.unmarshaller.Loader.childElement(Loader.java:
65)
at
com
.sun
.xml
.bind
.v2
.runtime
.unmarshaller.StructureLoader.childElement(StructureLoader.java:209)
at
com
.sun
.xml
.bind
.v2
.runtime
.unmarshaller
.UnmarshallingContext._startElement(UnmarshallingContext.java:366)
at
com
.sun
.xml
.bind
.v2
.runtime
.unmarshaller
.UnmarshallingContext.startElement(UnmarshallingContext.java:347)
at
com
.sun
.xml
.bind
.v2.runtime.unmarshaller.SAXConnector.startElement(SAXConnector.java:
101)
at org.xml.sax.helpers.XMLFilterImpl.startElement(XMLFilterImpl.java:
527)
at org.apache.openejb.jee.wls.JaxbWls
$NamespaceFilter.startElement(JaxbWls.java:127)
at
com
.sun
.org
.apache
.xerces
.internal
.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:533)
at
com
.sun
.org
.apache
.xerces
.internal.impl.dtd.XMLDTDValidator.startElement(XMLDTDValidator.java:
798)
at
com
.sun
.org
.apache
.xerces
.internal
.impl
.XMLNSDocumentScannerImpl
.scanStartElement(XMLNSDocumentScannerImpl.java:330)
at
com.sun.org.apache.xerces.internal.impl.XMLDocument
Re: JNDI lookup help
On Nov 7, 2007, at 6:14 AM, Casey Rayman wrote:
Forgive my ignorance... Is there an established place to download
binary snapshots or do you mean an output of Maven via checking out
a snapshot from the repository?
Sorry, I assumed you were using maven (it would auto-download
everything). I've put up a server binary here for you:
http://people.apache.org/~dblevins/openejb-592874/
Out of curiosity, what build/test environment are you using? I know
things are nice and easy for maven, but I definitely want to make sure
we're doing what we can for other setups too -- any suggestions on how
we could make life easier are very welcome.
On another note: There is a download.html and a downloads.html(note
the s) on the website. I confused myself for a few seconds when I
mistyped the url.
Definitely confusing. We'll get that cleared up.
Thanks!
-David
Thanks,
Casey
On Nov 6, 2007, at 11:21 PM, David Blevins wrote:
On Nov 2, 2007, at 12:52 PM, David Blevins wrote:
On Nov 2, 2007, at 8:54 AM, Casey Rayman wrote:
We are using the tags to force a JNDI name in
our weblogic-ejb-jar.xml file. Openejb appears to allow the
same tag in the openejb-jar.xml, but seems to ignore it
completely.
We don't quite have the same tag in the openejb-jar.xml. You've
hit upon one of the only remaining todos, let me see if i can
hack something up for you. Ideally we should support your
weblogic-ejb-jar.xml directly so you don't have to maintain an
openejb-jar.xml file.
Ok, I've added the support we've been needing for per ejb jndi names:
http://issues.apache.org/jira/browse/OPENEJB-253
Note that you can still use a template if you like, i.e. "ejb/
org.superbiz.Foo" works or you can just "ejb/{interfaceClass}".
Then I also hooked up support for pulling the jndi names out of the
weblogic-ejb-jar.xml file also, so you really don't need to bother
with an openejb-jar.xml. The wls conversion code so far only
supports and . It'll take a bit to
add cmp conversion (we use JPA for our CMP), but by the looks of
the entity you posted, it should work fine as-is because the field
names match the column names which is JPA default.
Back on the subject of JNDI names, do you happen to know the jndi
format WebLogic uses for EJB 3 business interfaces? I poked around
but didn't find anything definitive, got the impression they were
just using interface name. I'd like to adjust the default template
appropriately to match.
New snapshots have been published. Just switch your dependency
version to 3.0.0-SNAPSHOT, give it a try and let us know if it works.
-David
Re: JNDI lookup help
Forgive my ignorance... Is there an established place to download
binary snapshots or do you mean an output of Maven via checking out a
snapshot from the repository?
On another note: There is a download.html and a downloads.html(note
the s) on the website. I confused myself for a few seconds when I
mistyped the url.
Thanks,
Casey
On Nov 6, 2007, at 11:21 PM, David Blevins wrote:
On Nov 2, 2007, at 12:52 PM, David Blevins wrote:
On Nov 2, 2007, at 8:54 AM, Casey Rayman wrote:
We are using the tags to force a JNDI name in
our weblogic-ejb-jar.xml file. Openejb appears to allow the same
tag in the openejb-jar.xml, but seems to ignore it completely.
We don't quite have the same tag in the openejb-jar.xml. You've
hit upon one of the only remaining todos, let me see if i can hack
something up for you. Ideally we should support your weblogic-ejb-
jar.xml directly so you don't have to maintain an openejb-jar.xml
file.
Ok, I've added the support we've been needing for per ejb jndi names:
http://issues.apache.org/jira/browse/OPENEJB-253
Note that you can still use a template if you like, i.e. "ejb/
org.superbiz.Foo" works or you can just "ejb/{interfaceClass}".
Then I also hooked up support for pulling the jndi names out of the
weblogic-ejb-jar.xml file also, so you really don't need to bother
with an openejb-jar.xml. The wls conversion code so far only
supports and . It'll take a bit to add
cmp conversion (we use JPA for our CMP), but by the looks of the
entity you posted, it should work fine as-is because the field names
match the column names which is JPA default.
Back on the subject of JNDI names, do you happen to know the jndi
format WebLogic uses for EJB 3 business interfaces? I poked around
but didn't find anything definitive, got the impression they were
just using interface name. I'd like to adjust the default template
appropriately to match.
New snapshots have been published. Just switch your dependency
version to 3.0.0-SNAPSHOT, give it a try and let us know if it works.
-David
Re: JNDI lookup help
On Nov 2, 2007, at 12:52 PM, David Blevins wrote:
On Nov 2, 2007, at 8:54 AM, Casey Rayman wrote:
We are using the tags to force a JNDI name in
our weblogic-ejb-jar.xml file. Openejb appears to allow the same
tag in the openejb-jar.xml, but seems to ignore it completely.
We don't quite have the same tag in the openejb-jar.xml. You've
hit upon one of the only remaining todos, let me see if i can hack
something up for you. Ideally we should support your weblogic-ejb-
jar.xml directly so you don't have to maintain an openejb-jar.xml
file.
Ok, I've added the support we've been needing for per ejb jndi names:
http://issues.apache.org/jira/browse/OPENEJB-253
Note that you can still use a template if you like, i.e. "ejb/
org.superbiz.Foo" works or you can just "ejb/{interfaceClass}".
Then I also hooked up support for pulling the jndi names out of the
weblogic-ejb-jar.xml file also, so you really don't need to bother
with an openejb-jar.xml. The wls conversion code so far only supports
and . It'll take a bit to add cmp
conversion (we use JPA for our CMP), but by the looks of the entity
you posted, it should work fine as-is because the field names match
the column names which is JPA default.
Back on the subject of JNDI names, do you happen to know the jndi
format WebLogic uses for EJB 3 business interfaces? I poked around but
didn't find anything definitive, got the impression they were just
using interface name. I'd like to adjust the default template
appropriately to match.
New snapshots have been published. Just switch your dependency
version to 3.0.0-SNAPSHOT, give it a try and let us know if it works.
-David
Re: JNDI lookup help
http://www.bea.com/servers/wls700/dtd/weblogic-ejb-jar.dtd";> AuxGenderRO 1000 15 ReadOnly false WebLogic_CMP_RDBMS 6.0 META-INF/weblogic-cmp-rdbms-jar.xml True AuxGenderHomeRO http://java.sun.com/dtd/ejb-jar_2_0.dtd";> AuxGenderRO com...entity.AuxGenderHome com...entity.AuxGender com...entity.AuxGenderBean Container com...entity.AuxGenderPK False 2.x AuxGenderBeanRO genderId genderCode modifiedBy sourceId genderDesc modifiedDate status effectiveDate findAll AuxGenderRO * NotSupported http://www.bea.com/servers/wls700/dtd/weblogic-rdbms20-persistence-700.dtd";> AuxGenderRO DataSource AuxGender genderId GenderId genderCode GenderCode modifiedBy ModifiedBy sourceId SourceId genderDesc GenderDesc modifiedDate ModifiedDate status Status effectiveDate EffectiveDate I've attached all 3 weblogic deployment descriptors. The class names have been masked to protect the guilty :) Thanks, Casey On Nov 6, 2007, at 2:20 AM, Jacek Laskowski wrote: On 11/5/07, Casey Rayman <[EMAIL PROTECTED]> wrote: That would be awesome. Thanks David. Could you send the weblogic-ejb-jar.xml you're working with? It'd be an excellent example to start with and add more features as they're needed. Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
Re: JNDI lookup help
On 11/5/07, Casey Rayman <[EMAIL PROTECTED]> wrote: > That would be awesome. Thanks David. Could you send the weblogic-ejb-jar.xml you're working with? It'd be an excellent example to start with and add more features as they're needed. Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
Re: JNDI lookup help
That would be awesome. Thanks David. Casey On Nov 2, 2007, at 12:52 PM, David Blevins wrote: On Nov 2, 2007, at 8:54 AM, Casey Rayman wrote: I'm looking at openejb as a testing environment for some entity beans. Our production environment is Weblogic. We are using the tags to force a JNDI name in our weblogic-ejb- jar.xml file. Openejb appears to allow the same tag in the openejb- jar.xml, but seems to ignore it completely. Does anyone have any suggestions for forcing OpenEJB to use a JNDI name rather than using generated names via the openejb.jndiname.format property? Hi Casey, We don't quite have the same tag in the openejb-jar.xml. You've hit upon one of the only remaining todos, let me see if i can hack something up for you. Ideally we should support your weblogic-ejb- jar.xml directly so you don't have to maintain an openejb-jar.xml file. -David
Re: JNDI lookup help
On Nov 2, 2007, at 8:54 AM, Casey Rayman wrote: I'm looking at openejb as a testing environment for some entity beans. Our production environment is Weblogic. We are using the tags to force a JNDI name in our weblogic-ejb- jar.xml file. Openejb appears to allow the same tag in the openejb- jar.xml, but seems to ignore it completely. Does anyone have any suggestions for forcing OpenEJB to use a JNDI name rather than using generated names via the openejb.jndiname.format property? Hi Casey, We don't quite have the same tag in the openejb-jar.xml. You've hit upon one of the only remaining todos, let me see if i can hack something up for you. Ideally we should support your weblogic-ejb- jar.xml directly so you don't have to maintain an openejb-jar.xml file. -David
