could use
kickstarter (or others) to crowd fund this effort. Put a link on jibx
site on top and email the jibx user group. I am confident the
community will support it. I will for sure.
Thanks
Shri
On Thursday, May 1, 2014 3:59 PM, Dennis Sosnoski d...@sosnoski.com
wrote:
For starters, the BCEL
For starters, the BCEL tool used by JiBX is incompatible with Java 8. It
looks like there's been some work to address this, but there's no new
release of BCEL and no indication when there might be.
My preferred approach to solve this would be to replace BCEL with the
more-modern and better
Hi Adhamh,
I am looking into the issues with Java 8, but I'm also swamped with
other things right now. I'll have an answer for how to deal with Java 8
support by the end of the month.
JiBX is not being actively maintained, but I do provide paid support for
clients at a discounted rate. In
Hi Kendall,
You might be able to do this with JiBX/WS, but I haven't tried and
wouldn't guarantee it would work correctly. The most likely problem
would be that you're marshalling the same class as several different
elements. JiBX allows this, but you'd need to have a way of identifying
the
I've now released JiBX 1.2.5. The only real change in this one is full
support for Java 7. With 1.2.5 you can bind class files compiled with
Java 7 and keep full Java 7 compatibility for these class files. Class
files generated by JiBX continue to use an older form, but are loaded
without any
I've got a working build of JiBX with Java 7 support included available
for trial at http://www.jibx.org/jibx_1_2_5_SNAPSHOT.zip I'll do the
formal release early next week, but wanted to give interested parties a
chance to try it out first.
Let me know if you run into problems.
Thanks,
-
Jibx2Wsdl doesn't support default values in the schema. I don't think
any of the web services stacks that work with schemas pay any attention
to default values anyway, so it's never been a feature of interest.
Are you trying to do this just to reduce the size of the XML?
- Dennis
Dennis M.
Hi all,
I've had some people asking me about continued support for JiBX,
including Java 7 support without the workarounds currently required, so
thought I'd let users know the situation and see if anything can be done.
From the beginning, commercial clients have motivated much of the work
Hi Jack,
The problem here is that your schema defines *abstract* types, which
cannot be used directly in XML documents. You need to have concrete
types that extend the abstract types in order to actually use them in
documents. Judging from the binding error you're getting, it looks like
there
Hi Brando,
No, there's no default support for DataHandler. This is something I've
been interested in implementing in the past, since it could allow JiBX
to hook into the MTOM attachment support in Axis2 and CXF.
- Dennis
Dennis M. Sosnoski
Java SOA and Web Services Consulting
It looks like Java 1.7 made non-backward compatible changes to the
bytecode verifier, and now requires some sort of new instruction
structure. I haven't found where this is spelled out in the Java 1.7
documentation, but Snoracle doesn't seem especially forthcoming about
the changes they're
Hi Vikas,
Can you provide some details of how this fails? Off hand, I'd think it
should work as you'd expect.
- Dennis
Dennis M. Sosnoski
Java SOA and Web Services Consulting http://www.sosnoski.com/consult.html
Axis2/CXF/Metro SOA and Web Services Training
Hi Janice,
The JiBX binding compiler embeds information in the mapped classes about
the associated bindings (there may be more than one, if you choose).
This exception means that JiBX looked in the class and found the list of
bindings, but the binding name you specified was not included in
Hi Shri,
There's currently no MTOM support, but there has been some interest from
other users on getting this added. I don't have time to implement this
myself, but If anyone wants to try to make it work we can start a
discussion on the jibx-devs list about how to make it happen.
- Dennis
Hi Klaus,
The only case where a null collection would make sense would be when
there's a wrapper element around the collection, and the presence or
absence of that element is indicated by a non-null/null value of the
collection. But in the case you quote there is no wrapper element, so
the
Hi Archie,
This has always been the behavior for JiBX. I go through some special
handling in the schema data mode code (org.jibx.schema.elements package,
and the SchemaBase class in particular for the actual verification) to
catch unknown attributes, and if you are willing to take the same
Consulting http://www.sosnoski.com/consult.html
Axis2/CXF/Metro SOA and Web Services Training
http://www.sosnoski.com/training.html
Web Services Jump-Start http://www.sosnoski.com/jumpstart.html
On 09/29/2011 11:35 PM, Dennis Sosnoski wrote:
Hi Klaus,
The only case where a null collection would
Hi Vikas,
You can set user information in the UnmarshallingContext, which is then
available in your methods. See the setUserContext()/getUserContext()
methods, which allow you to work with a data object defined by your
application.
There's no way to get the file path directly, since jiBX
If you're generating code from schema there's no way to handle this
automatically, but you could modify the generated binding. You should
have two static conversion methods defined in your generated enumeration
class, convert(String) and fromValue(String). The exception is being
thrown by the
Hi Todd,
The Java class structure really doesn't matter much for this. You want
to use value ... style=text.../ for the content of the totalCost
element, so something along these lines should work with your classes:
structure name=totalCost get-method=getMoney ...
value style=attribute
:
beautiful, so its the enumeration itself generating the exception not
jibx. thats beautiful, i can handle that.
and as a rule i never use code generators. i do everything by hand.
i don't like losing that control
On Thu, Sep 29, 2011 at 5:21 AM, Dennis Sosnoski d...@sosnoski.com
mailto:d
Absolutely. JiBX doesn't require xsds, so you can just use a binding
definition for the XML structure you want to use. For a collection, you
would need to define some sort of wrapper element (since XML only allows
one root element in the document).
- Dennis
Dennis M. Sosnoski
Java SOA and Web
On 03/14/2011 04:24 AM, Archie Cobbs wrote:
On Sat, Mar 12, 2011 at 10:05 PM, Dennis Sosnoski d...@sosnoski.com
mailto:d...@sosnoski.com wrote:
From your response I'm not sure if you're just saying that you
don't like having to use concrete mappings in this case, or if
there's
Hi Richard,
It looks like the exception is occurring during CodeGen's internal
validation of the generated bindings. If you supply the location of the
schema I'll give this a try and see what's going wrong. This would
probably be another good schema to include in the JiBX Schema Library. :-)
-
Hi Dmitri,
The JiBX 1.2.3 release includes a number of bug fixes for code
generation from schema. Can you try this using the 1.2.3 release? If you
still get this problem with 1.2.3, please create a Jira problem report
and attach the set of schemas so I can recreate the problem.
Thanks,
-
Hi Michael,
A similar issue came up recently, with this solution:
http://www.mail-archive.com/jibx-users%40lists.sourceforge.net/msg04568.html
Hopefully you can apply the same approach in your application.
- Dennis
Dennis M. Sosnoski
Java SOA and Web Services Consulting
On 01/19/2011 03:22 AM, Archie Cobbs wrote:
On Mon, Jan 17, 2011 at 3:24 AM, Dennis Sosnoski d...@sosnoski.com
mailto:d...@sosnoski.com wrote:
I'd planned to support annotations for schema constraints at some
point, and it shouldn't be a huge job to add them in. It would
involve
On 01/19/2011 04:10 AM, jcaristi wrote:
Archie Cobbs wrote:
I have a somewhat contrarian view, but IMHO this is a good example of why
XSD documents are basically useless. Invariably XML documents require
programmatic, runtime validation beyond what XSD provides. As I understand
things
Hi Bob,
You can do this in your own code, by getting the IXMLWriter and calling
the writeComment method. You can get the IXMLWriter from the
UnmarshallingContext, which is always the implementation class for the
IUnmarshallingContext, and you can get the IUnmarshallingContext as a
parameter to
Hi Sowali,
I tested to make sure style='cdata' is working correctly with the
current code, even using separate input and output bindings as in
Ellecer's output binding example. I can't see any problems.
In a quick look at the Spring JibxMarshaller I did see that depending on
the form of output
On 11/20/2010 04:15 AM, Archie Cobbs wrote:
On Thu, Nov 18, 2010 at 8:37 PM, Dennis Sosnoski d...@sosnoski.com
mailto:d...@sosnoski.com wrote:
The issue with flexible unmarshalling is that JiBX normally
generates code based on the expected order of elements in order to
get
Hi Erik,
The problem with the schema is that no type information is supplied for
the elements, meaning any content may be present in the actual
documents. This isn't an error, but it does mean the only way to handle
these elements is by using a DOM representation for the content. I think
that's
Hi Michael,
Unfortunately JAX-WS was not designed to support data bindings other
than JAXB (this was one of the issues discussed by the expert group, and
I and a few others who really wanted to support alternative techniques
lost out). However, individual implementations of JAX-WS *can* support
The issue with flexible unmarshalling is that JiBX normally generates
code based on the expected order of elements in order to get the most
efficient processing - at any point in the unmarshalling it can just
check for the next expected element, and if it's not found skip to the
following one, an
My own preferred approach for doing this is to start with BindGen
(http://jibx.sourceforge.net/fromcode/bindgen.html) and compare the
generated schema to what I want, then use BindGen customizations to fix
any differences between the two. The tutorial at
Hi Jack,
Looks like a BindGen bug. You might want to create a Jira to make sure
this is corrected for 1.2.3.
- Dennis
Dennis M. Sosnoski
XML and Web Services in Java
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ
Hi Ed,
You should be able to use a tool such as JarJar
(http://code.google.com/p/jarjar/) to modify the third part library and
the older version of the JiBX runtime (renaming the org.jibx classes to
some other package). Then these won't conflict with the newer version
used by your code.
-
Hi Rajesh,
I took a look at the JiBX code involved, but don't see any obvious way
for this to happen. There must be some issue with the reset handling, as
Nigel said.
Do you know if this happens every time you get a client time out, or
only occasionally?
Thanks,
- Dennis
Dennis M. Sosnoski
Hi Rudy,
The schema date/time handling is inherently a mess, mostly because the
schema people were more concerned about what they wanted in documents
for human-readable text exchange than in data exchange between
applications. The deserializeDate method should set the Date value
correctly in UTC
The namespace handling is a little awkward with JiBX 1.x. You've
basically got two ways of doing this. The first (and easiest) is to use
separate binding definitions for the Response element and the Struc
element, using a different namespace as the default for each (and
includeing the second
Hi Rajesh,
The Axis2 distribution really should include the WSDL so that it'll be
available for queries. I'll change it in the next release to do that. In
the meantime, you can change the build packaging yourself to copy the
WSDL to the META-INF directory of the Axis2 AAR file. I think that's all
Unfortunately, you're correct that there's no way for you to access the
schema metadata at present. Longer-term I'd like to standardize the
schema code generation model and expose it as an official API, but it'll
take a substantial refactoring before I'm ready to do that.
That said, it should be
Hi Stephan,
Are you *sure* you're using the 1.2.2 jars?
The JiBX/OTA subproject has a modular build example which uses include
from classpath. In that case the binding is coming from the META-INF
directory of the jar, so the include is:
include path=classpath:META-INF/base-binding.xml
Hi Frank,
No way to do this currently. If you want to create a Jira to track this
as an issue
(http://jira.codehaus.org/secure/BrowseProject.jspa?id=10410) I'll try
to add it in the future.
Thanks,
- Dennis
Dennis M. Sosnoski
XML and Web Services in Java
Training and Consulting
Hi Jürgen,
This looks like an AXIOM issue to me. As far as I can see from the stack
trace the JiBX code is not involved at this point in the execution. In
fact, it looks to me (judging from the createDocumentElement and
StAXSOAPModelBuilder.init methods in the stack trace) that the problem
is
Hi Matthew,
JiBX should be able to work with the classes in the jar as long as
you're only using public fields or methods. If the fields aren't public,
you need to either switch to public get/set methods (if available) or
unjar the class files so that the JiBX binding compiler can modify them.
Hi Joern,
No, this is not possible. The reason for this goes down to how XML is
parsed - basically, the document is *always* disassembled to its
component pieces on the way in, so if you want part of the text back as
XML you have to actively reassemble it.
The best you could do would be to
I don't know of any connection between this message and JiBX. Can you
supply the details of how you're getting it?
- Dennis
Dennis M. Sosnoski
XML and Web Services in Java
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ
Alexander Brosch wrote:
Hi Dennis,
I have the same problem in my code.
Is there a workaround until jibx 1.2.3 is released, e.g. to manually
change the wsdl / xsd / binding file ?
I've suggested people who need this drop back to JiBX 1.2.1, if that
works for them. I've gotten bogged down
Hi Sanjiv,
Validation can be done by using a StAX parser with validation turned on.
See the javax.xml.stream.XMLInputFactory JavaDocs from 1.6 or later JDK
- you basically need to create an instance of this factory class with an
implementation which supports validation (such as the one
Hi Alex,
I've been distracted by other projects, but I'm hoping to resolve the
remaining Axis2 issue this week. In the meantime, you should be able to
work with the 1.2.1 version of JiBX.
- Dennis
Dennis M. Sosnoski
XML and Web Services in Java
Training and Consulting
Hi Rice,
Thanks for reporting this - I verified the problems and partially fixed
them in the current CVS code (right now it's not generating the data
model components matching the base type in this type of situation), and
added the Jira issue http://jira.codehaus.org/browse/JIBX-374 to track
Hi Howard,
I just tried this myself and can confirm that there's a bug in the JiBX
1.2.2 Jibx2Wsdl code. Sorry - the normal build steps don't invoke the
Axis2 code, so I hadn't noticed this.
I'll get the problem fixed and update JiBX with a 1.2.3 release this week.
Thanks,
- Dennis
Dennis
Hi Michael,
I think I see where this could be going wrong, and I'll try looking into
the issue. If you create a Jira problem report and attach a project that
demonstrates the problem it'll get done sooner. :-)
In the meantime, rather than modifying the schema you can try using a
schema-type
Hi Rice,
Unfortunately there's no way to do this. There's never been a reason to
implement a different form of UnmarshallingContext within the JiBX code,
so there's no provision for handling it.
What is it you want to do with your UnmarshallingContext variation?
There may be a different way
Hi Don,
I'm very glad to hear you're enjoying your JiBX experience!
I think splitting the JiBX/OTA code generation into independent jars is
great - it should be possible to just add this as an alternative form of
the build. Making them osgi-compatible is also a good idea. But rather
than
Hi Ahu,
I don't understand your problem based on this email - can you provide
more details on what is going wrong?
Thanks,
- Dennis
Dennis M. Sosnoski
XML and Web Services in Java
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 -
Hi Alain,
JiBX 1.2 does not support xsi:type. I thought this was discussed in the
documentation, but I'm not finding it now that I look for that. I'll add
a Schema Compatibility page back into the next build to cover this issue
and some other less-significant issues.
I am working on adding
Hi Alain,
From the email, it looks like you've got an xs:group ref=.../
element as the content of an xs:extension or xs:restriction element.
I suspect this is happening as a result of some of the optimizations
CodeGen performs before building the Java representation for a schema,
but it
us from adopting pre-compiled binaries).
Thanks,
Alison
On 04/19/2009 08:25 PM, Dennis Sosnoski wrote:
Hi Karel,
I like the classpath:binding.xml path idea for precompiled bindings, and
will see if I can easily add that. I'll also take a look at your maven
precompiled bindings
JiBX 1.2.2 has been released, with many bug fixes, improvements, and new
features,. Here's a partial list of the changes:
* Added support for Joda time conversions for better representation
of schema date/time types.
* Fixed namespace handling for concrete mappings in precompiled
The file you attached is using JAXB, not JiBX. Assuming you're actually
using JiBX (which seems to be the case, given the exception you're
seeing), it's possible the error you're getting is a result of some
broken features in the 1.2.1 release. You should probably try generating
your data
- you need to get a copy of
commons-logging.jar and drop it into the JiBX/WS lib directory.
- Dennis
Ben Davies wrote:
Hi Dennis,
Any details on this subproject?
It would probably be of interest to me.
Ben
-Original Message-
From: Dennis Sosnoski [mailto:d...@sosnoski.com
Oh, and for now you need to use the current JiBX CVS code for everything
to work properly...
- Dennis
Dennis Sosnoski wrote:
Hi Ben,
I'm including a couple of variations on code generation from the OTA
schemas, an example of generating a WSDL based on a Java interface
definition using
:
*xsd:element name=creationTime type=dateTime/*
and the actual value in the xml that i need to parse is
this: *2009-08-12 12:18:06*
Best Regards,
Prashanth
Message: 4
Date: Fri, 15 Jan 2010 11:42:57 +1300
From: Dennis Sosnoski d...@sosnoski.com mailto:d...@sosnoski.com
Subject: Re
Hi Som,
I don't understand from your email exactly what you're doing. Is the
example.A class created by CodeGen from a schema definition? If so, and
if the class corresponds to a global element definition in the schema,
this code should work correctly.
Can you provide the definition of A from
Hi Prashanth
The issue you're referring to is an old one, relating to xsd:date
values. What is the type of value you're using, and what is the actual
value in the document? If the Java value is a java.util.Date the XML
representation *does* need to include the 'T' separator.
- Dennis
Hi Bogdan,
It's easy to filter a collection, though you need to write your own
collection load/store methods to do it. Easiest is to define an Iterator
for going through the items of the collection, returning only those
which match your criteria. This means the hasNext() method of the
Hi Whiz,
Nothing like that which I'm aware of, though it looks pretty simple.
But you say the mappings are not one-to-one java class to xml, yet it
sounds like you're working with generated mappings. Can you explain what
you're doing in more detail? It might be possible for you to adjust the
The chameleon namespace issues should be fixed in the latest 1.2.2 code.
I'm really, seriously, working to get this released soon, but in the
meantime I've uploaded the latest build to
http://jibx.sourceforge.net/jibx_1_2_2-SNAPSHOT.zip Can you give that a
try and see if it works?
Thanks,
Hi Robin,
I did fix several issues with the schema generation in the process of
getting this to work for the CodeGen customizations (since I wanted a
schema for those, and ran into the issues when I tried generating one).
I don't know if this includes your particular issue, though.
I've
I just tried this with the latest code, and although the problem you're
encountering with 1.2.1 has been fixed there's still another issue. I'll
get that fixed today and have it in place for the 1.2.2 release next week.
That's my least-favorite schema style, by the way, with all the global
Hi Davide,
You can't do what you want directly, but can easily fake it for
unmarshalling with a small code change. Just define a method addItem()
to add a new item to the collection, then use the binding structure:
binding direction=input
mapping name=root class=Root ordered=false
By using default=all on the namespace element you're telling JiBX to
apply it to /all/ elements. You want to just apply it to the thumbnail
element. Take off the default=all, and add
ns=http://search.yahoo.com/mrss; on the structure name=thumbnail
... element.
- Dennis
Dennis M. Sosnoski
I'm working on the final updates now - mostly around the CodeGen
examples and documentation, though there are still a couple of bugs in
extras to be fixed, and a couple of issues from the 1.2.2 test build.
The release will be within a week, though, whether everything I wanted
is in place or
Hi Erik,
The mapping element in a binding definition applies to a class as a
whole, so you can't use a field=... attribute directly on this
element. You'd instead need to use this type of binding:
binding
namespace uri=http://www.fao.org/fi/domain/flattener;
prefix=fact
Nigel Charman wrote:
A few comments on codegen from schema with the SNAPSHOT release:
* There are a lot of nice little improvements to the generated
code :-)
Glad to hear that!
* When generating code for multiple schema, the default package
name for the wrapper
debug it further.
cheers
nigel
Dennis Sosnoski wrote:
The JiBX 1.2.2 release is finally about ready to go. There are many
changes in and new features in this release, so in the hope of making
sure it's solid I'm posting a test build at
http://www.jibx.org/jibx_1_2_2-SNAPSHOT.zip
.
- Dennis
Dennis Sosnoski wrote:
The JiBX 1.2.2 release is finally about ready to go. There are many
changes in and new features in this release, so in the hope of making
sure it's solid I'm posting a test build at
http://www.jibx.org/jibx_1_2_2-SNAPSHOT.zip to encourage users to give
it a try
The JiBX 1.2.2 release is finally about ready to go. There are many
changes in and new features in this release, so in the hope of making
sure it's solid I'm posting a test build at
http://www.jibx.org/jibx_1_2_2-SNAPSHOT.zip to encourage users to give
it a try. Since this is not a formal
Should be working with the 1.2.2 code - I tried this out over the weekend.
- Dennis
jibx-us...@abilsoft.com wrote:
Hello,
I'm not sure if this is another variant of JIBX-263, or a completely
separate problem??? However, when I run CodeGen on Intuit's
QuickBooks schemas, I get the
Hi Peter,
Your XML document doesn't match your schema. If you want to allow
arbitrary content inside the Meta element (including nested elements)
you can't type it as xs:string.
If you don't give a type for the element (i.e., just have element
name=Meta/) the definition will be correct in
What's the generated binding for VerDTD look like now? And what's the
schema definition?
- Dennis
Peter Wu wrote:
Hi Dennis,
If I replace those xml strings inside Meta tags, I'm still receiving
the old error...
Expected {http://protocol.columboid.com/syncml/representation}VerDTD;
Hi Peter,
You don't show the mapping definition for the VerDTD element. From the
message you're getting, I wonder if this mapping might be referencing
itself.
Out of curiosity, do you really need each of the elements to be
represented by a separate class? It looks like most of these just
Peter Wu wrote:
...
mapping class=com.columboid.protocol.syncml.representation.VerDTD
name=VerDTD
value style=element name=VerDTD get-method=getVerDTD
set-method=setVerDTD/
/mapping
And actually, this mapping was generated by CodeGen with default settings
from an XSD.
Ah,
Hi Markus,
In theory you should be able to handle this with two separate methods to
test that boolean value, one which returns the value and one which
returns the inverse. You'd need to structure your binding definition
this way (I'm assuming you're doing an output-only binding... if you're
Hi Kishore,
CodeGen isn't really designed for direct use from application code, at
least not yet. The APIs for this class are still changing, so if you get
anything going with the current code there's a good chance it'll be
broken by the next release. If you do want to use it from your code,
Hi Bjoern,
Yes, you should be able to do this easily. Just use the finish() method
call to add a constructor with parameters matching each of the fields in
the class. You could instead use the valueAdded() method to collect
information about all the different values in the class (which avoids
Hi Alex,
Should be fixed in the 1.2.2 code (which you can try out by downloading
the 1.2.2SNAPSHOT jars from the Maven(1) repository, at
http://jibx.sourceforge.net/maven/jibx/jars/ ). It was solved by
checking for an empty name string and substituting _ as the name
(while keeping the empty
Hi Nahuel,
You'd probably need to do your own marshaller/unmarshaller for this. You
could base it on the org.jibx.extras samples, and basically just extend
the map handling code in extras (http://jibx.sourceforge.net/extras.html).
- Dennis
Nahuel Burgos wrote:
Hello everyone
I have a
times for each element. Based
on this, it seems like I would need to override a method somewhere else.
-Original Message-
From: Dennis Sosnoski [mailto:d...@sosnoski.com]
Sent: Saturday, September 26, 2009 12:45 AM
To: JiBX users
Subject: Re: [jibx-users] strip-suffixes is recursive
There's currently no support for BindGen breaking up the bindings in
this way. It could certainly be done, but at this point it seems like
there are a lot more people using CodeGen so that's where I've been
adding most of the enhancements. If you're interested in adding this
type of
Hi Hoolam,
This issue is due to missing support for xs:all in CodeGen. I've now
hopefully added this in the 1.2.2 code. You can download the jars from
the Maven(1) repository, at http://jibx.sourceforge.net/maven/jibx/jars/
if you want to try this for yourself (look for the 1.2.2-SNAPSHOT
You're correct that CodeGen didn't handle xs:all correctly, but that
should be fixed in the latest code.
- Dennis
Hoolam Woon wrote:
Hi all,
I get a JiBXException when I tried to unmarshall the following very
simple XML document:
style name=header
font face=Arial/
color
Hi Hoolam,
To specify the Java name for a value in the schema you need to use the
value-name='...' attribute on a customization for that value. The IBM
devWorks tutorial has some discussion of customizing values, though it
doesn't use this particular attribute:
Hi Rajiv,
Yes, it's true that JiBX will ignore attributes which are not defined in
the binding. Checking for unknown attributes is difficult in the current
code, and basically requires you to add extension code for this purpose.
I do this for all the XML documents used by JiBX (binding,
Oops. Fixed this for 1.2.2. :-)
Thanks,
- Dennis
Dennis M. Sosnoski
XML and Web Services in Java
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
Bob Reynolds wrote:
I was trying change the
Hi Adam,
It kind of depends on what you've done. In your earlier email you
mentioned eliminating reflection usage, ArrayList, Hashmap (though I
think you meant HashMap, right?), List, Iterator, Collections,
Comparator, and Classloader. Some of these are pretty easy to change,
others might
I've fixed the issues in the latest 1.2.2 code. You can download the
jars from the Maven(1) repository, at
http://jibx.sourceforge.net/maven/jibx/jars/ if you want to try this for
yourself (look for the 1.2.2-SNAPSHOT jars).
- Dennis
Dennis Sosnoski wrote:
Hi Mat,
They've created
Hi Tony,
I don't understand this, either. The requirement to xs:include a schema
if you're going to use it is not something unique to JiBX, it's part of
the schema specification. How did you construct this schema which is
using a type without including the type definition?
If you can give
1 - 100 of 757 matches
Mail list logo