I’m using XMLBeans in a project running on:
[x] jdk 1.5
My project will update to jdk 1.6 or newer in:
[x] less than 1 year
Kai Ludwig
-
To unsubscribe, e-mail: user-unsubscr...@xmlbeans.apache.org
For additional commands,
Hi Jacob and thanks for the reply,
Let's start from scratch. I have WSDL files with WSDL imports. I use
WSDL4j to parse the wsdl files...so, when i get the types section of
the WSDL document i hold on a Xmlobject array all the XSDs from the
types element. After doing this procedure to store
I’m using XMLBeans in several projects running on:
[X] jdk 1.6
Maarten
Hi everyone!
I'm using XMLBeans in a project running on:
[X] jdk 1.5
We have no firm plans for an upgrade to 1.6, but I suspect within
the next year.
Jeff
--
Jeff Lusted tel: +44 (0)116 252 3581
Astrogrid Project mob: +44 (0)7941 599062
Dept Physics Astronomy email:
I’m using XMLBeans in a project running on:
[x] jdk 1.5
[ ] jdk 1.6
We're on WebSphere 6.1 -- no plans to migrate yet.
Thanks,
Hes.
I'm using XMLBeans in a project running on:
[X] jdk 1.5
No current firm plans to upgrade the jdk.
--
Dennis R. Sherman
Development Team Leader
Ex Libris Group
847-227-2976
dennis.sher...@exlibrisgroup.com
http://www.exlibrisgroup.com http://www.exlibrisgroup.com/
We're using XMLBeans in a project running on:
[ ] jdk 1.3
[ ] jdk 1.4
[ ] jdk 1.5
[X] jdk 1.6
1.4 support is not required for us.
From: Cezar Andrei [mailto:cezar.and...@oracle.com]
Sent: Monday, May 11,
Hmm, I think you are making it too hard on yourself with all of the
WSDL4J to pull out the types element. XMLBeans' scomp tool can be run
on wsdls. Have/can you give this a try?
I ran the following from the command line without much of a problem.
# scomp
Hi Jacob and thank you for your answer,
The think is that i can't pull out the WSDL4j from my code because my
work is a part of a bigger project that uses WSDL4j.
Could you tell me please the way to convert the relative URLs on the
imports to absolute URLs?I hope u did that by xmloptions or
Hi,
I’m using XMLBeans in a project running on:
[x ] jdk 1.4
My project will update to jdk 1.5 or newer in:
[x ] less than 1 year
Thanks!
Giuseppe Battista
Software Developer
Hi Michael,
I did just convert the wsdl imports by hand because it was the
quickest and easiest way for me to.
There shouldn't be a problem using the relative URLs so long as the
schemaLocation values are all correct (point to proper files) once the
scomp is run.
Are you doing your compilation
Hey Jacob,
Yes, i'm doing the compilation programmatically with compileXSD
method...and that was a compileXSD error apparently.
I've checked the xmloptions to find a way to skip this error but nothing.
Jacob Danner wrote:
Hi Michael,
I did just convert the wsdl imports by hand because
I?m using XMLBeans in a project running on:
[ ] jdk 1.3
[ ] jdk 1.4
[ ] jdk 1.5
[X] jdk 1.6
Cezar Andrei cezar.and...@oracle.com
05/11/2009 01:58 PM
Please respond to
user@xmlbeans.apache.org
To
d...@xmlbeans.apache.org, user@xmlbeans.apache.org
cc
Subject
[POOL] jdk 1.4 support
You can't skip an error like this. It's valid. If I'm understanding
your case properly, the error message is telling you the imported
schemas cannot be found.
I would start by looking at how you are creating your XMLObject array.
What is the value of
worked perfect:
System.out.println(XmlBeans.getContextTypeLoader().findElement(
new
QName(http://www.klistret.com/cmdb/element/logical;,
Collection)).isAbstract());
--
View this message in context:
Hi Jacob,
You were right, every single xmlobject (schema) has source name null...
What i should do now?
Jacob Danner wrote:
You can't skip an error like this. It's valid. If I'm understanding
your case properly, the error message is telling you the imported
schemas cannot be found.
I would
If been a while since I've tinkered with these APIs, but I would try setting the
sourceName value to the value of the schemaLocation
ie, setSourceName(../foo.xsd);
Let the list know how this turns out.
-jacobd
On Tue, May 12, 2009 at 10:34 AM, Jacob Danner jacob.dan...@gmail.com wrote:
You
Ok, but the schemaLocations are attributes of the import elements...how
could i manipulate every import and correct it , in order to compile?
Every import could have different namespace and schemaLocation fields
With setSourceName you just set the url of the whole schema...
Could you
Okay, taking your example from above
import namespace=http://blahblahzdoing.com;
SchemaLocation=./../X/Y/Z/SchemaExample.xsd/
You are probably doing something like this to load SchemaExample.xsd
XMLObject xo = XMLObject.Factory.parse(StringOfSchemaExample.xsd);
you might be able to do something
Actually, i am going to tell you exactly what i do...
compilationObject is ArrayListXmlObject and contains all my schemas,
but before adding all the schemas to the ArrayList i take the string
representation of every xmlobject (schema) to change sth on the
namespaces section and again parse
What do you mean by to change sth on the namespaces ?
Okay so a couple of things...
-You are parsing String representations of schemas which is why you
are having trouble resolving references. If you parsed the files, this
probably wouldn't be an issue.
-You are having these troubles because
21 matches
Mail list logo
