JAXB xsd error

I am trying to create JAXB project. I have a schema file for a XML. I am getting several errors in the schema (xsd) file because of the way the xml structure.
One of my xml file elemnets is as follows.
<m:properties>
    <d:Id m:type="Edm.Int32">19</d:Id>
</m:properties>
and corresponding xsd is as follows.
<xs:element name="m:properties">
    <xs:complexType>
       <xs:sequence>
         <xs:element name="d:Id" type="xs:int">
               <xs:complexType>
                 <xs:attribute name="m:type" type="xs:string"></xs:attribute>
               </xs:complexType>
         </xs:element>
        </xs:sequence>
      </xs:complexType>
</xs:element>
Now since, this the tag/attribute names contain ":", I get following errors. And I am not able to compile my code.
Multiple annotations found at this line:
    - s4s-elt-invalid-content.1: The content of '#AnonType_d:UserIdm:propertiescontententryfeed' is invalid.
     Element 'attribute' is invalid, misplaced, or occurs too often.
    - s4s-att-invalid-value: Invalid attribute value for 'name' in element 'attribute'. Recorded reason: cvc-
     datatype-valid.1.2.1: 'm:type' is not a valid value for 'NCName'.
    - src-attribute.3.1: One of 'ref' or 'name' must be present in a local attribute declaration.
Can some one help me here.
Thanks

Sure. I will try to read about it. I did a very quick google search(not a good research) and realized that SAX faster than DOM, memory efficient and is easier to implement(to me). Hence just picked it and started using it. (Maybe it is 100 times slower than XPath.)
But it looks like I will have to scrap this code very soon. I am almost getting swayed towards JSON. My response is coming from a webservice. I choosed XML on first go. Looks like JSON is going to me much more efficient over the wire(less byte size). Hopefully its parsing is economical as well. SAX does not load the entire xml in memory hence I can count on SAX to not kill my server. Need to understand how Gson, parses the Huge JSON.
Thanks

Similar Messages

JAXB unmarshalling error for " " token as part of xsd:string type element

JAXB unmarshalling error for "<" token as part of xsd:string type element
We are getting a JAXB unmarshalling error:
while processing the following <condition> tag which is of type xsd:string
<condition> x < 100 </condition>
The error is probably happening due to "<" token as a part of string type.
xml.bind.JAXBException: Unexpected error in Unmarshalling
at oracle.xml.jaxb.JaxbUnmarshaller.unmarshal(JaxbUnmarshaller.java:224)
Any ideas how to resolve this issue?
Note
<condition> x > 100 </condition> is getting unmarshalled successfully by JAXB unmarshaller.
Thanks

Hi,
Did you tried to put & lt; (without space) instead of < ?
Best Regards,
Paweł

JAXB compiler error : Complex Type Definition Representation Error

Hi,
I have a problem when I try to generate Java classes for the XML Digital Signature schema along with the XAdES extension. Apparently, we got an XML validation issue when the XAdES schema is parsed.
Here is the xjc tool ouput :
[ERROR] src-ct.1: Complex Type Definition Representation Error for type 'IdentifierType'. When complexContent is used, the base type must be a complexType.
line 33 of XAdES.xsd
[ERROR] src-ct.1: Complex Type Definition Representation Error for type 'EncapsulatedPKIDataType'. When complexContent is used, the base type must be a complexType.
line 57 of XAdES.xsdNow these are the schema lines from XAdES.xsd that cause the problem :
<xsd:complexType name="IdentifierType">
<xsd:complexContent>
    <xsd:extension base="xsd:anyURI">
      <xsd:attribute name="Qualifier" type="QualifierType" use="optional"/>
    </xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="EncapsulatedPKIDataType">
<xsd:complexContent>
    <xsd:extension base="xsd:base64Binary">
      <xsd:attribute name="Id" type="xsd:ID" use="optional"/>
    </xsd:extension>
</xsd:complexContent>
</xsd:complexType>The most disturbing thing is that those two schemas I used (e.g. xmldsig-core-schema.xsd and XAdES.xsd) come directly from the W3C, so they should be fully compliant to the XML schema spec, shouldn't they ?
Moreover, I tried to validate these two schemas with XML Spy 4.3 and the problem occurs in slightly different way. In fact, the <xsd:complexContent> tags are replaced silently by XML Spy with <xsd:simpleContent> tags in order to validate the schema. So XML Spy seems to have a problem too with these complex type definitions. Besides, if I replace the <xsd:complexContent> tags the same way as XML Spy does, and if I run again the JAXB compiler, it works fine...
Does anyone have any knowledge about this issue ? I'd like very much to hear about anyone who has experienced or better solved the same kind of issue.
By the way, here is the version of JAXB that I use :
xjc version "1.0.2-b15-fcs"
JavaTM Architecture for XML Binding(JAXB) Reference Implementation, (build 1.0.2-b15-fcs)Any help appreciated.
Thanks,
Gregory

<xsd:extension base="xsd:anyURI">
<xsd:extension base="xsd:base64Binary">
The base attribute of the xs:extension elements shoule refer to a complexType.
For example,
<xs:complexType name="complexTypeA">
</xs:complexType>
<xsd:complexType name="IdentifierType">
<xsd:complexContent>
<xsd:extension base="complexTypeA">
<xsd:attribute name="Qualifier" type="QualifierType" use="optional"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>

JAXB Parsing error. Could it be a configuration problem?

Do version mismatches produce schema errors or are the errors below true schema mismatches do you think?
running this command.
Error:
C:\perforce\strata\v3\pools\prjSTA\src\classes>C:\Sun\jwsdp-1.5\jaxb\bin\xjc.bat
-extension -use-runtime com.bofa.strata.component.xml.JAXBruntime1_0_4 -d C:\pe
rforce\strata\v3\pools\prjSTA\src\classes\com\bofa\strata\business\cdrom\schema
-p com.bofa.strata.business.cdrom.schema C:\perforce\strata\v3\pools\prjSTA\src\
classes\com\bofa\strata\business\cdrom\schema\MonthlyBillingRequest.xsd
parsing a schema...
[ERROR] src-resolve: Cannot resolve the name 'tscd:BillingId.SimpleType' to a(n)
'type definition' component.
line 18 of MonthlyBillingRequest.xsd
[ERROR] src-resolve: Cannot resolve the name 'ts:SigningMethod.Enumeration' to a
(n) 'type definition' component.
line 23 of MonthlyBillingRequest.xsdFailed to parse a schema.
C:\perforce\strata\v3\pools\prjSTA\src\classes>C:\Sun\jwsdp-1.5\jaxb\bin\xjc.bat
-extension -use-runtime com.bofa.strata.component.xml.JAXBruntime1_0_4 -d C:\pe
rforce\strata\v3\pools\prjSTA\src\classes\com\bofa\strata\business\cdrom\schema
-p com.bofa.strata.business.cdrom.schema C:\perforce\strata\v3\pools\prjSTA\src\
classes\com\bofa\strata\business\cdrom\schema\MonthlyBillingResponse.xsd
parsing a schema...
[ERROR] src-resolve: Cannot resolve the name 'tscd:BillingId.SimpleType' to a(n)
'type definition' component.
line 11 of MonthlyBillingResponse.xsd
[ERROR] src-resolve: Cannot resolve the name 'ts:AccountNumber.SimpleType' to a(
n) 'type definition' component.
line 13 of CDROM.xsdFailed to parse a schema.

I've been looking around on eBay and I'm not quite sure which antenna I need. There's different types like 9dBi, 12dBi and 19dBi. Which type is best? Is this one any good?
http://cgi.ebay.com.au/2-4GHz-12dBi-WIFI-Booster-Wireless-Antenna-WLAN-RP-SMA-/1 40523920864?pt=AUComputers_Networking_Accessories&hash=item20b7e0dde0#ht_3432wt932

JAXB compiling errors

I have a problem during the compiling of a schema. It returns the following errors:
parsing a schema...
[WARNING] src-import.0: Failed to read imported schema document 'xlink.xsd'.
line 29 of graphml-structure.xsd
[ERROR] src-resolve: Cannot resolve the name 'xlink:href' to a(n) attribute decl
aration component.
line 663 of graphml-structure.xsd
[ERROR] src-ct.0.1: Complex Type Definition Representation Error for type 'locat
or.type'. Element 'attribute' is invalid, misplaced, or occurs too often.
line 663 of graphml-structure.xsd
At the 29th line of "graphml-structure.xsd" is written:
<xs:import namespace="http://www.w3.org/1999/xlink" schemaLocation="xlink.xsd">
I visited that page but I haven't found any xlink.xsd. Any idea?

Well, in the end I fixed that in some way... I got from a friend of mine the xlink.xsd (why is it not available at w3c web site?! Or maybe I simply didn't find it) and succeeded in the compiling. The Java code generated was too much for my tastes though, so I decided to drop JAXB and use Xerces/SAX in its place. That surely meant a little more coding efforts, but it defintely resulted in a cleaner and shorter code, hence in a faster execution of the application.

JAXB xjc error on name collision

The xjc is invoked with the following command line:
C:\jwsdp-1.3\jaxb\bin>xjc -p com.multex.rrapi -d \multex -extension ReutersResearchAPI.xsd
The ReutersResearchAPI.xsd looks like below:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="http://api.reutersresearch.com/ReutersResearchAPI"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="http://api.reutersresearch.com/ReutersResearchAPI"
xmlns:ns1="http://api.reutersresearch.com/Estimates" xmlns:ns="http://api.reutersresearch.com/Collaboration"
elementFormDefault="qualified">
<xs:import namespace="http://api.reutersresearch.com/Collaboration" schemaLocation="Collaboration.xsd"/>
<xs:import namespace="http://api.reutersresearch.com/Estimates" schemaLocation="Estimates.xsd"/>
<xs:element name="ENTER_NAME_OF_ROOT_ELEMENT_HERE">
</xs:element>
</xs:schema>
The Collaboration.xsd looks like below:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="http://api.reutersresearch.com/Collaboration"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="http://api.reutersresearch.com/Collaboration"
elementFormDefault="qualified">
<xs:element name="status">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:int"/>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:schema>
The Estimates.xsd looks like below:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="http://api.reutersresearch.com/Estimates" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="http://api.reutersresearch.com/Estimates" elementFormDefault="qualified">
<xs:element name="Status">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="errorCode" type="errorCode_AttrT" use="optional"/>
<xs:attribute name="success" type="success_AttrT" use="required"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:schema>
The xjc generates the following error message:
[ERROR] A class/interface with the same name "com.multex.rrapi.Status" is alread
y in use.
line 285 of Estimates.xsd
[ERROR] (Relevant to above error) another one is generated from here.
line 2017 of Collaboration.xsd

Thank you. I read the fix-collision sample. In my case I have to fix collision between an <element> from one namespace and an <element> from another. Would appending the "element" suffix eliminate the collision?

JAXB unmarshalling error

We are getting a JAXB unmarshalling error:
while processing the following <condition> tag which is of type xsd:string
<condition> x < 100 </condition>
The error is probably happening due to "<" token as a part of string type.
xml.bind.JAXBException: Unexpected error in Unmarshalling
at oracle.xml.jaxb.JaxbUnmarshaller.unmarshal(JaxbUnmarshaller.java:224)
Any ideas how to resolve this issue?
Note
<condition> x >100 </condition> is getting unmarshalled successfully by JAXB unmarshaller.
Thanks

Hi,
Did you tried to put & lt; (without space) instead of < ?
Best Regards,
Paweł

XSD error messages

Are the XSD-* error messages documented anywhere? I have searched for them but can't find them.
I think they are generated from XMLParser (I am using SchemaUtil) but I could be wrong.
Thanks, Peter

Hello Peter,
Oracle XSD Processor error messages start with LSX. You can find the description of all error messages at http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96525/lsxus.htm#1004903.
Thanks.

JAXB: Encoding error (Malformed UTF-8, trying to set ISO)

Hi, I get this error when doing a Unmarshaller.unmarshal( anURL );
DefaultValidationEventHandler: [WARNING]: Declared encoding "ISO-8859-1" does not match actual one "UTF-8"; this might not be an error.
DefaultValidationEventHandler: [FATAL_ERROR]: Character conversion error: "Malformed UTF-8 char -- is an XML encoding declaration missing?" (line number may be too low).
org.xml.sax.SAXParseException: Character conversion error: "Malformed UTF-8 char -- is an XML encoding declaration missing?" (line number may be too low).
at org.apache.crimson.parser.InputEntity.fatal(InputEntity.java:1100)
(...) etc..So far, I set the ISO-8859-1 encoding 4 places;
1. the xml response from the servlet: xml.append("<?xml version=\"1.0\" encoding=\"ISO-8859-1\"?>\n\n")
2. the original XSD which the JAXB classes was generated from
3. In the client, after recieving the string containing the XML: bytes b[] = xmlString.getBytes("ISO-8859-1");
4. In the client; when posting to the server: httpConn.setRequestProperty("Content-Type","text/xml;charset=ISO-8859-1");
Yet, JAXB still thinks I'm doing UTF-8 here! Did I forget something?
thanks,
bjorn

bump .. no one knows why this happens?

JAXB Validation Error

Hi,
Iam using JAXB. I get an validation error. When i try to marshal an object to XML. The code is simple as shown below
1. Container.xsd
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="http://agi.com"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://agi.com"
elementFormDefault="qualified">
<complexType name="ContainerType" abstract="true">
<sequence>
<choice>
<element name="File" type="anyType" />
<element name="Pen" type="anyType" />
</choice>
</sequence>
</complexType>
<element name="Container" type="tns:ContainerType" abstract="true" />
</schema>
2. Holder.xsd
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="http://agi.com"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://agi.com"
elementFormDefault="qualified">
<include schemaLocation="Container.xsd"></include>
<complexType name="HolderType">
<complexContent>
<restriction base="tns:ContainerType">
<sequence>
<choice>
<element name="File">
<complexType>
<sequence>
<element name="FileName"
type="string">
</element>
<element name="Capacity"
type="integer">
</element>
</sequence>
</complexType>
</element>
<element name="Pen">
<complexType>
<sequence>
<element name="Make"
type="string">
</element>
</sequence>
</complexType>
</element>
</choice>
</sequence>
</restriction>
</complexContent>
</complexType>
<element name="Holder" type="tns:HolderType"></element>
</schema>
Main.java
package test.client;
import java.io.PrintWriter;
import java.io.StringWriter;
import java.math.BigInteger;
import java.util.List;
import javax.xml.bind.JAXBContext;
import javax.xml.bind.Marshaller;
import javax.xml.bind.Unmarshaller;
import javax.xml.bind.Validator;
import test.vo.AnyType;
import test.vo.Holder;
import test.vo.ObjectFactory;
import test.vo.HolderType.FileType;
import test.vo.HolderType.PenType;
import com.sun.xml.bind.StringInputStream;
public class Main {
public static void main(String s[]) throws Exception{
JAXBContext ctx = JAXBContext.newInstance("test.vo" );
ObjectFactory obj = new ObjectFactory();
Holder input = obj.createHolder();
FileType file = obj.createHolderTypeFileType();
file.setCapacity( BigInteger.valueOf(35) );
file.setFileName("Accounts");
AnyType any = obj.createAnyType();
List lst = any.getContent();
lst.add(file);
input.setFile(any);
Marshaller marsh = ctx.createMarshaller();
marsh.setProperty(Marshaller.JAXB_FORMATTED_OUTPUT,
new Boolean(true));
marsh.setProperty(Marshaller.JAXB_SCHEMA_LOCATION,
"http://agi.com");
Validator validator = ctx.createValidator();
validator.validate(input);
StringWriter sw = new StringWriter();
marsh.marshal(input, new PrintWriter(sw) );
StringBuffer sb = sw.getBuffer();
System.out.println(sb.toString() );
This throws the following exception
DefaultValidationEventHandler: [ERROR]: tag name "test.vo.AnyType" is not allowed. Possible tag names are: <test.vo.HolderType.FileType>
Location: obj: test.vo.impl.HolderImpl@1cd8669
Exception in thread "main" com.sun.xml.bind.serializer.AbortSerializationException: tag name "test.vo.AnyType" is not allowed. Possible tag names are: <test.vo.HolderType.FileType>
at test.vo.impl.runtime.ValidationContext.reportEvent(ValidationContext.java:199)
at test.vo.impl.runtime.ValidationContext.reportEvent(ValidationContext.java:166)
at test.vo.impl.runtime.MSVValidator.childAsElementBody(MSVValidator.java:336)
at test.vo.impl.runtime.MSVValidator.childAsBody(MSVValidator.java:292)
at test.vo.impl.ContainerTypeImpl.serializeBody(ContainerTypeImpl.java:52)
at test.vo.impl.HolderTypeImpl.serializeBody(HolderTypeImpl.java:30)
at test.vo.impl.HolderImpl.serializeBody(HolderImpl.java:43)
at test.vo.impl.runtime.MSVValidator._validate(MSVValidator.java:102)
at test.vo.impl.runtime.MSVValidator.validate(MSVValidator.java:77)
at test.vo.impl.runtime.ValidationContext.validate(ValidationContext.java:75)
at test.vo.impl.runtime.ValidatorImpl.validate(ValidatorImpl.java:121)
at test.vo.impl.runtime.ValidatorImpl.validate(ValidatorImpl.java:104)
at test.client.Main.main(Main.java:63)
However if i commentout the validation it works fine yeilding the
following result
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Holder xsi:schemaLocation="http://agi.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://agi.com">
<File>
<FileName>Accounts</FileName>
<Capacity>35</Capacity>
</File>
</Holder>
Which look good conforming to the schema above
It willbe helpful if someout could point out the mistake iam doing
Please help
Regards
Agilan Palani

I changed the code
marsh.setProperty(Marshaller.JAXB_SCHEMA_LOCATION,"http://agi.com Holder.xsd");
to
marsh.setProperty(Marshaller.JAXB_SCHEMA_LOCATION,"http://agi.com E:/Agilan/Holder.xsd");
But still the same error.
I have validated the generated xml using XMLObjective. It says the generated xml is valid against the schema.
I really dont know why the JAXB validation fails?
Please help

JAXB Compile error

I am new to JAXB and I would like to access XML data directly from an XML file without regarding the XML format and structure. As a result, I have followed the steps mentioned in the http://java.sun.com/developer/technicalArticles/WebServices/jaxb/index.html.
Step 1>
I can successfully generate a set of java classes and interfaces that represent the schema.
Step 2>
I run the following command: javac GCCities/jaxb/*.java GCCities/jaxb/impl/*.java
and then get the following error:
"GCCities\jaxb\impl\GuaranteeCalculatorCitiesReturnMessagesImpl.java:1: illegal escape character"
"GCCities\jaxb\impl\GuaranteeCalculatorCitiesReturnMessagesImpl.java:2: illegal escape character"
"GCCities\jaxb\impl\GuaranteeCalculatorCitiesReturnMessagesImpl.java:27: illegal escape character"
For your Information:
My OS is windows XP and jwsdp 1.5. Please help!

I dump the content of the GuaranteeCalculatorCitiesReturnMessagesImpl.java file.
// This file was generated by the JavaTM Architecture for XML Binding(JAXB) Reference Implementation, v@@BUILD_VERSION@@
//      See http://java.sun.com/xml/jaxb
//      Any modifications to this file will be lost upon recompilation of the source schema.
//      Generated on: 2005.05.12 於 11:22:12 GMT+08:00
\u000d\u000a\u0070\u0061\u0063\u006b\u0061\u0067\u0065\u0020\u0047\u0043\u0043\u0069\u0074\u0069\u0065\u0073\u002e\u006a .....
The content of the java file is very strange but it is generated by the jAXB bining compiler automatically by running the following command:
xjc.bat -p GCCities.jaxb GCCities.xsd -d work
On the other hands, Even if I try the sample attached with the JAXB(jwsdp-1.5), the same error "illegal escape character" is met.

JAXB xjc Error

I am new to JAXB. I installed JWSDP 1.3 and tried to ran xjc.
I ran xjc in the example below and have the
following errors. Even I run the example in C:\jwsdp-1.3\jaxb\samples
and have same error. Any ideas??
http://java.sun.com/developer/technicalArticles/WebServices/jaxb/index.html
D:\jaxbtest>xjc -p test.jaxb book.xsd -d work
parsing a schema...
compiling a schema...
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.io.IOException: work: non-existent directory
at com.sun.codemodel.writer.FileCodeWriter.<init>(FileCodeWriter.java:43
at com.sun.tools.xjc.Driver.createCodeWriter(Driver.java:410)
at com.sun.tools.xjc.Driver.run(Driver.java:226)
at com.sun.tools.xjc.Driver._main(Driver.java:80)
at com.sun.tools.xjc.Driver.access$000(Driver.java:46)
at com.sun.tools.xjc.Driver$1.run(Driver.java:60)

The eror report says:
work: non-existent directory
So: does the destination directory exist?

JAXB validation error with sample applications

Hi,
When trying to generate the java from po.xsd in the first example I get two compile errors in the result :
"PurchaseOrderImpl.java": Error #: 454 : class {deleted root}.generated.impl.PurchaseOrderImpl should be declared abstract; it does not define method validateThis() in interface javax.xml.bind.Element at line 11, column 8
"CommentImpl.java": Error #: 454 : class {deleted root}.generated.impl.CommentImpl should be declared abstract; it does not define method validateThis() in interface javax.xml.bind.Element at line 11, column 8
where {deleted root} represents parent packages in our source tree.
Anyone else seen this?
I'm using Ant1.51 to kick off the build, with the patch referred to in Apache bug 14640. (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14640)
The target to do the build is defined as follows :-
<target name="schema" depends="init"
description="Compile schema">
<echo message="Compiling the schema..."/>
<jaxb destDir="${src}"
readOnly="true"
strictValidation="true"
xjcjar="${JAXB_HOME}\lib\jaxb-xjc.jar">
<schemas dir="${basedir}" includes="po.xsd"/>
<targetPackageMapper type="regexp"
from="(.*)\.xsd" to="{deleted root}.generated"/>
</jaxb>
</target>
where ${src} is the root of the source tree and ${basedir} is the parent directory of "generated", containing the build.xml.

More precisely, this is a compile time error for the generated Java classes. The methods
void invalidate()
void validate()
void validate(Validator v)
void validateThis()
defined in
com.sun.xml.bind.validator.ValidatableObject
are not being built for
generated.impl/XTypeImpl.java
which extends
generated.impl/XImpl.java

In xsd error " expected name insted of "

I am new to xsd ... i got some sxd from My frd
while am copying that xsd in j dev am getting error "expected name insted of "
<?xml version="1.0" encoding="ISO-8859-1" ?>
<xs:schemaxmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="http://www.raj.com/e1/rajcenterbom"
targetNamespace="http://www.raj.com/e1/rajcenterbom"
elementFormDefault="qualified">
<xs:element name="DATA">
</xs:schema>
Please help me

Hay ...
I got this ... its very silly prob
thanks and regards
rky

OWSM GATEWAY PROBLEM .xsd error

Hi,
I am working on OWSM gateways.I deployed a mail web service and tried to virtualise it using OWSM gateways. I have registered the service . When i use the link for service wsdl generated by OWSM in internet explorer i can see the wsdl file but when do the same using test page in OWSM i get the following error.
java.io.IOException: The document 'http://localhost:8888/gateway/services/alshirawiMail.xsd' contains HTML tags.
Also i have only tried with web services but when i try to virtualise THE WHOLE BPEL PROCESS i get error like
java.io.IOException: The document 'http://localhost:8888/gateway/services/rule_doesnot_work.xsd' contains HTML tags.
Please reply.
Thanks and regards.
Vishnu
Message was edited by:
user607746

Hi
The problem with xsd resolved but now when i invoke the service from test page i am getting this error.
<env:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">null
<env:Body>
<env:Fault
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>env:Server</faultcode>
<faultstring>ORABPEL-08021 Cannot find partner wsdl. parnterLink "OWSM_SYNC_BPEL_PROCESS" is not found in process "OWSM_SYNC_BPEL_PROCESS" (revision "1.0") Please check the deployment descriptor of the process to find the correct partnerLink name. </faultstring>
null</env:Fault>
</env:Body>
</env:Envelope>

JAXB xsd error

Similar Messages

Maybe you are looking for