from:"Jacob Danner"

[
https://issues.apache.org/jira/browse/XMLBEANS-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jacob Danner resolved XMLBEANS-248.
---

Resolution: Cannot Reproduce
Fix Version/s: (was: Version 1)

I tried to create a sample repro case for this using the latest XMLBeans and
could not get any such error to repro.
Given date, suggesting close.

Cannot parse/validate xml-fragments that use default namespace
--

Key: XMLBEANS-248
URL: https://issues.apache.org/jira/browse/XMLBEANS-248
Project: XMLBeans
Issue Type: Bug
Components: XmlObject
Affects Versions: Version 1
Environment: Win2K, Java 1.4
Reporter: Mark Cohen

I recently ran into a problem with XMLBeans 1.0.2 parsing and validating
XmlObjects. Here's the scenario:
I have a simple XML schema which I then turned into XMLBeans using the
org.apache.xmlbeans.impl.tool.XMLBean class. For the sake of discussion, the
namespace for the schema is http://common.toolkit/bean, and the package for
the generated beans is toolkit.common.bean.
Next, I want to convert an XML fragment to an XMLBean. (I know, ideally
there wouldn't be XML fragments, but there's not much I can do about it for
now.) If I have something like the following... (Please ignore any obvious
syntax errors -- I'm re-typing this.)
xml-fragment xmlns:bean=http://common.toolkit/bean;
bean:field1value/bean:field1
bean:field2value/bean:field2
/xml-fragment
... and I run it through a parse and a validation...
MyClass myObject = MyClass.Factory.parse(xml);
myObject.validate();
... everything works fine. If, however, I use the following XML instead...
xml-fragment xmlns=http://common.toolkit/bean;
field1value/field1
field2value/field2
/xml-fragment
... the validation fails. The error is along the lines of:
Message: Expected element text-
fie...@http://common.toolkit/bean instead of
xml-fragm...@http://common.toolkit/bean here
Location of invalid XML: [my XML fragment repeated here]
Thoughts/ideas? Thanks in advance!

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

-
To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
For additional commands, e-mail: dev-h...@xmlbeans.apache.org

[jira] Resolved: (XMLBEANS-250) Validation fails on an xml whose root node is unknown

[
https://issues.apache.org/jira/browse/XMLBEANS-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jacob Danner resolved XMLBEANS-250.
---

Resolution: Cannot Reproduce

Unable to reproduce this using information given from bug. If this is still an
issue for you from this scenario, please include a test case and/or include
information from error listener in xmloptions.setErrorListener to see detailed
information about the issue.

Validation fails on an xml whose root node is unknown
-

Key: XMLBEANS-250
URL: https://issues.apache.org/jira/browse/XMLBEANS-250
Project: XMLBeans
Issue Type: Bug
Components: Validator
Affects Versions: Version 2
Reporter: rafiq ahmad
Fix For: Version 2

I am trying to validate an xml file whose root node is unknown. So I am using
the following code to parse and validate but validation fails.
XMLObject xmlObject = XmlObject.Factory.parse(new FileReader(file));
boolean isValid = xmlObject.validate(); //isValid becomes false eventhough
file is valid
When I looked at closely, I notice xmlObject is not pointing to the root
document object (In my case ReturnDataDocument since ReturnData is the root
node of xml) but pointing to XmlAnyTypeImpl.
When I use the specific object , it works.
ReturnDataDocument xmlObject = ReturnDataDocument .Factory.parse(new
FileReader(file));
boolean isValid = xmlObject.validate(); //isValid is true

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

-
To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
For additional commands, e-mail: dev-h...@xmlbeans.apache.org

[jira] Resolved: (XMLBEANS-229) addXXX method not generated


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacob Danner resolved XMLBEANS-229.
---

Resolution: Won't Fix

This seems like a doc issue more than anything. Note that this should be 
possible when compiling the schema with 
-javasource 1.5 
then doing something like 
getLineItemList().add(...)

 addXXX method not generated
 ---

 Key: XMLBEANS-229
 URL: https://issues.apache.org/jira/browse/XMLBEANS-229
 Project: XMLBeans
  Issue Type: Bug
Affects Versions: Version 2, Version 2.1
 Environment: Windows XP
Reporter: Michael Hill
 Attachments: test.xsd


 When generating Multiple Occurrence Methods the , void addXXX(XXXType 
 newValue) which is supposed to add the specified XXX to the end of the list 
 of XXX child elements is not being generated.
 Does this require some configuration?
 See below for added comments.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
For additional commands, e-mail: dev-h...@xmlbeans.apache.org

[jira] Resolved: (XMLBEANS-240) ArrayStoreException when invoking XmlObject.selectPath()


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacob Danner resolved XMLBEANS-240.
---

Resolution: Fixed

I think this has already been fixed. I know I'm missing context from 05, but by 
simple repro case worked without arraystore exception being thrown

 ArrayStoreException when invoking XmlObject.selectPath()
 

 Key: XMLBEANS-240
 URL: https://issues.apache.org/jira/browse/XMLBEANS-240
 Project: XMLBeans
  Issue Type: Bug
  Components: XPath
Affects Versions: Version 2, Version 2.1
Reporter: Radu Preotiuc-Pietro
Assignee: Cezar Andrei

 Copied from message:
 I've been getting some ArrayStoreException errors when invoking the 
 selectPath() method in an XmlObject subclass. Tracking the traceback 
 exception I noticed that this occurs in the XmlObjectBase._typedArray() 
 method, when the input array argument has a XmlAnyTypeImpl object and the 
 System.arraycopy is invoked.
 I'm failing to understand what's the need of having a _typedArray() because 
 apparently it can't handle XmlAnyTypeImpl classes and every class (including 
 the XmlAnyTypeImpl class) implements the XmlObject interface. 
 Given that both selectPath(String,XmlOptions) and 
 execQuery(String,XmlOptions) return a XmlObject[] and these are invokers of 
 the _typedArray() method, what is the need for a method that crashes and 
 apparently is redundant?
 Cheers,
 Celso

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
For additional commands, e-mail: dev-h...@xmlbeans.apache.org

[jira] Commented: (XMLBEANS-235) scomp fails with error encoded string too long


[ 
https://issues.apache.org/jira/browse/XMLBEANS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12772366#action_12772366
 ] 

Jacob Danner commented on XMLBEANS-235:
---

Can you attach or reference a schema to be used for reproducing this issue. I 
think I've seen similar from an xsd with 75K enum values and this hit a 
limitation in java.

 scomp fails with error encoded string too long
 

 Key: XMLBEANS-235
 URL: https://issues.apache.org/jira/browse/XMLBEANS-235
 Project: XMLBeans
  Issue Type: Bug
Affects Versions: Version 2.1
 Environment: WIndows XP, J2SE Version 1.5.0 (build 1.5.0_06-b05)
Reporter: Chris Isbell
Priority: Blocker

 scomp fails with the following output:
 Time to build schema type system: 1.492 seconds
 Exception in thread main org.apache.xmlbeans.SchemaTypeLoaderException: 
 encoded string too long: 80643 bytes 
 (schemaorg_apache_xmlbeans.system.sD8C47734011B153A3D6BBC3BCCA9AC04.allassetsmodelgroup)
  - code 9
   at 
 org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$StringPool.writeTo(SchemaTypeSystemImpl.java:1021)
   at 
 org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$XsbReader.writeRealHeader(SchemaTypeSystemImpl.java:1602)
   at 
 org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.saveModelGroup(SchemaTypeSystemImpl.java:1406)
   at 
 org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.saveModelGroups(SchemaTypeSystemImpl.java:1347)
   at 
 org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.save(SchemaTypeSystemImpl.java:1296)
   at 
 org.apache.xmlbeans.impl.tool.SchemaCompiler.compile(SchemaCompiler.java:1098)
   at 
 org.apache.xmlbeans.impl.tool.SchemaCompiler.main(SchemaCompiler.java:368)
 The problem appears to be with the line output.writeUTF(str); in the method 
 writeTo in class org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl (line 
 1016). java.io.DataOutputStream.writeUTF has an implicit 64K byte length 
 limit (because it stores the length in a two-byte integer) and this limit is 
 being exceeded.
 The schema I am compiling comes from a third party and it is unlikely that it 
 can be modified to work around this problem.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
For additional commands, e-mail: dev-h...@xmlbeans.apache.org

[jira] Closed: (XMLBEANS-231) Parsing embedded xml to cdata


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacob Danner closed XMLBEANS-231.
-

Resolution: Incomplete

No word back on this one since 05, closing

 Parsing embedded xml to cdata
 -

 Key: XMLBEANS-231
 URL: https://issues.apache.org/jira/browse/XMLBEANS-231
 Project: XMLBeans
  Issue Type: Bug
Affects Versions: Version 2.1
 Environment: Windows XP, Sun One 7, XmlBeans 2.10
Reporter: Ricardo

 I am parsing an xml document  which has another xml document, but the xml 
 which is into the first xml is escaped, I mean : 
  lt;?xml version=quot;1.0quot; ?gt;
 I am calling to XmlObject.factory.parse with the xml as a string and I am 
 gettin the xml which is embedded as a CDATA section and the characters ,  
 and , but I don't want a CDATA section neither the tags, so I want the xml 
 as is in the string.
 I have been looking in Jira but I haven't got the solution, I am working with 
 xmlbeans 2.1, but I don't know what to do to get this.
 Thank you.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
For additional commands, e-mail: dev-h...@xmlbeans.apache.org

[jira] Updated: (XMLBEANS-131) ArrayIndexOutOfBoundsException when extension defines overloaded methods


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacob Danner updated XMLBEANS-131:
--

Summary: ArrayIndexOutOfBoundsException when extension defines overloaded 
methods  (was: XmlBeans ant task throws ArrayIndexOutOfBoundsException)

 ArrayIndexOutOfBoundsException when extension defines overloaded methods
 

 Key: XMLBEANS-131
 URL: https://issues.apache.org/jira/browse/XMLBEANS-131
 Project: XMLBeans
  Issue Type: Bug
  Components: Binding
Affects Versions: Version 2 Beta 1
 Environment: Windows XP
 jdk 1.4.06
 ant 1.6
Reporter: Roshan Punnoose
Assignee: Cezar Andrei

 I am using the XMLBeans 2.0 beta. Specifically I am using the Extensions 
 capability that is built in with this version.
 If I have a function with more than 2 parameters, for example:
 public EventRef createEventRef(String identifier, String href, String temp);
 in my interface and handler, the xmlbeans ant task to generate a jar file 
 will throw this error:
 java.lang.ArrayIndexOutOfBoundsException: 2
 If I take the String temp out:
 public EventRef createEventRef(String identifier, String href);
 it works perfectly.
 Thank You.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
For additional commands, e-mail: dev-h...@xmlbeans.apache.org

[jira] Closed: (XMLBEANS-194) XmlBeans generates incorrect code for complex types w/simple content and attributes with use=prohibited


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacob Danner closed XMLBEANS-194.
-

   Resolution: Cannot Reproduce
Fix Version/s: (was: TBD)
   Version 2.4.1 

Compilation succeeded for me
scomp -dl basicTypes.xsd gml4swe.xsd

Closing

 XmlBeans generates incorrect code for complex types w/simple content and 
 attributes with use=prohibited
 -

 Key: XMLBEANS-194
 URL: https://issues.apache.org/jira/browse/XMLBEANS-194
 Project: XMLBeans
  Issue Type: Bug
  Components: Binding
Reporter: Radu Preotiuc-Pietro
 Fix For: Version 2.4.1 

 Attachments: basicTypes.xsd, gml4swe.xsd


 Errors like the following are output by javac when compiling the generated 
 classes:
 src\net\opengis\swe\impl\SoftTypedMeasureInt
 ervalTypeImpl.java:14: 
 net.opengis.swe.impl.SoftTypedMeasureIntervalTypeImpl is not abstract and 
 does not override abstract method unsetCount() in 
 net.opengis.swe.SoftTypedMeasureOrNullListType
 public class SoftTypedMeasureIntervalTypeImpl extends 
 org.apache.xmlbeans.impl.values.XmlListImpl implements 
 net.opengis.swe.SoftTypedMeasureIntervalType

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
For additional commands, e-mail: dev-h...@xmlbeans.apache.org

[jira] Closed: (XMLBEANS-190) Namespaces in QName is not preserved after copy of the XMLBeans from one tree to anoter.


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacob Danner closed XMLBEANS-190.
-

Resolution: Won't Fix

XmlBeans does not modify namespace prefixes from string representations. If you 
need it modified try XmlCursor.

 Namespaces in QName is not preserved after copy of the XMLBeans from one tree 
 to anoter.
 

 Key: XMLBEANS-190
 URL: https://issues.apache.org/jira/browse/XMLBEANS-190
 Project: XMLBeans
  Issue Type: Bug
Affects Versions: Version 2.1
Reporter: daryoush mehrtash
 Attachments: CopyTest.java


 I parse a schema file to XMLBeans, the schema defines the impl namespace.  
 I then parse another document, which is also a schema file that uses impl 
 namespace but is set to a different namespace than the orignial schema.
 WHen I copy the XMLObjects from one schema to the other, the QNames of the 
 schema objects are not updated to reflect the new namespaces.
 I have attached a simple program to reproduce the problem.  Notice that the 
 Person element in the s2 uses   xsd:element name=\addr\ 
 type=\impl:Address\/  after it is copied to the s1 i expect the impl 
 be changed to tns1  but it remains impl   which is not the correct 
 namespace in the target schema.
 The output of my attached code is:
 After add the schema: xsd:schema elementFormDefault=qualified 
 targetNamespace=http://byXmlBeanNS; 
 xmlns:apachesoap=http://xml.apache.org/xml-soap; xmlns:impl=http://web; 
 xmlns:intf=http://web; xmlns:tns1=http://byXmlBeanNS; 
 xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; 
 xmlns:wsdlsoap=http://schemas.xmlsoap.org/wsdl/soap/; 
 xmlns:xsd=http://www.w3.org/2001/XMLSchema;
   xsd:element name=Person
 xsd:complexType
   xsd:sequence
 xsd:element name=name type=xsd:string/
 xsd:element name=addr type=impl:Address/ 
 -
   /xsd:sequence
 /xsd:complexType
   /xsd:element
 /xsd:schema
 But I expected
 After add the schema: xsd:schema elementFormDefault=qualified 
 targetNamespace=http://byXmlBeanNS; 
 xmlns:apachesoap=http://xml.apache.org/xml-soap; xmlns:impl=http://web; 
 xmlns:intf=http://web; xmlns:tns1=http://byXmlBeanNS; 
 xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; 
 xmlns:wsdlsoap=http://schemas.xmlsoap.org/wsdl/soap/; 
 xmlns:xsd=http://www.w3.org/2001/XMLSchema;
   xsd:element name=Person
 xsd:complexType
   xsd:sequence
 xsd:element name=name type=xsd:string/
 xsd:element name=addr type=tns1:Address/ 
 --
   /xsd:sequence
 /xsd:complexType
   /xsd:element
 /xsd:schema

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
For additional commands, e-mail: dev-h...@xmlbeans.apache.org

[jira] Commented: (XMLBEANS-189) namespace attributes gets lost when a XMLBean node is converted to DOM


[ 
https://issues.apache.org/jira/browse/XMLBEANS-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12772378#action_12772378
 ] 

Jacob Danner commented on XMLBEANS-189:
---

This only appears to be an issue using the impl schemaDocument type

 namespace attributes gets lost when a XMLBean node is converted to DOM
 --

 Key: XMLBEANS-189
 URL: https://issues.apache.org/jira/browse/XMLBEANS-189
 Project: XMLBeans
  Issue Type: Bug
  Components: DOM
Affects Versions: Version 2
Reporter: daryoush mehrtash
 Attachments: DOMNamespaceTest.java


 When I create a Schema object I get the name space attribute 
xmlns=http://www.w3.org/2001/XMLSchema;
 in the Object, but when I convert this to DOM node the attribute is not 
 present.  I have attached a simple program to reproduce the problem.When 
 I run the following code:
 public static void main(String[] args) {
 SchemaDocument schema1 = SchemaDocument.Factory.newInstance();
 schema1.addNewSchema();
 System.out.println(Schema in XMLBeans + schema1);
 
 System.out.println(Schema as DOM Node);
 Node node = schema1.getDomNode();
 node = node.getFirstChild();
 System.out.println(Node Name:  + node.getNodeName());
 System.out.println(Attributes: );
 NamedNodeMap nnm = node.getAttributes();
 if (nnm != null) {
 int len = nnm.getLength();
 Attr attr;
 for (int i = 0; i  len; i++) {
 attr = (Attr) nnm.item(i);
 System.out.println(\t  + attr.getNodeName() + =\ + 
 attr.getNodeValue() + '');
 }
 }
 System.out.println(End of Attributes);  
 }
 my output is:
 Schema in XMLBeansschema xmlns=http://www.w3.org/2001/XMLSchema/
 Schema as DOM Node
 Node Name: schema
 Attributes: 
 End of Attributes
 I expected teh xmlns= to show up as attribute of the dom node.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
For additional commands, e-mail: dev-h...@xmlbeans.apache.org

[jira] Commented: (XMLBEANS-189) namespace attributes gets lost when a XMLBean node is converted to DOM


[ 
https://issues.apache.org/jira/browse/XMLBEANS-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12772379#action_12772379
 ] 

Jacob Danner commented on XMLBEANS-189:
---

Working Sample
the xmlns shows up as an attribute in this case
 XmlObject schema1 = XmlObject.Factory.parse(schema xmlns=\http://foo\; 
bar=\bam\ /);
System.out.println(Schema in XMLBeans + schema1);

System.out.println(Schema as DOM Node);
Node node = schema1.getDomNode();
node = node.getFirstChild();
System.out.println(Node Name:  + node.getNodeName());
System.out.println(Node NS:  + 
node.getNamespaceURI()+-+node.getNodeValue());
System.out.println(Attributes: );
NamedNodeMap nnm = node.getAttributes();
if (nnm != null) {
int len = nnm.getLength();
Attr attr;
for (int i = 0; i  len; i++) {
attr = (Attr) nnm.item(i);
System.out.println(\t  + attr.getNodeName() + =\ + 
attr.getNodeValue() + '');
}
}
System.out.println(End of Attributes);

 namespace attributes gets lost when a XMLBean node is converted to DOM
 --

 Key: XMLBEANS-189
 URL: https://issues.apache.org/jira/browse/XMLBEANS-189
 Project: XMLBeans
  Issue Type: Bug
  Components: DOM
Affects Versions: Version 2
Reporter: daryoush mehrtash
 Attachments: DOMNamespaceTest.java


 When I create a Schema object I get the name space attribute 
xmlns=http://www.w3.org/2001/XMLSchema;
 in the Object, but when I convert this to DOM node the attribute is not 
 present.  I have attached a simple program to reproduce the problem.When 
 I run the following code:
 public static void main(String[] args) {
 SchemaDocument schema1 = SchemaDocument.Factory.newInstance();
 schema1.addNewSchema();
 System.out.println(Schema in XMLBeans + schema1);
 
 System.out.println(Schema as DOM Node);
 Node node = schema1.getDomNode();
 node = node.getFirstChild();
 System.out.println(Node Name:  + node.getNodeName());
 System.out.println(Attributes: );
 NamedNodeMap nnm = node.getAttributes();
 if (nnm != null) {
 int len = nnm.getLength();
 Attr attr;
 for (int i = 0; i  len; i++) {
 attr = (Attr) nnm.item(i);
 System.out.println(\t  + attr.getNodeName() + =\ + 
 attr.getNodeValue() + '');
 }
 }
 System.out.println(End of Attributes);  
 }
 my output is:
 Schema in XMLBeansschema xmlns=http://www.w3.org/2001/XMLSchema/
 Schema as DOM Node
 Node Name: schema
 Attributes: 
 End of Attributes
 I expected teh xmlns= to show up as attribute of the dom node.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
For additional commands, e-mail: dev-h...@xmlbeans.apache.org

Re: JDK 1.5

2009-08-16 Thread Jacob Danner

+1, I'm all for this!
-jacobd

On Thu, Aug 13, 2009 at 3:24 PM, Wing Yew Poon wing.yew.p...@oracle.comwrote:

 Hi,
 Cezar took a poll to see which jdk version folks were running xmlbeans on,
 and only one respondent (out of an admittedly very small sample) was still
 using 1.4. Almost everyone was using 1.5 or even 1.6.
 Given this, I think it would be useful to compile a list of changes that
 we should make if xmlbeans were to support jdk 1.5 as its base jdk version.
 We can also add a list of jdk 1.6-supported features, such as @Generated,
 as someone proposed in https://issues.apache.org/jira/browse/XMLBEANS-413.
 Thanks,
 Wing Yew

 -
 To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
 For additional commands, e-mail: dev-h...@xmlbeans.apache.org

[jira] Resolved: (XMLBEANS-408) How to suppress Namespace in XmlBeans Object ?

2009-05-21 Thread Jacob Danner (JIRA)


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacob Danner resolved XMLBEANS-408.
---

Resolution: Invalid

This is not a bug, but rather something that should be posted to the xmlbeans 
user mailing list. Please post your question there.
http://xmlbeans.apache.org/community/index.html

 How to suppress Namespace in XmlBeans Object ?
 --

 Key: XMLBEANS-408
 URL: https://issues.apache.org/jira/browse/XMLBEANS-408
 Project: XMLBeans
  Issue Type: Improvement
  Components: Binding
Affects Versions: Version 1.0.4
 Environment: TEST
Reporter: Rajeshkumar
Priority: Critical
 Fix For: Version 2.1


 Hi
 Im using XmlBeans for paste 1yr, i dont know much on this topics, but i got 
 one requirement  for that want to suppress total Namespace
 from input xml. My scenario im getting xml like this
 ?xml version=1.0 encoding=UTF-8?
 XSDPaymentRequestMsg xmlns=urn:XSD:xsd:XSDPaymentRequestMsg.00.03.00
   xmlns:HE2E=urn:XSD:xsd:XSDHdrSrv.001.07
   xmlns:HTRT=urn:XSD:xsd:XSDHdrTrt.001.07
   xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
   XSDBdyPaymentRequest
   xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
   xmlns:SSRD=urn:XSD:xsd:XSDBdyPaymentRequest.00.03.00
   xmlns:SGNT=urn:XSD:xsd:XSDSgnInf.001.04
   xmlns:GPRS=urn:XSD:xsd:XSDPaymentRequest.00.03.00
   SSRD:XSDEnvelPaymentRequest
   SSRD:XSDPaymentRequest
   GPRS:GrpHdr
   GPRS:MsgId2008013100010/GPRS:MsgId
   
 GPRS:CreDtTm2008-01-31T15:14:53/GPRS:CreDtTm
   GPRS:NbOfTxs2/GPRS:NbOfTxs
   GPRS:CtrlSum27.00/GPRS:CtrlSum
   GPRS:GrpgGRPD/GPRS:Grpg
   GPRS:InitgPty
   GPRS:NmFortunati Maria 
 Grazia/GPRS:Nm
   GPRS:Id
   GPRS:OrgId
   GPRS:TaxIdNb
   
 FRTMGR70D60G337W
   /GPRS:TaxIdNb
   GPRS:PrtryId
   
 GPRS:Id0031885X/GPRS:Id
   
 GPRS:IssrACBI/GPRS:Issr
   /GPRS:PrtryId
   /GPRS:OrgId
   /GPRS:Id
   /GPRS:InitgPty
   /GPRS:GrpHdr
   /SSRD:XSDPaymentRequest
   /SSRD:XSDEnvelPaymentRequest
   /XSDBdyPaymentRequest
 /XSDPaymentRequestMsg
 if i get object like this...
 final XSDPaymentRequestMsgDocument requestMsgDocument  = 

 XSDPaymentRequestMsgDocument.Factory.parse(inputXml,new 
 XmlOptions().setSaveAggresiveNamespaces());
   XSDBdyPaymentRequest000305 request000305  = 
  
 requestMsgDocument.getXSDPaymentRequestMsg().getXSDBdyPaymentRequest();
XSDPaymentRequest000305 request0003052 =
  request000305.getXSDEnvelPaymentRequestArray(0).getXSDPaymentRequest();
  XSDGenericIdentification1 pmtrequest = 
 request0003052.getGrpHdr().getInitgPty().getId().getOrgId().getPrtryId();
 System.out.println( pmtrequest   = +pmtrequest );
 OUTPUT 
 
 I will get like this.
  xml-fragment 
  xmlns:urn=urn:XSD:xsd:XSDPaymentRequest.00.03.05 
  xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; 
  xmlns:HTRT=urn:XSD:xsd:XSDHdrTrt.001.07 
  xmlns:HE2E=urn:XSD:xsd:XSDHdrSrv.001.07\ 
  xmlns:BODY=urn:XSD:xsd:XSDBdyPaymentRequest.00.03.05
  GPRS:Id0031885X/GPRS:Id
  GPRS:IssrACBI/GPRS:Issr
  /xml-fragment
 but i Expect output is like this.
 xml-fragment
  Id0031885X/Id
  IssrACBI/Issr
  /xml-fragment
 Can you please suggest me to how to do get this  scenario?
 Regards,
 Rajesh.
  
   

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
For additional commands, e-mail: dev-h...@xmlbeans.apache.org

Re: Timeout while using XMLBeans...

2009-04-13 Thread Jacob Danner

Where is the xml your query is querying?
-jacobd

On Mon, Apr 13, 2009 at 9:57 AM, Tony Anecito adanec...@yahoo.com wrote:

 Hi All,

 I am using Weblogic Portal server 10.1 with Apache XML beans and getting the 
 following message as we increase the number of users for a load test:

 Apr 9, 2009 4:41:27 PM CDT Error WebLogicServer BEA-000337 [STUCK] 
 ExecuteThread: '197' for queue: 'weblogic.kernel.Default (self-tuning)' has 
 been busy for 692 seconds working on the request Http Request: 
 /wlp/appmanager/dsf/portal, which is more than the configured time 
 (StuckThreadMaxTime) of 600 seconds. Stack trace:

 org.apache.xmlbeans.impl.values.XmlObjectBase.execQuery(XmlObjectBase.java:467)

 As you can see we were executing a XML query. What is interesting is the 
 query was hitting the disk and more interesting it might be opneing an EAR or 
 zip file because the call that was blocking was a java.util.Zip.getEntry().

 Has anyone ever seen this and know how to resolve it?

 Thanks,
 -Tony





 -
 To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
 For additional commands, e-mail: dev-h...@xmlbeans.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
For additional commands, e-mail: dev-h...@xmlbeans.apache.org

Re: somebody tell me how to parse xsd files with xmlbeans?

2009-03-10 Thread Jacob Danner

Have you taken a peek in the user mailing list archives? I think this same
(or at least real similar (how to get attributes)) question was answered on
the mailing list a few days ago.
The user list is more appropriate for these usage kind of questions.

-jacobd

On Tue, Mar 10, 2009 at 12:37 AM, anchorTan tantingf...@163.com wrote:


 i want to get the detail structure of each xs:element in the schema file,
 and i tried with the following codes in the xmlbeans2.0 api document:

 schemaList.addAll(Arrays.asList(schemaTypeSys.documentTypes()));
 schemaList.addAll(Arrays.asList(schemaTypeSys.attributeTypes()));
 schemaList.addAll(Arrays.asList(schemaTypeSys.globalTypes()));
 for (int i = 0; i  schemaList.size(); i++) {
 SchemaType sType = (SchemaType) schemaList.get(i);
 //System.out.println(sType
 name==+sType.getName()+,issimpletype==+sType.isSimpleType());
 chemaList.addAll(Arrays.asList(sType.getAnonymousTypes()));
 }

 and with the above codes, i can get get the shemaType's attribute
 information.but some elements such as:
 xs:element name=test
  xs:complexType
xs:attributeGroup ref=something/
  /xs:complexType
 /xs:element

 i cannot get these elements' attribute information. somebody met this
 situations  please help me!
 --
 View this message in context:
 http://www.nabble.com/somebody-tell-me-how-to-parse-xsd-files-with-xmlbeans--tp22429276p22429276.html
 Sent from the Xml Beans - Dev mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
 For additional commands, e-mail: dev-h...@xmlbeans.apache.org

[jira] Resolved: (XMLBEANS-400) XMlBeans : same complex type in multiple xsd files

2009-02-26 Thread Jacob Danner (JIRA)


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacob Danner resolved XMLBEANS-400.
---

Resolution: Invalid

This isn't really an issue with XMLBeans but rather the way the schemas are 
structured.
There are several things the user can do for duplicate type definitions.

For this issue I would use the sfactor tool to refactor the schemas so only one 
type definition is defined.

Refactors a directory of XSD files to remove name conflicts.
Usage: sfactor [-import common.xsd] [-out outputdir] inputdir
-import common.xsd - The XSD file to contain redundant
 definitions for importing.
-out outputdir - The directory into which to place XSD
 files resulting from refactoring,
 plus a commonly imported common.xsd.
inputdir - The directory containing the XSD files with
   redundant definitions.
-license - Print license information.


 XMlBeans : same complex type in multiple xsd files
 --

 Key: XMLBEANS-400
 URL: https://issues.apache.org/jira/browse/XMLBEANS-400
 Project: XMLBeans
  Issue Type: Test
Reporter: Deepa.B
 Attachments: Prb_Xsd.zip, SEPA.xml


 Problem i face is that there are same complextype elements in multiple xsd's 
 and when i try to build them under the same package using xsd config files, 
 the complex types with the same name of  different xsd's are overwitten. 
 When tried to give different packages for each of such duplicate complex 
 type, even then i face a prbm. 
 Can u please suggest us a way to solve the problem. 
 Senario no : 1 (same package) 
 == 
 CBIPartyIdentification1 is an ComplexType, 
 which exist in 3 different xsd files like 
 CreditTransfer.xsd 
 CBIPaymentRequest.00.03.05.xsd 
 CBICdtrPmtStatusReport.00.03.05.xsd 
 while trying to take object of type (CBIPartyIdentification1) in 
 CBIPaymentRequest.00.03.05.xsd file, 
 but its overlapping type of CBICdtrPmtStatusReport.00.03.05.xsd, so while 
 getting object in java source is NULL. 
 Senario no : 2 (diff package) 
 == 
 In this senario, while taking object type of CBIPartyIdentification1 in 
 CBIPaymentRequest.00.03.05.xsd file, 
 the last CBICdtrPmtStatusReport.00.03.05.xsd file type is overlapped with 
 CBIPaymentRequest.00.03.05.xsd 
 so im getting package is different( not expected one), due to this 
 ClassCastException araise. 
 //sample snippet which we tried here 
 CBIPaymentRequestMsgDocument requestDocument = 
 CBIPaymentRequestMsgDocument.Factory.parse(getInputXml()); 
 CBIBdyPaymentRequest000305 request000305 = 
 requestDocument.getCBIPaymentRequestMsg().getCBIBdyPaymentRequest(); 
 CBIPaymentRequest000305 paymentRequest000305 = 
 request000305.getCBIEnvelPaymentRequestArray(0).getCBIPaymentRequest(); 
 CBIPartyIdentification1 identification1 = 
 paymentRequest000305.getGrpHdr().getInitgPty(); 
 System.out.println(identification1.getId().getOrgId().getPrtryId().getId()); 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
For additional commands, e-mail: dev-h...@xmlbeans.apache.org

Re: Problem in parsing xml

2009-02-25 Thread Jacob Danner

What happens when you validate the new instance?
I imagine this will give you an indication on why getMyElementArray is
returning null.
-jacobd

On Wed, Feb 25, 2009 at 6:55 AM, Moses R eltsa...@amdocs.com wrote:

 Hi,

 I encounter with strange behavior in xml beans.

 I moved xml object to string by String str = xmlObject.xmlText();
 My xml object contains an array as sub element. The array size in the xml is
 one.
 When I parse the string to xml object by xmlObject.Factory.parse(str), the
 xml object look good in the debugger,
 but when I tried to get my array with xmlObject.getMyElementArray() the
 array does not contains elements (array size is zero).

 Does someone have an idea?

 Thanks

 --
 View this message in context: 
 http://www.nabble.com/Problem-in-parsing-xml-tp22204412p22204412.html
 Sent from the Xml Beans - Dev mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
 For additional commands, e-mail: dev-h...@xmlbeans.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
For additional commands, e-mail: dev-h...@xmlbeans.apache.org

[jira] Resolved: (XMLBEANS-399) Getting Null while parsing with XSD

2009-02-18 Thread Jacob Danner (JIRA)


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacob Danner resolved XMLBEANS-399.
---

Resolution: Invalid

You should be looking to use ORGInfoRequestMsgDocument instead of 
ORGInfoRequestMsg. The reasons why are explained in the getting started 
documentation. Next time please query or send this kind of issue to the user 
mailing list. Also, when in doubt, try validating your instance. I believe had 
you done that a proper error would have been displayed.
Resolving as invalid as this is not an issue with XMLBeans, will close next.

 Getting Null while parsing with XSD
 ---

 Key: XMLBEANS-399
 URL: https://issues.apache.org/jira/browse/XMLBEANS-399
 Project: XMLBeans
  Issue Type: Bug
Affects Versions: Version 1.0.4
 Environment: Windows,Linux,Java 1.5 , xmlbeans-1.0.4
Reporter: Guna
Priority: Critical
 Fix For: unspecified


 Hi ,
 I'm really new to xmlbeans and I have a question. I have 3 xsd and 3 
 xsdconfig files.
 {noformat}
 ORGInfoRequestMsg.00.03.04.xsd:
 ==
 ?xml version=1.0 encoding=UTF-8?
 xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema;
xmlns:HTRT=urn:ORG:xsd:ORGHdrTrt.001.07
xmlns:HE2E=urn:ORG:xsd:ORGHdrSrv.001.07
xmlns=urn:ORG:xsd:ORGInfoRequestMsg.00.03.04 
 targetNamespace=urn:ORG:xsd:ORGInfoRequestMsg.00.03.04 
 elementFormDefault=qualified
   xs:import namespace=urn:ORG:xsd:ORGHdrTrt.001.07 
 schemaLocation=ORGHdrTrt.001.07.xsd/
   xs:import namespace=urn:ORG:xsd:ORGHdrSrv.001.07 
 schemaLocation=ORGHdrSrv.001.07.xsd/
   
   xs:element name=ORGInfoRequestMsg type=ORGInfoRequestMsg.00.03.04/
   
   xs:complexType name=ORGInfoRequestMsg.00.03.04
   xs:sequence
   xs:element name=ORGHdrTrt 
 type=HTRT:ORGHdrTrt.001.07/
   xs:element name=ORGHdrSrv 
 type=HE2E:ORGHdrSrv.001.07/
   /xs:sequence
   /xs:complexType
 /xs:schema
 ORGInfoRequestMsg.00.03.04.xsdconfig:
 
 xb:config xmlns:xb=http://xml.apache.org/xmlbeans/2004/02/xbean/config;
   xb:namespace uri=##any
   xb:packageinforeqmsg.xsd/xb:package
   /xb:namespace
 /xb:config
 ORGHdrTrt.001.07.xsd :
 =
 ?xml version=1.0 encoding=UTF-8?
 xs:schema targetNamespace=urn:ORG:xsd:ORGHdrTrt.001.07 
 xmlns=urn:ORG:xsd:ORGHdrTrt.001.07 
 xmlns:xs=http://www.w3.org/2001/XMLSchema; elementFormDefault=qualified
   
   xs:element name=ORGHdrTrt type=ORGHdrTrt.001.07
xs:annotation
   xs:documentation Some Infor /xs:documentation
   /xs:annotation
   /xs:element   
   
   
   xs:complexType name=ORGHdrTrt.001.07
   xs:sequence
   xs:element name=IdMsgTrt type=IdMsgTrt1/
   /xs:sequence
   /xs:complexType
   xs:simpleType name=IdMsgTrt1
   xs:restriction base=Max61Text
   xs:pattern value=[a-zA-Z0-9]{61,61}/
   /xs:restriction
   /xs:simpleType
 /xs:schema
 ORGHdrTrt.001.07.xsdconfig:
 ===
 xb:config xmlns:xb=http://xml.apache.org/xmlbeans/2004/02/xbean/config;
   xb:namespace uri=##any
   xb:packagehdrtrt.xsd/xb:package
   /xb:namespace
 /xb:config
 ORGHdrSrv.001.07.xsd:
 
 ?xml version=1.0 encoding=UTF-8?
 xs:schema targetNamespace=urn:ORG:xsd:ORGHdrSrv.001.07 
 xmlns=urn:ORG:xsd:ORGHdrSrv.001.07 
 xmlns:xs=http://www.w3.org/2001/XMLSchema; elementFormDefault=qualified
   
   xs:element name=ORGHdrSrv type=ORGHdrSrv.001.07
xs:annotation
   xs:documentation release 6.05 /xs:documentation
   /xs:annotation
   /xs:element  
   
   xs:complexType name=ORGHdrSrv.001.07
   xs:sequence
   xs:element name=IdE2EMsg type=IdE2EMsg1/
   /xs:sequence
   /xs:complexType
   xs:simpleType name=IdE2EMsg1
   xs:restriction base=Max44Text
   xs:pattern value=[a-zA-Z0-9]{44,44}/
   /xs:restriction
   /xs:simpleType
 /xs:schema
 ORGHdrSrv.001.07.xsdconfig:
 ===
 xb:config xmlns:xb=http://xml.apache.org/xmlbeans/2004/02/xbean/config;
   xb:namespace uri=##any
   xb:packagehdrsrv.xsd/xb:package
   /xb:namespace
 /xb:config
 {noformat}
 Input Xml :
 
 {noformat}
 ?xml version=1.0 encoding=UTF-8?
 ORGInfoRequestMsg xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; 
   
 xmlns=urn:ORG:xsd:ORGInfoRequestMsg.00.03.05 
   
 xmlns:HTRT=urn:ORG:xsd:ORGHdrTrt.001.07

Re: sorting xml data in alphabetical order

2008-12-15 Thread Jacob Danner

Can you post the query you are using?
-jacobd

On Mon, Dec 15, 2008 at 1:50 AM, Rauf khan forum.k...@gmail.com wrote:

 I tried by using Saxon Query but couldnt get to the final solution. Can
 anyone please help me out with a java program in getting the expected result
 [sorted xml data].. Please no use of Array/Hashmap type of logic.

 UnSorted XML Data
 ?xml version=1.0 encoding=UTF-8?
 World
Country name=Pakistan
State name=Karachi population=999/
State name=Islamabad population=900/
State name=Rawalpandi population=909/
/Country
Country name=India
State name=Bangalore population=100/
State name=AP population=200/
State name=Madras population=300/
State name=Kerala population=400/
State name=Hyderabad population=500/
State name=Delhi population=600/
/Country
 /World

 Expected Result: Sorted XML Data
 ?xml version=1.0 encoding=UTF-8?
 World
Country name=India
State name=AP population=200/
State name=Bangalore population=100/
State name=Delhi population=600/
State name=Hyderabad population=500/
State name=Kerala population=400/
State name=Madras population=300/
/Country
Country name=Pakistan
State name=Islamabad population=900/
State name=Karachi population=999/
State name=Rawalpandi population=909/
/Country
 /World


 - Khan


 Sachin Thatte wrote:

 Sorting should be possible using the order by clause in Saxon Xquery.

 -Sachin

 -Original Message-
 From: Jacob Danner [mailto:jacob.dan...@gmail.com]
 Sent: Friday, October 10, 2008 9:34 AM
 To: dev@xmlbeans.apache.org; u...@xmlbeans.apache.org
 Subject: Re: sorting xml data in alphabetical order

 Passing on the the user list since this is more of a user question.
 AFAIK, xmlbeans provides no way to do this internally so you are going to
 need to manually sort the array before you set the value of country. The
 JDK provides Arrays.sort, but you can investigate using other sort
 routines.

 HTH,
 -jacobd


 On Fri, Oct 10, 2008 at 8:11 AM, Rauf khan forum.k...@gmail.com wrote:

 Hi,

  Using the jar of the xsd i was able to create an xml file  read it.
 Now can anyone pls let me know how to sort the xml file in
 alphabetical order including the parent  its child nodes. My xml file
 structure is like this:

 country name=India
stateGoa/state
stateRajastan/state
stateBhopal/state
 /country
 country name=America
stateTexas/state
stateWashington/state
stateMaryland/state
stateAlaska/state
 /country


 Expected Result:
 -
 country name=America
stateAlaska/state
stateMaryland/state
stateTexas/state
stateWashington/state
 /country
 country name=India
stateBhopal/state
stateGoa/state
stateRajastan/state
 /country


 Thanks in Advance.
 Rauf Khan

 --
 View this message in context:
 http://www.nabble.com/sorting-xml-data-in-alphabetical-order-tp1992024
 6p19920246.html Sent from the Xml Beans - Dev mailing list archive at
 Nabble.com.


 -
 To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
 For additional commands, e-mail: dev-h...@xmlbeans.apache.org



 -
 To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
 For additional commands, e-mail: dev-h...@xmlbeans.apache.org


 Notice:  This email message, together with any attachments, may contain
 information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
 entities,  that may be confidential,  proprietary,  copyrighted  and/or
 legally privileged, and is intended solely for the use of the individual
 or entity named in this message. If you are not the intended recipient,
 and have received this message in error, please immediately return this by
 email and then delete it.


 -
 To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
 For additional commands, e-mail: dev-h...@xmlbeans.apache.org




 --
 View this message in context: 
 http://www.nabble.com/sorting-xml-data-in-alphabetical-order-tp19920246p21010971.html
 Sent from the Xml Beans - Dev mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
 For additional commands, e-mail: dev-h...@xmlbeans.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
For additional commands, e-mail: dev-h...@xmlbeans.apache.org

Re: [REPORT] XMLBeans - December 2008

2008-12-04 Thread Jacob Danner

looks good to me
-jacobd

On Thu, Dec 4, 2008 at 2:23 PM, Cezar Andrei [EMAIL PROTECTED] wrote:
 It's time for the usual board report, same drill – please send comments in
 the next couple of days.







 XMLBeans board report December 2008





 As usual traffic on the mailing list remains stable, there are many
 questions from fresh new users. The process of adding Wing Yew as a new
 committer has been finished.



 Development was focused mainly on bug fixes, many of them found by the
 community, some even had fix patches.



 There were no new releases this quarter, and there were no issues requiring
 board's attention.



 Cezar

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

[jira] Resolved: (XMLBEANS-386) XmlObject.Factory.parse throws Unexpected element: CDATA

2008-10-27 Thread Jacob Danner (JIRA)


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacob Danner resolved XMLBEANS-386.
---

Resolution: Invalid

The issues with your file appears to be in the thats been added to your xml file
If you modify your PI from:
?xml version=1.0 encoding=ISO-8859-1?
to:
?xml version=1.0 ?
or modify the document and put a proper encoding into your instance
?xml version=1.0 encoding=[insertvalidencoding] ?
and things should work.

How was this document created and how was the encoding established for this 
instance? 

 XmlObject.Factory.parse throws Unexpected element: CDATA
 --

 Key: XMLBEANS-386
 URL: https://issues.apache.org/jira/browse/XMLBEANS-386
 Project: XMLBeans
  Issue Type: Bug
  Components: XmlObject
Affects Versions: Version 2.4 
 Environment: Java 1.5.0_11, Windows Server 2003, XmlBeans 2.4.0
Reporter: Aleksei Kazantsev
Priority: Minor
 Attachments: __d3configserver.xml


 Attached XML fails to be parsed.
 Java code to reproduce the problem:
   XmlObject xml = XmlObject.Factory.parse(new 
 File(d:/__d3configserver.xml));
 Throws:
 org.apache.xmlbeans.XmlException: d:\__d3configserver.xml:457:1: error: 
 Unexpected element: CDATA
   at 
 org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3486)
   at 
 org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1276)
   at 
 org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1263)
   at 
 org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:345)
   at 
 org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:252)
   at org.apache.xmlbeans.XmlObject$Factory.parse(XmlObject.java:639)
   at 
 com.agfa.apomedia.translation.UtilsTest.testGetTranslatedFile(UtilsTest.java:122)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:585)
   at junit.framework.TestCase.runTest(TestCase.java:154)
   at 
 org.jmock.integration.junit3.VerifyingTestCase.runBare(VerifyingTestCase.java:37)
   at junit.framework.TestResult$1.protect(TestResult.java:106)
   at junit.framework.TestResult.runProtected(TestResult.java:124)
   at junit.framework.TestResult.run(TestResult.java:109)
   at junit.framework.TestCase.run(TestCase.java:118)
   at junit.framework.TestSuite.runTest(TestSuite.java:208)
   at junit.framework.TestSuite.run(TestSuite.java:203)
   at 
 org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
   at 
 org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
   at 
 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
   at 
 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
   at 
 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
   at 
 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
 Caused by: org.xml.sax.SAXParseException: Unexpected element: CDATA
   at 
 org.apache.xmlbeans.impl.piccolo.xml.Piccolo.reportFatalError(Piccolo.java:1038)
   at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.parse(Piccolo.java:723)
   at 
 org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3454)
   ... 24 more

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Re: sorting xml data in alphabetical order

2008-10-10 Thread Jacob Danner

Passing on the the user list since this is more of a user question.
AFAIK, xmlbeans provides no way to do this internally so you are going
to need to manually sort the array before you set the value of
country. The JDK provides Arrays.sort, but you can investigate using
other sort routines.

HTH,
-jacobd


On Fri, Oct 10, 2008 at 8:11 AM, Rauf khan [EMAIL PROTECTED] wrote:

 Hi,

  Using the jar of the xsd i was able to create an xml file  read it. Now
 can anyone pls let me know how to sort the xml file in alphabetical order
 including the parent  its child nodes. My xml file structure is like this:

 country name=India
stateGoa/state
stateRajastan/state
stateBhopal/state
 /country
 country name=America
stateTexas/state
stateWashington/state
stateMaryland/state
stateAlaska/state
 /country


 Expected Result:
 -
 country name=America
stateAlaska/state
stateMaryland/state
stateTexas/state
stateWashington/state
 /country
 country name=India
stateBhopal/state
stateGoa/state
stateRajastan/state
 /country


 Thanks in Advance.
 Rauf Khan

 --
 View this message in context: 
 http://www.nabble.com/sorting-xml-data-in-alphabetical-order-tp19920246p19920246.html
 Sent from the Xml Beans - Dev mailing list archive at Nabble.com.


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



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

Re: Help with XML Beans

2008-06-03 Thread Jacob Danner

What is happening in your application when this issue occurs?
-jacobd

On Tue, Jun 3, 2008 at 9:57 PM, Mohan Thurairajah
[EMAIL PROTECTED] wrote:
 Hi All,

 We are using XML Beans in a multithreaded environment. We use webstart and
 xml beans on the client side. It looks like xml beans is having trouble with
 jnlp class loader and it is causing two or more threads to spin 100% CPU.
 Could you help plz? we need to go to prod soon but this is causing lots of
 trouble:

 HB-Requestor daemon prio=6 tid=0x0478cc00 nid=0x1110 runnable
 [0x0612e000..0x0612fd14]
java.lang.Thread.State: RUNNABLE
 at java.util.HashMap.put(Unknown Source)
 at com.sun.deploy.cache.CacheEntry.readManifest(Unknown Source)
 at com.sun.deploy.cache.CacheEntry.readManifest(Unknown Source)
 at com.sun.deploy.cache.CacheEntry.access$300(Unknown Source)
 at com.sun.deploy.cache.CacheEntry$2.run(Unknown Source)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sun.deploy.cache.CacheEntry.getJarFile(Unknown Source)
 at com.sun.deploy.net.DownloadEngine.getCachedJarFile(Unknown Source)
 at com.sun.deploy.net.DownloadEngine.getCachedJarFile(Unknown Source)
 at com.sun.jnlp.JNLPClassLoader$3.run(Unknown Source)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sun.jnlp.JNLPClassLoader.getJarFile(Unknown Source)
 at com.sun.jnlp.JNLPCachedJarURLConnection.connect(Unknown Source)
 at com.sun.jnlp.JNLPCachedJarURLConnection.getInputStream(Unknown Source)
 at java.net.URL.openStream(Unknown Source)
 at java.lang.ClassLoader.getResourceAsStream(Unknown Source)
 at
 org.apache.xmlbeans.impl.schema.SchemaTypeLoaderImpl.crackEntry(SchemaTypeLoaderImpl.java:337)
 at
 org.apache.xmlbeans.impl.schema.SchemaTypeLoaderImpl.typeSystemForComponent(SchemaTypeLoaderImpl.java:256)
 at
 org.apache.xmlbeans.impl.schema.SchemaTypeLoaderImpl.findDocumentTypeRef(SchemaTypeLoaderImpl.java:430)
 at
 org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.findDocumentType(SchemaTypeLoaderBase.java:129)
 at org.apache.xmlbeans.impl.store.Locale.autoTypeDocument(Locale.java:312)
 at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1273)
 at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1257)
 - locked 0x078a0500 (a org.apache.xmlbeans.impl.store.Locale)
 at
 org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:345)
 at org.fixprotocol.fixml50.FIXMLDocument$Factory.parse(Unknown Source)
 at
 com.cpex.ptms.gateway.FixMLGatewayMessageFactory.createGatewayMessage(FixMLGatewayMessageFactory.java:131)
 at
 com.cpex.ptms.gateway.transport.AbstractGatewayConnection.receive(AbstractGatewayConnection.java:56)
 at
 com.cpex.ptms.gateway.client.ClientGateway.sendAndReceive(ClientGateway.java:314)
 at
 com.cpex.ptms.gateway.client.ClientGateway.marshalSendAndReceive(ClientGateway.java:237)
 at
 com.cpex.ptms.gateway.client.ClientGateway.marshalSendAndReceive(ClientGateway.java:230)
 at
 com.cpex.ptms.gateway.client.ClientGateway.marshalSendAndReceive(ClientGateway.java:220)
 at
 com.cpex.ptms.client.gateway.HeartBeatManager$HeartBeatRequestor.run(HeartBeatManager.java:279)
 at java.lang.Thread.run(Unknown Source)

 HB-Monitor daemon prio=6 tid=0x0478b800 nid=0x12b4 waiting on condition
 [0x04c3f000..0x04c3fd94]
java.lang.Thread.State: TIMED_WAITING (sleeping)
 at java.lang.Thread.sleep(Native Method)
 at
 com.cpex.ptms.client.gateway.HeartBeatManager$1.run(HeartBeatManager.java:130)
 at java.lang.Thread.run(Unknown Source)

 PTMSStreamer prio=6 tid=0x031d4400 nid=0x970 runnable
 [0x033de000..0x033dfa14]
java.lang.Thread.State: RUNNABLE
 at java.util.HashMap.put(Unknown Source)
 at com.sun.deploy.cache.CacheEntry.readManifest(Unknown Source)
 at com.sun.deploy.cache.CacheEntry.readManifest(Unknown Source)
 at com.sun.deploy.cache.CacheEntry.access$300(Unknown Source)
 at com.sun.deploy.cache.CacheEntry$2.run(Unknown Source)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sun.deploy.cache.CacheEntry.getJarFile(Unknown Source)
 at com.sun.deploy.net.DownloadEngine.getCachedJarFile(Unknown Source)
 at com.sun.deploy.net.DownloadEngine.getCachedJarFile(Unknown Source)
 at com.sun.jnlp.JNLPClassLoader$3.run(Unknown Source)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sun.jnlp.JNLPClassLoader.getJarFile(Unknown Source)
 at com.sun.jnlp.JNLPCachedJarURLConnection.connect(Unknown Source)
 at com.sun.jnlp.JNLPCachedJarURLConnection.getInputStream(Unknown Source)
 at java.net.URL.openStream(Unknown Source)
 at java.lang.ClassLoader.getResourceAsStream(Unknown Source)
 at
 org.apache.xmlbeans.impl.schema.SchemaTypeLoaderImpl.crackEntry(SchemaTypeLoaderImpl.java:337)
 at
 org.apache.xmlbeans.impl.schema.SchemaTypeLoaderImpl.typeSystemForComponent(SchemaTypeLoaderImpl.java:256)
 at
 org.apache.xmlbeans.impl.schema.SchemaTypeLoaderImpl.findElementRef(SchemaTypeLoaderImpl.java:480)
 at

Re: XMLBeans and Saxon

2008-03-31 Thread Jacob Danner

Awesome Wing Yew, Can't wait to try this out.
-jacobd

On Mon, Mar 31, 2008 at 7:12 PM, Wing Yew Poon [EMAIL PROTECTED] wrote:
 I have attached the changes necessary to support saxon 9
  (I tested it with the current saxon release, 9.0.0.4), to
  https://issues.apache.org/jira/browse/XMLBEANS-367.
  The checkin test suite passes 100% with my changes.
  The detailed test suite has the same failures and errors
  as before my change.
  Chris,
  if you could pick up my change (if you do not wish to work
  with the source, you can simply use the xbean_xpath.jar I
  attached to the JIRA, replacing the one for 2.3.0), and
  try it out, that would be great. The saxon jars that are
  needed are saxon9.jar and saxon9-dom.jar.
  Please report any problems or issues - or lack thereof. :-)

 Thanks,
  Wing Yew

  -Original Message-
  From: Chris [mailto:[EMAIL PROTECTED]

 Sent: Friday, February 08, 2008 9:27 AM
  To: dev@xmlbeans.apache.org
  Subject: XMLBeans and Saxon



 I noticed the FAQ (http://wiki.apache.org/xmlbeans/XmlBeansFaq#whatJars)

  seems out of date.

  Is it still true that for XPath queries you just need saxon8.jar and
  saxon8-dom.jar in the classpath when using XMLBeans 2.3.0 and Saxon 8.8?
  What is saxon-xpath.jar for?

  If required, I would be willing to update the FAQ for you.

  What is the progress on the next version of Xbeans? Will it support
  Saxon 9 and hence XPath 2.0?

  Thanks
  --
  Chris
  HMGCC

  The information contained in this message (and any attachments) may
  be confidential and is intended for the sole use of the named addressee.
  Access, copying, alteration or re-use of the e-mail by anyone other
  than the intended recipient is unauthorised. If you are not the intended
  recipient please advise the sender immediately by returning the e-mail
  and deleting it from your system.

  This information may be exempt from disclosure under Freedom Of
  Information
  Act 2000 and may be subject to exemption under other UK information
  legislation. Refer disclosure requests to the Information Officer.


  The original of this email was scanned for viruses by the Government
  Secure Intranet virus scanning service supplied by CableWireless in
  partnership with MessageLabs. (CCTM Certificate Number 2007/11/0032.) On
  leaving the GSi this email was certified virus free.
  Communications via the GSi may be automatically logged, monitored and/or
  recorded for legal purposes.

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



 Notice:  This email message, together with any attachments, may contain 
 information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated 
 entities,  that may be confidential,  proprietary,  copyrighted  and/or 
 legally privileged, and is intended solely for the use of the individual or 
 entity named in this message. If you are not the intended recipient, and have 
 received this message in error, please immediately return this by email and 
 then delete it.

  -


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





-- 
I'm competing in a Half-Ironman distance triathlon to raise money for
the fight against cancer!
Please help support my efforts by going to:
http://www.active.com/donate/tntwaak/jacobd

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

[jira] Commented: (XMLBEANS-356) xception in thread main org.apache.xmlbeans.SchemaTypeLoaderException: Simple type does not have a recognized variety (schemaorg_apache_xmlbeans.system.sF1DBD93096C6

2007-12-11 Thread Jacob Danner (JIRA)


[ 
https://issues.apache.org/jira/browse/XMLBEANS-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550826
 ] 

Jacob Danner commented on XMLBEANS-356:
---

Alex, can you post the output of when you do a 
ned.addNewNameElement();
// add thsi line
System.out.println(NED: +ned.xmlText());

I suspect this is the cause of your problems (there is no content in your 
instance) and this will verify that.
Thanks,
-jacobd

 xception in thread main org.apache.xmlbeans.SchemaTypeLoaderException: 
 Simple type does not have a recognized variety 
 (schemaorg_apache_xmlbeans.system.sF1DBD93096C623A6A85C0BCA912AE262.nameelementd068elemtype)
  - code 8
 -

 Key: XMLBEANS-356
 URL: https://issues.apache.org/jira/browse/XMLBEANS-356
 Project: XMLBeans
  Issue Type: Bug
Affects Versions:  Version 2.3
Reporter: Alex Rykov
 Attachments: TestSchema.xsd, XBeanTest.java


 Attached schema compiles fine. However, when trying to create the top level 
 element in the document the following exception occurs:
 Exception in thread main org.apache.xmlbeans.SchemaTypeLoaderException: 
 Simple type does not have a recognized variety 
 (schemaorg_apache_xmlbeans.system.sF1DBD93096C623A6A85C0BCA912AE262.nameelementd068elemtype)
  - code 8
   at 
 org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$XsbReader.finishLoadingType(SchemaTypeSystemImpl.java:2659)
   at 
 org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.resolveHandle(SchemaTypeSystemImpl.java:3507)
   at 
 org.apache.xmlbeans.SchemaComponent$Ref.getComponent(SchemaComponent.java:104)
   at org.apache.xmlbeans.SchemaType$Ref.get(SchemaType.java:872)
   at 
 org.apache.xmlbeans.impl.schema.SchemaPropertyImpl.getType(SchemaPropertyImpl.java:92)
   at 
 org.apache.xmlbeans.impl.schema.SchemaTypeImpl.createElementType(SchemaTypeImpl.java:965)
   at 
 org.apache.xmlbeans.impl.values.XmlObjectBase.create_element_user(XmlObjectBase.java:893)
   at org.apache.xmlbeans.impl.store.Xobj.getUser(Xobj.java:1657)
   at org.apache.xmlbeans.impl.store.Cur.getUser(Cur.java:2654)
   at org.apache.xmlbeans.impl.store.Xobj.insertElement(Xobj.java:2099)
   at org.apache.xmlbeans.impl.store.Xobj.add_element_user(Xobj.java:2179)
   at schema.impl.NameElementDocumentImpl.addNewNameElement(Unknown Source)
   at test.XBeanTest.main(XBeanTest.java:13)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Re: StackOverflowError when validating long patterns in Windows Java 1.6.0_03

2007-11-28 Thread Jacob Danner

Hi Chris,
Thanks for finding an investigating an issue like this.
Can I get you to file a jira issue to track this?
Thanks,
-jacobd

On Nov 28, 2007 2:20 AM, Chris [EMAIL PROTECTED] wrote:

 After looking further into this issue, in java6 the default stack size
 is not different between Linux and Windows but between 32bit and 64bit
 implementations.  This explains a lot as we're using 64bit linux.
 I can't find what the default stack sizes were in java5 though.  I guess
 I'll just have to add a -Xss parameter to my application although this
 doesn't fill me with confidence,
 Options that begin with -X are non-standard (not guaranteed to be
 supported on all VM implementations), and are subject to change without
 notice in subsequent releases of the JDK. -
 http://java.sun.com/javase/technologies/hotspot/vmoptions.jsp

 Chris wrote:
  I have come across a repeatable error and enclose the test case.
  When the following xml is validated with a ValidatingStreamReader it
  causes an SOE.
  If the sample string is shorter, this does not happen. With more complex
  schemas, the string does not have to be as long to still cause an SOE.
  I have not yet determined whether the complexity of the pattern is a
  factor.
  Increasing the size of the stack using java -Xss64M does prevent this
  issue.
 
  This only happens in Windows, Linux does not have this behaviour. This
  does not happen on any platform in java 5.
 
  Note there were changes in java6 to the way stack sizes are implemented.
  http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6316197
 
  I'm not sure if this is really a bug in xmlbeans since it does work on
  other platforms... is there any reason why it would use more stack space
  on windows? Is the default stack size different on windows and linux?
 
  Thanks for your help
 
  See stack trace below:
  org.apache.xmlbeans.impl.regex.RangeToken.match(line 481)
  org.apache.xmlbeans.impl.regex.RegularExpression.matchString(line 1673)
  org.apache.xmlbeans.impl.regex.RegularExpression.matchString(line 1872)
  org.apache.xmlbeans.impl.regex.RegularExpression.matchString(line 1872)
  org.apache.xmlbeans.impl.regex.RegularExpression.matchString(line 1872)
  org.apache.xmlbeans.impl.regex.RegularExpression.matchString(line 1872)
  ...
 
 
  
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]

 --
 Chris
 HMGCC

 The information contained in this message (and any attachments) may
 be confidential and is intended for the sole use of the named addressee.
 Access, copying, alteration or re-use of the e-mail by anyone other
 than the intended recipient is unauthorised. If you are not the intended
 recipient please advise the sender immediately by returning the e-mail
 and deleting it from your system.

 This information may be exempt from disclosure under Freedom Of
 Information
 Act 2000 and may be subject to exemption under other UK information
 legislation. Refer disclosure requests to the Information Officer.


 The original of this email was scanned for viruses by the Government
 Secure Intranet Anti-Virus service supplied by CableWireless in partnership
 with MessageLabs. (CCTM Certificate Number 2006/04/0007.) On leaving the GSi
 this email was certified virus free.
 Communications via the GSi may be automatically logged, monitored and/or
 recorded for legal purposes.

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

[jira] Assigned: (XMLBEANS-347) XmlComplexContentImpl.equal_to() fails to throw exception when unable to return correct value

2007-11-07 Thread Jacob Danner (JIRA)


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacob Danner reassigned XMLBEANS-347:
-

Assignee: Jacob Danner

 XmlComplexContentImpl.equal_to() fails to throw exception when unable to 
 return correct value
 -

 Key: XMLBEANS-347
 URL: https://issues.apache.org/jira/browse/XMLBEANS-347
 Project: XMLBeans
  Issue Type: Bug
Affects Versions:  Version 2.3
 Environment: n/a
Reporter: Charles Butterfield
Assignee: Jacob Danner
Priority: Critical

 I was recently horrified to discover that valueEquals() fails silently for 
 complex types.  For complex types the comparison is delegated to 
 XmlComplexContentImpl.equal_to() which simply returns true with the comment 
 BUGBUG: by-value structure comparison undone.
 Clearly the method should throw an exception to alert users to the issue, as 
 do various neighboring methods.
 I first ran into this problem (today) while using an old xbean.jar  (built in 
 early 2004).  I then checked the 2.3.0 source and the bug still exists.  So 
 its been there unchanged since version 1.0.4 at least.
 Hopefully adding the exception is a no-brainer.  Perhaps a working 
 implementation could follow.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Assigned: (XMLBEANS-348) 2 Dubious assignments, probably should be equality tests

2007-11-07 Thread Jacob Danner (JIRA)


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacob Danner reassigned XMLBEANS-348:
-

Assignee: Jacob Danner

 2 Dubious assignments, probably should be equality tests
 

 Key: XMLBEANS-348
 URL: https://issues.apache.org/jira/browse/XMLBEANS-348
 Project: XMLBeans
  Issue Type: Bug
Affects Versions:  Version 2.3
 Environment: n/a
Reporter: Charles Butterfield
Assignee: Jacob Danner

 While peeking at the source code to report bug XMLBEANS-347, I (or rather the 
 compiler) ran across two dubious assignments that were probably meant to be 
 equality tests as shown below:
 1) org.apache.xmlbeans.impl.common.XPath: line 717:
if ((_lastDeepDot = deepDot))
 NOTE: if this really is meant to be an assignment, then the following 
 conditional _lastDeepDot = true; is clearly
 redundant, which helped me conclude this is a bug, rather than an evil 
 combined assignment and test.
 2) org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl: line 756:
   assert assertEnabled = true;
 Hope you find this useful,
 Regards
 -- Charlie

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Re: XMLBEANS-174

2007-08-29 Thread Jacob Danner

The easiest way to create a patch is via the cmd line. Tools like
TortoiseSVN can also be useful.
Basically, just go to the trunk directory of your copy of the svn
depot and enter something like:
svn diff  patch.txt
and attach that to the jira issue.

If you didn't grab the src from the svn depot (ie. the src dist), then
just the changed files would be easiest.
Thanks,
-Jacob Danner

On 8/29/07, Schalk Neethling [EMAIL PROTECTED] wrote:
 Do I just add the changes files or the xbean.jar? I am thinking the
 changes files.

 Jacob Danner wrote:
  Hi Schalk,
  The usual process is to attach the changes and tests as a patch to the
  jira issue.
  Thanks,
  -Jacobd
 
  On 8/27/07, Schalk Neethling [EMAIL PROTECTED] wrote:
 
 
 
  Greetings Radu,
 
 
 
  I have implemented the no parameter constructor for generated XMLBeans. I
  have tested it on my code over here and everything builds and works
  perfectly. Please let me know if you want me to check these changes in and
  if so, what the process is to follow. Thanks!
 
 
 
  --
 
  Kind Regards,
 
  Schalk Neethling
 
 
 
  This email and all content are subject to the following disclaimer:
 
 
 
  http://content.momentum.co.za/content/legal/disclaimer_email.htm
 
 
 
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 

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



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

Re: adding data members and methods to generated classes that will not produce XML

2007-07-31 Thread Jacob Danner

I think what you are asking for is possible via the extension
mechanism in XMLBeans. Its an advanced feature, but isn't too
difficult to use. I think the first place you should go is
http://wiki.apache.org/xmlbeans/ExtensionInterfacesFeature

then grab a snapshot of the svn srcs and take a peek at the test code
for this feature.

If you have any further questions on how the feature works, don't
hesitate to post to the list. You may however want to post to
[EMAIL PROTECTED] as thats a more appropriate forum for these
kinds of questions.

Best of luck,
-Jacob Danner

On 7/31/07, ojasrege [EMAIL PROTECTED] wrote:

I want to use XMLBeans XMLObject for a project, but for the classes generated
by XMLBeans, I want to add some additional data members and methods to
handle program state that I do not want to have written out to an XML
document.

I have been using .NET's system.xml.XmlParser class, and it provides this
sort of capability.

In looking at the code produced by XMLObject, it looks possible.

Question: Does anyone have any thoughts on the best way to accomplish what I
want to do? Is there a good design pattern to follow?

Question: Are there any gotchas in doing this? The only immediate one I can
think of is that everytime the .java files are regenerated by XMLObject, I
will have to reinsert my data members and methods.

--
View this message in context:
http://www.nabble.com/adding-data-members-and-methods-to-generated-classes-that-will-not-produce-XML-tf4196225.html#a11934308
Sent from the Xml Beans - Dev mailing list archive at Nabble.com.

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

[jira] Updated: (XMLBEANS-340) derivation-ok-restriction.5.1 failure thrown incorrectly

2007-07-23 Thread Jacob Danner (JIRA)


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacob Danner updated XMLBEANS-340:
--

Priority: Minor  (was: Major)

 derivation-ok-restriction.5.1 failure thrown incorrectly 
 ---

 Key: XMLBEANS-340
 URL: https://issues.apache.org/jira/browse/XMLBEANS-340
 Project: XMLBeans
  Issue Type: Bug
Affects Versions:  Version 2.3
 Environment: MacOSX, Java1.5
Reporter: kombi
Priority: Minor

 I downloaded the DublinCore xml schemas and tried to create xmlbeans of them 
 and got several derivation-ok-restriction.5.1 error messages:
 [xmlbean] schemas/dcterms.xsd:130:3: error: derivation-ok-restriction.5.1: A 
 complex type with a simple content model can only restrict a complex type 
 with simple or mixed content model.
 The problem is here is the line in question:
   xs:complexType name=MESH
xs:simpleContent
 xs:restriction base=dc:SimpleLiteral
 xs:simpleType
   xs:restriction base=xs:string/
 /xs:simpleType
 xs:attribute ref=xml:lang use=prohibited/
 /xs:restriction
/xs:simpleContent
   /xs:complexType
 Here is the base for the restriction:
   xs:complexType name=SimpleLiteral
xs:complexContent mixed=true
 xs:restriction base=xs:anyType
  xs:sequence
   xs:any processContents=lax minOccurs=0 maxOccurs=0/
  /xs:sequence
  xs:attribute ref=xml:lang use=optional/
 /xs:restriction
/xs:complexContent
   /xs:complexType
 As you can see, the complex type with a simple content model is restricting a 
 complex type with mixed content model.
 This seems like an error.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Resolved: (XMLBEANS-340) derivation-ok-restriction.5.1 failure thrown incorrectly

2007-07-23 Thread Jacob Danner (JIRA)


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacob Danner resolved XMLBEANS-340.
---

Resolution: Won't Fix
  Assignee: Jacob Danner

This is a valid error in the XSD, and the validation in xmlbeans is why you are 
seeing this error.
If you are curious about the where's and why's of the error, more information 
can be found at:
http://www.w3.org/TR/xmlschema11-1/#derivation-ok-restriction

There are some other warnings also:
dc.xsd:63:7: warning: p-props-correct.2.2: maxOccurs must be greater than or 
equal to 1.
  xs:any processContents=lax minOccurs=0 maxOccurs=0/

To make the XSD compile using xmlbeans scomp target, try the following:
scomp -noupa -nopvr  *.xsd
dc.xsd:63:7: warning: p-props-correct.2.2: maxOccurs must
 be greater than or equal to 1.
Time to build schema type system: 4.375 seconds
Time to generate code: 3.813 seconds
Time to compile code: 12.031 seconds
Compiled types to: xmltypes.jar

(it worked for me)

Since XmlBeans does not control the XSDs in question, I think it best bet would 
be to contact the group or person you recieved the XSD from.

 derivation-ok-restriction.5.1 failure thrown incorrectly 
 ---

 Key: XMLBEANS-340
 URL: https://issues.apache.org/jira/browse/XMLBEANS-340
 Project: XMLBeans
  Issue Type: Bug
Affects Versions:  Version 2.3
 Environment: MacOSX, Java1.5
Reporter: kombi
Assignee: Jacob Danner
Priority: Minor

 I downloaded the DublinCore xml schemas and tried to create xmlbeans of them 
 and got several derivation-ok-restriction.5.1 error messages:
 [xmlbean] schemas/dcterms.xsd:130:3: error: derivation-ok-restriction.5.1: A 
 complex type with a simple content model can only restrict a complex type 
 with simple or mixed content model.
 The problem is here is the line in question:
   xs:complexType name=MESH
xs:simpleContent
 xs:restriction base=dc:SimpleLiteral
 xs:simpleType
   xs:restriction base=xs:string/
 /xs:simpleType
 xs:attribute ref=xml:lang use=prohibited/
 /xs:restriction
/xs:simpleContent
   /xs:complexType
 Here is the base for the restriction:
   xs:complexType name=SimpleLiteral
xs:complexContent mixed=true
 xs:restriction base=xs:anyType
  xs:sequence
   xs:any processContents=lax minOccurs=0 maxOccurs=0/
  /xs:sequence
  xs:attribute ref=xml:lang use=optional/
 /xs:restriction
/xs:complexContent
   /xs:complexType
 As you can see, the complex type with a simple content model is restricting a 
 complex type with mixed content model.
 This seems like an error.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Re: Enumerated types base index

2007-07-17 Thread Jacob Danner


Hi Jason,
I'm not sure why this is the case, but if its really an issue, I think
you could modify the generated src or modify your index to start at
one.

static final int INT_FOO = 1;
static final int INT_BAZ = 2;

I've attached an example src file in case you wanted to peek at it.
I've never needed an Enum value to have a int val beginning at zero

switch(enumVal)
 case Enum.INT_FOO:
doSomething();
break;
// 

And so using this code, I do not need the enumeration value to be a
specific int. This also makes the code a little easier to read as
well.

Hope this helps,
-Jacob Danner


On 7/17/07, Green, Jason M. [EMAIL PROTECTED] wrote:




Hey all,
I have been attempting to use the Enum.forInt method for some of my
enumerated types.  I am passing in a value that is provided in a text file.
Often times the value is zero, but when I pass that in, I get a
XmlValueNotNillableException.  I know what this means, but I am confused as
to why the enumerated values would start at 1 and not 0.  In the schema,
there is obv no numberign associated.  Since nearly every language that I
know of is 0 based, why would this be 1 based?  Is there a way to change
this?

Thanks,

Jason


TextEnum.java
Description: Binary data
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Enumerated types

2007-07-17 Thread Jacob Danner


Hi Siwei,
I have to ask, why the need for enumerations if you don't want the
check or validation. Why not just use a String type?
As far as I understand xsd:enumerations to work, they say, you can
only use value A, B, or C. If the value is NOT A, B,  or C then this
is not a valid enumeration.


Back to your problem, if you are doing something like
SomeXmlObject.Factory.parse(...)
and don't want this to fail validation, you might be able to try using
the XmlOptions API with methods setCompileNoValidation()

Hope this helps,
-Jacob Danner

On 7/17/07, Kuang, Siwei [EMAIL PROTECTED] wrote:

I have a different issue about the enumeration from Xmlbeans. I look for
a way to enable or disable enumeration check without having to modify,
(say, add/remove one item defined in the schema enumeration block and
recompile to Java type via Xmlbeans). In other words, I try to find a
way to by-pass the enumeration validation check when parsing an XML
document.

There are always new items from XML document beyond what have already
defined in the schema enumeration block. If this happens, Xmlbeans
always give an error, saying XmlOutofRangeException. I was intent to
work around this without modifying the schema, but couldn't get it work.

Any idea or suggestion is appreciated.

Siwei Kuang

-Original Message-
From: Jacob Danner [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 17, 2007 10:20 AM
To: dev@xmlbeans.apache.org
Subject: Re: Enumerated types base index

Hi Jason,
I'm not sure why this is the case, but if its really an issue, I think
you could modify the generated src or modify your index to start at one.

 static final int INT_FOO = 1;
 static final int INT_BAZ = 2;

I've attached an example src file in case you wanted to peek at it.
I've never needed an Enum value to have a int val beginning at zero

switch(enumVal)
  case Enum.INT_FOO:
 doSomething();
 break;
 // 

And so using this code, I do not need the enumeration value to be a
specific int. This also makes the code a little easier to read as well.

Hope this helps,
-Jacob Danner


On 7/17/07, Green, Jason M. [EMAIL PROTECTED] wrote:



 Hey all,
 I have been attempting to use the Enum.forInt method for some of my
 enumerated types.  I am passing in a value that is provided in a text
file.
 Often times the value is zero, but when I pass that in, I get a
 XmlValueNotNillableException.  I know what this means, but I am
 confused as to why the enumerated values would start at 1 and not 0.
 In the schema, there is obv no numberign associated.  Since nearly
 every language that I know of is 0 based, why would this be 1 based?
 Is there a way to change this?

 Thanks,

 Jason



*
If you wish to communicate securely with Commerce Bank and its
affiliates, you must log into your account under Online Services at
http://www.commercebank.com or use the Commerce Bank Secure
Email Message Center at https://securemail.commercebank.com

NOTICE: This electronic mail message and any attached files are
confidential. The information is exclusively for the use of the
individual or entity intended as the recipient. If you are not
the intended recipient, any use, copying, printing, reviewing,
retention, disclosure, distribution or forwarding of the message
or any attached file is not authorized and is strictly prohibited.
If you have received this electronic mail message in error, please
advise the sender by reply electronic mail immediately and
permanently delete the original transmission, any attachments
and any copies of this message from your computer system.
*

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




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

[jira] Commented: (XMLBEANS-338) After save, the xml file becomes incomplete

2007-07-03 Thread Jacob Danner (JIRA)


[ 
https://issues.apache.org/jira/browse/XMLBEANS-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510061
 ] 

Jacob Danner commented on XMLBEANS-338:
---

Hi Helen,
1.Can you repro this just using your java src.
I meant is it possible to execute the failing code outside of your environment 
(RE: 
OS: Windows 2003 Server
 App Server: Weblogic 9.2 mp1)
via like a main method  (RE: 
public static void main(String[] args) )

I don't have the problem when I execute code like the following:
XmlOptions xOpt = new XmlOptions().setSavePrettyPrint();
XmlObject xo = XmlObject.Factory.parse(String with your content above /);
xo.save(new FileWrite(..), xOpt)

 After save, the xml file becomes incomplete
 -

 Key: XMLBEANS-338
 URL: https://issues.apache.org/jira/browse/XMLBEANS-338
 Project: XMLBeans
  Issue Type: Bug
  Components: XmlObject
 Environment: OS: Windows 2003 Server
 App Server: Weblogic 9.2 mp1
Reporter: Helen Liu
Priority: Critical

 Hi,
 We are the xmlbean user.
 Recently, we encounter a strange issue, that is, when the program execute the 
 following code, the xml file become incomplete.
 obj.save( writer, prettyPrintOpts );
 Here, obj is an object of org.apache.xmlbeans.XmlObject;
  writer is an instance of java.io.StringWriter;
  prettyPrintOpts is org.apache.xmlbeans.XmlOptions;
 In obj, everything is well, the xml file is complete, but after obj.save( 
 writer, prettyPrintOpts );, the string in writer is incomplete, the last 
 charactors is Pac, instead of /Package.
 But if I add some attributes or delete some attributes in Action node, this 
 issue would be gone.
 And only this xml file has this issue.
 Any idea about this problem should be appreciated!
 Following is the xml file:
 ?xml version=1.0 encoding=UTF-8 standalone=yes?
 ns1:ConfigInfo xmlns:ns1=http://configload/Common;ns1:Header 
 CreateTime=Wed Feb 08 12:02:07 EST 2006 CreateBy=sisa Version=4.0 
 Type=wfTemplatens1:Keysns1:Key Value=IBS Add 
 12/ns1:Key/ns1:Keys/ns1:Headerns1:BodyXMLItem?xml version=1.0 
 encoding=UTF-8 standalone=yes?
 ns1:Package Name=Workflow Id=Workflow 
 xmlns:ns1=http://www.wfmc.org/XPDL1.0;
 ns1:PackageHeader
 ns1:XPDLVersion1.0/ns1:XPDLVersion
 ns1:VendorHP/ns1:Vendor
 ns1:Created/ns1:Created
 /ns1:PackageHeader
 ns1:RedefinableHeader PublicationStatus=/ns1:RedefinableHeader
 ns1:ConformanceClass GraphConformance=NON_BLOCKED/ns1:ConformanceClass
 ns1:WorkflowProcesses
 ns1:WorkflowProcess Name=IBS Add 12 AccessLevel=PUBLIC Id=IBS Add 12
 ns1:ProcessHeader DurationUnit=D
 ns1:Created/ns1:Created
 /ns1:ProcessHeader
 ns1:RedefinableHeader PublicationStatus=/ns1:RedefinableHeader
 ns1:Activities
 ns1:Activity Id=Notify Target
 ns1:Implementation
 ns1:No/ns1:No
 /ns1:Implementation
 ns1:FinishMode
 ns1:Automatic/ns1:Automatic
 /ns1:FinishMode
 ns1:TransitionRestrictions
 ns1:TransitionRestriction
 ns1:Join Type=XOR/ns1:Join
 ns1:Split Type=XOR/ns1:Split
 /ns1:TransitionRestriction
 /ns1:TransitionRestrictions
 ns1:ExtendedAttributes
 ns1:ExtendedAttribute Name=XOffset Value=151/ns1:ExtendedAttribute
 ns1:ExtendedAttribute Name=YOffset Value=602/ns1:ExtendedAttribute
 ns1:ExtendedAttribute Name=ActionVertexType 
 Value=0/ns1:ExtendedAttribute
 ns1:ExtendedAttribute Name=activityTypeId Value=/ns1:ExtendedAttribute
 ns1:ExtendedAttribute Name=actions Value=actions/ns1:ExtendedAttribute
 ns1:ExtendedAttribute Name=actions Value=actions
 ns1:Actions
 ns1:Action Name=workflowstudio.customactiondefine.xml.callsub 
 Id=CallSubworkflow
 ns1:FixedParams
 ns1:Param Name=tempId IsText=false Value=quot;IBS 
 Notificationquot;/ns1:Param
 ns1:Param Name=callMode IsText=false/ns1:Param
 ns1:Param Name=activityId IsText=false 
 Value=quot;successquot;/ns1:Param
 ns1:Param Name=childCallback IsText=false/ns1:Param
 /ns1:FixedParams
 /ns1:Action
 /ns1:Actions
 /ns1:ExtendedAttribute
 /ns1:ExtendedAttributes
 /ns1:Activity
 ns1:Activity Id=Prepare Oracle
 ns1:Implementation
 ns1:No/ns1:No
 /ns1:Implementation
 ns1:FinishMode
 ns1:Automatic/ns1:Automatic
 /ns1:FinishMode
 ns1:ExtendedAttributes
 ns1:ExtendedAttribute Name=XOffset Value=151/ns1:ExtendedAttribute
 ns1:ExtendedAttribute Name=YOffset Value=372/ns1:ExtendedAttribute
 ns1:ExtendedAttribute Name=ActionVertexType 
 Value=0/ns1:ExtendedAttribute
 ns1:ExtendedAttribute Name=activityTypeId Value=/ns1:ExtendedAttribute
 ns1:ExtendedAttribute Name=actions Value=actions/ns1:ExtendedAttribute
 ns1:ExtendedAttribute Name=actions Value=actions
 ns1:Actions
 ns1:Action Name=workflowstudio.customactiondefine.xml.app Id=Service
 ns1:FixedParams
 ns1:Param Name=id IsText=false Value=ExternalCall/ns1:Param
 ns1:Param Name=async IsText=false/ns1:Param
 ns1:Param Name=retVar IsText=false Value=/ns1:Param
 /ns1:FixedParams
 ns1:Params
 ns1:Param Name=External Call

[jira] Commented: (XMLBEANS-338) After save, the xml file becomes incomplete

2007-06-29 Thread Jacob Danner (JIRA)


[ 
https://issues.apache.org/jira/browse/XMLBEANS-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509127
 ] 

Jacob Danner commented on XMLBEANS-338:
---

Can you repro this just using your java src.

Also, why is there an extra PI in your instance. 
RE:
XMLItem?xml version=1.0 encoding=UTF-8 standalone=yes?
ns1:Package Name=Workflow Id=Workflow 
xmlns:ns1=http://www.wfmc.org/XPDL1.0;
ns1:PackageHeader

Thanks,
-Jacob Danner

 After save, the xml file becomes incomplete
 -

 Key: XMLBEANS-338
 URL: https://issues.apache.org/jira/browse/XMLBEANS-338
 Project: XMLBeans
  Issue Type: Bug
  Components: XmlObject
 Environment: OS: Windows 2003 Server
 App Server: Weblogic 9.2 mp1
Reporter: Helen Liu
Priority: Critical

 Hi,
 We are the xmlbean user.
 Recently, we encounter a strange issue, that is, when the program execute the 
 following code, the xml file become incomplete.
 obj.save( writer, prettyPrintOpts );
 Here, obj is an object of org.apache.xmlbeans.XmlObject;
  writer is an instance of java.io.StringWriter;
  prettyPrintOpts is org.apache.xmlbeans.XmlOptions;
 In obj, everything is well, the xml file is complete, but after obj.save( 
 writer, prettyPrintOpts );, the string in writer is incomplete, the last 
 charactors is Pac, instead of /Package.
 But if I add some attributes or delete some attributes in Action node, this 
 issue would be gone.
 And only this xml file has this issue.
 Any idea about this problem should be appreciated!
 Following is the xml file:
 ?xml version=1.0 encoding=UTF-8 standalone=yes?
 ns1:ConfigInfo xmlns:ns1=http://configload/Common;ns1:Header 
 CreateTime=Wed Feb 08 12:02:07 EST 2006 CreateBy=sisa Version=4.0 
 Type=wfTemplatens1:Keysns1:Key Value=IBS Add 
 12/ns1:Key/ns1:Keys/ns1:Headerns1:BodyXMLItem?xml version=1.0 
 encoding=UTF-8 standalone=yes?
 ns1:Package Name=Workflow Id=Workflow 
 xmlns:ns1=http://www.wfmc.org/XPDL1.0;
 ns1:PackageHeader
 ns1:XPDLVersion1.0/ns1:XPDLVersion
 ns1:VendorHP/ns1:Vendor
 ns1:Created/ns1:Created
 /ns1:PackageHeader
 ns1:RedefinableHeader PublicationStatus=/ns1:RedefinableHeader
 ns1:ConformanceClass GraphConformance=NON_BLOCKED/ns1:ConformanceClass
 ns1:WorkflowProcesses
 ns1:WorkflowProcess Name=IBS Add 12 AccessLevel=PUBLIC Id=IBS Add 12
 ns1:ProcessHeader DurationUnit=D
 ns1:Created/ns1:Created
 /ns1:ProcessHeader
 ns1:RedefinableHeader PublicationStatus=/ns1:RedefinableHeader
 ns1:Activities
 ns1:Activity Id=Notify Target
 ns1:Implementation
 ns1:No/ns1:No
 /ns1:Implementation
 ns1:FinishMode
 ns1:Automatic/ns1:Automatic
 /ns1:FinishMode
 ns1:TransitionRestrictions
 ns1:TransitionRestriction
 ns1:Join Type=XOR/ns1:Join
 ns1:Split Type=XOR/ns1:Split
 /ns1:TransitionRestriction
 /ns1:TransitionRestrictions
 ns1:ExtendedAttributes
 ns1:ExtendedAttribute Name=XOffset Value=151/ns1:ExtendedAttribute
 ns1:ExtendedAttribute Name=YOffset Value=602/ns1:ExtendedAttribute
 ns1:ExtendedAttribute Name=ActionVertexType 
 Value=0/ns1:ExtendedAttribute
 ns1:ExtendedAttribute Name=activityTypeId Value=/ns1:ExtendedAttribute
 ns1:ExtendedAttribute Name=actions Value=actions/ns1:ExtendedAttribute
 ns1:ExtendedAttribute Name=actions Value=actions
 ns1:Actions
 ns1:Action Name=workflowstudio.customactiondefine.xml.callsub 
 Id=CallSubworkflow
 ns1:FixedParams
 ns1:Param Name=tempId IsText=false Value=quot;IBS 
 Notificationquot;/ns1:Param
 ns1:Param Name=callMode IsText=false/ns1:Param
 ns1:Param Name=activityId IsText=false 
 Value=quot;successquot;/ns1:Param
 ns1:Param Name=childCallback IsText=false/ns1:Param
 /ns1:FixedParams
 /ns1:Action
 /ns1:Actions
 /ns1:ExtendedAttribute
 /ns1:ExtendedAttributes
 /ns1:Activity
 ns1:Activity Id=Prepare Oracle
 ns1:Implementation
 ns1:No/ns1:No
 /ns1:Implementation
 ns1:FinishMode
 ns1:Automatic/ns1:Automatic
 /ns1:FinishMode
 ns1:ExtendedAttributes
 ns1:ExtendedAttribute Name=XOffset Value=151/ns1:ExtendedAttribute
 ns1:ExtendedAttribute Name=YOffset Value=372/ns1:ExtendedAttribute
 ns1:ExtendedAttribute Name=ActionVertexType 
 Value=0/ns1:ExtendedAttribute
 ns1:ExtendedAttribute Name=activityTypeId Value=/ns1:ExtendedAttribute
 ns1:ExtendedAttribute Name=actions Value=actions/ns1:ExtendedAttribute
 ns1:ExtendedAttribute Name=actions Value=actions
 ns1:Actions
 ns1:Action Name=workflowstudio.customactiondefine.xml.app Id=Service
 ns1:FixedParams
 ns1:Param Name=id IsText=false Value=ExternalCall/ns1:Param
 ns1:Param Name=async IsText=false/ns1:Param
 ns1:Param Name=retVar IsText=false Value=/ns1:Param
 /ns1:FixedParams
 ns1:Params
 ns1:Param Name=External Call Name IsText=false 
 Value=quot;UserEnableDisableWFExtCallquot;/ns1:Param
 ns1:Param Name=requestId IsText=false 
 Value=toInt($RequestId)/ns1:Param
 ns1:Param Name=wf instance Id IsText=false Value=$_instId/ns1:Param
 ns1

Re: Validation Errors.

2007-06-27 Thread Jacob Danner


This is really more of a question for the user group so including that
list with this email.

To get error information on the validation errors you need to use an
XmlOptions with an errorListener set.
I think this is covered in the documentation, but just in case here is
a snippet of how you might do this.

List err = new LinkedList();
XmlOptions xo = XmlOptions().setErrorListener(err);
XmlObject.validate(xo);

The  err object  will now be populated if any valdation errors occured
then you can cast the list item  to an XmlError and get the same
information you saw using validate.cmd.

-Jacob Danner


On 6/27/07, baisa, darwin [EMAIL PROTECTED] wrote:

Can any one help me to get Validation errors when we validate a node or
file? The method validate() is giving whether the node is valid or not.
But I am unable to get the validation errors. When I validate a XML file
against a XSD using validate.cmd its giving detailed list errors. Is
there any way in API to get these lists of errors?



Regards,

Darwin Baisa






Confidentiality Notice:
The information contained in this electronic message and any attachment(s)
to this message are intended for the exclusive use of the recipient(s) and
may contain confidential, privileged or proprietary information. If you are
not the intended recipient, please notify the sender immediately, delete all
copies of this message and any attachment(s). Any other use of the E-Mail by
you is prohibited.




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

Re: [VOTE] XmlBeans 2.3.0 Release

2007-05-23 Thread Jacob Danner


[X] +1  -  I am in favor of this release, and can help

-Jacob Danner

On 5/23/07, Cezar Andrei [EMAIL PROTECTED] wrote:

[X] +1  -  I am in favor of this release, and can help

Cezar

 -Original Message-
 From: Radu Preotiuc-Pietro [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, May 22, 2007 7:29 PM
 To: dev@xmlbeans.apache.org; [EMAIL PROTECTED];
 [EMAIL PROTECTED]
 Subject: [VOTE] XmlBeans 2.3.0 Release

 Based on the feedback received:


http://mail-archives.apache.org/mod_mbox/xmlbeans-user/200705.mbox/ajax/
 [EMAIL PROTECTED]

http://mail-archives.apache.org/mod_mbox/xmlbeans-dev/200705.mbox/ajax/%
 [EMAIL PROTECTED]

 I am cancelling the current vote and start a new one in its place to
 extend the deadline. I think everyone who voted for RC3 will have to
 re-cast their vote, since this is a new set of files.

 Please vote on the release of XmlBeans 2.3.0 as it currently exists on
 http://xmlbeans.apache.org/dist as xmlbeans-2.3.0-RC4*. If the vote
 turns out positive, these archives are going to become the final
release
 and be renamed to xmlbeans-2.3.0*, then signed and uploaded to the
 download servers.

 Everyone is welcome to make their opinion heard, however the only
 binding votes are those of commiters and PMC members. In order for the
 vote to pass, we need a majority approval and at least three binding
+1
 votes.

 This vote will end Friday, May 25th, 2007, 5pm PDT, so make sure to
cast
 your vote by then as follows:

 [ ] +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)

 Radu

 Notice:  This email message, together with any attachments, may
contain
 information  of  BEA Systems,  Inc.,  its subsidiaries  and
affiliated
 entities,  that may be confidential,  proprietary,  copyrighted
and/or
 legally privileged, and is intended solely for the use of the
individual
 or entity named in this message. If you are not the intended
recipient,
 and have received this message in error, please immediately return
this by
 email and then delete it.

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


Notice:  This email message, together with any attachments, may contain 
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated 
entities,  that may be confidential,  proprietary,  copyrighted  and/or legally 
privileged, and is intended solely for the use of the individual or entity 
named in this message. If you are not the intended recipient, and have received 
this message in error, please immediately return this by email and then delete 
it.

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




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

Re: [VOTE] XmlBeans 2.3.0 Release

2007-05-18 Thread Jacob Danner


[x ] +1  -  I am in favor of this release, and can help
-Jacob Danner

On 5/18/07, Chris [EMAIL PROTECTED] wrote:

Quick question - why is the source zip/tgz for RC3 3MB smaller than for
the first 2 RCs?


 [ ] +1  -  I am in favor of this release, and can help
 [x] +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)


--
Chris
HMGCC

The information contained in this message (and any attachments) may
be confidential and is intended for the sole use of the named addressee.
Access, copying, alteration or re-use of the e-mail by anyone other
than the intended recipient is unauthorised. If you are not the intended
recipient please advise the sender immediately by returning the e-mail
and deleting it from your system.

This information may be exempt from disclosure under Freedom Of Information
Act 2000 and may be subject to exemption under other UK information
legislation. Refer disclosure requests to the Information Officer.


The original of this email was scanned for viruses by the Government Secure 
Intranet Anti-Virus service supplied by CableWireless in partnership with 
MessageLabs. (CCTM Certificate Number 2006/04/0007.) On leaving the GSi this email 
was certified virus free.
Communications via the GSi may be automatically logged, monitored and/or 
recorded for legal purposes.

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




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

Re: XMLBeans v2.3.0 RC2

2007-05-11 Thread Jacob Danner


(All Non-Binding)
+1 for fixing Maven dependencies
+1 for removing QName from xmlbeans jar
+1 for a new RC

let me know what I can do to help,
-Jacob Danner


On 5/11/07, Cezar Andrei [EMAIL PROTECTED] wrote:

+1 for fixing Maven dependencies
+1 for removing QName from xmlbeans jar
+1 for a new RC

Cezar

 -Original Message-
 From: Radu Preotiuc-Pietro [mailto:[EMAIL PROTECTED]
 Sent: Thursday, May 10, 2007 9:12 PM
 To: dev@xmlbeans.apache.org
 Subject: Re: XMLBeans v2.3.0 RC2

 Thanks Chris,

 I'd say let's go with the current jsr173_api.jar for now and when we
 update the Maven repository (after release), we'll add the dependency
to
 stax-api there. This way, Maven people are happy, users downloading
the
 release are happy (because they don't need to change their classpath)
 and people who want the release and stax-api can also get what they
want
 obviously.

 On the other hand, about XMLBEANS-330 and XMLBEANS-324 (the QName
class
 conflict), after putting in some thought, I would actually like to
clean
 that up before the release and move the offending classes in a
different
 jar. I have the change ready to check in, but after that we would need
 to create a new RC...

 Radu

 On Tue, 2007-05-08 at 10:15 +0100, Chris wrote:
  My module tests still work fine with this version.
  Have you looked at bug 308 (use stax-api-1.0.1 instead of
jsr173-1.0)
  since January? Seems like an easy change if it's all ASL...
  https://issues.apache.org/jira/browse/XMLBEANS-308
 
  +1 from me
  Chris
 

 Notice:  This email message, together with any attachments, may
contain
 information  of  BEA Systems,  Inc.,  its subsidiaries  and
affiliated
 entities,  that may be confidential,  proprietary,  copyrighted
and/or
 legally privileged, and is intended solely for the use of the
individual
 or entity named in this message. If you are not the intended
recipient,
 and have received this message in error, please immediately return
this by
 email and then delete it.

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


Notice:  This email message, together with any attachments, may contain 
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated 
entities,  that may be confidential,  proprietary,  copyrighted  and/or legally 
privileged, and is intended solely for the use of the individual or entity 
named in this message. If you are not the intended recipient, and have received 
this message in error, please immediately return this by email and then delete 
it.

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




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

[jira] Resolved: (XMLBEANS-330) javax.xml.namespace classes included in archive

2007-05-08 Thread Jacob Danner (JIRA)


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacob Danner resolved XMLBEANS-330.
---

Resolution: Duplicate
  Assignee: Jacob Danner

Looks like another case of:
http://issues.apache.org/jira/browse/XMLBEANS-324

The issue has a solution (removing the class from the jar) but also some 
explanation as to why XmlBeans contains that class.

'''
Problem is XmlBeans is designed to work with JDK1.4 and JDK1.4 doesn't have 
this class if I am not mistaken. Having that class in the jar allows users of 
both JDK1.4 and JDK1.5 and above to use XmlBeans without having to worry about 
a dependency that really is not available anywhere for download.

What environment are you in that makes this error happen? Is it possible for 
you to remove this class from the jar? 
'''

 javax.xml.namespace classes included in archive
 ---

 Key: XMLBEANS-330
 URL: https://issues.apache.org/jira/browse/XMLBEANS-330
 Project: XMLBeans
  Issue Type: Bug
Affects Versions: Version 2.2
 Environment: N/A
Reporter: David J. M. Karlsen
 Assigned To: Jacob Danner
Priority: Blocker

 The archive at http://repo1.maven.org/maven2/xmlbeans/xbean/2.2.0/ includes 
 javax.xml.namespace classes (QName and NamespaceContext) - which are part of 
 the API specification - and thus should not be included in the archive.
 This is especially problematic when using xbeans inside containers which also 
 loads these classes, ending up in ClassCast exceptions, LinkageError and the 
 likes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Assigned: (XMLBEANS-329) Problems with ADB Client and XMLBeans Service

2007-05-06 Thread Jacob Danner (JIRA)

[
https://issues.apache.org/jira/browse/XMLBEANS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jacob Danner reassigned XMLBEANS-329:
-

Assignee: Jacob Danner

Problems with ADB Client and XMLBeans Service
-

Key: XMLBEANS-329
URL: https://issues.apache.org/jira/browse/XMLBEANS-329
Project: XMLBeans
Issue Type: Bug
Components: Binding
Affects Versions: Version 2.2
Environment: Windows XP SP2, Axis 2 1.2, Java 1.6
Reporter: Jorge Fernández
Assigned To: Jacob Danner
Attachments: API.wsdl, ClientXmlBeans.java, CodeGenerationUtility.java

This JIRA is related with the message from the axis-user mailing list Issue
with ADB and parsing a response message (namespaces)
I couldn't reproduce the problem I described in that email but when I fixed
that problem I found another one and this is which I'm reporting.
First, some introduction.
In my response message there is an array of Stages which have one or more
Configurations. Each Configuration has AbstractParameters and
PrimitiveParameters (that inherit from Parameter). Also each Parameter may
depend on other so the class Parameter has an array of Parameter called
dependencies.
My problem happens only if I have ADB at client side and XMLBeans at service
side. Any other combination works perfectly. (I attach the wsdl and client
and service for both databindings).
When my ADB client parses the response message, it enters Stage.Factory.parse
method, then it enters, Configuration.Factory.parse method. Next,
AbstractParameter.Factory.parse method (because the first parameter is
abstract) and later it want to parse the dependencies of this parameter so it
enters Parameter.Factory.parse method. Here, there is a PrimitiveParameter
with no dependencies on oher parameters so it enters Signal.Factory.parse
method for getting signal dependencies. It returns ok
Finally, the problem comes out when after getting SignalDependencies from
this PrimitiveParameter, it gets the Type element which is in the Parameter
class and now there is the gain element that is part of PrimitiveParameter
and not of his parent. so it throws an exception because it didn't expect it.
Hope this explanation could be useful but if not, the wsdl could be.
I refer you to JIRA: https://issues.apache.org/jira/browse/AXIS2-2578
That JIRA is the same as this one. I reported it as an ADB bug but as you can
see there, finally the problem seems to be xmlbeans. You can also find there
the files to reproduce the JIRA.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

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

[jira] Commented: (XMLBEANS-329) Problems with ADB Client and XMLBeans Service

2007-05-06 Thread Jacob Danner (JIRA)

[
https://issues.apache.org/jira/browse/XMLBEANS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493938
]

Jacob Danner commented on XMLBEANS-329:
---

I'll give it a look this afternoon and/or try to repro this issue using Axis.
thx Amila/Jorge

Problems with ADB Client and XMLBeans Service
-

Key: XMLBEANS-329
URL: https://issues.apache.org/jira/browse/XMLBEANS-329
Project: XMLBeans
Issue Type: Bug
Components: Binding
Affects Versions: Version 2.2
Environment: Windows XP SP2, Axis 2 1.2, Java 1.6
Reporter: Jorge Fernández
Attachments: API.wsdl, ClientXmlBeans.java, CodeGenerationUtility.java

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

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

[jira] Commented: (XMLBEANS-329) Problems with ADB Client and XMLBeans Service

2007-05-05 Thread Jacob Danner (JIRA)


[ 
https://issues.apache.org/jira/browse/XMLBEANS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493890
 ] 

Jacob Danner commented on XMLBEANS-329:
---

It appears the first difference I notice in the instance you generated in your 
comment versus the instance generated from straight xmlbeans code is that the 
attributes like:
xsi:type=xsd:PrimitiveParameter 
are missing.
Can you indicate why this might be happening? In xmlbeans code, this is 
appearing, but it is not present in the payload you attached.

I'm still curious about how your default package name is getting created. The 
package name and the fact that the code gets generated properly using plain 
xmlbeans leads me to think that you might not be using the type (axiom vs. 
xmlbeans) you think you are using.

I've confirmed the same plain xmlbeans code works just fine with with version 
2.2 and the latest svn bits.

I'm not familiar with axis2. Can you tell me how you are generating the types 
you are using from this WSDL? Can you also try the code I've attached (with 
modifications) and let us know if you are having problems.

 Problems with ADB Client and XMLBeans Service
 -

 Key: XMLBEANS-329
 URL: https://issues.apache.org/jira/browse/XMLBEANS-329
 Project: XMLBeans
  Issue Type: Bug
  Components: Binding
Affects Versions: Version 2.2
 Environment: Windows XP SP2, Axis 2 1.2, Java 1.6
Reporter: Jorge Fernández
 Attachments: API.wsdl, ClientXmlBeans.java


 This JIRA is related with the message from the axis-user mailing list Issue 
 with ADB and parsing a response message (namespaces)
 I couldn't reproduce the problem I described in that email but when I fixed 
 that problem I found another one and this is which I'm reporting.
 First, some introduction.
 In my response message there is an array of  Stages which have one or more 
 Configurations. Each Configuration has AbstractParameters and 
 PrimitiveParameters (that inherit from Parameter). Also each Parameter may 
 depend on other so the class Parameter has an array of Parameter called 
 dependencies.
 My problem happens only if I have ADB at client side and XMLBeans at service 
 side. Any other combination works perfectly. (I attach the wsdl and client 
 and service for both databindings).
 When my ADB client parses the response message, it enters Stage.Factory.parse 
 method, then it enters, Configuration.Factory.parse method. Next, 
 AbstractParameter.Factory.parse method (because the first parameter is 
 abstract) and later it want to parse the dependencies of this parameter so it 
 enters Parameter.Factory.parse method. Here, there is a PrimitiveParameter 
 with no dependencies on oher parameters so it enters Signal.Factory.parse 
 method for getting signal dependencies. It returns ok
 Finally, the problem comes out when after getting SignalDependencies from 
 this PrimitiveParameter, it gets the Type element which is in the Parameter 
 class and now there is the gain element that is part of PrimitiveParameter 
 and not of his parent. so it throws an exception because it didn't expect it.
 Hope this explanation could be useful but if not, the wsdl could be.
 I refer you to JIRA: https://issues.apache.org/jira/browse/AXIS2-2578 
 That JIRA is the same as this one. I reported it as an ADB bug but as you can 
 see there, finally the problem seems to be xmlbeans. You can also find there 
 the files to reproduce the JIRA.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Commented: (XMLBEANS-329) Problems with ADB Client and XMLBeans Service


[ 
https://issues.apache.org/jira/browse/XMLBEANS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493749
 ] 

Jacob Danner commented on XMLBEANS-329:
---

Hi Jorge,
Can we get some more information on this. What is the error you are seeing? Is 
there a stacktrace? have you tried validating teh instance? Are there errors 
with the validation? What do the payloads/instances look like? What should they 
look like?


I noticed in srcs attached to the Axis jira issue that the package name is 
different from what is generated by xmlbeans by default from running scomp 
API.wsdl. 
The package used in your code:
api.op_messages.xsd ...
but by default is
api.opMessages.xsd ...

are there other types being used in your application that might be causing some 
kind of conflict.
Also, what needs to be done to repro this issue with your sources? 

Thanks,
-Jacob Danner

 Problems with ADB Client and XMLBeans Service
 -

 Key: XMLBEANS-329
 URL: https://issues.apache.org/jira/browse/XMLBEANS-329
 Project: XMLBeans
  Issue Type: Bug
  Components: Binding
Affects Versions: Version 2.2
 Environment: Windows XP SP2, Axis 2 1.2, Java 1.6
Reporter: Jorge Fernández

 This JIRA is related with the message from the axis-user mailing list Issue 
 with ADB and parsing a response message (namespaces)
 I couldn't reproduce the problem I described in that email but when I fixed 
 that problem I found another one and this is which I'm reporting.
 First, some introduction.
 In my response message there is an array of  Stages which have one or more 
 Configurations. Each Configuration has AbstractParameters and 
 PrimitiveParameters (that inherit from Parameter). Also each Parameter may 
 depend on other so the class Parameter has an array of Parameter called 
 dependencies.
 My problem happens only if I have ADB at client side and XMLBeans at service 
 side. Any other combination works perfectly. (I attach the wsdl and client 
 and service for both databindings).
 When my ADB client parses the response message, it enters Stage.Factory.parse 
 method, then it enters, Configuration.Factory.parse method. Next, 
 AbstractParameter.Factory.parse method (because the first parameter is 
 abstract) and later it want to parse the dependencies of this parameter so it 
 enters Parameter.Factory.parse method. Here, there is a PrimitiveParameter 
 with no dependencies on oher parameters so it enters Signal.Factory.parse 
 method for getting signal dependencies. It returns ok
 Finally, the problem comes out when after getting SignalDependencies from 
 this PrimitiveParameter, it gets the Type element which is in the Parameter 
 class and now there is the gain element that is part of PrimitiveParameter 
 and not of his parent. so it throws an exception because it didn't expect it.
 Hope this explanation could be useful but if not, the wsdl could be.
 I refer you to JIRA: https://issues.apache.org/jira/browse/AXIS2-2578 
 That JIRA is the same as this one. I reported it as an ADB bug but as you can 
 see there, finally the problem seems to be xmlbeans. You can also find there 
 the files to reproduce the JIRA.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Commented: (XMLBEANS-329) Problems with ADB Client and XMLBeans Service


[ 
https://issues.apache.org/jira/browse/XMLBEANS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493765
 ] 

Jacob Danner commented on XMLBEANS-329:
---

I whittled down your src from the other jira issue and will post it later, here 
is the content of the instances you are creating and working with. Can you let 
us know how/where this is failing for you and what is being expected?

Detailed monitoring stages.
XMLTEXT-REQUEST: xsd:getDetailedMonitoringStages 
xmlns:xsd=http://op_messages.api/xsd;
  xsd:param0string/xsd:param0
/xsd:getDetailedMonitoringStages
XMLTEXT-RESPONSE: xsd:getDetailedMonitoringStagesResponse 
xmlns:xsd=http://op_messages.api/xsd;
  xsd:return
xsd1:stageID xmlns:xsd1=http://api/xsd;0/xsd1:stageID
xsd1:configurations xmlns:xsd1=http://api/xsd;
  xsd1:abstractParameters
xsd1:nameabstract0/xsd1:name
xsd:parameterDependencies xsi:type=xsd:PrimitiveParameter 
xmlns:xsd=http://api/xsd; 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
  xsd:nameprimitive0/xsd:name
  xsd:signalDependencies
xsd:namesignal0/xsd:name
  /xsd:signalDependencies
  xsd:signalDependencies
xsd:namesignal1/xsd:name
  /xsd:signalDependencies
  xsd:typeprimitiveType0/xsd:type
  xsd:unitsunits0/xsd:units
  xsd:max2/xsd:max
  xsd:min1/xsd:min
/xsd:parameterDependencies
xsd:parameterDependencies xsi:type=xsd:AbstractParameter 
xmlns:xsd=http://api/xsd; 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
  xsd:nameabstract1/xsd:name
  xsd:signalDependencies
xsd:namesignal0/xsd:name
  /xsd:signalDependencies
  xsd:signalDependencies
xsd:namesignal1/xsd:name
  /xsd:signalDependencies
  xsd:typeabstractType1/xsd:type
  xsd:valuesvalue0/xsd:values
  xsd:valuesvalue1/xsd:values
/xsd:parameterDependencies
xsd1:signalDependencies
  xsd1:namesignal0/xsd1:name
/xsd1:signalDependencies
xsd1:signalDependencies
  xsd1:namesignal1/xsd1:name
/xsd1:signalDependencies
xsd1:typeabstractType0/xsd1:type
xsd1:valuesvalue0/xsd1:values
xsd1:valuesvalue1/xsd1:values
  /xsd1:abstractParameters
  xsd1:abstractParameters
xsd1:nameabstract1/xsd1:name
xsd1:signalDependencies
  xsd1:namesignal0/xsd1:name
/xsd1:signalDependencies
xsd1:signalDependencies
  xsd1:namesignal1/xsd1:name
/xsd1:signalDependencies
xsd1:typeabstractType1/xsd1:type
xsd1:valuesvalue0/xsd1:values
xsd1:valuesvalue1/xsd1:values
  /xsd1:abstractParameters
  xsd1:id0/xsd1:id
  xsd1:primitiveParameters
xsd1:nameprimitive0/xsd1:name
xsd1:signalDependencies
  xsd1:namesignal0/xsd1:name
/xsd1:signalDependencies
xsd1:signalDependencies
  xsd1:namesignal1/xsd1:name
/xsd1:signalDependencies
xsd1:typeprimitiveType0/xsd1:type
xsd1:unitsunits0/xsd1:units
xsd1:max2/xsd1:max
xsd1:min1/xsd1:min
  /xsd1:primitiveParameters
  xsd1:primitiveParameters
xsd1:nameprimitive1/xsd1:name
xsd1:signalDependencies
  xsd1:namesignal0/xsd1:name
/xsd1:signalDependencies
xsd1:signalDependencies
  xsd1:namesignal1/xsd1:name
/xsd1:signalDependencies
xsd1:typeprimitiveType1/xsd1:type
xsd1:unitsunits1/xsd1:units
xsd1:max2/xsd1:max
xsd1:min1/xsd1:min
  /xsd1:primitiveParameters
/xsd1:configurations
xsd1:configurations xmlns:xsd1=http://api/xsd;
  xsd1:abstractParameters
xsd1:nameabstract0/xsd1:name
xsd:parameterDependencies xsi:type=xsd:PrimitiveParameter 
xmlns:xsd=http://api/xsd; 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
  xsd:nameprimitive0/xsd:name
  xsd:signalDependencies
xsd:namesignal0/xsd:name
  /xsd:signalDependencies
  xsd:signalDependencies
xsd:namesignal1/xsd:name
  /xsd:signalDependencies
  xsd:typeprimitiveType0/xsd:type
  xsd:unitsunits0/xsd:units
  xsd:max2/xsd:max
  xsd:min1/xsd:min
/xsd:parameterDependencies
xsd:parameterDependencies xsi:type=xsd:AbstractParameter 
xmlns:xsd=http://api/xsd; 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
  xsd:nameabstract1/xsd:name
  xsd:signalDependencies
xsd:namesignal0/xsd:name
  /xsd:signalDependencies
  xsd:signalDependencies
xsd:namesignal1/xsd:name
  /xsd:signalDependencies
  xsd:typeabstractType1/xsd:type
  xsd:valuesvalue0/xsd:values
  xsd:valuesvalue1/xsd:values
/xsd:parameterDependencies
xsd1:signalDependencies
  xsd1

[jira] Updated: (XMLBEANS-329) Problems with ADB Client and XMLBeans Service

[
https://issues.apache.org/jira/browse/XMLBEANS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jacob Danner updated XMLBEANS-329:
--

Attachment: ClientXmlBeans.java

client srcs used to produce text output

Problems with ADB Client and XMLBeans Service
-

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

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

[jira] Updated: (XMLBEANS-329) Problems with ADB Client and XMLBeans Service

[
https://issues.apache.org/jira/browse/XMLBEANS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jacob Danner updated XMLBEANS-329:
--

Attachment: API.wsdl

run scomp over this WSDL, from teh Axis Jira issue.

Not granting ASF license as this WSDL came from another issue

Problems with ADB Client and XMLBeans Service
-

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

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

Re: URGENT: Could not resolve the node to a handle

2007-04-26 Thread Jacob Danner


Hi Asaf,
You say
... code that is currently failing worked perfectly until recently. ...
Thats not usually how code works, are you sure nothing has changed. If
so it would help us figure out whats going on.

What is the error you are seeing? What does the instance and query you
are trying to run look like?

Are you using the proper version of saxon with XmlBeans? What version
of xmlbeans are you using?


Have you tried with a different DOM implementation? ie. save our your
XML to a file, the reload it using standard DOM apis and execute the
code? Can you try this and let us know the result. I ask this because
the code snippet you posted above looks more like saxon than xmlbeans.

adding the user email alias as that seems like a more appropriate
place for this kind of question.

-Jacob Danner


On 4/26/07, Asaf Lahav [EMAIL PROTECTED] wrote:

Hi Everybody... I need your help on this...
This is quite urgent...

-Original Message-
From: Asaf Lahav [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 26, 2007 5:57 PM
To: dev@xmlbeans.apache.org
Subject: RE: URGENT: Could not resolve the node to a handle

tried it... didn't work either...


-Original Message-
From: Chris [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 26, 2007 1:39 PM
To: dev@xmlbeans.apache.org
Subject: Re: URGENT: Could not resolve the node to a handle

If you want to use the saxon XPath engine (to use xpath2 for example)
you should explicitly set the system parameter, not rely on the classpath.

Use:

System.setProperty(javax.xml.transform.TransformerFactory,
net.sf.saxon.TransformerFactoryImpl);

before initialising a singleton factory.

or pass it to the jvm as a parameter:
java myclass
-Djavax.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl

HTH
Chris

Asaf Lahav wrote:
 Sorry for cross posting. it is urgent.



 Hi all,



 First I wanted to state that the code that is currently failing worked
 perfectly until recently. And I can't recall of any changes that were
 made to the environment in which the JVM is running.

 The problem is that when I perform the following code on a Xmlbean dom
 node, it fails:

 public static Node SeekNode(XPathExpression expression, Element element)
 throws XPathExpressionException{

 return (Node)expression.evaluate(element,XPathConstants.NODE);

 }



 SOMETIMES fails.



 Apparently, the XPathExpression actual object is resolved to jaxp xpath
 engine even though SAXON is available in classpath. Could that be the
 problem?



 Any help would be appreciated.

 Thanks in advance,

 Asaf


 This email was received from the INTERNET and scanned by the Government
 Secure Intranet Anti-Virus service supplied by CableWireless in
 partnership with MessageLabs. (CCTM Certificate Number 2006/04/0007.) In
 case of problems, please call your organisation's IT Helpdesk.
 Communications via the GSi may be automatically logged, monitored and/or
 recorded for legal purposes.

--
Chris
HMGCC

The information contained in this message (and any attachments) may
be confidential and is intended for the sole use of the named addressee.
Access, copying, alteration or re-use of the e-mail by anyone other
than the intended recipient is unauthorised. If you are not the intended
recipient please advise the sender immediately by returning the e-mail
and deleting it from your system.

This information may be exempt from disclosure under Freedom Of Information
Act 2000 and may be subject to exemption under other UK information
legislation. Refer disclosure requests to the Information Officer.


The original of this email was scanned for viruses by the Government Secure
Intranet Anti-Virus service supplied by CableWireless in partnership with
MessageLabs. (CCTM Certificate Number 2006/04/0007.) On leaving the GSi this
email was certified virus free.
Communications via the GSi may be automatically logged, monitored and/or
recorded for legal purposes.

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


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


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




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

[jira] Commented: (XMLBEANS-187) sax spec requires local name

2007-04-26 Thread Jacob Danner (JIRA)


[ 
https://issues.apache.org/jira/browse/XMLBEANS-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492145
 ] 

Jacob Danner commented on XMLBEANS-187:
---

This is what java doc for org.xml.sax.Attributes says:
http://java.sun.com/javase/6/docs/api/index.html


The list will not contain attributes that were declared #IMPLIED but not
specified in the start tag. It will also not contain attributes used as
Namespace declarations (xmlns*) unless the
http://xml.org/sax/features/namespace-prefixes feature is set to true
(it is false by default). Because SAX2 conforms to the original
Namespaces in XML recommendation, it normally does not give namespace
declaration attributes a namespace URI.

Some SAX2 parsers may support using an optional feature flag
(http://xml.org/sax/features/xmlns-uris) to request that those
attributes be given URIs, conforming to a later backwards-incompatible
revision of that recommendation. (The attribute's local name will be
the prefix, or xmlns when defining a default element namespace.) For
portability, handler code should always resolve that conflict, rather
than requiring parsers that can change the setting of that feature flag.

If the namespace-prefixes feature (see above) is false, access by
qualified name may not be available; if the
http://xml.org/sax/features/namespaces feature is false, access by
Namespace-qualified names may not be available.



 sax spec requires local name
 

 Key: XMLBEANS-187
 URL: https://issues.apache.org/jira/browse/XMLBEANS-187
 Project: XMLBeans
  Issue Type: Bug
Affects Versions: Version 1.0.4, Version 2
 Environment: windows xp, tested on java 1.4.2 and 1.5
Reporter: Ben Anderson
 Attachments: ben.patch


 I posted this as a mail note a while back:
 http://marc.theaimsgroup.com/?l=xmlbeans-devm=111599749418156w=2
 The problem came about when I tried using the save method in cocoon with 
 saxon.  With xalan everthing works fine, but not with saxon.  Michael Kay 
 claims that saxon is correct:
 http://marc.theaimsgroup.com/?l=xmlbeans-devm=111599522507748w=2
 according to the sax spec:
 http://www.saxproject.org/apidoc/org/xml/sax/Attributes.html#g
 So, no big deal but it definitely breaks unless the patch I will attach is 
 applied.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Closed: (XMLBEANS-318) not able to generate inner classes/interfaces


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacob Danner closed XMLBEANS-318.
-

Assignee: (was: Jacob Danner)

Closing per comments earlier

 not able to generate inner classes/interfaces
 -

 Key: XMLBEANS-318
 URL: https://issues.apache.org/jira/browse/XMLBEANS-318
 Project: XMLBeans
  Issue Type: Bug
Affects Versions: Version 2.2
 Environment: Linux Fedora fc5, tomcat 6.0.7, java1.5.0_11, Axis2 
 1.1.1, xmlbeans 2.2.0
Reporter: Federica Ciotti
Priority: Minor

 I'm using the wsdl2java axis ant task with xmlbeans.
 For each complex element in my xsd referenced in wsdl, let say save_business, 
 I get 
 the two interfaces:
 SaveBusiness.java
 SaveBusinessDocument.java
 and the two classes:
 impl/SaveBusinessDocumentImpl.java
 impl/SaveBusinessImpl.java
 Why don't I get SaveBusiness interface contained in SaveBusinessDocument?
 I thought it depends on the -u options but using this option doesn't make any 
 difference in my case.
   Many Thanks

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Assigned: (XMLBEANS-170) Javadoc error: @link class not fully qualified


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacob Danner reassigned XMLBEANS-170:
-

Assignee: Jacob Danner  (was: Rajiv Bala)

 Javadoc error: @link class not fully qualified
 --

 Key: XMLBEANS-170
 URL: https://issues.apache.org/jira/browse/XMLBEANS-170
 Project: XMLBeans
  Issue Type: Bug
Affects Versions: Version 2
Reporter: Jasper Rosenberg
 Assigned To: Jacob Danner
Priority: Minor

 The following code is generated:
 code
 /** @deprecated [EMAIL PROTECTED] XMLInputStream} */
 public static noNamespace.Address 
 parse(org.apache.xmlbeans.xml.stream.XMLInputStream xis) throws 
 org.apache.xmlbeans.XmlException, 
 org.apache.xmlbeans.xml.stream.XMLStreamException {
   return (noNamespace.Address) 
 org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( xis, type, null ); 
 }
 
 /** @deprecated [EMAIL PROTECTED] XMLInputStream} */
 public static noNamespace.Address 
 parse(org.apache.xmlbeans.xml.stream.XMLInputStream xis, 
 org.apache.xmlbeans.XmlOptions options) throws 
 org.apache.xmlbeans.XmlException, 
 org.apache.xmlbeans.xml.stream.XMLStreamException {
   return (noNamespace.Address) 
 org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( xis, type, options 
 ); }
 
 /** @deprecated [EMAIL PROTECTED] XMLInputStream} */
 public static org.apache.xmlbeans.xml.stream.XMLInputStream 
 newValidatingXMLInputStream(org.apache.xmlbeans.xml.stream.XMLInputStream 
 xis) throws org.apache.xmlbeans.XmlException, 
 org.apache.xmlbeans.xml.stream.XMLStreamException {
   return 
 org.apache.xmlbeans.XmlBeans.getContextTypeLoader().newValidatingXMLInputStream(
  xis, type, null ); }
 
 /** @deprecated [EMAIL PROTECTED] XMLInputStream} */
 public static org.apache.xmlbeans.xml.stream.XMLInputStream 
 newValidatingXMLInputStream(org.apache.xmlbeans.xml.stream.XMLInputStream 
 xis, org.apache.xmlbeans.XmlOptions options) throws 
 org.apache.xmlbeans.XmlException, 
 org.apache.xmlbeans.xml.stream.XMLStreamException {
   return 
 org.apache.xmlbeans.XmlBeans.getContextTypeLoader().newValidatingXMLInputStream(
  xis, type, options ); }
 /code
 I get these warnings from eclipse:
Javadoc: XMLInputStream cannot be resolved to a type
 I believe it just needs to be change to generate this instead:
 code
 /** @deprecated [EMAIL PROTECTED] 
 org.apache.xmlbeans.xml.stream.XMLInputStream} */
 /code

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Assigned: (XMLBEANS-153) validate on set feature doesn't catch values that are invalid against xs:int patterns


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacob Danner reassigned XMLBEANS-153:
-

Assignee: Jacob Danner  (was: Rajiv Bala)

 validate on set feature doesn't catch values that are invalid against 
 xs:int patterns
 ---

 Key: XMLBEANS-153
 URL: https://issues.apache.org/jira/browse/XMLBEANS-153
 Project: XMLBeans
  Issue Type: Bug
  Components: Validator
Affects Versions: Version 2 Beta 1
Reporter: Steve Traut
 Assigned To: Jacob Danner
Priority: Minor

 Using XmlOptions.setValidateOnSet will set up XMLBeans to throw an exception 
 in some cases, but not others. 
 For example, an exception will be thrown when schema restricts xs:int to a 
 max value of 100, but a value higher is set. It will NOT throw an exception 
 when schema restricts xs:int to a pattern of three numerals in succession, 
 but a longer value is set. Setting a longer value does render the XML 
 invalid, as a call to XmlObject.validate shows. But validate on set doesn't 
 catch this. 
 validate on set should set up XMLBeans to catch *anything* that would be 
 invalid in a call to the validate method. Otherwise, it's too 
 counterintuitive to be useful.
 Here's a snippet of the Java code that tries to incorrectly set the value of 
 an id attribute (defined in schema below):
 public boolean isValidOnTheFly()
 {
 private XmlOptions validationOptions = new XmlOptions();
 validationOptions.setValidateOnSet();
 
 TodolistDocument todoList = 
 TodolistDocument.Factory.newInstance(validationOptions);
 Todolist list = todoList.addNewTodolist();
 ItemType item = list.addNewItem();
 item.setName(Procrastinate);
 item.setDescription(A new item.);
 item.setAction(ActionType.SOMEDAY_MAYBE_DEFER);
 
 // Should throw an exception because the value renders the XML 
 invalid.
 item.setId(8587);
 
 System.out.println(todoList.validate());
 return true;
 }
 Here's a snippet from the schema I'm using. Note the id attribute defined as 
 idType:
 xs:complexType name=itemType
 xs:sequence
 xs:element name=name type=xs:string/
 xs:element name=description type=xs:string/
 xs:element name=due_by type=xs:dateTime/
 xs:element name=action type=actionType/
 /xs:sequence
 xs:attribute name=id type=idType/ 
 /xs:complexType
 When the idType is defined as follows, the code throws an exception:
 xs:simpleType name=idType
 xs:restriction base=xs:int
 xs:maxExclusive value=100/
 /xs:restriction
 /xs:simpleType
 When the idType is defined this way, the code throws no exception, although 
 the value set by the code above still renders the XML I'm building invalid:
 xs:simpleType name=idType
 xs:restriction base=xs:int
 xs:pattern value=[0-9][0-9][0-9]/
 /xs:restriction
 /xs:simpleType

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Assigned: (XMLBEANS-161) Unable to cast from cursor.getObject to type generated from schema.


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacob Danner reassigned XMLBEANS-161:
-

Assignee: Jacob Danner  (was: Yana Kadiyska)

 Unable to cast from cursor.getObject to type generated from schema.
 ---

 Key: XMLBEANS-161
 URL: https://issues.apache.org/jira/browse/XMLBEANS-161
 Project: XMLBeans
  Issue Type: Bug
  Components: Cursor
Affects Versions: Version 2 Beta 1
Reporter: Steve Traut
 Assigned To: Jacob Danner
 Attachments: TestCode.zip


 When retrieving XML using cursor.getObject, it appears not possible to cast 
 the returned XML to a specific schema type even when the XML conforms to the 
 schema. The following snippet attempts to retrieve elements using XPath, use 
 a cursor to reach a returned element's parent, then cast the parent XML to a 
 schema type. But the cast fails.
 Code attached.
 private String m_namespaceUri = 
 http://xmlbeans.apache.org/samples/any;;
 String namespaceDecl = declare namespace any=' + m_namespaceUri
 + '; ;
 XmlObject[] someElements = rootDoc.selectPath(namespaceDecl
 + $this//any:stringelement);
 for (int i = 0; i  someElements.length; i++)
 {
 XmlCursor editCursor = someElements[i].newCursor();
 editCursor.toParent();
 ListOfStrings stringList = null;
 try
 {
 // Shouldn't this cast work? //
 stringList = (ListOfStrings) editCursor.getObject();
 System.out.println(stringList);
 } catch (ClassCastException cce)
 {
 continue;
 }
 }

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Assigned: (XMLBEANS-200) XmlObject node copy yields IllegalArgumentException: DocumentWrapper#wrap in Saxon on further XPath executions of copied node


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacob Danner reassigned XMLBEANS-200:
-

Assignee: Jacob Danner  (was: Yana Kadiyska)

 XmlObject node copy yields IllegalArgumentException: DocumentWrapper#wrap in 
 Saxon on further XPath executions of copied node
 -

 Key: XMLBEANS-200
 URL: https://issues.apache.org/jira/browse/XMLBEANS-200
 Project: XMLBeans
  Issue Type: Bug
  Components: XPath
Affects Versions: Version 2
 Environment: Windows XP, Saxon 8.1, Java 1.4_05, XmlBeans 2.0
Reporter: Brian Rafalowski
 Assigned To: Jacob Danner
 Fix For: Version 2

 Attachments: XPathCopy.zip


 A selectPath(Query)  returns a child node of the wrapped document.  The child 
 node is then copied with the XmlObject.copy() method. My application requires 
 a copy of the child node since it will be passed into a Threaded application 
 which has no need to modify the resulting XML. The Child node has further 
 children that I would like to use XPath queries to pull the desired node. 
 However, when I issue a select path on the returned child node, I get the 
 following error:
 java.lang.IllegalArgumentException: DocumentWrapper#wrap: supplied node does 
 not belong to the wrapped DOM document
 I do not wish to construct a new XML document for the Child (and its 
 children) to pass into my application. I just need the fragment to query, as 
 the XML just represents ini type information.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Updated: (XMLBEANS-150) xmlbeans-1.0.4-jdk1.3-src -- ant target docs fails

2007-04-24 Thread Jacob Danner (JIRA)


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacob Danner updated XMLBEANS-150:
--

Priority: Trivial  (was: Major)

 xmlbeans-1.0.4-jdk1.3-src -- ant target docs fails
 

 Key: XMLBEANS-150
 URL: https://issues.apache.org/jira/browse/XMLBEANS-150
 Project: XMLBeans
  Issue Type: Bug
Affects Versions: Version 1.0.4 (jdk1.3 port)
 Environment: winxp/pro, ant 1.6.2, Classic VM (build 1.3.1, J2RE 
 1.3.1 IBM Windows 32 build cn131-20031021
Reporter: korebantic
 Assigned To: Cezar Andrei
Priority: Trivial
 Attachments: patch


   [javadoc] Generating Javadoc
   [javadoc] Javadoc execution
   [javadoc] javadoc: Destination directory not found 
 C:\src\xmlbeans-1.0.4-jdk1.
 3-src\build\docs\reference\reference
   [javadoc] 1 error
  [copy] Copying 1 file to 
 C:\src\xmlbeans-1.0.4-jdk1.3-src\build\docs\refere
 nce
  [copy] Copying 10 files to 
 C:\src\xmlbeans-1.0.4-jdk1.3-src\build\docs\refe
 rence\guide
  [copy] Copying 2 files to 
 C:\src\xmlbeans-1.0.4-jdk1.3-src\build\docs\refer
 ence\images

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Commented: (XMLBEANS-325) Assertion failure in Saver.java:1229

2007-04-19 Thread Jacob Danner (JIRA)


[ 
https://issues.apache.org/jira/browse/XMLBEANS-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489950
 ] 

Jacob Danner commented on XMLBEANS-325:
---

Thats great, thanks Kirk, It's late here, but I'll pick this up in a couple of 
hours.
Thanks again,
-Jacob Danner

 Assertion failure in Saver.java:1229
 

 Key: XMLBEANS-325
 URL: https://issues.apache.org/jira/browse/XMLBEANS-325
 Project: XMLBeans
  Issue Type: Bug
Affects Versions: Version 2.2
 Environment: Java 5, XMLBeans release 2.2.0
Reporter: Kirk Wylie
Priority: Blocker

 I've started seeing assertion failures in Saver.java line 1229 as indicated 
 by the following stack trace:
 java.lang.AssertionError
   at 
 org.apache.xmlbeans.impl.store.Saver$TextSaver.preEmit(Saver.java:1229)
   at org.apache.xmlbeans.impl.store.Saver$TextSaver.emit(Saver.java:1147)
   at 
 org.apache.xmlbeans.impl.store.Saver$TextSaver.emitFinish(Saver.java:946)
   at org.apache.xmlbeans.impl.store.Saver.processFinish(Saver.java:333)
   at org.apache.xmlbeans.impl.store.Saver.process(Saver.java:308)
   at 
 org.apache.xmlbeans.impl.store.Saver$TextSaver.ensure(Saver.java:1547)
   at org.apache.xmlbeans.impl.store.Saver$TextSaver.read(Saver.java:1634)
   at org.apache.xmlbeans.impl.store.Saver$TextReader.read(Saver.java:2233)
   at org.apache.xmlbeans.impl.store.Cursor._save(Cursor.java:613)
   at org.apache.xmlbeans.impl.store.Cursor.save(Cursor.java:2562)
   at 
 org.apache.xmlbeans.impl.values.XmlObjectBase.save(XmlObjectBase.java:183)
   at 
 com.kbcfp.fotech.couteau.xml.XmlHelper.writeDocument(XmlHelper.java:43)
   at 
 com.kbcfp.fotech.couteau.xml.V2OrganizationDataProcessor.writeToWriter(V2OrganizationDataProcessor.java:346)
 REDACTED/
 When debugging, the line is:
 assert _in == _out;
 in the context of:
 int used = getAvailable();
 // if we are about to emit and there is noting in the buffer, 
 reset
 // the buffer to be at the beginning so as to not grow it anymore
 // than needed.
 if (used == 0)
 {
 assert _in == _out;
 assert _free == _buf.length;
 _in = _out = 0;
 }
 In the debugger, in this case _in = 16384 and _out = 0.
 This has only started happening recently.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

RE: I am very new to xmlbean Plz help me

2007-03-29 Thread Jacob Danner

I recommend getting the srcs for the latest release first.
http://xmlbeans.apache.org/sourceAndBinaries/index.html#XMLBeans+Source

Then get familiar with the APIs
http://xmlbeans.apache.org/docs/2.2.0/reference/org/apache/xmlbeans/Sche
maTypeLoader.html
http://xmlbeans.apache.org/docs/2.2.0/reference/org/apache/xmlbeans/Sche
maTypeSystem.html
You'll want to look at the srcs for compilation APIs
Then take a look at the srcs in the tests for some examples on how to
use some of these APIs.
http://svn.apache.org/viewvc/xmlbeans/trunk/test/src/compile/
I just want to mention again, it seems to me like this might be
possible, but I have never done, nor had the requirement to, compile
only certain types of an XSD.

Best of luck,
-Jacobd



-Original Message-
From: raov [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, March 28, 2007 11:34 PM
To: dev@xmlbeans.apache.org
Subject: Re: I am very new to xmlbean Plz help me


hi Jacob,

Thanks for u'r reply. I am using schema compiler scomp this is
compiling
entire xsd file but my requirement is compiling only part of xsd file
means
generate specified beans ( according to some complex types). if u don't
mind
can u send some useful links to me.

thanks
raov


Jacob Danner-2 wrote:
 
 I can't state for certain as I've never tried, but you might be able
 to do this using the schemacompiler, schematypesystem, and
 schematypeloader apis. If you grab the srcs from the depot there may
 be some code/tests that provide some insight into how you an
 manipulate these apis.
 I'm curious how your requirement came about. Can you give us somemore
 info about how/why you can only have certain types from the schema
 compiled?
 thanks,
 -Jacob Danner
 
 On 3/28/07, raov [EMAIL PROTECTED] wrote:

 Thank you Poorna,

 i had already done that way. but i need to know is there any other
 possibilities.
 any how thanks for u'r reply


 Poornachandran wrote:
 
  I dont think, there is any way to do this. I think, you can simply
  ignore the other classes generated.
 
  ~Poorna
 
  raov wrote:
  Hi,
 
  I am very new to xml beans. i  have an xsd file
 
  xs:schema targetNamespace=http://openuri.org/easypo;
  xmlns:po=http://openuri.org/easypo;
  xmlns:xs=http://www.w3.org/2001/XMLSchema;
  elementFormDefault=qualified
 
  xs:element name=purchase-order
  xs:complexType
  xs:sequence
  xs:element name=customer type=po:customer/
  xs:element name=line-item type=po:line-item
  minOccurs=0 maxOccurs=unbounded/
  /xs:sequence
  /xs:complexType
  /xs:element
  xs:complexType name=customer
  xs:sequence
  xs:element name=name type=xs:string/
  xs:element name=address type=xs:string/
  /xs:sequence
  /xs:complexType
  xs:complexType name=line-item
  xs:sequence
  xs:element name=description type=xs:string/
  xs:element name=per-unit-ounces type=xs:decimal/
  xs:element name=price type=xs:double/
  xs:element name=quantity type=xs:int/
  /xs:sequence
  /xs:complexType
 
  /xs:schema
 
  when i was compiling  this xsd file i am getting beans
  customer,lineitem,purchaseorderdocument, purchaseorder. but my
  requirement
  is, I want to compile part of xsd file means need to generate only
  customer related beans no need to generate lineItem beans. Is
 there
  any
  way to compile part of xsd file. if it's there or not let me know.
 kindly
  help ASAP.
 
 
 
 
 
 
-
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

 --
 View this message in context:

http://www.nabble.com/I-am-very-new-to-xmlbean-Plz-help-me-tf3478850.htm
l#a9710927
 Sent from the Xml Beans - Dev mailing list archive at Nabble.com.


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


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

-- 
View this message in context:
http://www.nabble.com/I-am-very-new-to-xmlbean-Plz-help-me-tf3478850.htm
l#a9727808
Sent from the Xml Beans - Dev mailing list archive at Nabble.com.


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


Notice:  This email message, together with any attachments, may contain 
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated 
entities,  that may be confidential,  proprietary,  copyrighted  and/or legally 
privileged, and is intended solely for the use of the individual or entity 
named in this message. If you are not the intended recipient, and have received 
this message

[jira] Commented: (XMLBEANS-320) compiled schema Unable to parse xs:date field

2007-03-29 Thread Jacob Danner (JIRA)


[ 
https://issues.apache.org/jira/browse/XMLBEANS-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485230
 ] 

Jacob Danner commented on XMLBEANS-320:
---

Any updates on this?
I don't have a 64-bit machine to repro on.

 compiled schema Unable to parse xs:date field
 -

 Key: XMLBEANS-320
 URL: https://issues.apache.org/jira/browse/XMLBEANS-320
 Project: XMLBeans
  Issue Type: Bug
  Components: XmlObject
Affects Versions: Version 2.2
 Environment: Linux-Debian/Ubuntu 6.10/X86_64
Reporter: Andy Brook
 Attachments: ContentOrder.xml, DateParseTest.java, 
 DateParseTest.java, ManifestFile1.xsd


 I have a provided schema that contains a Duration, comprising of start and 
 end xs:date fields.  The schema compiled perfectly and Im pulling out all 
 data.  The only problem is xs:date fields.  As soon as I access getStart 
 (xs:date) I get the following stack:
 Exception in thread main 
 org.apache.xmlbeans.impl.values.XmlValueOutOfRangeException: Invalid date 
 value: wrong type: 2007-04-01
   at 
 org.apache.xmlbeans.impl.values.XmlObjectBase$ValueOutOfRangeValidationContext.invalid(XmlObjectBase.java:285)
   at 
 org.apache.xmlbeans.impl.values.JavaGDateHolderEx.lex(JavaGDateHolderEx.java:81)
   at 
 org.apache.xmlbeans.impl.values.JavaGDateHolderEx.set_text(JavaGDateHolderEx.java:56)
   at 
 org.apache.xmlbeans.impl.values.XmlObjectBase.update_from_wscanon_text(XmlObjectBase.java:1135)
   at 
 org.apache.xmlbeans.impl.values.XmlObjectBase.check_dated(XmlObjectBase.java:1274)
   at 
 org.apache.xmlbeans.impl.values.JavaGDateHolderEx.calendarValue(JavaGDateHolderEx.java:192)
   at 
 org.apache.xmlbeans.impl.values.XmlObjectBase.getCalendarValue(XmlObjectBase.java:1516)
   at 
 com.bvi.schemas.itds.interfaces.manifestFile.impl.DurationImpl.getStart(DurationImpl.java:42)
 Given the only code I've actually written is the test code, and that I cannot 
 change the schema.  The xml document is valid according to the schema, and 
 the actual date node text appears to be ISO8601 (-MM-DD).  Is this a bug 
 or am I missing something?
 A workaround is to access the node directly, and get the child node values 
 out.  Schema, example XML and test code to be attached.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Commented: (XMLBEANS-320) compiled schema Unable to parse xs:date field

2007-03-27 Thread Jacob Danner (JIRA)


[ 
https://issues.apache.org/jira/browse/XMLBEANS-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484495
 ] 

Jacob Danner commented on XMLBEANS-320:
---

I am not able to repro this on my linux machine running Ubuntu 6.1 using the 
JRockit JVM.
Also, when I use the ManifestFile rather than the ManifestFileDocument, the 
repro passes for me as well. I'll attache my srcs, can you give it a try?

ManifestFile mf = 
ManifestFileDocument.Factory.parse(f).getManifestFile();

NODE Values (works) start=2007-04-01, end=2007-04-08
Duration start=2007-04-01, end=2007-04-01
NODE Values (works) start=2007-04-01, end=2007-04-08
Duration start=2007-04-01, end=2007-04-01


 compiled schema Unable to parse xs:date field
 -

 Key: XMLBEANS-320
 URL: https://issues.apache.org/jira/browse/XMLBEANS-320
 Project: XMLBeans
  Issue Type: Bug
  Components: XmlObject
Affects Versions: Version 2.2
 Environment: Linux-Debian/Ubuntu 6.10/X86_64
Reporter: Andy Brook
 Attachments: ContentOrder.xml, DateParseTest.java, 
 DateParseTest.java, ManifestFile1.xsd


 I have a provided schema that contains a Duration, comprising of start and 
 end xs:date fields.  The schema compiled perfectly and Im pulling out all 
 data.  The only problem is xs:date fields.  As soon as I access getStart 
 (xs:date) I get the following stack:
 Exception in thread main 
 org.apache.xmlbeans.impl.values.XmlValueOutOfRangeException: Invalid date 
 value: wrong type: 2007-04-01
   at 
 org.apache.xmlbeans.impl.values.XmlObjectBase$ValueOutOfRangeValidationContext.invalid(XmlObjectBase.java:285)
   at 
 org.apache.xmlbeans.impl.values.JavaGDateHolderEx.lex(JavaGDateHolderEx.java:81)
   at 
 org.apache.xmlbeans.impl.values.JavaGDateHolderEx.set_text(JavaGDateHolderEx.java:56)
   at 
 org.apache.xmlbeans.impl.values.XmlObjectBase.update_from_wscanon_text(XmlObjectBase.java:1135)
   at 
 org.apache.xmlbeans.impl.values.XmlObjectBase.check_dated(XmlObjectBase.java:1274)
   at 
 org.apache.xmlbeans.impl.values.JavaGDateHolderEx.calendarValue(JavaGDateHolderEx.java:192)
   at 
 org.apache.xmlbeans.impl.values.XmlObjectBase.getCalendarValue(XmlObjectBase.java:1516)
   at 
 com.bvi.schemas.itds.interfaces.manifestFile.impl.DurationImpl.getStart(DurationImpl.java:42)
 Given the only code I've actually written is the test code, and that I cannot 
 change the schema.  The xml document is valid according to the schema, and 
 the actual date node text appears to be ISO8601 (-MM-DD).  Is this a bug 
 or am I missing something?
 A workaround is to access the node directly, and get the child node values 
 out.  Schema, example XML and test code to be attached.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Re: org.apache.xmlbeans.XmlException: Element is not valid

2007-03-14 Thread Jacob Danner


Thanks Wing,
Ramesh, you may want to start with:
http://xmlbeans.apache.org/documentation/tutorial_getstarted.html
to get familiar. XMLBeans really is a great tool once you see how
everything fits together.
Best of luck,
-Jacobd

On 3/14/07, Ramesh Ranganathan [EMAIL PROTECTED] wrote:

Wing,

Thanks a lot for the information. I understood the problem.

I will use the mail id for future queries.

Regards,
Ramesh Kumar.R



On 3/14/07, Wing Yew Poon [EMAIL PROTECTED] wrote:


 Ramesh,
 assuming that Template.xsd is the xsd file for your schema, you are
parsing the Template schema (thus a schema instance) rather than a Template
instance, as Jacob suspected. What you want to do is to parse an xml
instance of your schema, not the schema.
 For future reference, you should post user questions to the user list (
user@xmlbeans.apache.org) rather than this list, which is for
development-related matters.
 - Wing Yew

 
 From: Ramesh Ranganathan [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, March 14, 2007 12:41 PM
 To: dev@xmlbeans.apache.org
 Subject: Re: org.apache.xmlbeans.XmlException: Element is
not valid




 Hi Jacob,

 Thanks for the reply. I am new to xmlbeans. Please find the xsd I used.


 ?xml version=1.0 encoding=UTF-8?
 schema xmlns=http://www.w3.org/2001/XMLSchema 
xmlns:templ=Template targetNamespace=Template
elementFormDefault=unqualified
attributeFormDefault=unqualified
  element name=Template type=templ:TemplateType
   annotation
documentationComment describing your root element/documentation
   /annotation
  /element
  complexType name=TemplateType
   sequence
element name=Block type=templ:BlockType minOccurs=0
maxOccurs=unbounded/
   /sequence
   attribute name=Name type=string use=optional/
   attribute name=Update type=string use=optional/
   attribute name=MinPaperSize type=string use=optional/
  /complexType
  complexType name=BlockType
   sequence
element name=LineItem type=templ:LineItemType minOccurs=0
maxOccurs=unbounded/
   /sequence
   attribute name=Name type=string use=optional/
   attribute name=Type type=string use=optional/
   attribute name=Update type=string use=optional/
   attribute name=MinPaperSize type=string use=optional/
  /complexType
  complexType name=LineItemType
   simpleContent
extension base=string
 attribute name=Type type=string use=optional/
 attribute name=FontName type=string use=optional/
 attribute name=FontSize type=int use=optional/
 attribute name=Bold type=templ:YesNoType use=optional/
 attribute name=Italic type=templ:YesNoType use=optional/
 attribute name=Alignment type=templ:AlignmentType
use=optional/
 attribute name=Underline type=templ:YesNoType/
/extension
   /simpleContent
  /complexType
  simpleType name=YesNoType
   restriction base=string
maxLength value=1/
pattern value=[Y|N]/
   /restriction
  /simpleType
  simpleType name=AlignmentType
   restriction base=string
maxLength value=1/
pattern value=[L|C|R]/
   /restriction
  /simpleType
 /schema

 I generated the jar using scomp.

 The code is  like this

 TemplateDocument poDoc = null;
 File xsdFile = new File(Template.xsd);
 try
 {
 // Bind the incoming XML to an XMLBeans type.
 poDoc = TemplateDocument.Factory.parse (xsdFile);
 } catch (XmlException e)
 {
 e.printStackTrace();
 } catch (IOException e)
 {
 e.printStackTrace();
 }


 Regards,
 Ramesh Kumar.R


 On 3/14/07, Jacob Danner [EMAIL PROTECTED]  wrote:
  Hi Ramesh,
  This looks like it might be an expected error.
 
  My guess is that when you call:
 
  TemplateDocument.Factory.parse()
 
  you are passing content that starts with
  xsd:schema ... /
  rather than
  Template ... /
 
  Can you confirm this is the case?
 
  -Jacobd
  On 3/14/07, Ramesh Ranganathan  [EMAIL PROTECTED] wrote:
   Hi,
  
   I am getting the following exception when I try to run my program.
  
   C:\Projects\SRS\Programs\xmlbeans\EasyPOjava
Template
   org.apache.xmlbeans.XmlException: Element
   schema@ http://www.w3.org/2001/XMLSchema is not a
valid
   [EMAIL PROTECTED] document or a valid substitution.
   at
  
org.apache.xmlbeans.impl.store.Locale.autoTypeDocument(Locale.java:322)
   at
  
org.apache.xmlbeans.impl.store.Locale.parseToXmlObject
   (Locale.java:1273)
   at
  
org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1257)
   at
  
org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse
(SchemaTypeLoaderBase.java:345)
   at
  
org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:252)
   at
template.TemplateDocument$Factory.parse(Unknown
   Source)
   at Template.main(Template.java :15)
   Exception in thread main java.lang.NullPointerException
   at Template.main(Template.java:23)
  
   Please help me on this.
  
   Regards

[jira] Updated: (XMLBEANS-307) XMLBeans scomp throws error code too large

2007-03-09 Thread Jacob Danner (JIRA)


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacob Danner updated XMLBEANS-307:
--

Attachment: xmlbeans_307_patch.diff

I think I've got a workaround for this issue in the attached patch. 
I've attached a unit test also and have verified compilation of both sets of 
schemas mentions in this issue (niem  jxdm).


 XMLBeans scomp throws error code too large
 

 Key: XMLBEANS-307
 URL: https://issues.apache.org/jira/browse/XMLBEANS-307
 Project: XMLBeans
  Issue Type: Bug
  Components: Compiler
Affects Versions: Version 1.0.4
 Environment: Window XP Service pack 2
Reporter: Harish K Swamy
Priority: Minor
 Fix For: Version 2.2

 Attachments: xmlbeans_307_patch.diff


 I am trying to run scomp on my schema which import many other schema's. Out 
 of many schema's one of them is having a size of 1.6 MB.
 Below is the error I get when i run scomp. It would be very much helpful if 
 somebody gives me resolution for this problem.
 Thanks in advance
 Harish
 C:\xmlbeans-2.2.0\binscomp -out 
 C:\WantedMissingInquiry\WantedMissingInquiryResponseIEPD\XMLSchemas\test.jar 
 C:\WantedMissingInqui
 ry\WantedMissingInquiryResponseIEPD\XMLSchemas\NYSMessage.xsd
 Time to build schema type system: 2.875 seconds
 Time to generate code: 8.015 seconds
 C:\DOCUME~1\hswamy\LOCALS~1\Temp\xbean8664.d\src\gov\niem\niem\ncic2000\x10\VMACodeSimpleType.java:15268:
  code too large
 public static final org.apache.xmlbeans.StringEnumAbstractBase.Table 
 table =
  ^
 1 error
 BUILD FAILED

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Resolved: (XMLBEANS-307) XMLBeans scomp throws error code too large

2007-03-09 Thread Jacob Danner (JIRA)


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacob Danner resolved XMLBEANS-307.
---

Resolution: Fixed
  Assignee: Radu Preotiuc-Pietro

Please check out my patch, I think it works around the issue.
The error occurs whenever the enum value is  3668.

 XMLBeans scomp throws error code too large
 

 Key: XMLBEANS-307
 URL: https://issues.apache.org/jira/browse/XMLBEANS-307
 Project: XMLBeans
  Issue Type: Bug
  Components: Compiler
Affects Versions: Version 1.0.4
 Environment: Window XP Service pack 2
Reporter: Harish K Swamy
 Assigned To: Radu Preotiuc-Pietro
Priority: Minor
 Fix For: Version 2.2

 Attachments: xmlbeans_307_patch.diff


 I am trying to run scomp on my schema which import many other schema's. Out 
 of many schema's one of them is having a size of 1.6 MB.
 Below is the error I get when i run scomp. It would be very much helpful if 
 somebody gives me resolution for this problem.
 Thanks in advance
 Harish
 C:\xmlbeans-2.2.0\binscomp -out 
 C:\WantedMissingInquiry\WantedMissingInquiryResponseIEPD\XMLSchemas\test.jar 
 C:\WantedMissingInqui
 ry\WantedMissingInquiryResponseIEPD\XMLSchemas\NYSMessage.xsd
 Time to build schema type system: 2.875 seconds
 Time to generate code: 8.015 seconds
 C:\DOCUME~1\hswamy\LOCALS~1\Temp\xbean8664.d\src\gov\niem\niem\ncic2000\x10\VMACodeSimpleType.java:15268:
  code too large
 public static final org.apache.xmlbeans.StringEnumAbstractBase.Table 
 table =
  ^
 1 error
 BUILD FAILED

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[XmlBeans-279] Add convenience XmlOptions setter methods with boolean arguments

2007-03-09 Thread Jacob Danner


http://issues.apache.org/jira/browse/XMLBEANS-279

Hey guys,
I've got a patch ready for the jira issue above, I think its a
improvement, but had some design questions I wanted to chat about.

In my patch I've added a method like
setSavePrettyPrint(boolean flag){
if(flag)
  return set( KEY );
else
  return checkAndRemove( KEY );
}

My questions are:
should methods like above be named:
savePrettyPrint(boolean flag)

Also, does/will it make sense to have similar convenience method for
methods that take parameters? For example,
setSavePrettyPrintIndent(boolean flag, int indent)
it doesn't really make sense to me, but I wanted to confirm.

Thanks,
-jacobd

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

Out of Office AutoReply: [jira] Resolved: (XMLBEANS-315) javac not found properly, couldn't find internet help

2007-03-07 Thread Jacob Danner

Hi,

I am at EclipseCon right now and will be returning the 9th. I'll be online and 
checking email intermittently.  If you need to reach me faster than that, Alex 
Ramirez and Julie Zhuo have my cell phone #.

Thanks,
-jacobd
___
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.

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

[jira] Resolved: (XMLBEANS-312) Scomp - genearting classes for multiple schema into one jar file

2007-03-07 Thread Jacob Danner (JIRA)


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacob Danner resolved XMLBEANS-312.
---

Resolution: Cannot Reproduce
  Assignee: Jacob Danner

Harish, 
have you tried:
 scomp -out jarname.jar *.xsd

Is this what you are requesting?
Thanks,
-Jacobd

 Scomp - genearting classes for multiple schema into one jar file
 

 Key: XMLBEANS-312
 URL: https://issues.apache.org/jira/browse/XMLBEANS-312
 Project: XMLBeans
  Issue Type: Wish
  Components: XmlObject
Affects Versions: Version 1.0.4
 Environment: Window XP SP2
Reporter: Harish K Swamy
 Assigned To: Jacob Danner
Priority: Trivial

 Hi,
 I got multiple schemas with similar header but different payloads, I want to 
 do the following
 1. Generate XMLBeans for these schemas into one jar file
 2. Each schema needs to be prefixed, so that the classes are identical to 
 perticular schema.
 Is this possible?, If so please can any one give me the command to execute 
 the above?
 The way i am doing it for individual schema is as follows,
 C:\xmlbeans-2.2.0\binscomp -out schema1.jar Message.xsd myprefix.xsd
 Thanks in advance
 Harish

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Commented: (XMLBEANS-307) XMLBeans scomp throws error code too large

2007-03-07 Thread Jacob Danner (JIRA)


[ 
https://issues.apache.org/jira/browse/XMLBEANS-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479190
 ] 

Jacob Danner commented on XMLBEANS-307:
---

I've added an FAQ section on the wiki for this issue.
http://wiki.apache.org/xmlbeans/XmlBeansFaq

 XMLBeans scomp throws error code too large
 

 Key: XMLBEANS-307
 URL: https://issues.apache.org/jira/browse/XMLBEANS-307
 Project: XMLBeans
  Issue Type: Bug
  Components: Compiler
Affects Versions: Version 1.0.4
 Environment: Window XP Service pack 2
Reporter: Harish K Swamy
Priority: Minor
 Fix For: Version 2.2


 I am trying to run scomp on my schema which import many other schema's. Out 
 of many schema's one of them is having a size of 1.6 MB.
 Below is the error I get when i run scomp. It would be very much helpful if 
 somebody gives me resolution for this problem.
 Thanks in advance
 Harish
 C:\xmlbeans-2.2.0\binscomp -out 
 C:\WantedMissingInquiry\WantedMissingInquiryResponseIEPD\XMLSchemas\test.jar 
 C:\WantedMissingInqui
 ry\WantedMissingInquiryResponseIEPD\XMLSchemas\NYSMessage.xsd
 Time to build schema type system: 2.875 seconds
 Time to generate code: 8.015 seconds
 C:\DOCUME~1\hswamy\LOCALS~1\Temp\xbean8664.d\src\gov\niem\niem\ncic2000\x10\VMACodeSimpleType.java:15268:
  code too large
 public static final org.apache.xmlbeans.StringEnumAbstractBase.Table 
 table =
  ^
 1 error
 BUILD FAILED

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Out of Office AutoReply: [jira] Resolved: (XMLBEANS-290) QNameSet generated by QNameSet.forArray(QName[]) can't be unioned with other QNameSets

2007-01-05 Thread Jacob Danner

Hi,

I will be on vacation until Monday, Jan 15th.  I'll be online and checking 
email intermittently. If you need to reach me faster than than, Alex Ramirez 
has my cell phone #.

Thanks,
-jacobd
___
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.

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

[jira] Commented: (XMLBEANS-307) XMLBeans scomp throws error code too large


[ 
http://issues.apache.org/jira/browse/XMLBEANS-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461795
 ] 

Jacob Danner commented on XMLBEANS-307:
---

What are the memory settings for your version of java?
I've had success compiling with large schemas, but every now and then I need to 
add a memory flag (-DXmx=...)

From the error message you posted, it looks like the error you hit is actualy 
after the xmlbeans code has been generated. At this point, Xmlbeans basically 
just calls javac over the code and that looks like where your problem is 
occuring. 
Can you try increasing mem settings and letting us know the outcome?
Thanks,
-Jacobd

 XMLBeans scomp throws error code too large
 

 Key: XMLBEANS-307
 URL: http://issues.apache.org/jira/browse/XMLBEANS-307
 Project: XMLBeans
  Issue Type: Wish
Affects Versions: Version 1.0.4
 Environment: Window XP Service pack 2
Reporter: Harish K Swamy
 Fix For: Version 2.2


 I am trying to run scomp on my schema which import many other schema's. Out 
 of many schema's one of them is having a size of 1.6 MB.
 Below is the error I get when i run scomp. It would be very much helpful if 
 somebody gives me resolution for this problem.
 Thanks in advance
 Harish
 C:\xmlbeans-2.2.0\binscomp -out 
 C:\WantedMissingInquiry\WantedMissingInquiryResponseIEPD\XMLSchemas\test.jar 
 C:\WantedMissingInqui
 ry\WantedMissingInquiryResponseIEPD\XMLSchemas\NYSMessage.xsd
 Time to build schema type system: 2.875 seconds
 Time to generate code: 8.015 seconds
 C:\DOCUME~1\hswamy\LOCALS~1\Temp\xbean8664.d\src\gov\niem\niem\ncic2000\x10\VMACodeSimpleType.java:15268:
  code too large
 public static final org.apache.xmlbeans.StringEnumAbstractBase.Table 
 table =
  ^
 1 error
 BUILD FAILED

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Commented: (XMLBEANS-307) XMLBeans scomp throws error code too large


[ 
http://issues.apache.org/jira/browse/XMLBEANS-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461815
 ] 

Jacob Danner commented on XMLBEANS-307:
---

I think the syntax of your parameters is incorrect, try the following:
scomp -Xmx512m

from java -X
 -Xmssizeset initial Java heap size
 -Xmxsizeset maximum Java heap size


 XMLBeans scomp throws error code too large
 

 Key: XMLBEANS-307
 URL: http://issues.apache.org/jira/browse/XMLBEANS-307
 Project: XMLBeans
  Issue Type: Wish
Affects Versions: Version 1.0.4
 Environment: Window XP Service pack 2
Reporter: Harish K Swamy
 Fix For: Version 2.2


 I am trying to run scomp on my schema which import many other schema's. Out 
 of many schema's one of them is having a size of 1.6 MB.
 Below is the error I get when i run scomp. It would be very much helpful if 
 somebody gives me resolution for this problem.
 Thanks in advance
 Harish
 C:\xmlbeans-2.2.0\binscomp -out 
 C:\WantedMissingInquiry\WantedMissingInquiryResponseIEPD\XMLSchemas\test.jar 
 C:\WantedMissingInqui
 ry\WantedMissingInquiryResponseIEPD\XMLSchemas\NYSMessage.xsd
 Time to build schema type system: 2.875 seconds
 Time to generate code: 8.015 seconds
 C:\DOCUME~1\hswamy\LOCALS~1\Temp\xbean8664.d\src\gov\niem\niem\ncic2000\x10\VMACodeSimpleType.java:15268:
  code too large
 public static final org.apache.xmlbeans.StringEnumAbstractBase.Table 
 table =
  ^
 1 error
 BUILD FAILED

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Updated: (XMLBEANS-307) XMLBeans scomp throws error code too large


 [ 
http://issues.apache.org/jira/browse/XMLBEANS-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacob Danner updated XMLBEANS-307:
--

Component/s: Compiler
   Priority: Minor  (was: Major)
 Issue Type: Bug  (was: Wish)

correcting bug stats

 XMLBeans scomp throws error code too large
 

 Key: XMLBEANS-307
 URL: http://issues.apache.org/jira/browse/XMLBEANS-307
 Project: XMLBeans
  Issue Type: Bug
  Components: Compiler
Affects Versions: Version 1.0.4
 Environment: Window XP Service pack 2
Reporter: Harish K Swamy
Priority: Minor
 Fix For: Version 2.2


 I am trying to run scomp on my schema which import many other schema's. Out 
 of many schema's one of them is having a size of 1.6 MB.
 Below is the error I get when i run scomp. It would be very much helpful if 
 somebody gives me resolution for this problem.
 Thanks in advance
 Harish
 C:\xmlbeans-2.2.0\binscomp -out 
 C:\WantedMissingInquiry\WantedMissingInquiryResponseIEPD\XMLSchemas\test.jar 
 C:\WantedMissingInqui
 ry\WantedMissingInquiryResponseIEPD\XMLSchemas\NYSMessage.xsd
 Time to build schema type system: 2.875 seconds
 Time to generate code: 8.015 seconds
 C:\DOCUME~1\hswamy\LOCALS~1\Temp\xbean8664.d\src\gov\niem\niem\ncic2000\x10\VMACodeSimpleType.java:15268:
  code too large
 public static final org.apache.xmlbeans.StringEnumAbstractBase.Table 
 table =
  ^
 1 error
 BUILD FAILED

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Commented: (XMLBEANS-307) XMLBeans scomp throws error code too large


[ 
http://issues.apache.org/jira/browse/XMLBEANS-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461828
 ] 

Jacob Danner commented on XMLBEANS-307:
---

Have you tried placing the src files in a dir and javac'ing them?
I'm curious if you can reproduce this problem outside of scomp.

Can you attach the schema so I can try?

 XMLBeans scomp throws error code too large
 

 Key: XMLBEANS-307
 URL: http://issues.apache.org/jira/browse/XMLBEANS-307
 Project: XMLBeans
  Issue Type: Bug
  Components: Compiler
Affects Versions: Version 1.0.4
 Environment: Window XP Service pack 2
Reporter: Harish K Swamy
Priority: Minor
 Fix For: Version 2.2


 I am trying to run scomp on my schema which import many other schema's. Out 
 of many schema's one of them is having a size of 1.6 MB.
 Below is the error I get when i run scomp. It would be very much helpful if 
 somebody gives me resolution for this problem.
 Thanks in advance
 Harish
 C:\xmlbeans-2.2.0\binscomp -out 
 C:\WantedMissingInquiry\WantedMissingInquiryResponseIEPD\XMLSchemas\test.jar 
 C:\WantedMissingInqui
 ry\WantedMissingInquiryResponseIEPD\XMLSchemas\NYSMessage.xsd
 Time to build schema type system: 2.875 seconds
 Time to generate code: 8.015 seconds
 C:\DOCUME~1\hswamy\LOCALS~1\Temp\xbean8664.d\src\gov\niem\niem\ncic2000\x10\VMACodeSimpleType.java:15268:
  code too large
 public static final org.apache.xmlbeans.StringEnumAbstractBase.Table 
 table =
  ^
 1 error
 BUILD FAILED

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Commented: (XMLBEANS-307) XMLBeans scomp throws error code too large