On Wed, Nov 26, 2008 at 12:10, Dennis Sosnoski <[EMAIL PROTECTED]> wrote:
> Jérôme BERNARD wrote:
> > On Wed, Nov 26, 2008 at 01:46, Dennis Sosnoski <[EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>> wrote:
> >
> > There's another 1.2 change which might effect the way IDE plugins are
> > set up, which is using precompiled bindings. The new documentation
> > will
> > include the details, but the basic principle is that you can run the
> > JiBX binding compiler on a binding and then separately run the
> > compiler
> > again on a binding which extends the first one (essentially by
> > using an
> > <include> with a precompiled='true' flag). The binding compiler
> > recognizes that the base binding has already been compiled, and
> > doesn't
> > modify the classes which were used by that binding (which can even
> > be in
> > a jar, rather than having to be present as individual files). This
> > is an
> > especially nice feature for enterprise use, where different groups
> may
> > need to build on each other's work.
> >
> >
> > Can you elaborate a bit more on this?
> > I'm not sure I understand what you mean ;-)
>
> The JiBX binding compiler has always been set up on the basis that
> you'll compile all your bindings at one time, and it actively works at
> making sure any left-over methods added by previous binding compiler
> runs are deleted from the class files before it adds new code (actually,
> it reuses the old methods if possible - but that's a whole separate
> issue). So you use multiple bindings that include some of the same
> classes you always had to compile them at the same time.
>
> The new change allows for precompiled bindings, meaning you can take
> some base bindings and extend them with additional bindings, then
> compile the base bindings separately from the additional bindings. This
> is really useful in the case where one group within an organization is
> responsible for some base data structure, but there are other groups
> which extend that base data structure in their own ways to handle their
> particular requirements. With precompiled bindings, the group
> responsible for the base data structure can just give everyone else a
> jar containing the bound classes, along with a copy (possibly just a
> summary) of the binding. Then the other groups can add their own
> extensions, making use of the bindings already defined as part of the base.
>
> One concrete example is the OTA set of schemas for travel information.
> These include extension elements which are left open by the
> industry-wide schemas, but can be specified for use between particular
> partners. With precompiled bindings, the bindings for the base OTA
> schemas can be compiled first, and the extensions can be added by each
> individual group as needed.
This is really cool. Actually using JiBX for multimodules Maven build and
was in need of that...
> > Anyway to get access to an early release in order to work on the
> > IntelliJ plugin and be ready when 1.2 is released?
> > Is it in the same old CVS repo or did you move the repo (to SVN?)
> > somewhere else?
>
> The JiBX jar files are in the old CVS repo for now, at
> http://jibx.sourceforge.net/maven/jibx/jars/ - search for the
> "1.2-SNAPSHOT" matches for the latest versions. I'll be making some more
> changes before the beta release, but those should be minor.
Great. Just saw your other posts you sent a few minutes afterwards.
Jérôme.
--
Jerome Bernard,
Director, EMEA Operations,
Elastic Grid, LLC.
Blog: http://blog.elastic-grid.com
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
jibx-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jibx-devs
