Hi Jann:
Tagging xml-apis.jar as usual, is problematic. It involves external
interfaces. xml-commons is aware of this and there is a work in progress
in this area. As a workaround, use xml-apis.jar that is distributes with
the xerces you will use.
One of the main changes in xerces 2.7.0 is DOM3, hence xml-apis include
DOM3 interfaces. This is why you cannot use the xml.apis.jar from xerces
2.6.2.
Xerces in cocoon will be rollbacked to xerces 2.6.2. Not because 2.7.0
is buggy, but because was requested to keep backward compatibility.
Specially concerns are related to Applications servers (weird, right?
lol.) . Xerces 2.7.0 works like a charm and is faster than his
predecesor. I am a happy using it with Lenya 2.1.x-dev and cocoon
2.1.8-dev in our 15 days-old new intranet. Until now no problems at all.
Important thing to keep in mind: cocoon 2.2 will ship xerces 2.7.0. ;-)
I hope this helps.
Best Regards,
Antonio Gallardo.
Jann Forrer wrote:
Hi
Yesterday I had some problem with the create usecae. I could solve the
problem if i used the xml-apis.jar from $LENYA_HOME/lib instead of the one
shipped with cocoon-2.1.X (BTW the build process should copy the
$LENYA_HOME/lib to $LENYA_HOME/build/lenya/webapp/WEB-INF/lib/ but there
is already the xml-apis.jar from cocoon-2.1.X and it is not overwritten).
The following questions arised from this finding:
- Which xml-apis.jar should be used? The cocoon one or the lenya one?
- There is a xercesImpl-2.6.2.jar in $LENYA_HOME/lib and a
xercesImpl-2.7.0.jar in the cocoon lib. After build.sh I end up
whith both libraries in $LENYA_HOME/build/lenya/webapp/WEB-INF/lib/.
Are both libs necessary?
Jann
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
