On 6/4/07, Stephen Coy <[EMAIL PROTECTED]> wrote:

On 05/06/2007, at 12:08 AM, Jeff Mutonho wrote:

> On 6/4/07, Stephen Coy <[EMAIL PROTECTED]> wrote:
>> On 04/06/2007, at 10:48 PM, Jeff Mutonho wrote:>
>> If so, does the mapping file have a DOCTYPE? The "lazy" attribute
>> appears in the Hibernate 2.0 DTD, so it should be OK.
>
> Yes it does.It's like this :
>
> <?xml version="1.0" encoding="UTF-8"?>
>
> <!DOCTYPE hibernate-mapping PUBLIC
>    "-//Hibernate/Hibernate Mapping DTD 2.0//EN"
>    "http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd";>
>
> <hibernate-mapping
>>
>    <class
>        name="za.co.telkom.portal.Person"
>        lazy="true"
>    >
>

You have an XML parser error on line 58 according to your stack
trace. That seems to be way after this. You've probably got some
Hibernate 3.0 markup in your Person class and it has sneaked into the
mapping file. Do you have a validating xml editor than you can check
the mapping file with? If you can find the bad xml, you will be able
to locate the associated bean markup and fix it, instead of
continuing to hide it.


>
> The 1.2.1 version  looks like this :
> <?xml version="1.0"?>
>
> <!DOCTYPE hibernate-mapping PUBLIC
>    "-//Hibernate/Hibernate Mapping DTD 2.0//EN"
>    "http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd";>
>
> <hibernate-mapping>
>    <class
>        name="za.co.telkom.portal.Person"
>        dynamic-update="false"
>        dynamic-insert="false"
>    >
>
> Isn't it possible to get Maven xdoclet plugin to use  work with the
> 1.2.1 jars at runtime instead of the 1.2.3?

Anything's possible, but it won't be easy. Fix the markup in your
java classes instead.

Steve Coy


Thanx Steve for your help.Its a bit tricky for me to sort out the java
classes instead due to redtape in convincing the powers that be why we
need to get rid of the lazy="true"  ...more so  due  the fact that  a
pre-existing build.xml file that uses the 1.2.1 jars does not have the
same issues the maven xdoclet plugin had

I still find it hard to understand how  maven is denying me the
flexibility of me saying I wish to use 1.2.1 jars instead of the new
1.2.3 xdoclet jars.


"Don't take the name of root in vain."

Jeff  Mutonho
Cape Town
South Africa

GoogleTalk : ejbengine
Skype        : ejbengine
Registered Linux user number 366042

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to