Yeah, that makes sense. Since WebSphere by default loads its own,
incompatible version of QName, XMLBeans will only work with setting the
option to load classes from child classloader first (and you still need
xmlbeans-qname.jar).
Vance, if your app works with XMLBeans 2.2, then you are not in this
situation and you should be able to upgrade to 2.3 by adding
xmlbeans-qname.jar in your classpath, next to xbean.jar, without other
changes.
Radu
________________________________
From: Gustavo Aquino [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 26, 2007 1:12 PM
To: [email protected]
Subject: Re: XMLBeans 2.3.0 with WebSphere 5.1 ERROR !
Hi Vance,
Thanks about your vision, all releases before 2.3.0 had the same
problem with WebSphere.
But the configuration in WebSphere to him look objects in local
classloader, and parent after resolve the problem, now all work fine.
The QName.jar of IBM is completely different, but the path and
class name is the same, this is the problem, and all websphere core
depends this class.
Inverting the load of objects all work fine.
Best Regards.
On 6/26/07, Vance Vagell <[EMAIL PROTECTED]> wrote:
Hi Gustavo,
By "I'm trying use XMLBeans 2.x and had a problem with
all." do you mean that you also had this problem on earlier XmlBeans
releases, before 2.3.0? That's my key point of interest, to determine
risk for our project.
Thanks,
Vance
> -------- Original Message --------
> Subject: Re: XMLBeans 2.3.0 with WebSphere 5.1 ERROR !
> From: "Gustavo Aquino" < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> >
> Date: Tue, June 26, 2007 1:40 pm
> To: [email protected]
>
> Hi friends,
>
> I resolve this problem, put xmlbeans-qname.jar in
classpath does not
> resolve
> the problem because, WebSphere has a QName
implementation in your
> library,
> to resolve this problem i configure my EAR to search
objects in
> classloader
> local and if does not found search in load ob
>
> I cant replace QName library of websphere with new
Qname, because
> websphere
> does not working.
>
> Anybody resolve this problem diferent ?
>
> Obs:
>
> I'm trying use XMLBeans 2.x and had a problem with
all.
>
> Best Regards
>
>
> On 6/26/07, Vance Vagell <[EMAIL PROTECTED] >
wrote:
> >
> > Hi Radu,
> >
> > This could potentially affect our project as well.
However, I see that
> > this notice is listed under XMLBeans 2.3.0. We are
using 2.2.0 ;
> does this
> > requirement affect our version as well when using
with WebSphere and
> Java
> > 1.4?
> >
> > Regards,
> > Vance
> >
> > > -------- Original Message --------
> > > Subject: RE: XMLBeans 2.3.0 with WebSphere 5.1
ERROR !
> > > From: "Radu Preotiuc-Pietro" <[EMAIL PROTECTED]>
> > > Date: Mon, June 25, 2007 10:22 pm
> > > To: <[email protected]>
> > >
> > > See the Website for the JDK1.4 announcement:
> http://xmlbeans.apache.org
> > > You need xmlbeans-qname.jar on your classpath
because the version of
> > > QName that WebSphere 5.1.1 includes is (from the
error message) an
> old
> > > version that doesn't work with XMLBeans.
> > >
> > > Hope this helps,
> > > Radu
> > >
> > >
> > > ________________________________
> > >
> > > From: Gustavo Aquino [mailto:
[EMAIL PROTECTED]
> > > Sent: Monday, June 25, 2007 6:30 PM
> > > To: [email protected]
> > > Subject: XMLBeans 2.3.0 with WebSphere 5.1
ERROR !
> > >
> > >
> > > Hi friends,
> > >
> > > I'm a long time XMLBeans user, and i want to
use new XMLBeans
> > > 2.3.0 in my new Project, first time that i need
run xmlbeans under
> > > WebSphere.
> > >
> > > My WebSphere is 5.1.1 and Run under IBM JDK.
> > >
> > > My project have all XMLBeans .jar and my
schema.jar with my
> > > XMLObjects mapped in MANIFEST.MF, to start i
trying to run a simple
> > > test,
> > > a servlet with this simple code:
> > >
> > > ConsulteDocument consulteDoc =
> > > ConsultePjDocument.Factory.newInstance();
> > > Consulte consulte =
consulteDoc.addNewConsultePj ();
> > >
> > > EmpresaConsultada empresaConsultada
=
> > > consultePJ.addNewEmpresaConsultada();
> > >
> > > empresaConsultada.addNewEndereco ();
> > >
> > > Identificacao identificacao =
> > > empresaConsultada.addNewIdentificacao ();
> > >
> > >
> > > identificacao.addNewNumeroTelefone
().addNewListaTelefone().setTelefone(1
> > > 185689635);
> > >
> > >
> > > out.println(consulteDoc.xmlText());
> > >
> > > Running this, WebSphere return this error :
> > >
> > >
> > > [25/06/07 22:01:55:904 BRT] c723596
WebGroup I SRVE0180I:
> > > [TestWeb] [/TestWeb] [Servlet.LOG]: init
> > > [25/06/07 22:01:58:763 BRT] c723596
WebGroup E SRVE0026E:
> > > [Erro de Servlet]-[ javax.xml.namespace.QName:
method
> > >
<init>(Ljava/lang/String;Ljava/lang/String;Ljava/lang/
> > > String;)V not found]: java.lang.NoSuchMethodError:
> > > javax.xml.namespace.QName: method
> > >
<init>(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)V not
> > > found
> > > at at
> > >
org.apache.xmlbeans.impl.store.Locale.<clinit>(Locale.java:133).null(Unk
> > > nown Source)
> > > at
> > >
org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.newInstance
(SchemaT
> > > ypeLoaderBase.java:198)
> > > at
> > >
br.com.unixsolutions.test.dto.saidaconsultepj.ConsultePjDocument$Factory
> > > .newInstance (ConsultePjDocument.java :702)
> > > at br.com.unixsolutions
> > >
.test.servlet.EmpresarialCompletoServlet.doGet(EmpresarialCompletoServle
> > > t.java:43)
> > > at
> > >
javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
> > > at
> > >
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> > > at
> > >
com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService
> > > (StrictServletInstance.java:110)
> > > at
> > >
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLi
> > > fecycleServlet.java:174)
> > > at
> > >
com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycle
> > > Servlet.java:313)
> > > at
> > >
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service
> > > (StrictLifecycleServlet.java:116)
> > > at
> > >
com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.
> > > java:283)
> > > at
> > >
com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(Vali
> > > dServletReferenceState.java:42)
> > > at
> > >
com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch
(Servle
> > > tInstanceReference.java:40)
> > > at
> > >
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispa
> > > tch (WebAppRequestDispatcher.java :983)
> > > at
> > >
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRe
> > > questDispatcher.java:564)
> > > at
> > >
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppReq
> > > uestDispatcher.java:200)
> > > at
com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward
> > > (WebAppInvoker.java :119)
> > > at
> > >
com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInv
> > > oker.java:276)
> > > at
> > >
com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocati
> > > on(CachedInvocation.java:71)
> > > at
> > >
com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI
> > > (ServletRequestProcessor.java:182)
> > > at
> > >
com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSELis
> > > tener.java:334)
> > > at
> > >
com.ibm.ws.webcontainer.http.HttpConnection.handleRequest
(HttpConnection
> > > .java:56)
> > > at
com.ibm.ws.http.HttpConnection.readAndHandleRequest
> > > (HttpConnection.java:618)
> > > at
> > > com.ibm.ws.http.HttpConnection.run
(HttpConnection.java:439)
> > > at
> > >
com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:672)
> > >
> > >
> > > Anybody knows what happends ?
> > >
> > > Running this in TestCase, the code run
perfect, but in
> WebSphere
> > > container, this error is printed.
> > >
> > > Thx.
> > >
> > > Best Regards.
> > >
> > >
> > >
> > >
> > >
> > > Notice: This email message, together with any
attachments, may
> > > contain information of BEA Systems, Inc., its
subsidiaries and
> > > affiliated entities, that may be confidential,
proprietary,
> > > copyrighted and/or legally privileged, and is
intended solely for
> the
> > > use of the individual or entity named in this
message. If you are not
> > > the intended recipient, and have received this
message in error,
> > > please immediately return this by email and then
delete it.
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
[EMAIL PROTECTED]
> > For additional commands, e-mail:
[EMAIL PROTECTED]
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or legally
privileged, and is intended solely for the use of the individual or entity
named in this message. If you are not the intended recipient, and have received
this message in error, please immediately return this by email and then delete
it.
