Resending this, since it doesn't appear to have gone through...

It may be easiest to just call it an alpha release and let people start playing with it. I suspect you'll get plenty of feedback... I took a quick look at the limitations, here are some comments:

------------------------------------------------------------------------------
LIMITATIONS
  no enumeration support

Hopefully you just ignore the enumeration issue with a warning message and go with the base type, right (rather than dying)?

  no restriction/validation support

Yup.

  XML Schema types not supported: xs:any, xs:anyType

You *could* handle these with the DOM mapping, I think.

  xs:decimal type set as String.

This seems minor, though I suppose it should use BigDecimal by default (and integer should really use BigInteger). I haven't tried these classes, but they should work automatically given the default object serialization handling.

  prohibited attributes not supported

Minor issue, I'd think - here again, hopefully you just ignore with a warning and keep going.

  an anonymous/inline sequence as a choice.
    workaround: make it a complex type and reference it

That probably hits some of the schemas, but at least it's a reasonably easy workaround.

------------------------------------------------------------------------------

I've just added base64 encoding as the default for byte[], so if it's easy you can add that to the code generation.

Congratulations on the progress! And *thanks*, too - as I'm getting JibxSoap out at last this will be a great fit. Lets get them all ready to go by Tuesday and I'll release the whole set (xsd2jibx, JibxSoap, and
JiBX beta 3c) at once. The only reason I'm planning to wait until then is to hopefully hear back on a couple of open issues.


As for packaging and such, I'll fit your text into a nice HTML layout and include it in the build. Aside from that the only thing is to have your build.xml generate a zip that includes everything you want as part of the distribution.

  - Dennis

Cameron Taggart wrote:

OK, I modified the batch files and the build and they both now use the JIBX_HOME environment variable (with the necessary jars expected in $JIBX_HOME/lib). Everything is checked in and ready for a v0.1 release. :) I tested xsd2jibx out on my Linux box and the Customer, WMS, and WFS demo's work well. I was hoping to have some huge industry standard schema-based spec working as an example, but not for this release. I gave several a try: J2EE Servlet 2.4, FpML, SreadsheetML (Excel 2003). Each one is currently blocked by one of the limitations that I added to the readme. I hope to resolve some of these limitations for the next release.

How do I go about creating the release? Some pre-release testing by someone else would be appreciated as well.

Thanks,
Cameron

Dennis Sosnoski wrote:



No clues from me. On a side note, I'd suggest actually not committing the JiBX jars as part of the subproject CVS or including them in the distribution. Kind of by definition, I'd see anybody who's using the subprojects also installing JiBX.

As an aside, I think I'll do a minor beta 3c release, to clean up a couple of recently-reported problems and to add some functions I've found useful for the JibxSoap project (basically access methods in the generated BindingDirectory class that let you get the lists of mapped classes and associated element namespaces/names). I'll also be checking in the JibxSoap code and doing an initial alpha release of that this weekend.

- Dennis

Cameron Taggart wrote:



Eclipse 3.0 M9 has improved CVS support. I like that it has an option to keep the CVS files compatible with the rest of the CVS clients. I loaded Eclipse and got must everything committed except for the jibx jars. For some reason, I'm getting a lock error:

The server reported an error while performing the "cvs commit" command.
xsd2jibx: cvs commit: failed to create lock directory for `/cvsroot/jibx/xsd2jibx/lib/jibx-1.0b3b' (/cvsroot/jibx/xsd2jibx/lib/jibx-1.0b3b/#cvs.lock): No such file or directory
xsd2jibx: cvs commit: lock failed - giving up
xsd2jibx: cvs [commit aborted]: lock failed - giving up



I tried it out via cygwin cvs and received the same error. Any ideas?

Cameron








-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
jibx-devs mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jibx-devs

Reply via email to