The BEA Workshop facet for XmlBeans simply exposes XmlBeans to your
project classpath (and it exposes the same version of Apache XmlBeans
that is used by the WLS server at runtime,
wl_home/commmon/lib/apache_xbean.jar); you can turn this facet off (and
not get that classpath container exposing the XmlBeans classes to your
project), but this will not alter the version of XmlBeans that is
referenced by the other pieces of WLW and WLS logic (this code is
unaware of your User Library and the 2.3.0 version).

Note: I believe there is a plan to update the version of XmlBeans
shipped with 9.2 MP2 to 2.3.0

-Rob 

-----Original Message-----
From: Dicks, Matthew [mailto:[EMAIL PROTECTED] 
Sent: Friday, June 29, 2007 10:07 AM
To: [email protected]
Subject: RE: 2.3.0 and BEA Workshop 9.2


I'm not using 2.1.  I have turned off the BEA Workshop Facet for
XmlBeans.  My project uses a User Library with 2.3.0.  However, Workshop
seems to use its own integrated 2.1 when it comes to building WSDLs.  I
would have expected the XmlBeans implementation in both Workshop and
WebLogic Server to be modular in that whatever version is plugged-in
will work.

Matt

-----Original Message-----
From: Radu Preotiuc-Pietro [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 28, 2007 6:58 PM
To: [email protected]
Subject: RE: 2.3.0 and BEA Workshop 9.2


If this boils down to trying to recompile your Schemas with XMLBeans 2.3
and use them in a runtime that has XMLBeans 2.1, then I can confirm that
it is not supported. Even if it was, that would not enable you to use
any new 2.3 functionality anyway. On the other hand of course, if you
tried to compile you Schemas with XMLBeans 2.1 and use them in a runtime
that supported XMLBeans 2.3, that would work.

Does all of this make sense?
Radu

On Thu, 2007-06-28 at 16:22 -0400, Dicks, Matthew wrote:
> Using the 2.3.0 bin (I checked the version before I compiled with: 
> scomp -version)
>  
>   Apache Software Foundation, org.apache.xmlbeans.XmlBeans version 
> 2.3.0-r540734
>  
>   scomp -out c:\xml\2.3.0\nav2.3.0.jar C:\xml\2.3.0\schemas\nav 
> \nav.xsd -compiler c:\java\jdk1.5.0_11\bin\javac.exe
>  
>  
>         -----Original Message-----
>         From: Jacob Danner [mailto:[EMAIL PROTECTED]
>         Sent: Thursday, June 28, 2007 4:09 PM
>         To: [email protected]
>         Subject: Re: 2.3.0 and BEA Workshop 9.2
>         
>         
>         I'm not sure how a user library would affect the app in this
>         way. How did you recompile the xmlbeans types?
>         
>         
>         On 6/28/07, Dicks, Matthew <[EMAIL PROTECTED]> wrote: 
>                 I turned off the Workshop XmlBeans Facet and use a
>                 User Library to support XmlBeans 2.2.0, which I have
>                 been doing for nearly a year without any trouble.  I
>                 was trying to get CDATA support by moving to 2.3.0 but
>                 Workshop crashes when I attempt to generate a WSDL
>                 that uses a 2.3.0 XmlBean.  If I go back to 2.2.0 can
>                 I just encode the CDATA section?
>                  
>                 Matt
>                         -----Original Message-----
>                         From: Jacob Danner
>                         [mailto:[EMAIL PROTECTED]
>                         Sent: Thursday, June 28, 2007 2:17 PM
>                         To: [email protected]
>                         Subject: Re: 2.3.0 and BEA Workshop 9.2
>                         
>                         
>                         Hi Matthew,
>                         How did you switch to XmlBeans 2.3 with
>                         workshop 9.2? Are you talking talking adding a
>                         newly compiled xmlbeans jar to a workshop
>                         project or using the J2EE utility project with
>                         the xmlbeans builder facet. 
>                         If that is the case it you may want to verify
>                         this is supported.
>                         Please let us know,
>                         -Jacob Danner
>                         
>                         On 6/28/07, Dicks, Matthew
>                         <[EMAIL PROTECTED]> wrote: 
>                                 After switching to XmlBeans 2.3.0 and
>                                 recompiling all my beans, Workshop 9.2
>                                 crashed when trying generate WSDLs for
>                                 web services:
>                                 
>                                 java.lang.NoClassDefFoundError 
>                                         at
>
sun.misc.Unsafe.ensureClassInitialized(Native Method) 
>                                         at
>
sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAcces
sorFactory.java:25) 
>                                         at
>
sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:12
2) 
>                                         at
>
java.lang.reflect.Field.acquireFieldAccessor(Field.java:917) 
>                                         at
>
java.lang.reflect.Field.getFieldAccessor(Field.java:898) 
>                                         at
>
java.lang.reflect.Field.get(Field.java:357) 
>                                         at
>
weblogic.wsee.util.XBeanUtil.getApacheSchemaTypeForApacheXmlBean(XBeanUt
il.java:322) 
>                                         at
>
weblogic.wsee.util.XBeanUtil.getXsdPathForXmlBean(XBeanUtil.java:280) 
>                                         at
>
weblogic.wsee.util.XBeanUtil.getSchemaTypeSourceName(XBeanUtil.java:217)

>                                         at
>                                 
>
weblogic.wsee.bind.buildtime.internal.SoapAwareJava2Schema.generateWrapp
edXmlBeanSchemaTypes(SoapAwareJava2Schema.java:429)
>                                 
>                                         at
>
weblogic.wsee.bind.buildtime.internal.SoapAwareJava2Schema.postProcessOu
tputs(SoapAwareJava2Schema.java:318) 
>                                         at
>
com.bea.staxb.buildtime.Java2Schema.internalBind(Java2Schema.java:421) 
>                                         at
>
com.bea.staxb.buildtime.BindingCompiler.bind(BindingCompiler.java:125) 
>                                         at
>
com.bea.staxb.buildtime.BindingCompiler.bindAsExplodedTylar(BindingCompi
ler.java:161) 
>                                         at
>                                 
>
weblogic.wsee.bind.buildtime.internal.SoapAwareJava2Schema.bindAsExplode
dTylar(SoapAwareJava2Schema.java:1150)
>                                 
>                                         at
>                                 
>
weblogic.wsee.bind.buildtime.internal.TylarJ2SBindingsBuilderImpl.create
BuildtimeBindings(TylarJ2SBindingsBuilderImpl.java:210)
>                                 
>                                         at
>
weblogic.wsee.tools.jws.WebServiceInfo.createBindings(WebServiceInfo.jav
a:213) 
>                                         at
>
weblogic.wsee.tools.jws.wsdl.WsdlBuilder.process(WsdlBuilder.java:41) 
>                                         at
>
weblogic.wsee.tools.jws.process.CompositeProcessor.process(CompositeProc
essor.java:36) 
>                                         at
>
weblogic.wsee.tools.jws.build.JwsCompiler.buildWebServices(JwsCompiler.j
ava:466) 
>                                         at
>
weblogic.wsee.tools.jws.build.JwsCompiler.compile(JwsCompiler.java:438) 
>                                         at
>
com.bea.wlw.webservices.core.compiler.WebServiceCompiler$3.invoke(WebSer
viceCompiler.java:247) 
>                                         at
>
com.bea.wlw.webservices.core.compiler.WebServiceCompiler.accessCompiler(
WebServiceCompiler.java:291) 
>                                         at
>
com.bea.wlw.webservices.core.compiler.WebServiceCompiler.compile0(WebSer
viceCompiler.java:244) 
>                                         at
>
com.bea.wlw.webservices.core.compiler.WebServiceCompiler.compile(WebServ
iceCompiler.java:202) 
>                                         at
>
com.bea.wlw.webservices.ui.actions.GenerateWsdlFromJwsAction.run(Generat
eWsdlFromJwsAction.java:149) 
>                                         at
>
org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:246)

>                                         at
>
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(Ac
tionContributionItem.java:538) 
>                                         at
>
org.eclipse.jface.action.ActionContributionItem.access$2(ActionContribut
ionItem.java:488) 
>                                         at
>
org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionCont
ributionItem.java:400) 
>                                         at
>
org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) 
>                                         at
>
org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843) 
>                                         at
>
org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125) 
>                                         at
>
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758) 
>                                         at
>
org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699) 
>                                         at
>
org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663) 
>                                         at
>
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:3
67) 
>                                         at
>
org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143) 
>                                         at
>
org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103) 
>                                         at
>
org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActiva
tor.java:226) 
>                                         at
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:
376) 
>                                         at
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:
163) 
>                                         at
>
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
>                                         at
>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39) 
>                                         at
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25) 
>                                         at
>
java.lang.reflect.Method.invoke(Method.java:585) 
>                                         at
>
org.eclipse.core.launcher.Main.invokeFramework(Main.java:334) 
>                                         at
>
org.eclipse.core.launcher.Main.basicRun(Main.java:278) 
>                                         at
>
org.eclipse.core.launcher.Main.run(Main.java:973) 
>                                         at
>                                 
> org.eclipse.core.launcher.Main.main(Main.java:948)
>                                 
>                                 Any ideas?
>                                 
>                                 Matt
>                                 
>                                 
>                                 
>                                 
>                                 IMPORTANT:  E-mail sent through the
Internet is not secure. Legg Mason therefore 
>                                 recommends that you do not send any
confidential or sensitive information to us 
>                                 via electronic mail, including social
security numbers, account numbers, or personal 
>                                 identification numbers. Delivery, and
or timely delivery of Internet mail is not 
>                                 guaranteed. Legg Mason therefore
recommends that you do not send time sensitive 
>                                 or action-oriented messages to us via 
> electronic mail.
>                                 
>                                 This message is intended for the
addressee only and may contain
>                                 privileged or confidential
information. Unless you are the intended
>                                 recipient, you may not use, copy or
disclose to anyone any information
>                                 contained in this message. If you have
received this message in error, 
>                                 please notify the author by replying
to this message and then kindly
>                                 delete the message. Thank you.
>                         
>                         
>                 
>                 
>                 
>                 IMPORTANT:  E-mail sent through the Internet is not
secure. Legg Mason therefore 
>                 recommends that you do not send any confidential or
sensitive information to us 
>                 via electronic mail, including social security
numbers, account numbers, or personal
>                 identification numbers. Delivery, and or timely
delivery of Internet mail is not 
>                 guaranteed. Legg Mason therefore recommends that you
do not send time sensitive 
>                 or action-oriented messages to us via electronic mail.
>                 
>                 This message is intended for the addressee only and
may contain
>                 privileged or confidential information. Unless you are
the intended
>                 recipient, you may not use, copy or disclose to anyone
any information
>                 contained in this message. If you have received this
message in error,
>                 please notify the author by replying to this message
and then kindly
>                 delete the message. Thank you.
>         
> 
> 
> 
> IMPORTANT:  E-mail sent through the Internet is not secure. Legg Mason

> therefore
> recommends that you do not send any confidential or sensitive
information to us 
> via electronic mail, including social security numbers, account
numbers, or personal
> identification numbers. Delivery, and or timely delivery of Internet
mail is not 
> guaranteed. Legg Mason therefore recommends that you do not send time
sensitive 
> or action-oriented messages to us via electronic mail.
> 
> This message is intended for the addressee only and may contain 
> privileged or confidential information. Unless you are the intended 
> recipient, you may not use, copy or disclose to anyone any information

> contained in this message. If you have received this message in error,

> please notify the author by replying to this message and then kindly 
> delete the message. Thank you.

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]


IMPORTANT:  E-mail sent through the Internet is not secure. Legg Mason
therefore 
recommends that you do not send any confidential or sensitive
information to us 
via electronic mail, including social security numbers, account numbers,
or personal identification numbers. Delivery, and or timely delivery of
Internet mail is not 
guaranteed. Legg Mason therefore recommends that you do not send time
sensitive 
or action-oriented messages to us via electronic mail.

This message is intended for the addressee only and may contain
privileged or confidential information. Unless you are the intended
recipient, you may not use, copy or disclose to anyone any information
contained in this message. If you have received this message in error,
please notify the author by replying to this message and then kindly
delete the message. Thank you.


---------------------------------------------------------------------
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.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to