[jelly] jaxme tag library xml version woes

[robert burrell donkin <ro...@blueyonder.co.uk>]

the required jaxme jars are now in the maven repository. (the mess 
hasn't been cleared up but i think that the repo team are looking to 
establish better procedures for the future rather than fix past 
mistakes.) so i've been taking a look at adding the jaxme tag library 
into jelly-tags and i've run into a bit of a problem.

the tag library builds fine without dependencies but once the 
project.xml extends tag-project.xml, the tests fail. the issue is that 
the DOM libraries which ships with xerces 2.2.1 are incompatible with 
the ones used by jaxme. (if i comment out the parser dependencies in 
the project.xml, it works fine.) what makes solving this one tougher is 
that really the generator needs to use the parser from the base 
classloader (and so must have no xml parser dependencies in the the 
POM).

any ideas?

(i may - for the moment - remove the generation test since this is the 
only one that fails and it isn't a particularly good test in any case.)

- robert


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org

Re: [jelly] jaxme tag library xml version woes

[robert burrell donkin <ro...@blueyonder.co.uk>]

On 24 Mar 2004, at 15:50, Paul Libbrecht wrote:

<snip>

> Would the other way be to run the test in a forked VM ?

hi paul

thanks: running in a forked VM seems to have made a big improvement. 
i've committed a first cut of the jaxme stuff. hopefully people will 
take a look and note any issues (either with formatting or code). i do 
intend to come back sometime soonish and improvement the documentation 
(and work out exactly how the automagic tag library documentation 
works). i should also like to add more unit tests.

i've left out the generation test. i wasn't very happy with the test 
anyway and i now can see a better test cycle (generate -> compile -> 
marshall/unmarshall generated products) so i'll try to get that working 
sometime rather than the older test.

the feature set is very basic at the moment. i'll try to come back and 
add more as i learn more about jaxme.

BTW do you know why the gump build is failing?

- robert


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org

Re: [jelly] jaxme tag library xml version woes

[robert burrell donkin <ro...@blueyonder.co.uk>]

On 24 Mar 2004, at 15:50, Paul Libbrecht wrote:

> On 24-Mar-04, at 09:57 Uhr, robert burrell donkin wrote:
>> the tag library builds fine without dependencies but once the 
>> project.xml extends tag-project.xml, the tests fail. the issue is 
>> that the DOM libraries which ships with xerces 2.2.1 are incompatible 
>> with the ones used by jaxme. (if i comment out the parser 
>> dependencies in the project.xml, it works fine.) what makes solving 
>> this one tougher is that really the generator needs to use the parser 
>> from the base classloader (and so must have no xml parser 
>> dependencies in the the POM).
>>
>> any ideas?
>
> So upgrading the Xerces dependency wouldn't solve anything, correct ?

not sure but i'll give it a try. it's hard to know which jars come with 
which xerces implementation...

> Kind of dark.
> You should test it but I don't think there's any reliance on that 
> particular Xerces version (there shouldn't really).

(i'm not sure but) i seem to remember some issue about problems with 
backwards compatibility between different versions of w3c DOM. i think 
that the issue is that different versions of xerces ship with 
incompatible DOM implementations.

> Would the other way be to run the test in a forked VM ?

i'll look into this but i suspect the that maven will provide the 
incompatible inherited xerces dependency in the forked VM (which will 
cause the test to fail).

- robert


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org

Re: [jelly] jaxme tag library xml version woes

[Paul Libbrecht <pa...@dfki.de>]

On 24-Mar-04, at 09:57 Uhr, robert burrell donkin wrote:
> the tag library builds fine without dependencies but once the 
> project.xml extends tag-project.xml, the tests fail. the issue is that 
> the DOM libraries which ships with xerces 2.2.1 are incompatible with 
> the ones used by jaxme. (if i comment out the parser dependencies in 
> the project.xml, it works fine.) what makes solving this one tougher 
> is that really the generator needs to use the parser from the base 
> classloader (and so must have no xml parser dependencies in the the 
> POM).
>
> any ideas?

So upgrading the Xerces dependency wouldn't solve anything, correct ?
Kind of dark.
You should test it but I don't think there's any reliance on that 
particular Xerces version (there shouldn't really).

Would the other way be to run the test in a forked VM ?

paul


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org