[
https://issues.apache.org/jira/browse/XMLBEANS-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263706#comment-13263706
]
Chris White edited comment on XMLBEANS-479 at 4/27/12 2:4
[
https://issues.apache.org/jira/browse/XMLBEANS-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263706#comment-13263706
]
Chris White commented on XMLBEANS-479:
--
I have a similar problem. It looks
Issue Type: Bug
Components: Compiler
Affects Versions: Version 2.4
Environment: JDK 1.5.0
Reporter: Chris Rose
Priority: Critical
When generating java code from an XSD, one of the generated classes ends up
with this bit of magic in it
Reporter: Chris Clark
After generating code for GML 3.1.1, the code fails to compile. The following
compilation error is given:
generatedSetterHelperImpl(org.apache.xmlbeans.XmlObject,javax.xml.namespace.QName,int,short)
in org.apache.xmlbeans.impl.values.XmlObjectBase cannot be applied to
Chris wrote:
BTW: I assume 2.4.0 will work with Saxon 9.0.x not just 9.0.0.4
(9.0.0.5 and 9.0.0.6 have been released).
I'll see if it works with 9.1.0.1 too.
It does! According to the Saxon website they only added stuff to the API
in 9.1 and it passes all my unit tests with 2.4.0.
The
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
this
by email and then delete it.
--
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 unautho
MessageLabs. (CCTM Certificate Number 2007/11/0032.) 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
Yes, just added some XPath 2 queries to our application and it works
with the new jar.
Well done - that is really useful to me.
Note: with both the old and new jars I don't actually seem to need the
saxonx-dom.jar. What causes this jar to be loaded?
Thanks again
Chris
Chris wrote:
T
ase.
Can anyone suggest if and when these changes could be put into an
official xml beans release?
Many Thanks
Chris
Wing Yew Poon 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/XM
Does XML Beans support any of the XML Catalog standards such as OASIS or
XCatalog?
This functionality is provided by the Apache XML Commons library.
Thanks for your help
--
Chris
HMGCC
The information contained in this message (and any attachments) may
be confidential and is intended for the
[
https://issues.apache.org/jira/browse/XMLBEANS-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Schmidt updated XMLBEANS-362:
---
Attachment: XsdTest.java
Simple test that exhibits the problem. Note that it expects the
[
https://issues.apache.org/jira/browse/XMLBEANS-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Schmidt updated XMLBEANS-362:
---
Attachment: xsdBase.xsd
Base xsd that the other imports
> XmlObject.changeType does
[
https://issues.apache.org/jira/browse/XMLBEANS-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Schmidt updated XMLBEANS-362:
---
Attachment: inheritType.xsd
xsd that inherits from a type in the base
Issue Type: Bug
Components: XmlObject
Affects Versions: Version 2.3
Reporter: Chris Schmidt
I have two xsds. One imports the other one and contains a type that inherits
from a type within the imported file. XmlBeans properly generates a class that
extends the base
Wing Yew Poon wrote:
Chris,
I believe that that is accurate - to use XMLBeans 2.3.0 with Saxon 8.8,
you need saxon8.jar and saxon8-dom.jar, along with the other jars
provided in the XMLBeans distribution. Have you found otherwise?
As for Saxon 9, that will require investigation. Are you willing
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
Cezar Andrei wrote:
Other requests on the user list were:
- upgrade support for latest stable version of Saxon.
I'd vote for this one - this would provide support for the final versions of
XPath 2.0 and XQuery 1.0.
--
Chris
HMGCC
The information contained in this message (an
couldn't see it.
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 unauthorise
I can, although I'm now pretty convinced it's not an XML Beans issue.
The fact is the default stack size must be smaller for 32bit jse6, and
long, complex patterns require a lot of stack.
Jacob Danner wrote:
Hi Chris,
Thanks for finding an investigating an issue like this.
Can I
." -
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 mor
tring(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)
...
--
Chris
HMGCC
The information contained in this message (and any attachments) may
be conf
Although in that link they do explicitly add a comment about the
intentional side-effect. If it had been commented in the first place,
you wouldn't have everyone looking at it now :)
Regards
Chris
Jacob Danner (JIRA) wrote:
[ https://issues.apache.org/jira/browse/XMLBEANS-348
+0
Chris
Radu Preotiuc-Pietro wrote:
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
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
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
--
Chris
HMGCC
The information contain
rrors:
at the top, 23th should be 23rd
Current release: 2.2.0 released on June 23*th*, 2006.
at the bottom under "Building XMLBeans"
"cd xml-xmlbeans\v1"
should that be v2 now?
Regards
Chris
Radu Preotiuc-Pietro wrote:
Chris,
Have you tried this Saxon 8.9 with the cur
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 faili
Any progress on this?
Do we have an ETA for 2.3.0?
Regards
Chris
Chris wrote:
Looking at the release notes for saxon 8.9 it does mention some XPath
API changes.
http://www.saxonica.com/documentation/changes/intro/jaxp89.html
Does XML Beans use net.sf.saxon.xpath (JAXP) or net.sf.saxon.sxpath
effort involved is too great.
-- --
Ken Kress
Information Technology
Lockwood®
10 Valley Stream Parkway
Malvern, PA 19355
Phone: (484) 605-4834
Fax: (484) 605-4903
Email: [EMAIL PROTECTED]
Chris <[EMAIL PROTECTED]>
03/08/2007 08
Saxon 8.9 is out and fully supports the final version of XSLT2.
I don't believe there are any API changes.
Perhaps this could be tested and then the new xml beans release could
recommend Saxon 8.9 (instead of 8.8).
Regards
Chris
Radu Preotiuc-Pietro wrote:
Hi all,
It's been some
You're using the Table class to parse a table (which admittedly sounds
reasonable :). It's complaining that it expects column or constraint,
NOT table.
I.e. you need to parse from a level up - try using
Application.Factory.parse() instead of Table.Factory.parse()
HTH
Chris
Kurt
n-B?
When can we expect an XML Beans *release* with Saxon 8.8 (SA and or B)
support? How stable are the current SVN versions (rev 500554?)?
Thanks
Chris
HMGCC
Cezar Andrei wrote:
I just checked in (rev 500554) which will automatically download
saxonb8-8j.zip. Build and checkin tests seem to be wo
no longer remember how the security managers exactly work, but
XMLBeans will need to be able to load the .xsb files from the classpath,
in addition to your .xml files.
What is the exception?
Radu
On Wed, 2006-10-18 at 13:09 +0100, Chris wrote:
Has anyone looked into the use of xml beans with a securi
reflection but if I give it permission to
read <> (not just the xml files I want it to read), it works...
Any ideas?
--
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, alte
I take it back, using scomp via Runtime.exec() does behave correctly
although certain files cause scompProcess.waitFor() to wait forever.
SchemaCompiler.main() still always successfully compiles schemas though.
Any help or light anyone can throw on this issue would be appreciated.
Chris
jar!
So, I tried running scomp directly using Runtime.exec(). This still
does not notice the error!
Running windows 2000 sp4, java 1.5.0_08, xml beans 2.2.0.
--
Chris
HMGCC
The information contained in this message (and any attachments) may
be confidential and is intended for the sole use of
[
http://issues.apache.org/jira/browse/XMLBEANS-226?page=comments#action_12363289
]
Chris Hagmann commented on XMLBEANS-226:
Exactly the same issue here with JAXP 1.3, Tomcat 5.5.12.
I'm not sure about the work around. It sounds to me as if
s 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 t
i386 GNU/Linux
Reporter: Chris Lamey
Priority: Minor
The following elements in our xml cause a
java.lang.ArrayIndexOutOfBoundsException in Document.save(StringWriter,
XmlOptions) in xmlbeans when we first call setSavePrettyPrint() on the
XmlOptions object we pass into the Document.s
40 matches
Mail list logo