[prev in list] [next in list] [prev in thread] [next in thread]
List: barracuda
Subject: RE: [Barracuda] Question about new release
From: "Christian Cryder" <christianc () granitepeaks ! com>
Date: 2003-05-28 15:38:28
[Download RAW message or body]
Yep. That's it...I think the other stuff you listed should continue to be
separate. The basic reason for including the plankton stuff in with the core
is that the barracuda-core.jar is unusable without the plankton classes
(although the converse is not true).
Christian
----------------------------------------------
Christian Cryder [christianc@atmreports.com]
Internet Architect, ATMReports.com
Barracuda - http://barracudamvc.org
----------------------------------------------
"Coffee? I could quit anytime, just not today"
-----Original Message-----
From: barracuda-admin@barracudamvc.org
[mailto:barracuda-admin@barracudamvc.org]On Behalf Of Jacob Kjome
Sent: Wednesday, May 28, 2003 9:23 AM
To: barracuda@barracudamvc.org
Subject: RE: [Barracuda] Question about new release
Yes, I suppose that might be prudent.... except that it should only
include barracuda-core.jar and plankton.jar rather than also including the
contents of all jars such as admin, config, examples, testbed, and
tutorials, and the taskdefs. barracuda.jar should just be the runtime
libraries. Is this what you have in mind? If people really want to add
stuff like the admin or config app to their project, they can add the
specific jars.
Jake
At 08:17 AM 5/28/2003 -0600, you wrote:
> I think the single jar is simpler to deal with and causes less
> confusion that using individual jars.... especially the xerces
> jar which isn't "really* xerces for all intents and purposes.
> This just caused needless confusion. The fact is, xmlc's xerces
> library is for xmlc's internal use only.
Yes, I agree, actually.
Along these lines, I think we ought to reconsider making a single
barracuda.jar that combines the core and plankton stuff needed for
runtime...we can actually do this right now, using the jars.master
taskdef -
it creates a single barracuda.jar, but it just leaves it in /lib-cvs,
rather
than deploying inot /lib. We deploy all of our webapps using that single
jar
just because fewer jars seems to make it easier to keep track of. I
suspect
most people would probably prefer this (and we could still build the
barracuda-core.jar and plankton.jar in /lib-cvs...just not deploy them).
Anyway...just a thought...not a burning issue or anything.
Christian
----------------------------------------------
Christian Cryder [christianc@atmreports.com]
Internet Architect, ATMReports.com
Barracuda - http://barracudamvc.org
----------------------------------------------
"Coffee? I could quit anytime, just not today"
> -----Original Message-----
> From: barracuda-admin@barracudamvc.org
> [mailto:barracuda-admin@barracudamvc.org]On Behalf Of Jacob Kjome
> Sent: Tuesday, May 27, 2003 7:43 PM
> To: barracuda@barracudamvc.org
> Subject: Re: [Barracuda] Question about new release
>
>
>
> almost. Here's the actual list...
>
> wireless
> xhtml
> xmlc
> xerces
>
> Xalan has nothing to do with the XMLC stuff. And note that
> xmlc-taskdef is still a separate jar as it isn't part of the xmlc
> runtime libraries.
>
> The reason why I did this is twofold...
>
> 1. XMLC's xerces libraries were moved into the
> org.enhydra.apache.xerces namespace which hides it from other
> versions of Xerces such as the ubiquitous Xerces2 that comes, by
> default, with Ant, Tomcat, and lots of other packages.
>
> 2. #1 is great, but there were still endorsed package such as
> javax.xml.*, org.w3c.dom.*, and org.xml.* that existed in the
> xerces jar. This is a problem in webapps because it is against
> the Sun classloader spec and the servlet spec to load endorsed
> packages from a child classloader (ie... the WebappClassLoader).
> XMLC beta1 was released with these endorsed packages still
> included in the xerces.jar file. I decided that there was no
> need for this and removed the endorsed packages. This makes
> XMLC's xerces libraries totally free of any classloader issues.
> As such, the xmlc-runtime jar file is able to be added directly
> into WEB-INF/lib which makes deploying Barracuda an absolute
> no-brainer now that there is no extra copy-step (ie... copying
> xerces.jar to CATALINA_HOME/shared/lib).
>
> Now, you may say "isn't this what we were trying to get away from
> before...an integrated jar file that might collide with existing
> jars"? Well, that used to be the case, but now since the single
> xmlc-runtime jar file no longer contains libraries that would
> conflict with anything else out there, this is not an issue.
> "But, now I have this big jar." "What if I don't need wireless
> and xhtml libraries"? Well, for one, they are very small parts
> of the xmlc-runtime jar file and secondly, you can switch out the
> xmlc-runtime for individual jars in the xmlc distribution
> (currently under XMLC's CVS with the tag
> "XMLC_2_2_POST_BETA_1_BARRACUDA_1_2_0").
>
> I think the single jar is simpler to deal with and causes less
> confusion that using individual jars.... especially the xerces
> jar which isn't "really* xerces for all intents and purposes.
> This just caused needless confusion. The fact is, xmlc's xerces
> library is for xmlc's internal use only.
>
> One thing you need to make sure of is that the JAXP, DOM, and SAX
> libraries exist in the classpath. This is usually provide by
> Xerces and the xmlParserAPIs.jar or xml-apis.jar that it comes
> with. So, if you didn't have these in ANT_HOME/lib and
> CATALNIA_HOME/common/endorsed, you definitely should now.
>
> Hopefully that clears things up.
>
> Jake
>
>
> At 03:53 PM 5/27/2003 -0600, you wrote:
>
> Hey Jake, it looks like there's been some consolidation of jars in the
> Barracuda WEB-INF/jars directory...can you confirm that
>
> /WEB-INF/jars/wireless-xmlc-2.2.jar
> /WEB-INF/jars/xalan-2.5.0.jar
> /WEB-INF/jars/xhtml-xmlc-2.2.jar
>
> have all been collapsed into
>
> /WEB-INF/jars/xmlc-all-runtime-2.2.jar
>
> Thanks,
> Christian
> ----------------------------------------------
> Christian Cryder [christianc@atmreports.com]
> Internet Architect, ATMReports.com
> Barracuda - http://barracudamvc.org
> ----------------------------------------------
> "Coffee? I could quit anytime, just not today"
>
> _______________________________________________
> Barracuda mailing list
> Barracuda@barracudamvc.org
> http://barracudamvc.org/lists/listinfo/barracuda
_______________________________________________
Barracuda mailing list
Barracuda@barracudamvc.org
http://barracudamvc.org/lists/listinfo/barracuda
[Attachment #3 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2800.1170" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=415113715-28052003><FONT face=Arial color=#0000ff size=2>Yep.
That's it...I think the other stuff you listed should continue to be separate.
The basic reason for including the plankton stuff in with the core is that the
barracuda-core.jar is unusable without the plankton classes (although the
converse is not true).</FONT></SPAN></DIV>
<DIV><SPAN class=415113715-28052003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=415113715-28052003><FONT face=Arial color=#0000ff
size=2>Christian</FONT></SPAN></DIV>
<DIV><SPAN class=415113715-28052003></SPAN><FONT
size=2>----------------------------------------------<BR>Christian Cryder
[christianc@atmreports.com]<BR>Internet Architect, ATMReports.com<BR>Barracuda -
<A href="http://barracudamvc.org/"
target=_blank>http://barracudamvc.org</A><BR>----------------------------------------------<BR>"Coffee? \
I could quit anytime, just not today" </FONT></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; \
MARGIN-RIGHT: 0px"> <DIV class=OutlookMessageHeader dir=ltr align=left><FONT \
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B>
barracuda-admin@barracudamvc.org
[mailto:barracuda-admin@barracudamvc.org]<B>On Behalf Of </B>Jacob
Kjome<BR><B>Sent:</B> Wednesday, May 28, 2003 9:23 AM<BR><B>To:</B>
barracuda@barracudamvc.org<BR><B>Subject:</B> RE: [Barracuda] Question about
new release<BR><BR></FONT></DIV><FONT size=3><BR>Yes, I suppose that might be
prudent.... except that it should only include barracuda-core.jar and
plankton.jar rather than also including the contents of all jars such as
admin, config, examples, testbed, and tutorials, and the taskdefs.
barracuda.jar should just be the runtime libraries. Is this what you
have in mind? If people really want to add stuff like the admin or
config app to their project, they can add the specific
jars.<BR><BR>Jake<BR><BR>At 08:17 AM 5/28/2003 -0600, you wrote:<BR>
<BLOCKQUOTE class=cite cite="" type="cite">> I think the single jar is
simpler to deal with and causes less<BR>> confusion that using individual
jars.... especially the xerces<BR>> jar which isn't "really* xerces for
all intents and purposes.<BR>> This just caused needless confusion.
The fact is, xmlc's xerces<BR>> library is for xmlc's internal use
only.<BR><BR>Yes, I agree, actually.<BR><BR>Along these lines, I think we
ought to reconsider making a single<BR>barracuda.jar that combines the core
and plankton stuff needed for<BR>runtime...we can actually do this right
now, using the jars.master taskdef -<BR>it creates a single barracuda.jar,
but it just leaves it in /lib-cvs, rather<BR>than deploying inot /lib. We
deploy all of our webapps using that single jar<BR>just because fewer jars
seems to make it easier to keep track of. I suspect<BR>most people would
probably prefer this (and we could still build the<BR>barracuda-core.jar and
plankton.jar in /lib-cvs...just not deploy them).<BR><BR>Anyway...just a
thought...not a burning issue or
anything.<BR><BR>Christian<BR><BR>----------------------------------------------<BR>Christian \
Cryder [christianc@atmreports.com]<BR>Internet Architect,
ATMReports.com<BR>Barracuda - <A href="http://barracudamvc.org/"
eudora="autourl">http://barracudamvc.org</A><BR>----------------------------------------------<BR>"Coffee? \
I could quit anytime, just not today"<BR><BR>> -----Original
Message-----<BR>> From: barracuda-admin@barracudamvc.org<BR>> [<A
href="mailto:barracuda-admin@barracudamvc.org"
eudora="autourl">mailto:barracuda-admin@barracudamvc.org</A>]On Behalf Of
Jacob Kjome<BR>> Sent: Tuesday, May 27, 2003 7:43 PM<BR>> To:
barracuda@barracudamvc.org<BR>> Subject: Re: [Barracuda] Question about
new release<BR>><BR>><BR>><BR>> almost. Here's the actual
list...<BR>><BR>> wireless<BR>> xhtml<BR>> xmlc<BR>>
xerces<BR>><BR>> Xalan has nothing to do with the XMLC
stuff. And note that<BR>> xmlc-taskdef is still a separate
jar as it isn't part of the xmlc<BR>> runtime libraries.<BR>><BR>>
The reason why I did this is twofold...<BR>><BR>> 1. XMLC's
xerces libraries were moved into the<BR>> org.enhydra.apache.xerces
namespace which hides it from other<BR>> versions of Xerces such as the
ubiquitous Xerces2 that comes, by<BR>> default, with Ant, Tomcat, and
lots of other packages.<BR>><BR>> 2. #1 is great, but there were
still endorsed package such as<BR>> javax.xml.*, org.w3c.dom.*, and
org.xml.* that existed in the<BR>> xerces jar. This is a problem in
webapps because it is against<BR>> the Sun classloader spec and the
servlet spec to load endorsed<BR>> packages from a child classloader
(ie... the WebappClassLoader).<BR>> XMLC beta1 was released with these
endorsed packages still<BR>> included in the xerces.jar file. I
decided that there was no<BR>> need for this and removed the endorsed
packages. This makes<BR>> XMLC's xerces libraries totally free of
any classloader issues.<BR>> As such, the xmlc-runtime jar file is able
to be added directly<BR>> into WEB-INF/lib which makes deploying
Barracuda an absolute<BR>> no-brainer now that there is no extra
copy-step (ie... copying<BR>> xerces.jar to
CATALINA_HOME/shared/lib).<BR>><BR>> Now, you may say "isn't this what
we were trying to get away from<BR>> before...an integrated jar file that
might collide with existing<BR>> jars"? Well, that used to be the
case, but now since the single<BR>> xmlc-runtime jar file no longer
contains libraries that would<BR>> conflict with anything else out there,
this is not an issue.<BR>> "But, now I have this big jar." "What if
I don't need wireless<BR>> and xhtml libraries"? Well, for one,
they are very small parts<BR>> of the xmlc-runtime jar file and secondly,
you can switch out the<BR>> xmlc-runtime for individual jars in the xmlc
distribution<BR>> (currently under XMLC's CVS with the tag<BR>>
"XMLC_2_2_POST_BETA_1_BARRACUDA_1_2_0").<BR>><BR>> I think the single
jar is simpler to deal with and causes less<BR>> confusion that using
individual jars.... especially the xerces<BR>> jar which isn't "really*
xerces for all intents and purposes.<BR>> This just caused needless
confusion. The fact is, xmlc's xerces<BR>> library is for xmlc's
internal use only.<BR>><BR>> One thing you need to make sure of is
that the JAXP, DOM, and SAX<BR>> libraries exist in the classpath.
This is usually provide by<BR>> Xerces and the xmlParserAPIs.jar or
xml-apis.jar that it comes<BR>> with. So, if you didn't have these
in ANT_HOME/lib and<BR>> CATALNIA_HOME/common/endorsed, you definitely
should now.<BR>><BR>> Hopefully that clears things up.<BR>><BR>>
Jake<BR>><BR>><BR>> At 03:53 PM 5/27/2003 -0600, you
wrote:<BR>><BR>> Hey Jake, it looks like there's been some
consolidation of jars in the<BR>> Barracuda WEB-INF/jars directory...can
you confirm that<BR>><BR>> /WEB-INF/jars/wireless-xmlc-2.2.jar<BR>>
/WEB-INF/jars/xalan-2.5.0.jar<BR>>
/WEB-INF/jars/xhtml-xmlc-2.2.jar<BR>><BR>> have all been collapsed
into<BR>><BR>> /WEB-INF/jars/xmlc-all-runtime-2.2.jar<BR>><BR>>
Thanks,<BR>> Christian<BR>>
----------------------------------------------<BR>> Christian Cryder
[christianc@atmreports.com]<BR>> Internet Architect,
ATMReports.com<BR>> Barracuda - <A href="http://barracudamvc.org/"
eudora="autourl">http://barracudamvc.org</A><BR>>
----------------------------------------------<BR>> "Coffee? I could quit
anytime, just not today"<BR>><BR>>
_______________________________________________<BR>> Barracuda mailing
list<BR>> Barracuda@barracudamvc.org<BR>> <A
href="http://barracudamvc.org/lists/listinfo/barracuda"
eudora="autourl">http://barracudamvc.org/lists/listinfo/barracuda</A><BR><BR>_______________________________________________<BR>Barracuda \
mailing list<BR>Barracuda@barracudamvc.org<BR><A
href="http://barracudamvc.org/lists/listinfo/barracuda"
eudora="autourl">http://barracudamvc.org/lists/listinfo/barracuda</A></FONT></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic