Please cast your vote for the XMLBeans v2.5.0-RC1, as published at http://xmlbeans.apache.org/dist/, to become XMLBeans v2.5.0 official release. The vote will be open until end of day Saturday, 12th of December. Anyone is allowed to show support or lack of it, but only XMLBeans committer votes are binding. [ ] +1 - I am in favor of this release, and can help [ ] +0 - I am in favor of this release, but cannot help [ ] -0 - I am not in favor of this release [ ] -1 - I am against this proposal (must include a reason) My vote is: [X] +1 - I am in favor of this release, and can help Cezar
haha ... O(∩_∩)O~ Congratulation! I've been using it. 2009/12/9 Cezar Andrei <cezar.andrei@oracle.com> > There seems to be no problems, except from the missing src.zip file which > I’ll copy shortly. I’ll follow up with the VOTE email. > > In the meantime, please do check it in your environment. > > > > Thank you, > > Cezar > > > ------------------------------ > > *From:* Cezar Andrei > *Sent:* Wednesday, November 25, 2009 5:25 PM > *To:* dev@xmlbeans.apache.org > *Cc:* user@xmlbeans.apache.org > *Subject:* [Release Candidate] XMLBeans 2.5.0-RC1 > > > > Hello everyone, > > > > The first release candidate for XMLBeans 2.5.0 is available at: > > http://xmlbeans.apache.org/dist/ > > > > Please give it a try and let us know if there are any problems with it. > > > > Thank you, > > Cezar Andrei >
There seems to be no problems, except from the missing src.zip file which I'll copy shortly. I'll follow up with the VOTE email. In the meantime, please do check it in your environment. Thank you, Cezar _____ From: Cezar Andrei Sent: Wednesday, November 25, 2009 5:25 PM To: dev@xmlbeans.apache.org Cc: user@xmlbeans.apache.org Subject: [Release Candidate] XMLBeans 2.5.0-RC1 Hello everyone, The first release candidate for XMLBeans 2.5.0 is available at: http://xmlbeans.apache.org/dist/ Please give it a try and let us know if there are any problems with it. Thank you, Cezar Andrei
I hope that the workaround that I describe is the correct solution. I
encountered a few and from what I best recall, this was the fix for this
issue. Feel free to contact me at paul_botta@hotmail.com.
There was an issue (either AXIS or with the XML beans generated classes)
where the namespace was not always being correctly appended with the
trailing '/'. I used some debug output statements to output the value. I
was not successful at uncovering the cause, but arrived at a workaround. I
ended up getting into the auto-gen stub that extends
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver and added the
following method:
public org.apache.axiom.soap.SOAPEnvelope
validateNamespace(org.apache.axiom.soap.SOAPEnvelope envelope) {
java.util.Iterator namespaceIterator = envelope.getBody().getChildren();
while (namespaceIterator.hasNext()) {
org.apache.axiom.om.OMNode ns = (org.apache.axiom.om.OMNode)
namespaceIterator.next();
org.apache.axiom.om.OMElement element = null;
if ( ns instanceof org.apache.axiom.om.OMElement){
element = (org.apache.axiom.om.OMElement)ns;
if ( element.getDefaultNamespace().getNamespaceURI() != null
&&
element.getDefaultNamespace().getNamespaceURI().equals("http://xyz.com/mobility/network/sector/schemas")
) {
element.declareDefaultNamespace("http://xyz.com/mobility/network/sector/schemas/");
}
}
}
return envelope;
In the various toEnvelope() methods within the same class I added the
following checks:
if (param != null) {
envelope.getBody().addChild(toOM(param, optimizeContent));
return validateNamespace(envelope);
}
Hope this helps.
--
View this message in context: http://old.nabble.com/Could-not-get-a-Java-Date-type-from-a-Schema-complex-type-tp13028826p26639796.html
Sent from the Xml Beans - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: user-help@xmlbeans.apache.org
Hi, did you ever find an answer to this? I'm having the exact same issue (working with the same company). Thanks, Ronnie bottabing wrote: > > I am getting the following exception. I am using XMLBeans and Axis. > > org.apache.xmlbeans.impl.values.XmlValueNotSupportedException: Could not > get a Java Date type from a Schema complex type > > The object that is being SOAPified doesn’t contain a date value. Below is > the SOAP call, the completed response prior to sending across the wire > (which looks fine), the stack trace and the WSDL. Thanks. > > 1- SOAP Call > <soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:xsd="http://www.w3.org/2001/XMLSchema" > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" > xmlns:end="http://endpoint.webservice.cssng.nis.cingular.com"> > > <soapenv:Header/> > <soapenv:Body> > <end:getLocationByKey > soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> > <locationId xsi:type="xsd:int">7</locationId> > </end:getLocationByKey> > </soapenv:Body> > > </soapenv:Envelope> > > > -- View this message in context: http://old.nabble.com/Could-not-get-a-Java-Date-type-from-a-Schema-complex-type-tp13028826p26636382.html Sent from the Xml Beans - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org For additional commands, e-mail: user-help@xmlbeans.apache.org
David, You're correct the classes in org.apache.xmlbeans.impl.xb.xsdschema are the classes XMLBeans uses internally to load up xsd files. They are just compiled xbeans of schema4schemas xsd, (because of this bootstrap is required) but you can use them directly. Those classes will help you deal with .xsd files in XML sense, but it seems you need to ask schema specific questions. For this you'll have to compile (use XMLBeans.compileXsd() ) the xsd files into a TypeSystem and than using the TypeSystem/SchemaType interfaces you can ask schema related questions (see java doc and articles linked from XMLBeans website). Cezar > -----Original Message----- > From: M. David Allen [mailto:dmallen@mitre.org] > Sent: Wednesday, December 02, 2009 12:14 PM > To: user@xmlbeans.apache.org > Subject: Processing schema instances > > > I'm trying to use XMLBeans to process schema instances (that is, actual > schema files). I've found that XMLBeans seems to have the types baked in > to > do this, via org.apache.xmlbeans.impl.xb.xsdschema.SchemaDocument; > SchemaDocument doc = SchemaDocument.Factory.parse(relative); > > So that works. But I'm not finding any javadocs for these classes as they > look like internals that might not have been meant for XMLBeans users. > > I need to ask questions of a schema instance such as, "which types are > derived from somepref:FooType"? and to get a list of all elements a schema > defines, with their corresponding types. > > Using XMLBeans to process schemas like they were any other document (i.e. > conforming to the XML schema schema) seemed like the way to go. Is there > a > different API I should be checking to do this? > > Thanks > -- > View this message in context: http://old.nabble.com/Processing-schema- > instances-tp26613672p26613672.html > Sent from the Xml Beans - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org > For additional commands, e-mail: user-help@xmlbeans.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org For additional commands, e-mail: user-help@xmlbeans.apache.org
Thank you for this suggestion. Using a different JDK hadn't even crossed my mind. I had already bumped my memory settings up to 1024 in eclipse and it was still failing under the Sun one. After swapping in JRockit, it worked perfectly! ~Dave Shuck /************************************** blog: www.daveshuck.com tweets: www.twitter.com/dshuck cf peeps: www.dfwcfug.org **************************************/ On Wed, Dec 2, 2009 at 5:23 PM, Wing Yew Poon <wing.yew.poon@oracle.com>wrote: > Just an idea: I have sometimes found that using a different JDK helps, > e.g., use JRockit instead of Sun's JDK. > > ------------------------------ > *From:* Dave Shuck [mailto:dshuck@gmail.com] > *Sent:* Wednesday, December 02, 2009 3:16 PM > *To:* user@xmlbeans.apache.org > *Subject:* Suggestions for out of memory error on xml bean ant task? > > I am trying to to build a JAR file from a _very_ large XSD file (12K lines) > on a laptop that is (unfortunately) running Windows 7 with 2GB of memory. > Both from within eclipse and from the command line, I am getting "[xmlbean] > java.lang.OutOfMemoryError: Java heap space" errors as it attempts to > compile 7604 source files after parsing the XSD. Within eclipse.ini I have > boosted the memory settings as high as I can without success. > > While I realize that this size XSD is pretty excessive, our company has a > Hudson server that does successfully build this XSD-->JAR nightly, so I know > that it can be compiled given the right environment. > > Does anyone have any suggestions for how I might be able to better manage > the memory to allow me to build on my development laptop? > > Thanks in advance for any help. > > > ~Dave Shuck > /************************************** > blog: www.daveshuck.com > tweets: www.twitter.com/dshuck > cf peeps: www.dfwcfug.org > **************************************/ >
In my project , the XSD file is bigger than 1000K . But XMLBeans work very good. I think you shall add some JVM args. like -Xmx512m 2009/12/3 Wing Yew Poon <wing.yew.poon@oracle.com> > Just an idea: I have sometimes found that using a different JDK helps, > e.g., use JRockit instead of Sun's JDK. > > ------------------------------ > *From:* Dave Shuck [mailto:dshuck@gmail.com] > *Sent:* Wednesday, December 02, 2009 3:16 PM > *To:* user@xmlbeans.apache.org > *Subject:* Suggestions for out of memory error on xml bean ant task? > > I am trying to to build a JAR file from a _very_ large XSD file (12K lines) > on a laptop that is (unfortunately) running Windows 7 with 2GB of memory. > Both from within eclipse and from the command line, I am getting "[xmlbean] > java.lang.OutOfMemoryError: Java heap space" errors as it attempts to > compile 7604 source files after parsing the XSD. Within eclipse.ini I have > boosted the memory settings as high as I can without success. > > While I realize that this size XSD is pretty excessive, our company has a > Hudson server that does successfully build this XSD-->JAR nightly, so I know > that it can be compiled given the right environment. > > Does anyone have any suggestions for how I might be able to better manage > the memory to allow me to build on my development laptop? > > Thanks in advance for any help. > > > ~Dave Shuck > /************************************** > blog: www.daveshuck.com > tweets: www.twitter.com/dshuck > cf peeps: www.dfwcfug.org > **************************************/ >
Just an idea: I have sometimes found that using a different JDK helps, e.g., use JRockit instead of Sun's JDK. _____ From: Dave Shuck [mailto:dshuck@gmail.com] Sent: Wednesday, December 02, 2009 3:16 PM To: user@xmlbeans.apache.org Subject: Suggestions for out of memory error on xml bean ant task? I am trying to to build a JAR file from a _very_ large XSD file (12K lines) on a laptop that is (unfortunately) running Windows 7 with 2GB of memory. Both from within eclipse and from the command line, I am getting "[xmlbean] java.lang.OutOfMemoryError: Java heap space" errors as it attempts to compile 7604 source files after parsing the XSD. Within eclipse.ini I have boosted the memory settings as high as I can without success. While I realize that this size XSD is pretty excessive, our company has a Hudson server that does successfully build this XSD-->JAR nightly, so I know that it can be compiled given the right environment. Does anyone have any suggestions for how I might be able to better manage the memory to allow me to build on my development laptop? Thanks in advance for any help. ~Dave Shuck /************************************** blog: HYPERLINK "http://www.daveshuck.com"www.daveshuck.com tweets: HYPERLINK "http://www.twitter.com/dshuck"www.twitter.com/dshuck cf peeps: HYPERLINK "http://www.dfwcfug.org"www.dfwcfug.org **************************************/
I am trying to to build a JAR file from a _very_ large XSD file (12K lines) on a laptop that is (unfortunately) running Windows 7 with 2GB of memory. Both from within eclipse and from the command line, I am getting "[xmlbean] java.lang.OutOfMemoryError: Java heap space" errors as it attempts to compile 7604 source files after parsing the XSD. Within eclipse.ini I have boosted the memory settings as high as I can without success. While I realize that this size XSD is pretty excessive, our company has a Hudson server that does successfully build this XSD-->JAR nightly, so I know that it can be compiled given the right environment. Does anyone have any suggestions for how I might be able to better manage the memory to allow me to build on my development laptop? Thanks in advance for any help. ~Dave Shuck /************************************** blog: www.daveshuck.com tweets: www.twitter.com/dshuck cf peeps: www.dfwcfug.org **************************************/
I'm trying to use XMLBeans to process schema instances (that is, actual schema files). I've found that XMLBeans seems to have the types baked in to do this, via org.apache.xmlbeans.impl.xb.xsdschema.SchemaDocument; SchemaDocument doc = SchemaDocument.Factory.parse(relative); So that works. But I'm not finding any javadocs for these classes as they look like internals that might not have been meant for XMLBeans users. I need to ask questions of a schema instance such as, "which types are derived from somepref:FooType"? and to get a list of all elements a schema defines, with their corresponding types. Using XMLBeans to process schemas like they were any other document (i.e. conforming to the XML schema schema) seemed like the way to go. Is there a different API I should be checking to do this? Thanks -- View this message in context: http://old.nabble.com/Processing-schema-instances-tp26613672p26613672.html Sent from the Xml Beans - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org For additional commands, e-mail: user-help@xmlbeans.apache.org
Hello everyone, The first release candidate for XMLBeans 2.5.0 is available at: http://xmlbeans.apache.org/dist/ Please give it a try and let us know if there are any problems with it. Thank you, Cezar Andrei
Hi, I am using the following command in xmlbean 2.4.0 to compile a large schema into java objects: scomp -mx "1536m" -out ~/xmlOut/output.jar -src ~/xmlOut -d ~/xmlOut -verbose xmlApi.xsd > build.log 2>&1 xmlApi.xsd includes 300+ other xsd files. The output.jar was created. Its size is 95,377,307. The class files are listed in the src direct. However, the package is not listed under the jar file when it is expanded in eclipse. Only xsb's are listed. No error was reported in build.log. I used the same command to build the easyop.xsd, java objects were listed in the jar output file. Am I hitting some limit in the schemaCompiler? Thanks, kjiang --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org For additional commands, e-mail: user-help@xmlbeans.apache.org
Oliver,
That's the thing, changeType does change the schema type assigned to that node and returns
a new java object of a different class but it doesn't change the structure of the document.
What you're looking for can be done programmatically since all the info is available in the
schema types but to make it work correctly for all the type is no easy job.
Cezar
_____
From: Oliver Pfau [mailto:Oliver.Pfau@scalaris.com]
Sent: Tuesday, November 17, 2009 3:55 AM
To: user@xmlbeans.apache.org
Subject: AW: changeType to type with fewer element
Hi Cezar,
imagine the following: a complex type "Top" is existing and an inherited complex type "Sub"
from "Top" is existing. Sub does extend Top with a string value "Something".
If I do the following:
Top topsub = Top.Factory.newInstance();
topsub.changeType(Sub.type);
topsub.setSomething("a value only for sub");
topsub.changeType(Top.type));
boolean isValid = topsub.validate();
isValid will be false, because topsub is at the end of type Top but the xml output defines
the something element of sub. My expectation is that the changeType(Top.type) will cause that
the something element will be ignored and not unmarshalled to xml and validation.
Regards,
Oliver
_____
Von: Cezar Andrei [mailto:cezar.andrei@oracle.com]
Gesendet: Montag, 16. November 2009 21:45
An: user@xmlbeans.apache.org
Betreff: RE: changeType to type with fewer element
Oliver,
I'm not sure what is your question, but you have to keep in mind that validation is run only
when validate() method is invoked.
Especially when it is structure related operations modifying the document don't keep the document
valid. Most of the time a document has to go through a series of invalid states to become
valid again. XMLBeans' user cooperation is required to attain document's validity after modifications.
Cezar
_____
From: Oliver Pfau [mailto:Oliver.Pfau@scalaris.com]
Sent: Friday, November 13, 2009 7:03 AM
To: user@xmlbeans.apache.org
Subject: changeType to type with fewer element
Hi,
it seems that XmlBeans is generating invalid xml when I change the type to a type with fewer
elements. There is an example with abstract conrete types on the XmlBeans homepage called
"AbstractTypes". In the file AbstractTypes.java there is this section:
...
Circle circle = (Circle) s1.changeType(Circle.type);
circle.setRadius(10.0);
...
s1 is a shape (more common). If the type of circle is changed to a more common type, the radius
is nevertheless set for the Shape type. The Validation of the changed circle to a Shape will
fail, because the radius is existing in the xml event though the xsi:type is correct. The
xml and the java representation seems to be here out of sync. Isn't it ? Or is there a trick
?
Regards,
Oliver
Thank you. Yes the xml input is of different schematype. Mistake was corrected by using the right schema. Cezar Andrei-3 wrote: > > I'm not familiar with Spring Marshaller, but it seems that the source is > not parsed in the schema context you expect. > > Also you can declare your response an XmlObject and use changeType method. > > Cezar > >> -----Original Message----- >> From: pattabi [mailto:Pattabiraman.Meenakshisundaram@aig.com] >> Sent: Monday, November 16, 2009 10:55 AM >> To: user@xmlbeans.apache.org >> Subject: ClasscastException - XmlAnyTypeImpl cannot be cast to - Error >> >> >> Hi, >> I searched the forum and googled but could not get a solution. hence >> posting >> it. >> >> I am using Spring Marshaller with xmlbeans 2.4. In the bean config file, >> I >> am just defined the XmlbeansMarshaller with no properties set. >> >> I am accessing it this way: >> ResDecisionServiceType response = (ResDecisionServiceType) >> unmarshaller.unmarshal(source); >> >> and am getting the following error: >> org.apache.xmlbeans.impl.values.XmlAnyTypeImpl cannot be cast to >> decisionserviceapp.ResDecisionServiceType. >> >> Please help. >> Thanks >> >> >> -- >> View this message in context: http://old.nabble.com/ClasscastException--- >> XmlAnyTypeImpl-cannot-be-cast-to---Error-tp26375379p26375379.html >> Sent from the Xml Beans - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org >> For additional commands, e-mail: user-help@xmlbeans.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org > For additional commands, e-mail: user-help@xmlbeans.apache.org > > > -- View this message in context: http://old.nabble.com/ClasscastException---XmlAnyTypeImpl-cannot-be-cast-to---Error-tp26375379p26390786.html Sent from the Xml Beans - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org For additional commands, e-mail: user-help@xmlbeans.apache.org
Hi Cezar,
imagine the following: a complex type "Top" is existing and an inherited complex type "Sub"
from "Top" is existing. Sub does extend Top with a string value "Something".
If I do the following:
Top topsub = Top.Factory.newInstance();
topsub.changeType(Sub.type);
topsub.setSomething("a value only for sub");
topsub.changeType(Top.type));
boolean isValid = topsub.validate();
isValid will be false, because topsub is at the end of type Top but the xml output defines
the something element of sub. My expectation is that the changeType(Top.type) will cause that
the something element will be ignored and not unmarshalled to xml and validation.
Regards,
Oliver
________________________________
Von: Cezar Andrei [mailto:cezar.andrei@oracle.com]
Gesendet: Montag, 16. November 2009 21:45
An: user@xmlbeans.apache.org
Betreff: RE: changeType to type with fewer element
Oliver,
I'm not sure what is your question, but you have to keep in mind that validation is run only
when validate() method is invoked.
Especially when it is structure related operations modifying the document don't keep the document
valid. Most of the time a document has to go through a series of invalid states to become
valid again. XMLBeans' user cooperation is required to attain document's validity after modifications.
Cezar
________________________________
From: Oliver Pfau [mailto:Oliver.Pfau@scalaris.com]
Sent: Friday, November 13, 2009 7:03 AM
To: user@xmlbeans.apache.org
Subject: changeType to type with fewer element
Hi,
it seems that XmlBeans is generating invalid xml when I change the type to a type with fewer
elements. There is an example with abstract conrete types on the XmlBeans homepage called
"AbstractTypes". In the file AbstractTypes.java there is this section:
...
Circle circle = (Circle) s1.changeType(Circle.type);
circle.setRadius(10.0);
...
s1 is a shape (more common). If the type of circle is changed to a more common type, the radius
is nevertheless set for the Shape type. The Validation of the changed circle to a Shape will
fail, because the radius is existing in the xml event though the xsi:type is correct. The
xml and the java representation seems to be here out of sync. Isn't it ? Or is there a trick
?
Regards,
Oliver
Oliver, I'm not sure what is your question, but you have to keep in mind that validation is run only when validate() method is invoked. Especially when it is structure related operations modifying the document don't keep the document valid. Most of the time a document has to go through a series of invalid states to become valid again. XMLBeans' user cooperation is required to attain document's validity after modifications. Cezar _____ From: Oliver Pfau [mailto:Oliver.Pfau@scalaris.com] Sent: Friday, November 13, 2009 7:03 AM To: user@xmlbeans.apache.org Subject: changeType to type with fewer element Hi, it seems that XmlBeans is generating invalid xml when I change the type to a type with fewer elements. There is an example with abstract conrete types on the XmlBeans homepage called "AbstractTypes". In the file AbstractTypes.java there is this section: ... Circle circle = (Circle) s1.changeType(Circle.type); circle.setRadius(10.0); ... s1 is a shape (more common). If the type of circle is changed to a more common type, the radius is nevertheless set for the Shape type. The Validation of the changed circle to a Shape will fail, because the radius is existing in the xml event though the xsi:type is correct. The xml and the java representation seems to be here out of sync. Isn't it ? Or is there a trick ? Regards, Oliver
I'm not familiar with Spring Marshaller, but it seems that the source is not parsed in the schema context you expect. Also you can declare your response an XmlObject and use changeType method. Cezar > -----Original Message----- > From: pattabi [mailto:Pattabiraman.Meenakshisundaram@aig.com] > Sent: Monday, November 16, 2009 10:55 AM > To: user@xmlbeans.apache.org > Subject: ClasscastException - XmlAnyTypeImpl cannot be cast to - Error > > > Hi, > I searched the forum and googled but could not get a solution. hence > posting > it. > > I am using Spring Marshaller with xmlbeans 2.4. In the bean config file, I > am just defined the XmlbeansMarshaller with no properties set. > > I am accessing it this way: > ResDecisionServiceType response = (ResDecisionServiceType) > unmarshaller.unmarshal(source); > > and am getting the following error: > org.apache.xmlbeans.impl.values.XmlAnyTypeImpl cannot be cast to > decisionserviceapp.ResDecisionServiceType. > > Please help. > Thanks > > > -- > View this message in context: http://old.nabble.com/ClasscastException--- > XmlAnyTypeImpl-cannot-be-cast-to---Error-tp26375379p26375379.html > Sent from the Xml Beans - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org > For additional commands, e-mail: user-help@xmlbeans.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org For additional commands, e-mail: user-help@xmlbeans.apache.org
Hi, I searched the forum and googled but could not get a solution. hence posting it. I am using Spring Marshaller with xmlbeans 2.4. In the bean config file, I am just defined the XmlbeansMarshaller with no properties set. I am accessing it this way: ResDecisionServiceType response = (ResDecisionServiceType) unmarshaller.unmarshal(source); and am getting the following error: org.apache.xmlbeans.impl.values.XmlAnyTypeImpl cannot be cast to decisionserviceapp.ResDecisionServiceType. Please help. Thanks -- View this message in context: http://old.nabble.com/ClasscastException---XmlAnyTypeImpl-cannot-be-cast-to---Error-tp26375379p26375379.html Sent from the Xml Beans - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org For additional commands, e-mail: user-help@xmlbeans.apache.org
Hi, it seems that XmlBeans is generating invalid xml when I change the type to a type with fewer elements. There is an example with abstract conrete types on the XmlBeans homepage called "AbstractTypes". In the file AbstractTypes.java there is this section: ... Circle circle = (Circle) s1.changeType(Circle.type); circle.setRadius(10.0); ... s1 is a shape (more common). If the type of circle is changed to a more common type, the radius is nevertheless set for the Shape type. The Validation of the changed circle to a Shape will fail, because the radius is existing in the xml event though the xsi:type is correct. The xml and the java representation seems to be here out of sync. Isn't it ? Or is there a trick ? Regards, Oliver
Hi folks,
I'm using XMLBeans 2.4 and encountered a validation issue because of a missing namespace definition
on element level.
I defined an abstract base type "operator" in "schema.common". In that schema there is another
complex type "master" which contains some elements of type "operator".
In schema "schema.coolops" I defined derivations of that abstract "operator" type using extension.
"schema.coolops" of course imports "schema.common".
(Don't worry about the structure - it's just an excerpt of a complex system ;-))
For adding concrete "operator"s to "master" I coded
Master.addNewOperator().changeType(schema.coolops.AddOperator.type)
which returns me a concrete "operator" instance.
Upto here all works fine. I can save/load the XML BUT several XML validators (except XMLBeans)
claim
cvc-elt.4.2: Cannot resolve 'cops:AddOperator' to a type definition for element 'Operator'.
The XML looks like this:
<application xsi:schemaLocation="application http://example.org/application.xsd" xmlns="application"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:com="schema.common">
<com:master>
<com:operator xsi:type="cops:AddOperator" xmlns:cops="schema.coolops">
...
</com:operator>
</com:master>
</application>
If I add
xsi:schemaLocation="schema.coolops http://example.org/schema.coolops.xsd"
to the element "com:operator" it is declared to be valid.
Any ideas/hints/... how to get this "schemaLocation" set?
Thanks a lot.
Christoph
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: user-help@xmlbeans.apache.org
Hey I was just wondering if you ever resolved this problem .... I have the same issue. The one thing i've noticed though is that it has something to do with NetBeans and not ant. I modified the build file initially not specifying a namespace but later edited the file and added specified a namespace. when I build the project, the build/classes directory looks fine. If i run the app from the command line, everything works fine. If I use the run feature in netbeans, the TypeTypeSystemHolder file disappears from the schemaorg_apache_xmlbeans folder and a folder called noNamespace is generated (which was correct when I initially didn't specify a namespace). Any ideas on how to resolve this problem? Wynand Vermeulen wrote: > > Hello, > > I'm trying to get XMLBeans 2.4.0 to work in a standard Netbeans project. I > have a built.xml file in my project directory, which contains ANT script > to > build the XMLBeans source. I get no errors while performing the build, > but do get a runtime exeception "java.lang.RuntimeException: Cannot load > SchemaTypeSystem. Unable to load class with name > schemaorg_apache_xmlbeans.system.sBA558E54E426CCFF39A8E684578DC966.TypeSystemHolder. > Make sure the generated binary files are on the classpath.". > > I have been finecombing the documentation, and searching the web (and this > list's archives) for days now and have found several of these types of > messages reported, and usually the advice is to make sure the > TypeSystemHolder.class is on the classpath. My ANT script stores the > generated files in the project's build\classes folder, and directly after > the build I can see that the class file and xsd files have been generated > in > the proper location, however for some strange reason once I run the > application the TypeSystemHolder.class file disappears and the exception > occurs! > > I assume that everything in the build\classes folder is part of the > classpath. If not, how do I add the > schemaorg_apache_xmlbeans.system.sBA558E54E426CCFF39A8E684578DC966.TypeSystemHolder > to the classpath in Netbeans? I've tried right clicking on the project, > and > adding the folder to the compile and runtime classpaths, and I've tried > adding it to the classpath in the ANT script together with xbean.jar, but > as > then the compiler complains that the directory does not exist (since it > has > not yet been built). > > The ANT Script I use (based on tutorial at > http://lajavaloca.wordpress.com/2008/05/26/xmlbeans-with-netbeans-thats-a-lot-of-beans/ > ): > > <taskdef name="xmlbean" > classname="org.apache.xmlbeans.impl.tool.XMLBean" > classpath="../3rd Party/xmlbeans-2.4.0/lib/jsr173.jar: ../3rd > Party/xmlbeans-2.4.0/lib/xbean.jar" /> > <target name="-pre-compile"> > <antcall target="gen-schema2"/> > </target> > <target name="gen-schema"> > <xmlbean srconly="true" > verbose="true" > srcgendir="src" > classgendir="build/classes" > download="true" > destfile="DeviceListXmlTypes.jar" > schema="./src/CardWizard/resources/config/DeviceList.xsd"/> > </target> > > Please help, I really need to get XMLBeans working asap. > > Kind Regards > Wynand > > -- View this message in context: http://www.nabble.com/Cannot-load-SchemaTypeSystem-tp25423415p26079975.html Sent from the Xml Beans - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org For additional commands, e-mail: user-help@xmlbeans.apache.org
Thanks Cezar. I was able to generate the necessary output using GDateBuilder. Anirban On Sat, Oct 10, 2009 at 2:32 AM, Cezar Andrei <cezar.andrei@oracle.com> wrote: > Anirban, > > > > Did you look at GDateBuilder, specifically at using normalizeToTimeZone > methods? > > > > Cezar > > > > ________________________________ > > From: Anirban Mukherjee [mailto:amukherj@gmail.com] > Sent: Saturday, September 12, 2009 3:12 PM > To: user@xmlbeans.apache.org > Subject: Output dateTime in canonical form > > > > I wish to generate xml output where xs:dateTime values will be generated in > the canonical form rather than the natural form > > e.g. instead of 2009-10-13T01:11:17+05:30, I need 2009-10-12T19:41:17Z > (converted to UTC with Z indicating that it is UTC) > > Is there a straightforward way to achieve this ? > > The GDate class has a canonicalString() method that produces the form I > need, but the toString() produces the natural form. > > Note: If input xml contains dateTime values in the canonical form, they are > processed properly. > > As an experiment, I tried to inherit a subclass from GDate with the intent > of overriding toString() to invoke super.canonicalString() but the GDate > class is final and hence cannot be extended. > But even that would probably not have worked as the XmlDateTime would > probably not care about the canonical form. Refer below... > [ > GDate gdt = new GDate(cal); > XmlDateTime dt = XmlDateTime.Factory.newInstance(); > dt.setGDateValue(gdt); > sig.xsetExpirationDateTime(dt); > ... > ... > doc.save... > ] > > Any help would be appreciated. > > > Thanks, > Anirban --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org For additional commands, e-mail: user-help@xmlbeans.apache.org
Well, the error message is pretty clear. The xmlbeans your runtime is using has an earlier version than the version of xmlbeans used to compile your schema. You can use schema jars compiled with older versions of xmlbeans than your runtime, but not with newer. The situation is analogous to that of java classes and the jdk. Clearly, weblogic 9x shipped with a version of xmlbeans that is earlier than 2.4. Consult your weblogic documentation or experts on how to use a different version of apache xmlbeans than is shipped with the product. (Weblogic also uses a com.bea-repackaged version of xmlbeans internally; you should not replace this xmlbeans.) - Wing Yew -----Original Message----- From: jh10a957 [mailto:rakeshkumar.singh@gmail.com] Sent: Friday, October 23, 2009 11:02 AM To: user@xmlbeans.apache.org Subject: XML-BEANS compiled schema: Incompatible minor version - expecting up to 23, got 24 I was using xmlbean2.2 and upgraded to xmlbean2.4. Compilation of schema jars are fine but while deploying in Weblogic 9.2 I am getting the exception as below. Anyone else facing the same issue? Caused by: java.lang.RuntimeException: Could not instantiate SchemaTypeSystemImpl (java.lang.reflect.InvocationTargetException): is the version of xbean.jar correct? at schemaorg_apache_xmlbeans.system.sD10023A5BF0E00636EB8A1FCB541F982.TypeSystemHolder.loadTypeSystem(Unknown Source) at schemaorg_apache_xmlbeans.system.sD10023A5BF0E00636EB8A1FCB541F982.TypeSystemHolder.<clinit>(Unknown Source) ... 43 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) ... 45 more Caused by: org.apache.xmlbeans.SchemaTypeLoaderException: XML-BEANS compiled schema: Incompatible minor version - expecting up to 23, got 24 (schemaorg_apache_xmlbeans.system.sD10023A5BF0E00636EB8A1FCB541F982.index) - code 3 at org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$XsbReader.<init>(SchemaTypeSystemImpl.java:1522) at org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.initFromHeader(SchemaTypeSystemImpl.java:260) at org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.<init>(SchemaTypeSystemImpl.java:183) ... 49 more^^ -- View this message in context: http://www.nabble.com/XML-BEANS-compiled-schema%3A-Incompatible-minor-version---expecting-up-to-23%2C-got-24-tp26030820p26030820.html Sent from the Xml Beans - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org For additional commands, e-mail: user-help@xmlbeans.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org For additional commands, e-mail: user-help@xmlbeans.apache.org
I was using xmlbean2.2 and upgraded to xmlbean2.4. Compilation of schema jars are fine but while deploying in Weblogic 9.2 I am getting the exception as below. Anyone else facing the same issue? Caused by: java.lang.RuntimeException: Could not instantiate SchemaTypeSystemImpl (java.lang.reflect.InvocationTargetException): is the version of xbean.jar correct? at schemaorg_apache_xmlbeans.system.sD10023A5BF0E00636EB8A1FCB541F982.TypeSystemHolder.loadTypeSystem(Unknown Source) at schemaorg_apache_xmlbeans.system.sD10023A5BF0E00636EB8A1FCB541F982.TypeSystemHolder.<clinit>(Unknown Source) ... 43 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) ... 45 more Caused by: org.apache.xmlbeans.SchemaTypeLoaderException: XML-BEANS compiled schema: Incompatible minor version - expecting up to 23, got 24 (schemaorg_apache_xmlbeans.system.sD10023A5BF0E00636EB8A1FCB541F982.index) - code 3 at org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$XsbReader.<init>(SchemaTypeSystemImpl.java:1522) at org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.initFromHeader(SchemaTypeSystemImpl.java:260) at org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.<init>(SchemaTypeSystemImpl.java:183) ... 49 more^^ -- View this message in context: http://www.nabble.com/XML-BEANS-compiled-schema%3A-Incompatible-minor-version---expecting-up-to-23%2C-got-24-tp26030820p26030820.html Sent from the Xml Beans - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org For additional commands, e-mail: user-help@xmlbeans.apache.org
Content-type: multipart/alternative;
boundary="Boundary_(ID_Ls0mY350v37mNlWrIMRkZg)"
--Boundary_(ID_Ls0mY350v37mNlWrIMRkZg)
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Content-transfer-encoding: 7BIT
Hi,
I am running into java.lang.NullPointerException in the following
snippet at getSourceAsStream(source);
//get SchemaType for element
SchemaGlobalElement element =
typeLoader.findElement(QName.valueOf("{http://xml.netbeans.org/schema/Synchronous}typeA"));
//confirm element
System.out.println(
"{http://xml.netbeans.org/schema/Synchronous}typeA is:" +
element.getName() );
System.out.println("\t \t" + " -- details ns: " +
element.getName().getNamespaceURI()
+ " prefix: " + element.getName().getPrefix() + "
local name: " + element.getName().getLocalPart());
SchemaType st = element.getType();
// get the name of the schema source file
// Not sure, is it working right?
//schema source doc queried:
URI_SHA_1_E8BB73591F25D088F33651C66E86AE1809406E4B/Synchronous.xsd
//vs original:
file:/C:/tmp/mvnprojects/schemaParser/target/classes/resources/Synchronous.xsd
String source = st.getSourceName();
System.out.println("schema source doc queried: " + source + " vs
original: " + url);
SchemaTypeLoader stl = st.getTypeSystem();
java.io.InputStream is = stl.getSourceAsStream(source);
I am attaching the Java program and maven project to reproduce the
issue. Is this an user error? or an issue?
To build and run the test case
1. unzip attached zip file
2. move to the root folder
3. mvn clean assembly:assembly
4. java -cp
target\schemaParser-1.0-SNAPSHOT-jar-with-dependencies.jar myTest.App
Regards
Murali
--Boundary_(ID_Ls0mY350v37mNlWrIMRkZg)
Content-type: text/html; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
I am running into java.lang.NullPointerException in the following
snippet at getSourceAsStream(source); <br>
<br>
//get SchemaType for
element <br>
SchemaGlobalElement
element =
typeLoader.findElement(QName.valueOf("{<a class="moz-txt-link-freetext" href="http://xml.netbeans.org/schema/Synchronous">http://xml.netbeans.org/schema/Synchronous</a>}typeA"));<br>
//confirm element<br>
System.out.println(
"{<a class="moz-txt-link-freetext" href="http://xml.netbeans.org/schema/Synchronous">http://xml.netbeans.org/schema/Synchronous</a>}typeA
is:" +
element.getName() );<br>
System.out.println("\t \t" +
" -- details ns: " +
element.getName().getNamespaceURI() <br>
+ " prefix: " + element.getName().getPrefix() + "
local name: " + element.getName().getLocalPart());<br>
SchemaType st = element.getType();<br>
<br>
// get the name of
the schema source file <br>
// Not sure, is it
working right? <br>
//schema source doc
queried:
URI_SHA_1_E8BB73591F25D088F33651C66E86AE1809406E4B/Synchronous.xsd <br>
//vs original:
<a class="moz-txt-link-freetext" href="file:/C:/tmp/mvnprojects/schemaParser/target/classes/resources/Synchronous.xsd">file:/C:/tmp/mvnprojects/schemaParser/target/classes/resources/Synchronous.xsd</a><br>
String source = st.getSourceName();
<br>
System.out.println("schema
source doc queried: " + source + "
vs original: " + url);<br>
<br>
SchemaTypeLoader stl
= st.getTypeSystem();<br>
java.io.InputStream
is = stl.getSourceAsStream(source); <br>
<br>
I am attaching the Java program and maven project to reproduce the
issue. Is this an user error? or an issue?<br>
<br>
To build and run the test case <br>
<ol>
<li>unzip attached zip file</li>
<li>move to the root folder<br>
</li>
<li>mvn clean assembly:assembly<br>
</li>
<li>java -cp
target\schemaParser-1.0-SNAPSHOT-jar-with-dependencies.jar myTest.App<br>
</li>
</ol>
Regards<br>
Murali<br>
</body>
</html>
--Boundary_(ID_Ls0mY350v37mNlWrIMRkZg)--
Hi,
I am having some threadsafety issues with testng tests run in parallel
mode. The tests involve connecting to a webservice using spring-ws
configured with xmlbeans marshalling. After reading [1], i was
wondering if the thread safety issue could apply to my case. I will
try to explain with a small block of code that does the webservice
call
Object o1 = null;
GetPaymentDocumentDocument1 requestDocument = null;
try {
requestDocument = GetPaymentDocumentDocument1.Factory.newInstance();
requestDocument.addNewGetPaymentDocument();
GetPaymentDocumentRequest request =
GetPaymentDocumentRequest.Factory.newInstance();
requestDocument.getGetPaymentDocument().setRequest(request);
o1 = PaymentWebService.marshalSendAndReceive(requestDocument);
// POTENTIAL CCE BELOW
GetPaymentDocumentResponseDocument responseDocument =
(GetPaymentDocumentResponseDocument) o1;
return responseDocument.getGetPaymentDocumentResponse().getDocument();
} catch (ClassCastException cce) {
throw new RuntimeException(
(o == null ? "NULL" : o.getClass() + "___" +
o.getClass().getClassLoader()) + ">>>>"
+
GetPaymentDocumentResponseDocument.class.getClassLoader() + ">>>>>>\n"
+ o, cce);
}
In normal non-parallel testing, this code never fails. Recently
however i switched the tests to be run in parallel through TestNG's
parallel=methods feature, meaning that a thread pool is assigned to
execute methods from the test class concurrently.
Since then, the above block of code randomly throws CCE's when i try
to cast the object returned from the webservice to the
"GetPaymentDocumentResponseDocument". After doing some research i
found that o1 as returned from the webservice in these cases is
actually an instance of GetPaymentDocumentDocument1 (ie the request
document) !
Could this problem be related to XmlBeans ? Following [1] I built
xmlbeans myself from source a few weeks ago but that didn't change
anything. Any thoughts would be greatly appreciated. I tried to narrow
things down to a small testcase but i could never consistently
reproduce it.
Thanks !
Jorg
[1] http://www.mail-archive.com/user@xmlbeans.apache.org/msg03818.html
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: user-help@xmlbeans.apache.org
Hi
I'm writing a method to set the default namespace of a given XML fragment:
public static XmlObject setDefaultNamespace(XmlObject xmlFragment,
String namespace) {
XmlCursor eltCursor = xmlFragment.newCursor();
if (eltCursor.currentTokenType().isStartdoc())
eltCursor.toNextToken();
String defaultNs = eltCursor.namespaceForPrefix("");
if (defaultNs == null || defaultNs.length() == 0) {
System.out.println("No default namespace detected!");
eltCursor.insertNamespace("", namespace);
}
eltCursor.dispose();
return xmlFragment;
}
The call to "eltCursor.insertNamespace("", namespace);" does not work, it
doesn't set the default namespace in the result returned. I observed that it
works only when the prefix is set (eg. eltCursor.insertNamespace("pre",
namespace);).
What am I doing wrong ?
Thanks in advance for any help
Pascal
Anirban, Did you look at GDateBuilder, specifically at using normalizeToTimeZone methods? Cezar _____ From: Anirban Mukherjee [mailto:amukherj@gmail.com] Sent: Saturday, September 12, 2009 3:12 PM To: user@xmlbeans.apache.org Subject: Output dateTime in canonical form I wish to generate xml output where xs:dateTime values will be generated in the canonical form rather than the natural form e.g. instead of 2009-10-13T01:11:17+05:30, I need 2009-10-12T19:41:17Z (converted to UTC with Z indicating that it is UTC) Is there a straightforward way to achieve this ? The GDate class has a canonicalString() method that produces the form I need, but the toString() produces the natural form. Note: If input xml contains dateTime values in the canonical form, they are processed properly. As an experiment, I tried to inherit a subclass from GDate with the intent of overriding toString() to invoke super.canonicalString() but the GDate class is final and hence cannot be extended. But even that would probably not have worked as the XmlDateTime would probably not care about the canonical form. Refer below... [ GDate gdt = new GDate(cal); XmlDateTime dt = XmlDateTime.Factory.newInstance(); dt.setGDateValue(gdt); sig.xsetExpirationDateTime(dt); ... ... doc.save... ] Any help would be appreciated. Thanks, Anirban
Hi Mike, yesterday tried to solve exactly this problem. With your description it works. Thanks a lot. Regards, Oliver -----Ursprüngliche Nachricht----- Von: Michael Furtak [mailto:mfurtak@cra.com] Gesendet: Dienstag, 6. Oktober 2009 21:33 An: user@xmlbeans.apache.org Betreff: SchemaTypeLoader problems in Equinox (OSGi): A solution Hi, all. This is my first message to the mailing list, so I apologize if I am stating some very old news. Recently I have been encountering some classloading problems when using XMLBeans in an OSGi environment (Equinox), and I have seen some other users with similar issues [1, 2]. The common symptom was that xsi:type information could neither be generated, nor interpreted while running in an OSGi environment. To my understanding, the use of the Thread Context ClassLoader, within the SchemaTypeLoader [3] needs some extra help to work properly within an OSGi environment. Equinox provides this help in the form of "Buddy Class Loading" (unfortunately, this is *not* part of the OSGi spec, making it an Equinox specific fix) [4]. By marking the XMLBeans bundle with an Eclipse-BuddyPolicy header in its manifest, and the compiled schema bundle with an Eclipse-RegisterBuddy header in its manifest, Equinox is able to bridge the classloading gap between the core XMLBeans jar and your compiled schema classes. Assuming that my XMLBeans bundle has: Bundle-SymbolicName: org.apache.xmlbeans I would include in that XMLBeans bundle manifest the line: Eclipse-BuddyPolicy: registered I would then alter my scomp'd schema classes bundle manifest to include: Eclipse-RegisterBuddy: org.apache.xmlbeans After doing this, my problems are resolved. I hope this can help someone else, and was not incredibly old news. Regards, -Mike Furtak 1) http://markmail.org/message/vx2vdg7yhb4l3ej6#query:+page:1+mid:vx2vdg7yh b4l3ej6+state:results 2) http://mail-archives.apache.org/mod_mbox/ws-axis-user/200701.mbox/%3C8d2 a81130701171341p55f95b70o7f144ea7d941639a@mail.gmail.com%3E 3) http://grepcode.com/file/repo1.maven.org$maven2@org.apache.xmlbeans$xmlb eans@2.4.0@org$apache$xmlbeans$impl$schema$SchemaTypeLoaderImpl.java#Sch emaTypeLoaderImpl.getContextTypeLoader%28%29 4) http://wiki.eclipse.org/index.php/Context_Class_Loader_Enhancements#Ecli pse-BuddyPolicy_Header THIS MESSAGE IS INTENDED FOR THE USE OF THE PERSON TO WHOM IT IS ADDRESSED. IT MAY CONTAIN INFORMATION THAT IS PRIVILEGED, CONFIDENTIAL AND EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW. If you are not the intended recipient, your use of this message for any purpose is strictly prohibited. If you have received this communication in error, please delete the message and notify the sender so that we may correct our records. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org For additional commands, e-mail: user-help@xmlbeans.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org For additional commands, e-mail: user-help@xmlbeans.apache.org
Thanks Mike! I'll add this to the FAQs when I get a chance. -jacobd On Tue, Oct 6, 2009 at 12:33 PM, Michael Furtak <mfurtak@cra.com> wrote: > Hi, all. This is my first message to the mailing list, so I apologize if > I am stating some very old news. > > > Recently I have been encountering some classloading problems when using > XMLBeans in an OSGi environment (Equinox), and I have seen some other > users with similar issues [1, 2]. The common symptom was that xsi:type > information could neither be generated, nor interpreted while running in > an OSGi environment. > > To my understanding, the use of the Thread Context ClassLoader, within > the SchemaTypeLoader [3] needs some extra help to work properly within > an OSGi environment. Equinox provides this help in the form of "Buddy > Class Loading" (unfortunately, this is *not* part of the OSGi spec, > making it an Equinox specific fix) [4]. > > By marking the XMLBeans bundle with an Eclipse-BuddyPolicy header in its > manifest, and the compiled schema bundle with an Eclipse-RegisterBuddy > header in its manifest, Equinox is able to bridge the classloading gap > between the core XMLBeans jar and your compiled schema classes. > > > Assuming that my XMLBeans bundle has: > > Bundle-SymbolicName: org.apache.xmlbeans > > > I would include in that XMLBeans bundle manifest the line: > > Eclipse-BuddyPolicy: registered > > > I would then alter my scomp'd schema classes bundle manifest to include: > > Eclipse-RegisterBuddy: org.apache.xmlbeans > > > After doing this, my problems are resolved. I hope this can help someone > else, and was not incredibly old news. > > > Regards, > -Mike Furtak > > > 1) > http://markmail.org/message/vx2vdg7yhb4l3ej6#query:+page:1+mid:vx2vdg7yh > b4l3ej6+state:results<http://markmail.org/message/vx2vdg7yhb4l3ej6#query:+page:1+mid:vx2vdg7yh%0Ab4l3ej6+state:results> > > 2) > http://mail-archives.apache.org/mod_mbox/ws-axis-user/200701.mbox/%3C8d2 > a81130701171341p55f95b70o7f144ea7d941639a@mail.gmail.com%3E > > 3) > http://grepcode.com/file/repo1.maven.org$maven2@org.apache.xmlbeans$xmlb > eans@2.4.0@org$apache$xmlbeans$impl$schema$SchemaTypeLoaderImpl.java#Sch > emaTypeLoaderImpl.getContextTypeLoader%28%29 > > 4) > http://wiki.eclipse.org/index.php/Context_Class_Loader_Enhancements#Ecli > pse-BuddyPolicy_Header<http://wiki.eclipse.org/index.php/Context_Class_Loader_Enhancements#Ecli%0Apse-BuddyPolicy_Header> > > > > > THIS MESSAGE IS INTENDED FOR THE USE OF THE PERSON TO WHOM IT IS ADDRESSED. > IT MAY CONTAIN INFORMATION THAT IS PRIVILEGED, CONFIDENTIAL AND EXEMPT FROM > DISCLOSURE UNDER APPLICABLE LAW. If you are not the intended recipient, your > use of this message for any purpose is strictly prohibited. If you have > received this communication in error, please delete the message and notify > the sender so that we may correct our records. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org > For additional commands, e-mail: user-help@xmlbeans.apache.org > >
Hi, all. This is my first message to the mailing list, so I apologize if I am stating some very old news. Recently I have been encountering some classloading problems when using XMLBeans in an OSGi environment (Equinox), and I have seen some other users with similar issues [1, 2]. The common symptom was that xsi:type information could neither be generated, nor interpreted while running in an OSGi environment. To my understanding, the use of the Thread Context ClassLoader, within the SchemaTypeLoader [3] needs some extra help to work properly within an OSGi environment. Equinox provides this help in the form of "Buddy Class Loading" (unfortunately, this is *not* part of the OSGi spec, making it an Equinox specific fix) [4]. By marking the XMLBeans bundle with an Eclipse-BuddyPolicy header in its manifest, and the compiled schema bundle with an Eclipse-RegisterBuddy header in its manifest, Equinox is able to bridge the classloading gap between the core XMLBeans jar and your compiled schema classes. Assuming that my XMLBeans bundle has: Bundle-SymbolicName: org.apache.xmlbeans I would include in that XMLBeans bundle manifest the line: Eclipse-BuddyPolicy: registered I would then alter my scomp'd schema classes bundle manifest to include: Eclipse-RegisterBuddy: org.apache.xmlbeans After doing this, my problems are resolved. I hope this can help someone else, and was not incredibly old news. Regards, -Mike Furtak 1) http://markmail.org/message/vx2vdg7yhb4l3ej6#query:+page:1+mid:vx2vdg7yh b4l3ej6+state:results 2) http://mail-archives.apache.org/mod_mbox/ws-axis-user/200701.mbox/%3C8d2 a81130701171341p55f95b70o7f144ea7d941639a@mail.gmail.com%3E 3) http://grepcode.com/file/repo1.maven.org$maven2@org.apache.xmlbeans$xmlb eans@2.4.0@org$apache$xmlbeans$impl$schema$SchemaTypeLoaderImpl.java#Sch emaTypeLoaderImpl.getContextTypeLoader%28%29 4) http://wiki.eclipse.org/index.php/Context_Class_Loader_Enhancements#Ecli pse-BuddyPolicy_Header THIS MESSAGE IS INTENDED FOR THE USE OF THE PERSON TO WHOM IT IS ADDRESSED. IT MAY CONTAIN INFORMATION THAT IS PRIVILEGED, CONFIDENTIAL AND EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW. If you are not the intended recipient, your use of this message for any purpose is strictly prohibited. If you have received this communication in error, please delete the message and notify the sender so that we may correct our records. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org For additional commands, e-mail: user-help@xmlbeans.apache.org
Hi, I figured out that the problem is not in the xsd definitions. In the main method of a test class all works. In my application no more. I assume it is because it is an osgi application. Someone an idea what I can do ? Regards Oliver -----Ursprüngliche Nachricht----- Von: Oliver Pfau Gesendet: Dienstag, 6. Oktober 2009 10:31 An: 'user@xmlbeans.apache.org' Betreff: Inheritance problem, instance gets always super type Hi , instance gets always super type Hi, I have a problem using xmlbeans with inherited types with java. In my commons.xsd there is a complex type Operation and some other types which are extending Operation. In a MoreSpecifix.xsd is commons.xsd imported and a complex type Config is declared. This type Config does declare a sequence of Operation. So it should be possible to add all types which extend Operation to the sequence in Config. After the generation of the java classes I run into the following problems: First try: final ConfigDocument configDocument = ConfigDocument.Factory.newInstance(); final Config newConfig = configDocument.addNewConfig(); final Operation[] ops = new OperationType[1]; ops[0] = createConcreteOperationDummy(); newConfig.setOperationArray(ops); With the last line my concrete operation instance gets the type from the super class Operation and I can no more access the extended fields. Second try: final ConfigDocument configDocument = ConfigDocument.Factory.newInstance(); final Config newConfig = configDocument.addNewConfig(); final Operation newOperation = newConfig.addNewOperation(); final ConcreteOperation concreteOp = (ConcreteOperation) newOperation.changeType(ConcreteOperation.type); On the last line I get a ClassCastException. Has someone an idea what is wrong ? Probably the xsd definitions (made with XMLSpy) ? Regards, Oliver --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org For additional commands, e-mail: user-help@xmlbeans.apache.org
Hi , instance gets always super type Hi, I have a problem using xmlbeans with inherited types with java. In my commons.xsd there is a complex type Operation and some other types which are extending Operation. In a MoreSpecifix.xsd is commons.xsd imported and a complex type Config is declared. This type Config does declare a sequence of Operation. So it should be possible to add all types which extend Operation to the sequence in Config. After the generation of the java classes I run into the following problems: First try: final ConfigDocument configDocument = ConfigDocument.Factory.newInstance(); final Config newConfig = configDocument.addNewConfig(); final Operation[] ops = new OperationType[1]; ops[0] = createConcreteOperationDummy(); newConfig.setOperationArray(ops); With the last line my concrete operation instance gets the type from the super class Operation and I can no more access the extended fields. Second try: final ConfigDocument configDocument = ConfigDocument.Factory.newInstance(); final Config newConfig = configDocument.addNewConfig(); final Operation newOperation = newConfig.addNewOperation(); final ConcreteOperation concreteOp = (ConcreteOperation) newOperation.changeType(ConcreteOperation.type); On the last line I get a ClassCastException. Has someone an idea what is wrong ? Probably the xsd definitions (made with XMLSpy) ? Regards, Oliver --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org For additional commands, e-mail: user-help@xmlbeans.apache.org
Hi
I've wrote the following helper method to create or replace an XML element
into an XML document (this may help others).
I notice that I must specify the default namespace into my XML element (elt
parameter below), otherwise when the element is inserted xmlbeans add a
default one with no value ?! If I add an XML element <rule> into a <ruleset>
document, I get:
<ruleset xmlns="urn:ietf:params:xml:ns:common-policy">
<rule id="rule_1253695448_0" *xmlns=""*>
[...]
</rule>
</ruleset>
... and of course it does not validate against the schema.
What should I do in order to remove this value ? Or what should I do to
automatically set a default namespace to elt if it has none ?
Here's the code of my method, making use of XmlCursor.copyXml():
public static void createReplaceElement(XmlObject doc, String namespace,
XmlObject elt, String xpathQuery) {
int index;
// Create a cursor and move it to the position defined by XPath
query
XmlCursor docCursor = doc.newCursor();
String query = "declare default element namespace '" + namespace +
"';" + xpathQuery;
docCursor.selectPath(query);
// If element already exists, delete it first (Replace case)
if (docCursor.toNextSelection()) {
docCursor.removeXml();
// keep the cursor to insert the new element in the same place.
}
// Create case (element does not already exist)
else {
System.out.println("XmlBeansHelper: Element doesn't exist yet");
index = xpathQuery.lastIndexOf("/");
if (index != -1) {
String q = xpathQuery.substring(0, index);
query ="declare default element namespace '" + namespace +
"';" + q;
docCursor.selectPath(query);
if (docCursor.toNextSelection()) {
if (!docCursor.toFirstChild())
docCursor.toEndToken();
}
else
return;
}
}
// Element cursor
XmlCursor eltCursor = elt.newCursor();
if (eltCursor.currentTokenType().isStartdoc())
eltCursor.toNextToken();
eltCursor.copyXml(docCursor);
docCursor.dispose();
eltCursor.dispose();
}
Best Regards,
Pascal
Thanks a lot Jeff. My xmlobj is indeed at the document level. I'll try the approach you've suggested. Thanks again. Gugle. On Mon, Oct 5, 2009 at 3:33 PM, Jeff Lusted <jl99@star.le.ac.uk> wrote: > Hi Gugle! > > Yes indeed, that is what I am suggesting, provided the xmlobj you create > is at the document level, I believe. (So the token source would be the > equivalent of XmlCursor.TokenType of STARTDOC ... the singleton > start-document token type). I don't think the cast will be correct > otherwise. > > Regards > Jeff > > On Mon, 2009-10-05 at 15:09 +0530, first last wrote: > > Hi Jeff, > > Thanks for the quick respons. Are you suggesting that I do the > > following? > > > > > > org.apache.xmlbeans.xmlobject xmlObj = null; > > ... > > create/populate the xmlObj > > .... > > //directly typecast the xmlobj to Document > > org.w3c.dom.Document nd = (Document) xmlObj.getDomNode(); > > > > > > Is this correct? > > > > > > Regards, > > Gugle > > > > > > > > > > On Mon, Oct 5, 2009 at 2:50 PM, Jeff Lusted <jl99@star.le.ac.uk> > > wrote: > > Hi Gugle! > > > > > > On Mon, 2009-10-05 at 14:03 +0530, first last wrote: > > > Hi all, > > > I'm using XMLBeans to create an XML object which is of > > > type org.apache.xmlbeans.xmlobject. But I need to pass this > > XML > > > content to an API which expects an XML of type - > > org.w3c.dom.Document. > > > Does XMLBeans provide a direct way of converting from > > xmlobject to > > > dom.Document? I noticed that we can go from XmlObject to > > org.w3c.dom > > > Node Object using XmlObject.newDomNode(), but not sure how > > to get a > > > dom.Document object from XMLobject. Can someone let me know > > if this is > > > possible? > > > > > > My understanding is that if you use the XmlObject that is the > > equivalent > > of the document interface, then yourXmlObject.getDomNode() > > should return > > the correct Dom Node and this used tocast to a > > org.w3c.dom.Document... > > > > >From the api... > > > > > public Node getDomNode() > > > > > > > > > Returns a W3C DOM Node containing the XML represented by > > this source. > > > This is a live DOM node, not a copy. Any changes made > > through this > > > node are immediately reflected in the document associated > > with this > > > token source. Depending on the kind of token this > > XmlTokenSource > > > represents, an appropriate node will be returned. > > > > Haven't tried this any time recently. Hope my understanding is > > good. > > Regards > > Jeff > > -- > > Jeff Lusted tel: +44 (0)116 252 3581 > > Astrogrid Project mob: +44 (0)7941 599062 > > Dept Physics & Astronomy email: jl99@star.le.ac.uk > > University of Leicester web: http://www.astrogrid.org > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org > > For additional commands, e-mail: user-help@xmlbeans.apache.org > > > > > > > -- > Jeff Lusted tel: +44 (0)116 252 3581 > Astrogrid Project mob: +44 (0)7941 599062 > Dept Physics & Astronomy email: jl99@star.le.ac.uk > University of Leicester web: http://www.astrogrid.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org > For additional commands, e-mail: user-help@xmlbeans.apache.org > >
Hi Gugle! Yes indeed, that is what I am suggesting, provided the xmlobj you create is at the document level, I believe. (So the token source would be the equivalent of XmlCursor.TokenType of STARTDOC ... the singleton start-document token type). I don't think the cast will be correct otherwise. Regards Jeff On Mon, 2009-10-05 at 15:09 +0530, first last wrote: > Hi Jeff, > Thanks for the quick respons. Are you suggesting that I do the > following? > > > org.apache.xmlbeans.xmlobject xmlObj = null; > ... > create/populate the xmlObj > .... > //directly typecast the xmlobj to Document > org.w3c.dom.Document nd = (Document) xmlObj.getDomNode(); > > > Is this correct? > > > Regards, > Gugle > > > > > On Mon, Oct 5, 2009 at 2:50 PM, Jeff Lusted <jl99@star.le.ac.uk> > wrote: > Hi Gugle! > > > On Mon, 2009-10-05 at 14:03 +0530, first last wrote: > > Hi all, > > I'm using XMLBeans to create an XML object which is of > > type org.apache.xmlbeans.xmlobject. But I need to pass this > XML > > content to an API which expects an XML of type - > org.w3c.dom.Document. > > Does XMLBeans provide a direct way of converting from > xmlobject to > > dom.Document? I noticed that we can go from XmlObject to > org.w3c.dom > > Node Object using XmlObject.newDomNode(), but not sure how > to get a > > dom.Document object from XMLobject. Can someone let me know > if this is > > possible? > > > My understanding is that if you use the XmlObject that is the > equivalent > of the document interface, then yourXmlObject.getDomNode() > should return > the correct Dom Node and this used tocast to a > org.w3c.dom.Document... > > >From the api... > > > public Node getDomNode() > > > > > > Returns a W3C DOM Node containing the XML represented by > this source. > > This is a live DOM node, not a copy. Any changes made > through this > > node are immediately reflected in the document associated > with this > > token source. Depending on the kind of token this > XmlTokenSource > > represents, an appropriate node will be returned. > > Haven't tried this any time recently. Hope my understanding is > good. > Regards > Jeff > -- > Jeff Lusted tel: +44 (0)116 252 3581 > Astrogrid Project mob: +44 (0)7941 599062 > Dept Physics & Astronomy email: jl99@star.le.ac.uk > University of Leicester web: http://www.astrogrid.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org > For additional commands, e-mail: user-help@xmlbeans.apache.org > > > -- Jeff Lusted tel: +44 (0)116 252 3581 Astrogrid Project mob: +44 (0)7941 599062 Dept Physics & Astronomy email: jl99@star.le.ac.uk University of Leicester web: http://www.astrogrid.org --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org For additional commands, e-mail: user-help@xmlbeans.apache.org
Hi Jeff,Thanks for the quick respons. Are you suggesting that I do the following? org.apache.xmlbeans.xmlobject xmlObj = null; ... create/populate the xmlObj .... //directly typecast the xmlobj to Document org.w3c.dom.Document nd = (Document) xmlObj.getDomNode(); Is this correct? Regards, Gugle On Mon, Oct 5, 2009 at 2:50 PM, Jeff Lusted <jl99@star.le.ac.uk> wrote: > Hi Gugle! > > On Mon, 2009-10-05 at 14:03 +0530, first last wrote: > > Hi all, > > I'm using XMLBeans to create an XML object which is of > > type org.apache.xmlbeans.xmlobject. But I need to pass this XML > > content to an API which expects an XML of type - org.w3c.dom.Document. > > Does XMLBeans provide a direct way of converting from xmlobject to > > dom.Document? I noticed that we can go from XmlObject to org.w3c.dom > > Node Object using XmlObject.newDomNode(), but not sure how to get a > > dom.Document object from XMLobject. Can someone let me know if this is > > possible? > > My understanding is that if you use the XmlObject that is the equivalent > of the document interface, then yourXmlObject.getDomNode() should return > the correct Dom Node and this used tocast to a org.w3c.dom.Document... > > >From the api... > > > public Node getDomNode() > > > > > > Returns a W3C DOM Node containing the XML represented by this source. > > This is a live DOM node, not a copy. Any changes made through this > > node are immediately reflected in the document associated with this > > token source. Depending on the kind of token this XmlTokenSource > > represents, an appropriate node will be returned. > > Haven't tried this any time recently. Hope my understanding is good. > Regards > Jeff > -- > Jeff Lusted tel: +44 (0)116 252 3581 > Astrogrid Project mob: +44 (0)7941 599062 > Dept Physics & Astronomy email: jl99@star.le.ac.uk > University of Leicester web: http://www.astrogrid.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org > For additional commands, e-mail: user-help@xmlbeans.apache.org > >
Hi Gugle! On Mon, 2009-10-05 at 14:03 +0530, first last wrote: > Hi all, > I'm using XMLBeans to create an XML object which is of > type org.apache.xmlbeans.xmlobject. But I need to pass this XML > content to an API which expects an XML of type - org.w3c.dom.Document. > Does XMLBeans provide a direct way of converting from xmlobject to > dom.Document? I noticed that we can go from XmlObject to org.w3c.dom > Node Object using XmlObject.newDomNode(), but not sure how to get a > dom.Document object from XMLobject. Can someone let me know if this is > possible? My understanding is that if you use the XmlObject that is the equivalent of the document interface, then yourXmlObject.getDomNode() should return the correct Dom Node and this used tocast to a org.w3c.dom.Document... >>From the api... > public Node getDomNode() > > > Returns a W3C DOM Node containing the XML represented by this source. > This is a live DOM node, not a copy. Any changes made through this > node are immediately reflected in the document associated with this > token source. Depending on the kind of token this XmlTokenSource > represents, an appropriate node will be returned. Haven't tried this any time recently. Hope my understanding is good. Regards Jeff -- Jeff Lusted tel: +44 (0)116 252 3581 Astrogrid Project mob: +44 (0)7941 599062 Dept Physics & Astronomy email: jl99@star.le.ac.uk University of Leicester web: http://www.astrogrid.org --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org For additional commands, e-mail: user-help@xmlbeans.apache.org
Hi all,I'm using XMLBeans to create an XML object which is of type org.apache.xmlbeans.xmlobject. But I need to pass this XML content to an API which expects an XML of type - org.w3c.dom.Document. Does XMLBeans provide a direct way of converting from xmlobject to dom.Document? I noticed that we can go from XmlObject to org.w3c.dom Node Object using XmlObject.newDomNode(), but not sure how to get a dom.Document object from XMLobject. Can someone let me know if this is possible? Thanks in advance for your help. Regards, Gugle