Re: [xmlc] XMLC + Spring

Just a quick note.  I responded to Juergen Hoeller (privately) about the 
"1.8 MB of additional third-party jars".  Spring should only care about the 
compile-time dependencies, not the runtime ones.  As such, all they need is 
xmlc-base.jar which is about 520k.

Here's the location where XMLC integration with Spring is 
detailed.  Actually, not much detail there yet, but it doesn't look like 
there needs to be...
http://opensource.atlassian.com/confluence/spring/display/COOK/XMLC+integration


Jake

At 02:25 PM 4/1/2005 -0600, you wrote:
>Quoting Cameron Taggart <cameron.taggart@xxxxxxxxx>:
>
>> XMLC can be used as a view with Spring MVC with Spring v1.1.x and above.
>> 
http://www.jroller.com/comments/raible/home/xmlc_support_in_spring_1#comments
>>
>> Juergen Hoeller brings up a point about XMLC that I don't quite
>> understand yet either.  "This is nearly 1.8 MB of additional
>> third-party jars, half of it cause by the great XMLC
>> decision to depend on a repackaged Xerces version..."
>> http://article.gmane.org/gmane.comp.java.springframework.devel/7762
>>
>
>Thanks for alerting us to the Spring + XMLC integration!
>
>> Which version of Xerces is packaged with XMLC v2.2.5?  What are the
>> advantages and disadvantages of repackaging Xerces?  Is LazyDOM the
>> main benefit?
>>
>
>Xerces 1.4.4.  Look in xmlc-all-runtime.jar and look for the
>org.enhydra.apache.xerces package.
>
>I believe this was done because XMLC does some very low level stuff which 
ties
>it to the internal api's of Xerces; and we all know how much these API's can
>change.  And we still had a problem when XMLC depended on the 
org.apache.xerces
>package because it interfered with other versions of Xerces in the classpath,
>which was why we internalized the namespace to org.enhydra.apache.xerces.
>
>Note that XMLC ships with jars all split up in addition to the all inclusive
>xmlc-all-runtime.jar, meaning that xmlc-xerces.jar could be put in a global
>classloader area.  Additionally, if you don't need various stuff like the
>mobile or XHTML packages, you could also use the xmlc.jar which is as 
small as
>it gets.  And when the next release comes out, XMLC will use ASM 2.0 rather
>than BCEL for deferred parsing/dynamic loading.  This means that a ~500k
>dependency gets replaced by a ~20k dependency.  So, there are ways to reduce
>the size of XMLC and its dependencies.
>
>In any case, the way we depend on Xerces will need to be rethought in future
>versions.
>
>
>Jake
>
>> Cameron
>>
>>
>
>
>
>
>
>--
>You receive this message as a subscriber of the xmlc@xxxxxxxxxxxxx mailing
>list.
>To unsubscribe: mailto:xmlc-unsubscribe@xxxxxxxxxxxxx
>For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
>ObjectWeb mailing lists service home page: http://www.objectweb.org/wws



--
You receive this message as a subscriber of the xmlc@xxxxxxxxxxxxx mailing list.
To unsubscribe: mailto:xmlc-unsubscribe@xxxxxxxxxxxxx
For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws