JavaBinding using XMLBeans

Hi,
I have a javaObject which would be parsed to form a xml document using the XMLBeans.But while doing it i thought is there any pattern implementation that can be used.As i need to read the javaObject and then assign it to the particular element in the XMLBean info , all the examples provided with XMLBeans have assigned values directly into the beans , so if anyhas an example doing this type of implementation would be helpful.

Please do not cross-post. It dilutes the value of a conversation when it is split among threads. You already have something started here:
http://forum.java.sun.com/thread.jspa?threadID=703395&tstart=0
- Saish

Similar Messages

Returning Errors from a webservice using XMLBeans

I have a webservice that accepts XML as input and output parameters, and I'm using XMLBeans to handle this. I'm trying to work out how I can return error information from the webservice, so I created an Exception.xsd schema and 'include' it in the output XML Schema, so an exception xml element is valid in the output schema. The problem is, the XMLBean class generated from the output XML schema has no methods that allow me to create an Exception element. Is there some other way of handling the return of exceptions from webservices using XML?

The answer is just throw a SoapFaultException and put the exception.xsd XMLBean in the FaultDetail section of the SoapFaultException.

How can I use XMLBeans in a Web Services client?

How can I use XMLBeans in a standalone Java client with a Web Service?
I posted the message below earlier in the year, but have not yet been successful
in my
attempts.
regards
Eddie
Hi,
I'm trying to using XMLBeans to send a document to a web service from a standalone
Java client. I'm using the PurchaseOrder (easypo) example document, and the service
expects a parameter of type PurchaseOrderDocument. The client proxy class generated
by WebLogic Workshop, however, expects to send a parameter of type PurchaseOrder.
In the client, I can instantiate a PurchaseOrderDocument, and then obtain a PurchaseOrder
(e.g. pod.getPurchaseOrder() ), but the returned class is not compatible with
the PurchaseOrder type that the client proxy expects.
In a previous attempt (not using Workshop), the client would not compile because
it expected to send a non-abstract class with a public default constructor (presumably
a JAX-RPC requirement), and XMLBeans had generated an interface.
Any help would be greatly appreciated!
thanks & regards
Eddie

I have been experiencing similar problems with the HTML Editor and have managed to find an answer that should start to answer some of my questions. The Apex HTML Editor Standard is actually an HTML editor called FCKeditor. The FCKeditor has a Javascript API that can be found at http://docs.fckeditor.net/FCKeditor_2.x/Developers_Guide/JavaScript_API. Unfortuately this doesn't seem to give the whole answer and I found more at http://www.houseoffusion.com/groups/cf-talk/thread.cfm/threadid:49607.
I needed to get the text entered within my html editor standard (e.g. P1_MYTEXT) and use it within my javascript function. I did this by using the following script
<script language="JavaScript" type="text/javascript">
function showtext(){
var oEditor = FCKeditorAPI.GetInstance('P1_MYTEXT');
var editortext = escape(oEditor.GetXHTML(oEditor.FormatOutput));
alert(editortext);
</script>
Hope this helps.
Matthew

Help!. Problem with using XmlBeans 1.0 Stand-alone Library

Hi All,
I read that XmlBeans requires JDK1.4.1. Is there any way to use this successfully
within other AppServers ( not Bea 8.1) which are not at JDK1.4.1 Level yet??.
What I mean is, I am very much interested in using XmlBeans but unfortunately
the AppServer that is in Production ( WAS4.0) is at level jdk1.3.1.
Am I dead in the water? or is there any hope?
Thanks,
Sudha

"Sudha" <[email protected]> wrote:
>
the AppServer that is in Production ( WAS4.0) is at level jdk1.3.1.Today you do need JDK 1.4.x.
Am I dead in the water? or is there any hope?Although there should be few things in XMLBeans that intrinsically depend on JDK
1.4, a port to JDK 1.3 has not yet been done. If (when) we do a JDK 1.3 port,
we'll do it in the open-source project and I'd encourage you to watch for it,
try it, and contribute to it. But right now there's been no 1.3 work yet - you
need JDK 1.4.

Deprecated warnings while using XMLBeans

Greetings,
Using XMLBeans Builder in WorkShop 9.2 raises hundreds of deprecated warnings. It seems that the XMLBeans Builder generated code doesn't compile against ... XMLBeans itself ? It that possible ? Any workaround ?
Many thanks in advance,
Nicolas

Hi Nicolas,
To highlight your issue:
"""...how could I compile, without any warnings, including deprecation
warnings, XMLBeans Builder generated code. After all, as it's name
clearly suggests, an XMLBeans Builder generates code to be compiled
against XMLBeans. It seems very strange that a product which generates
XMLBeans compliant code cannot compile this code without deprecation
warnings."""
I spent some time working with XMLBeans and unfortunately, what you want
(code without deprecation warnings) is actually something to make a
request of from the Apache XmlBeans folks. The code the XMLBeans Builder
generates is not any different from that which the Apache XmlBeans
project would generate when a schema is compiled via the 'scomp' tool.
Here's how you can see the cause of this outside of the Xmlbeans builder
tool or the Workshop IDE
1) go to http://xmlbeans.apache.org and download a binary distribution
2) unzip the binary distribution to a dir on your filesystem
3) copy your xsds to <unzip-dir>\xmlbeans-2.2.20\bin
4) cd to <unzip-dir>\xmlbeans-2.2.20\bin
5) run the following:
scomp -src srcOutputDir *.xsd
This will generate the src files from the xsd (similar to how the
XMLBeans Builder tool would) on your filesystem.
From there, browse to a .java file and view in your favorite text editor.
You'll see that the java code produced from the XMLBeans tool itself
produces code with @deprecated javadoc
e.g,
/** @deprecated {@link XMLInputStream} */
public static org.apache.xmlbeans.xml.stream.XMLInputStream
Now to see this in the Workshop IDE, create a new J2EE Utility Project.
Make sure the XmlBeans->XmlBeans library facet is enabled.
Drag the contents of srcOutputDir (from above) to the src directory of
the J2EE Utility Project in the IDE window.
Upon successful rebuild of the srcs in the IDE, you'll be able to see
similar warnings from pure Apache XmlBeans related code.
If you really CANNOT have these deprecation warnings, your best bet may
be to email the Apache XmlBeans mailing list. At the very least they can
probably best explain why the deprecation is still left in the code.
The website for xmlbeans is:
http://xmlbeans.apache.org
and some helpful mailing lists can be found and queried from
http://xmlbeans.apache.org/community/index.html
Hope this helps,
-Jacobd
nicolas duminil wrote:
rfrost,
Many thanks for having taken the time to reply but ... you didn't get me. My point was not to disable compiler's deprecation warnings. I believe that it's very important to be aware that APIs you're using in your code is deprecated. This is certainly the reason which motivated the compiler's creators to provide an option able to signal deprecated calls in the code. Disabling this warnings doesn't provide any benefits, it is just hiding problems and the goal of a compiler is not to hide problems, but to hi
ghlight them. No, my point was simply to ask how could I compile, without any warnings, including deprecation warnings, XMLBeans Builder generated code. After all, as it's name clearly suggests, an XMLBeans Builder generates code to be compiled against XMLBeans. It seems very strange that a product which generates XMLBeans compliant code cannot compile this code without deprecation warnings. That's a big issue because a deprecation warning says to you: "Hey, you're using something you're not supposed to u
se any more". So, many thanks to you for having let me know how to disable compilation warnings, but this was not at all the point. The real point was how to use the XMLBeans Builder in order to generate XMLBeans code free of deprecation warnings. I understand you don't have the answer but, in this case, please don't feel obligated to reply.
Kind regards,
nicolas

How to get an object of choice from XML data using XMLBean?

I have xml schema and I have generated a jar to represent my schema using XMLBean. I also have few xml data files, these are valid xml for generated schema. Now I want to write a utility which takes xml file as input and returns an object of my choice (Assuming this Object type is available in the jar) as output and vice versa. Some thing like this â€“
1. Object getObjectFromXML(File xmldatafile, Class classname)
xmldatafile = presents the source of XML data
classname = an object of this class type as output filled from the xml data.
2. String getXMLStrFromObject(Object)
Pass Object and get XML as String output
Any pointer?
Thanks,

Hi! Maybe have a look at the documentation for XmlObject.Factory.parse(). It should allow you what you need to do.
Cheers,
G.

Parsing my xml using XMLBeans

I'm trying to use XMLBeans to load my xml file and access different elements of it. Here is my schema:
<?xml version="1.0" encoding="utf-8"?>
<xs:schema targetNamespace="http://testing.jsm.jtsd.com/testData"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<xs:element name="Hazard">
<xs:complexType>
<xs:sequence>
<xs:element name="Type" type="xs:string"/>
<xs:element name="Name" type="xs:string"/>
<xs:element name="LatLonLocation" type="xs:string"/>
<xs:element name="ZuluTime" type="xs:string"/>
<xs:element name="Agent" type="xs:string"/>
<xs:element name="Munition" type="xs:string"/>
<xs:element name="DeliveryMethod" type="xs:string"/>
<xs:element name="DispersalDevice" type="xs:int"/>
<xs:element name="TypeMatl" type="xs:string"/>
<xs:element name="MatlForm" type="xs:string"/>
<xs:element name="TypeMatlAmt" type="xs:int"/>
<xs:element name="MatlMass" type="xs:double"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
Here is my xml file:
<Hazard xmlns="http://testing.jsm.jtsd.com/testData">
<Type>TestHazard</Type>
<Name>Test_default</Name>
<LatLonLocation>20 N 20 E</LatLonLocation>
<ZuluTime>180200ZOCT2007</ZuluTime>
<Agent>GB</Agent>
<Munition>500 kg Bomb</Munition>
<DeliveryMethod>4 AC * 8 Bombs</DeliveryMethod>
</Hazard>
I can run scomp and generate a xmlbeans jar file.
When I try to load my xml file, I get this error:
org.apache.xmlbeans.XmlException: error: Unexpected element: CDATA
Here is my java code that tries to load my xml file and errors out:
HazardDocument myParsedDoc =
HazardDocument.Factory.parse(myXmlFile);
Please let me know what I'm doing wrong.

Thanks for the reply. And sorry for the confusion. I am passing a File to that method call. I've been working on this for awhile and I'm about to go back to JaxB.
My xsd snippet looks like this now:
<?xml version="1.0" encoding="utf-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://testing.jsm.jtsd.com">
<xs:element name="JSMData">
<xs:complexType>
<xs:sequence>
<xs:element name="Hazard" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="Type" type="xs:string"/>
<xs:element name="Name" type="xs:string"/>
I"m able to System out the JSMDataDocument and JSMData after my xml file gets parsed and I can see my xml printed out correctly, but when I do JSMData.sizeOfHazardArray , I get 0 when I should be getting 5 (1 for each Hazard element in my xml file).
Here is my xml file snippet:
<JSMData xmlns="http://testing.jsm.jtsd.com">
<Hazard>
<Type>RaWnHazard</Type>
<Name>RW_large_foo</Name>
Anything wrong here?

WLS 9.2 using XmlBeans error

Using WLS 9.2 MP1 and attempting to use XmlBean derived classes from a bean called from a JSP.
          Using XmlBeans v2.3.0.
          Server is WebLogic Server 9.2 MP1 Sun Jan 7 00:56:31 EST 2007 883308
          JSP version is 2.0
          Servlet API is 2.4
          An exception is thrown :
                    javax.servlet.jsp.el.ELException
               at javelin.jsp.el.ArrayRefEvaluator.evaluateBeanType(ArrayRefEvaluator.java:252)
               at javelin.jsp.el.ArrayRefEvaluator.evaluate(ArrayRefEvaluator.java:49)
               at javelin.jsp.el.ELNode$RefExpression.evaluate(ELNode.java:492)
               at javelin.jsp.el.ExpressionEvaluatorImpl$ELExpression.evaluate(ExpressionEvaluatorImpl.java:186)
               at javelin.jsp.el.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:124)
               at javelin.jsp.el.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:104)
               at jsp_servlet._order.__composeorder3._jsp__tag1(__composeorder3.java:229)
               at jsp_servlet._order.__composeorder3._jspService(__composeorder3.java:205)
               at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
               at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:223)
               at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
               at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
               at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
               at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3245)
               at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
               at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
               at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2003)
               at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1909)
               at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359)
               at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
               at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
                    This corresponds to the declaration of the root document within the bean e.g.
          ======== JSP code extract ===========
                    <%@ include file="/html/doctypes/StrictDoctype.html" %>
          <%@ taglib uri="utilTLD" prefix="util" %>
          <%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
          <%@ taglib uri="http://java.sun.com/jsp/jstl/xml" prefix="x" %>
          <%@ page import="com.web.order.*" %>
          <%@ page language="java" session="false" %>
          <jsp:useBean id="composeXmlBean" scope="request" class="com.web.order.composeXmlBean">
          <jsp:setProperty name="composeXmlBean" property="*"/>
          </jsp:useBean>
          <c:set scope="page" var="xml" value="${composeXmlBean.myXmlString}"/>
                    ============End Jsp code =======
          ========Java code extract =======
                    public class ComposeXmlBean {
               public Document getMyXmlString() {
                         // Use XML Beans to construct the XML String
                     DDServiceDocument rootDoc = DDServiceDocument.Factory.newInstance();
                    ========End Java code ===========
          Anyone have any ideas about what could be causing this error. I have used XmlBeans without problem in WLS 8.1. Is this a WLS9.2 problem caused by Javelin ?
          regards,
          Chris

Chris,
          Firstly, I think your pasted jsp's line below is not correct:
          <jsp:useBean id="composeXmlBean" scope="request"
          class="com.web.order.composeXmlBean">
          Should it be <jsp:useBean id="composeXmlBean" scope="request"
          class="com.web.order.ComposeXmlBean"> ?
          I tried to reprodcue your issues locally, but fails (my testcase works fine)
          since I have not your customerized classes.
          My codes are listed below:
          1) Bean codes:
          package com.web.order;
          public class ComposeXmlBean {
          public String getMyXmlString() {
          return "100";
          public void setMyXmlString(String setV) {
          return;
          2) JSP codes:
          <%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
          <%@ taglib uri="http://java.sun.com/jsp/jstl/xml" prefix="x" %>
          <%@ page import="com.web.order.*" %>
          <%@ page language="java" session="false" %>
          <jsp:useBean id="composeXmlBean" scope="request"
          class="com.web.order.ComposeXmlBean">
          <jsp:setProperty name="composeXmlBean" property="*"/>
          </jsp:useBean>
          <c:set scope="page" var="xml" value="${composeXmlBean.myXmlString}"/>
          My sugegstions:
          1) is it a XML bean related issue?
          can you remove XML releated logic to verify whether JSP compiler could
          support this kind of EL ( "${composeXmlBean.myXmlString}") correctly?
          2) If possible, can you pasted a reproducer here(a .war)?
          3) As for WLS8.1, which only support JSP1.2 and dose not support JSP2.0's
          EL, while your failed points is at EL: "${composeXmlBean.myXmlString}" in
          fact, I think your testcases are different during these two tests(WLS 8.1
          and WLS 9.2), Or that EL dose not work at all in WLS8.1. Can you help to
          clarify this?
          Regards
          Leon
          <Chris Thorp> wrote in message news:[email protected]...
          Using WLS 9.2 MP1 and attempting to use XmlBean derived classes from a bean
          called from a JSP.
          Using XmlBeans v2.3.0.
          Server is WebLogic Server 9.2 MP1 Sun Jan 7 00:56:31 EST 2007 883308
          JSP version is 2.0
          Servlet API is 2.4
          An exception is thrown :
                    javax.servlet.jsp.el.ELException
          at
          javelin.jsp.el.ArrayRefEvaluator.evaluateBeanType(ArrayRefEvaluator.java:252)
          at javelin.jsp.el.ArrayRefEvaluator.evaluate(ArrayRefEvaluator.java:49)
          at javelin.jsp.el.ELNode$RefExpression.evaluate(ELNode.java:492)
          at
          javelin.jsp.el.ExpressionEvaluatorImpl$ELExpression.evaluate(ExpressionEvaluatorImpl.java:186)
          at
          javelin.jsp.el.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:124)
          at
          javelin.jsp.el.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:104)
          at jsp_servlet._order.__composeorder3._jsp__tag1(__composeorder3.java:229)
          at jsp_servlet._order.__composeorder3._jspService(__composeorder3.java:205)
          at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
          at
          weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:223)
          at
          weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
          at
          weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
          at
          weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
          at
          weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3245)
          at
          weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
          at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
          at
          weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2003)
          at
          weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1909)
          at
          weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359)
          at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
          at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
                    This corresponds to the declaration of the root document within the bean
          e.g.
          ======== JSP code extract ===========
                    <%@ include file="/html/doctypes/StrictDoctype.html" %>
          <%@ taglib uri="utilTLD" prefix="util" %>
          <%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
          <%@ taglib uri="http://java.sun.com/jsp/jstl/xml" prefix="x" %>
          <%@ page import="com.web.order.*" %>
          <%@ page language="java" session="false" %>
          <jsp:useBean id="composeXmlBean" scope="request"
          class="com.web.order.composeXmlBean">
          <jsp:setProperty name="composeXmlBean" property="*"/>
          </jsp:useBean>
          <c:set scope="page" var="xml" value="${composeXmlBean.myXmlString}"/>
                    ============End Jsp code =======
          ========Java code extract =======
                    public class ComposeXmlBean {
          public Document getMyXmlString() {
                         // Use XML Beans to construct the XML String
                DDServiceDocument rootDoc =
          DDServiceDocument.Factory.newInstance();
                    ========End Java code ===========
          Anyone have any ideas about what could be causing this error. I have used
          XmlBeans without problem in WLS 8.1. Is this a WLS9.2 problem caused by
          Javelin ?
          regards,
          Chris

Error while using xmlbeans

I am using xmlbeans2.2 . I passed the wsdl to scomp utility to it,it returned me the jar which include all the classes and interfaces from the wsdl.in short using xmlbeans i converted wsdl type to java type(classes and interface).but when try to instantiate the class from the list i stuck to error " reference to Factory is ambiguous, "
found : org.apache.xmlbeans.XmlObject
required: com.pstn.soapapi.v1.AuthElem

user10310678 wrote:
I am using beta version. Oracle VM Manager 2.2.0If you have a beta version of 2.2, then you should be an Oracle employee. Please ask this question on an internal mailing list. If you are not an Oracle employee, please ask the employee that gave you this beta. As this is a beta, some functionality may not be operational yet, so I can't answer why this particular feature seems not to work.

Failure to generate WSDL from web service when use xmlbean

Hi, I have a web service that uses xmlbean generated by schema. The schema from 3rd party is in a separate project since it's used by another web app and ejb project. In wlw103 I have included the schema project in this web service project's Java Build Path. The web service compiles, but when I tried to generate WSDL a Error window shows and says "The WSDL cannot be generated from the web service due to unexpected runtime errors".
The following is the detail. What do I need to do to make the xmlbean available for my web service? Thanks
com.bea.workshop.webservices.core.gen.WebServicesException: weblogic.wsee.tools.jws.build.CompileException: Error compiling web service: C:\workspace\ws\src\myPackage\testWS.java
     at com.bea.workshop.webservices.core.compiler.WebServiceCompilerImpl$3.invoke(WebServiceCompilerImpl.java:335)
     at com.bea.workshop.webservices.core.compiler.WebServiceCompilerImpl.accessCompiler(WebServiceCompilerImpl.java:390)
     at com.bea.workshop.webservices.core.compiler.WebServiceCompilerImpl.compile0(WebServiceCompilerImpl.java:330)
     at com.bea.workshop.webservices.core.compiler.WebServiceCompilerImpl.compile(WebServiceCompilerImpl.java:275)
     at com.bea.workshop.webservices.ui.actions.GenerateWsdlFromJwsAction.run(GenerateWsdlFromJwsAction.java:169)
     at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:256)
     at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:546)
Caused by: weblogic.wsee.tools.jws.build.CompileException: Error compiling web service: C:\workspace\ws\src\myPackage\testWS.java
     at weblogic.wsee.tools.jws.build.JwsCompiler.buildWebServices(JwsCompiler.java:526)
     at weblogic.wsee.tools.jws.build.JwsCompiler.compile(JwsCompiler.java:483)
     at com.bea.workshop.webservices.core.compiler.WebServiceCompilerImpl$3.invoke(WebServiceCompilerImpl.java:333)
     ... 46 more
Caused by: weblogic.wsee.tools.WsBuildException: weblogic.wsee.bind.buildtime.BindingException: ERROR ! could not add Xml Schema Type for XmlBean named '\[com.domain.UserDocument\]'. This is completely unexpected and might be caused by missing *.xsb and *.xsd files in the build environment. The building and running of this Service is likely to FAIL.
     at weblogic.wsee.tools.jws.jaxrpc.JAXRPCWebServiceInfo.createBindings(JAXRPCWebServiceInfo.java:227)
     at weblogic.wsee.tools.jws.wsdl.WsdlBuilder.processImpl(WsdlBuilder.java:43)
     at weblogic.wsee.tools.jws.jaxrpc.JAXRPCProcessor.process(JAXRPCProcessor.java:27)
     at weblogic.wsee.tools.jws.process.CompositeProcessor.process(CompositeProcessor.java:47)
     at weblogic.wsee.tools.jws.build.JwsCompiler.buildWebServices(JwsCompiler.java:522)
     ... 48 more
Caused by: weblogic.wsee.bind.buildtime.BindingException: ERROR ! could not add Xml Schema Type for XmlBean named '\[com.domain.UserDocument\]'. This is completely unexpected and might be caused by missing *.xsb and *.xsd files in the build environment. The building and running of this Service is likely to FAIL.
     at weblogic.wsee.bind.buildtime.internal.SoapAwareJava2Schema.bindAsExplodedTylar(SoapAwareJava2Schema.java:1414)
     at weblogic.wsee.bind.buildtime.internal.TylarJ2SBindingsBuilderImpl.createBuildtimeBindings(TylarJ2SBindingsBuilderImpl.java:216)
     at weblogic.wsee.tools.jws.jaxrpc.JAXRPCWebServiceInfo.createBindings(JAXRPCWebServiceInfo.java:223)
     ... 52 more

HI,
I hope this issue can resolved by adding this patch CR349256
Try to contact weblogic support to get more details about this patch.
Regards,
Kal.

Deadlock in schema validation using XMLBeans

Hi,
I am using WLI8.1 SP2 XMLBeans. I have a schema which has a kind of an infinite
loop. ie I have a complexType element A which has a complexType child element
B which inturn has a complexType child element of type A with minoccurs="0".
When I try to validate the incoming XML using XMLBeans generated from the above
schema, the thread goes into a deadlock and the transaction rollbacks after the
given timeout period.
I checked the workshop_debug.log and found the thread gets struck when it calls
the validate() function of the XMLObject.
Has anybody faced this error or is it a bug in BEA XMLBeans validate function
to handle such schema. I tried to validate the same XML using XML SPY and it worked.
Here is the sample of my schema.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"
attributeFormDefault="unqualified">
     <xs:element name="ShippingOrderNotification">
          <xs:complexType>
               <xs:sequence>
                    <xs:element name="ShippingContainer" type="ShippingContainerType" minOccurs="0"
maxOccurs="unbounded"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:complexType name="ShippingContainerType">
          <xs:sequence>
               <xs:element name="SubContainer" minOccurs="0" maxOccurs="unbounded">
                    <xs:complexType>
                         <xs:sequence>
                              <xs:element name="ShippingContainer" type="ShippingContainerType" minOccurs="0"
maxOccurs="unbounded"/>
                         </xs:sequence>
                    </xs:complexType>
               </xs:element>
          </xs:sequence>
     </xs:complexType>
</xs:schema>

Please make sure that main xsd uses import or include tag to reference both schema1.xsd and schema2.xsd. If the main xsd does not do it, Pi cannot verify it. Since you package all the files as zip file, also make sure the path for the secondary files are in proper location.
In short, the import element allows you to use schema components from any schema; the include element allows you to add all the components of an included schema to the containing schema. If the target namespace is same for both then include tag should be good enough. If you don't find one, you might have to use include tag element in the main or parent xsd file.
Edited by: Baskar Gopal on Jan 31, 2012 5:18 PM

WLS 9: WebServices using XMLBeans

I'm attempting to implement a web service on WLS 9 (without workshop) that uses XMLbean types as parameters.
The docs for jwsc hint that XMLBeans are given special treatment when used as web service arguments, but I have had no luck creating a functional web service this way.
Does anyone have a functional example for this, or any other tips on how the get started?

I'm attempting to implement a web service on WLS 9 (without workshop) that uses XMLbean types as parameters.
The docs for jwsc hint that XMLBeans are given special treatment when used as web service arguments, but I have had no luck creating a functional web service this way.
Does anyone have a functional example for this, or any other tips on how the get started?

How to generate class files using XMLBeans

I had used XMLBeans scomp command to generate document classes from XSD.But problem is i got xsb files and java files, not class files.
I want to use jar of these generated files in my project , so i need to have class files.
Can anyone help me in overcoimg this problem...

well i got it...
i need to use this cmd.....
scomp -out sortie.jar -debug -compiler C:\jdk1.5.0_04\bin\javac b.xsd
as i was getting
java.io.IOException: CreateProcess: C:\Program @C:\DOCUME~1\CFERNA~1\LOCALS~1\Te
mp\javac18651 error=2

What are the llicensing issues with using XMLBeans?

I liked the xmlbeans compiler tool and I want to use the xml parser that the tool
has generated in my application. What licensing issues do I have to worry about
before using xmlbeans.jar and xsdTypes.jar in my application?
-- shiva

I liked the xmlbeans compiler tool and I want to use the xml parser that the tool
has generated in my application. What licensing issues do I have to worry about
before using xmlbeans.jar and xsdTypes.jar in my application?
-- shiva

Problem about using xmlbean as return parameter in workshop 9.2 jsr-181 WS

Hi
I met a problem with the jsr-181 web service's return parameters in workshop 9.2.
I wrote a web service which will return a jax-rpc-style javabean as return parameter. This javabean contained three xmlbean objects fields. So, the client can get those xmlbean objects when invoking the web service.
But I got the error like the following:
A java class "..." is being used as a parameter or return type that contains a property of field that is an xmlbean "...", this not allowed.
Maybe workshop 9.2 does not support xmlbean object as the returned javabean's field. But why, i can use that in the workshop 8.1. why workshop 9.2 does not support them.
And how can i do if the client want to get the three xmlbean objects when invoking the web service.
Thanks,
Xueh

Hi Xueh
I got it confirmed from engineering that we do NOT support any use of XmlBeans in a Pojo complex type.
The workaround is to create a top-level xmlbean type that references the other xmlbean types.
Thanks
Vimala
P.S: There seems to be some complexities involved in mapping a JAX RPC type (POJO) to a XMLBean Type. But we do have a internal bug that is tracking this issue.

JavaBinding using XMLBeans

Similar Messages

Maybe you are looking for