Hi Jose, I thought a binding editor might be one good extension to the plugin, but it's certainly not the only possibility. If you are interested in the editor idea, the email I sent in response to Lee's question yesterday discusses the binding validation operation. That would be what you'd need to build on for flagging problems in the binding.
Another thought is to have intelligent tracking of when you need to recompile the binding. The binding validation code is again what would be involved in implementing this. It'd take some extensions to the current code, though. Right now the code gets class information for all the classes referenced in the binding (and their superclasses). It doesn't track these classes, but it would be easy to extend the code so that it does (I think just create a variation of the IClassLocator implementation passed into the binding validation which keeps a hashset of the classes - right now the implementation of this is an anonymous inner class in the org.jibx.binding.model.BindingElement.newValidationContext() method, but it's simple to restructure; if you're interested I can do this myself tomorrow). Once you have the list of classes involved in the binding, you should be able to hook into the Eclipse notifications of class file changes and fire off a binding compile only when needed. I'm sure there are other features that would be really useful to have - you had quite a list in one of your first emails to me, which sounded very good. A lot of the nice features are going to depend on the new generation of the tools, and I'm trying to make some good progress on those this month. There's also an IDEA plugin, so maybe we can get some good ideas shared across the plugins in preparation for a great 1.2 release. - Dennis [EMAIL PROTECTED] wrote: > Hi guys, > > I will soon be releasing a 1.0 version of the jibx 1.x eclipse > plug-in. I have been informed that a binding editor might be usefull > but I would like to get an idea about what type of tooling (eclipse) > support would be most beneficial to JibX users. Please let me know you > ideas? > > Jose Badeau > > -----Original Message----- > From: [EMAIL PROTECTED] > To: [email protected] > Sent: Thu, 8 Jun 2006 12:11:18 -0700 > Subject: jibx-devs Digest, Vol 1, Issue 301 > > Send jibx-devs mailing list submissions to > [email protected] <mailto:jibx-devs%40lists.sourceforge.net> > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/jibx-devs > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] <mailto:jibx-devs-request%40lists.sourceforge.net> > > You can reach the person managing the list at > [EMAIL PROTECTED] <mailto:jibx-devs-owner%40lists.sourceforge.net> > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of jibx-devs digest..." > > > Today's Topics: > > 1. JiBX Contribution (Shih-gian Lee) > 2. JiBX JUnit tests (Shih-gian Lee) > 3. Re: JiBX Contribution (Dennis Sosnoski) > 4. [jira] Commented: (JIBX-110) Having a J2ME compatible > official jibx release (Dirk Bade (JIRA)) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 6 Jun 2006 23:23:16 -0500 > From: "Shih-gian Lee" <[EMAIL PROTECTED] <mailto:shihgian%40gmail.com>> > Subject: [jibx-devs] JiBX Contribution > To: [email protected] <mailto:jibx-devs%40lists.sourceforge.net> > Message-ID: > <[EMAIL PROTECTED] > <mailto:6a46def40606062123s27b5bcefjcb935d0fe58d2ca3%40mail.gmail.com>> > Content-Type: text/plain; charset="iso-8859-1" > > Hello, > > I would like to contribute to JiBX project. I have been using Castor but > came across this binding tool and it is kind of cool. So, I would like to > help out the community. > > I have done what is required on this page - > http://jibx.sourceforge.net/contributing.html > > I would like to know if you still need someone to work on the tasks listed > above? If so, I would like to start writing some JUnit test cases and get > familiar with the code base and hopefully can contribute to the source after > writing some JUnit test cases. I think writing test cases is a good way for > me to start learning the code base. > > Thank you. > > - Lee > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://sourceforge.net/mailarchive/forum.php?forum=jibx-devs/attachments/20060606/90b354ba/attachment.html > > > > ------------------------------ > > Message: 2 > Date: Wed, 7 Jun 2006 22:00:17 -0500 > From: "Shih-gian Lee" <[EMAIL PROTECTED] <mailto:shihgian%40gmail.com>> > Subject: [jibx-devs] JiBX JUnit tests > To: [email protected] <mailto:jibx-devs%40lists.sourceforge.net> > Message-ID: > <[EMAIL PROTECTED] > <mailto:6a46def40606072000y26af05a1p442b71cd33e49569%40mail.gmail.com>> > Content-Type: text/plain; charset="iso-8859-1" > > Hello JiBx experts, > > I would like to contribute to JiBX open-source. I would like to help > creating some JUnit test cases or replacing the black box test cases. > > I believe writing test cases is a great way for me to understand JiBX code > base before contributing to the core JiBX. > > Could you help to provide me with some suggestions or directions how I > should start? > > I will try to download the source and take a look at it. > > Thank you. > > - Lee > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://sourceforge.net/mailarchive/forum.php?forum=jibx-devs/attachments/20060607/4444d9b1/attachment.html > > > > ------------------------------ > > Message: 3 > Date: Thu, 08 Jun 2006 15:47:47 +1200 > From: Dennis Sosnoski <[EMAIL PROTECTED] <mailto:dms%40sosnoski.com>> > Subject: Re: [jibx-devs] JiBX Contribution > To: JiBX project developers <[email protected] > <mailto:jibx-devs%40lists.sourceforge.net>> > Message-ID: <[EMAIL PROTECTED] <mailto:44879DE3.4000302%40sosnoski.com>> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi Lee, > > I'd really appreciate some help in this test area, since it's crucial > for good user experiences. > > The current setup is that there are dozens of functional tests of JiBX > included under the /build/test directory. The functional tests mostly > take the form of a binding applied to some test classes and tested by > first unmarshalling a test document, then marshalling it back out, and > finally comparing the marshalled document to the original document, > ignoring whitespace and other nonessentials. The build.xml file has a > long list of these test cases (along with some variations where > different bindings are used for unmarshalling and marshalling, along > with different test documents). There's only a single JUnit test case at > present, org.jibx.runtime.UtilityTest. > > Now in and of itself I don't think this is a bad thing. I think it'd be > difficult to run the functional tests as JUnit test, because of the way > JiBX works and the number of different documents involved. But the big > thing that gets missed with this approach is that I'm only testing what > works, not what reports an error. I'd really like to see more testing of > error conditions in the binding compiler to make sure that problems are > reported directly to the user during the validation of the binding > definition, as opposed to just causing an exception during code > generation or (worse) some obscure runtime failure. > > The binding validation code works with a ValidationContext. When the > binding compiler is executed directly it does the validation and then > reports the errors in the console output. It's easy to run the same > process directly, though - just use the > org.jibx.binding.model.BindingElement newValidationContext() method, > followed by the validateBinding() method. All problems found in the > binding are recorded in the validation context. > > So what I'd suggest as a starting point in improving the JiBX testing is > to write some JUnit tests that try validating a bunch of different > bindings with known problems, and make sure that the appropriate > problems (warning, error, or fatal) are reported on the correct binding > elements (which you can get from the actual > org.jibx.binding.model.ValidationProblem item). I'd recommend setting up > a set of data classes to be used for the bindings, and just keeping the > binding definitions as XML files rather than embedding them in the JUnit > code. Some of the errors to be tested are obvious, such as references to > classes or methods that don't exist, but you can find others by going > through the JiBX documentation and trying things that are supposed to be > forbidden. If you find something that's supposed to be forbidden but is > not actually checked in the binding validation, either the documentation > needs to change or a check needs to be added to the validation. > > Once you've done some work on this we can discuss ways to make it > easier. For instance, it'd probably make sense to embed the expected > error information directly in the binding definitions. This could be > done using special added elements in the binding, say "<annotation>" > elements to mimic the schema approach. That's something I've been > thinking about implementing anyway, since I've thought of a few cases > where extension information (related to the binding, but not actually > part of it) would be useful in the binding definitions. > > The test work will hopefully get you familiar with both JiBX itself and > the binding model validation, which is a key part of JiBX for most of > the interesting developments to be done in the future (including the new > generation tools I'm working on now, along with things like IDE support > for flagging binding errors; I'll even be driving the code generation > directly off the binding model when I change over to using ASM for this > purpose). > > - Dennis > > Dennis M. Sosnoski > SOA, Web Services, and XML > Training and Consulting > http://www.sosnoski.com - http://www.sosnoski.co.nz > Seattle, WA +1-425-296-6194 - Wellington, NZ +64-4-298-6117 > > > > Shih-gian Lee wrote: > > Hello, > > > > I would like to contribute to JiBX project. I have been using Castor > > but came across this binding tool and it is kind of cool. So, I would > > like to help out the community. > > > > I have done what is required on this page - > > http://jibx.sourceforge.net/contributing.html > > > > I would like to know if you still need someone to work on the tasks > > listed above? If so, I would like to start writing some JUnit test > > cases and get familiar with the code base and hopefully can contribute > > to the source after writing some JUnit test cases. I think writing > > test cases is a good way for me to start learning the code base. > > > > Thank you. > > > > - Lee > > > > ------------------------------ > > Message: 4 > Date: Thu, 8 Jun 2006 10:29:43 -0500 (CDT) > From: "Dirk Bade (JIRA)" <[EMAIL PROTECTED] <mailto:jira%40codehaus.org>> > Subject: [jibx-devs] [jira] Commented: (JIBX-110) Having a J2ME > compatible official jibx release > To: [EMAIL PROTECTED] <mailto:jibx-devs%40lists.sf.net> > Message-ID: > <[EMAIL PROTECTED] > <mailto:106702698.1149780583540.JavaMail.haus-jira%40codehaus01.managed.contegix.com>> > > Content-Type: text/plain; charset=ISO-8859-1 > > [ http://jira.codehaus.org/browse/JIBX-110?page=comments#action_66947 ] > > Dirk Bade commented on JIBX-110: > -------------------------------- > > Thanks for your comment Dennis, i tried to run only the enablej2me-target and > it > told me that 0 files had been found or modified in my path > ("C:\Java\JiBX\build/src/[...]" > - mind the different slashes). I tried to run the same target under Linux and > it > worked fine. I looked through the JEnable-sources and the build-file and > found > that JEnable gets confused in case it has to deal with absolute file-paths > under > Windows. Changing the arguments of the JEnable-call in the ant file from > absolute to relative path-names worked (at least under Windows). Now > everything > works fine and the jibx-j2me-run.jar does its job also on my mobile device. > > > Having a J2ME compatible official jibx release > > ---------------------------------------------- > > > > Key: JIBX-110 > > URL: http://jira.codehaus.org/browse/JIBX-110 > > Project: JiBX > > Type: New Feature > > > Components: core > > Environment: J2ME > > Reporter: Lars > > Assignee: Dennis Sosnoski > > Fix For: JiBX 1.1 beta4 > > > > > > > It would be great having an offical jibx release for J2ME environments. > > With respect to our code analysis in the current version only slight > > modifications are necessary (below I have copied a part of the original > > post > of Dirk Bade from the jibx-users list): > > The only Problem is the usage of java.sql.Time, java.sql.Date and > java.sql.Timestamp within the jibx.runtime.Utility-class. > > If you simply remove the imports of these packages within the class and > > change > the methods for serialization and deserialization > > (using Object instead of java.sql.* in the method-signature) it works fine. > And because java.sql.* is not > > included in the 'Personal Profile' for mobile devices you won't miss the > methods anyway. The binding-compiler does not like the changes in the > method-signatures, so one has to use the original Utility-class for > binding-compiling. > > -- > This message is automatically generated by JIRA. > - > If you think it was sent incorrectly contact one of the administrators: > http://jira.codehaus.org/secure/Administrators.jspa > - > For more information on JIRA, see: > http://www.atlassian.com/software/jira > > > > > ------------------------------ > > > > ------------------------------ > > _______________________________________________ > jibx-devs mailing list > [email protected] <mailto:jibx-devs%40lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/jibx-devs > > > End of jibx-devs Digest, Vol 1, Issue 301 > ***************************************** > ------------------------------------------------------------------------ > *Check out AOL.com today* > <http://pr.atwola.com/promoclk/100122638x1081283466x1074645346/aol?redir=http%3A%2F%2Fwww%2Eaol%2Ecom>. > > Breaking news, video search, pictures, email and IM. All on demand. > Always Free. > ------------------------------------------------------------------------ > > _______________________________________________ > jibx-devs mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/jibx-devs > _______________________________________________ jibx-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jibx-devs
