Re: extra bcel jar
Gianugo Rabellino wrote: Antonio Gallardo wrote: Well, at a very least everything is under the ASL and in sync now... wouldn't Gump be able to spot the problem if we miss a cycle? BTW, I think it's a very bad idea to capsulate so many projects in their jar. The current jar includes BCEL, CUP and jakarta-regex. Note that we are use jakarta-regex twice?! I agree. We must make a xalan without bcel and jakarta-regex. It can also be a source of problems too. Well, *they* (the Xalan guys) should, not we. they do, in fact. it's just a matter of running the right target on the ant build file. -- Stefano. smime.p7s Description: S/MIME Cryptographic Signature
Re: extra bcel jar
Vadim Gritsenko dijo: > Tim Larson wrote: > >>On Mon, Mar 29, 2004 at 02:25:24PM -0600, Antonio Gallardo wrote: >> >> >>>While seeing inside the jars I also saw some parts that are interesting >>>for us (now with the Cocoon hat on). For example all the DOM management. >>> I >>>saw the DOMHelpers classes everywhere doing the same over and over. I >>>think inside Cocoon we can put all the DOM code in just one place. >>> >>> >> >>And add a toString method, please :) I see it duplicated in many >>projects, so it is needed. >> >> > > How about moving such code to xml-commons? +1 :-D > PS Yet another toString(): > http://cvs.apache.org/viewcvs.cgi/xml-xindice/java/src/org/apache/xindice/xml/TextWriter.java?rev=1.17&view=auto Yep. :-D Best Regards, Antonio Gallardo
Re: extra bcel jar
Tim Larson wrote: On Mon, Mar 29, 2004 at 02:25:24PM -0600, Antonio Gallardo wrote: While seeing inside the jars I also saw some parts that are interesting for us (now with the Cocoon hat on). For example all the DOM management. I saw the DOMHelpers classes everywhere doing the same over and over. I think inside Cocoon we can put all the DOM code in just one place. And add a toString method, please :) I see it duplicated in many projects, so it is needed. How about moving such code to xml-commons? PS Yet another toString(): http://cvs.apache.org/viewcvs.cgi/xml-xindice/java/src/org/apache/xindice/xml/TextWriter.java?rev=1.17&view=auto Vadim
RE: extra bcel jar
The bug number is 28032. I added this list as the CC. Ralph -Original Message- From: Joerg Heinicke [mailto:[EMAIL PROTECTED] Sent: Monday, March 29, 2004 12:56 PM To: [EMAIL PROTECTED] Subject: Re: extra bcel jar On 29.03.2004 22:38, Ralph Goers wrote: > Sure. If you are doing it, can you please post the bug number or add [EMAIL PROTECTED] as CC? Thanks, Joerg
Re: extra bcel jar
On 29.03.2004 22:38, Ralph Goers wrote: Sure. If you are doing it, can you please post the bug number or add [EMAIL PROTECTED] as CC? Thanks, Joerg
RE: extra bcel jar
Sure. Ralph -Original Message- From: Antonio Gallardo [mailto:[EMAIL PROTECTED] Sent: Monday, March 29, 2004 12:38 PM To: [EMAIL PROTECTED] Subject: RE: extra bcel jar Ralph Goers dijo: > I would suggest that someone open a bugzilla report with them and get them > to create a version without the dependent jars. Good idea. Can you do that? Best Regards, Antonio Gallardo
RE: extra bcel jar
Ralph Goers dijo: > I would suggest that someone open a bugzilla report with them and get them > to create a version without the dependent jars. Good idea. Can you do that? Best Regards, Antonio Gallardo
Re: extra bcel jar
On Mon, Mar 29, 2004 at 02:25:24PM -0600, Antonio Gallardo wrote: > While seeing inside the jars I also saw some parts that are interesting > for us (now with the Cocoon hat on). For example all the DOM management. I > saw the DOMHelpers classes everywhere doing the same over and over. I > think inside Cocoon we can put all the DOM code in just one place. And add a toString method, please :) I see it duplicated in many projects, so it is needed. --Tim Larson
Re: extra bcel jar
Gianugo Rabellino dijo: > Antonio Gallardo wrote: Well, at a very least everything is under the ASL and in sync now... wouldn't Gump be able to spot the problem if we miss a cycle? >>> >>>BTW, I think it's a very bad idea to capsulate so many projects in their >>>jar. The current jar includes BCEL, CUP and jakarta-regex. Note that we >>>are use jakarta-regex twice?! >> >> >> I agree. We must make a xalan without bcel and jakarta-regex. It can >> also >> be a source of problems too. > > Well, *they* (the Xalan guys) should, not we. Agreed. I thought as part of the ASF community. :-D While seeing inside the jars I also saw some parts that are interesting for us (now with the Cocoon hat on). For example all the DOM management. I saw the DOMHelpers classes everywhere doing the same over and over. I think inside Cocoon we can put all the DOM code in just one place. Best Regards, Antonio Gallardo
RE: extra bcel jar
I had problems with Xalan and Weblogic Portal 8.1 quite a while ago. Xalan started including XSLTC in xalan.jar. XSLTC uses bcel and a couple other classes that are also used by Weblogic Portal's "Java Page Flow". When xalan.jar was put in java's lib/endorsed the portal would not start. Without it, the JDK 1.4 default version of xalan was used which would cause Cocoon to have problems. The Xalan team ended up creating two versions so that lib/endorsed could be safely overridden, but the XSLTC part is still a problem. I would suggest that someone open a bugzilla report with them and get them to create a version without the dependent jars. Ralph -Original Message- From: Gianugo Rabellino [mailto:[EMAIL PROTECTED] Sent: Monday, March 29, 2004 11:47 AM To: [EMAIL PROTECTED] Subject: Re: extra bcel jar Joerg Heinicke wrote: > On 29.03.2004 19:47, [EMAIL PROTECTED] wrote: > >> Remove the bcel classes from the xalan.jar and >> create an extra jar for those. > > > *Ouch*. If I understand this correctly we have to do it for every update > on the Xalan jar until our continuations stuff goes into bcel that goes > later on into Xalan jar? Hopefully we will never forget it! Well, at a very least everything is under the ASL and in sync now... wouldn't Gump be able to spot the problem if we miss a cycle? Ciao, -- Gianugo Rabellino Pro-netics s.r.l. - http://www.pro-netics.com Orixo, the XML business alliance - http://www.orixo.com (Blogging at: http://www.rabellino.it/blog/)
Re: extra bcel jar
Antonio Gallardo wrote: Well, at a very least everything is under the ASL and in sync now... wouldn't Gump be able to spot the problem if we miss a cycle? BTW, I think it's a very bad idea to capsulate so many projects in their jar. The current jar includes BCEL, CUP and jakarta-regex. Note that we are use jakarta-regex twice?! I agree. We must make a xalan without bcel and jakarta-regex. It can also be a source of problems too. Well, *they* (the Xalan guys) should, not we. Ciao, -- Gianugo Rabellino Pro-netics s.r.l. - http://www.pro-netics.com Orixo, the XML business alliance - http://www.orixo.com (Blogging at: http://www.rabellino.it/blog/)
Re: extra bcel jar
Stephan Michels dijo: > Am Mo, den 29.03.2004 schrieb Gianugo Rabellino um 21:46: >> Joerg Heinicke wrote: >> >> > On 29.03.2004 19:47, [EMAIL PROTECTED] wrote: >> > >> >> Remove the bcel classes from the xalan.jar and >> >> create an extra jar for those. >> > >> > >> > *Ouch*. If I understand this correctly we have to do it for every >> update >> > on the Xalan jar until our continuations stuff goes into bcel that >> goes >> > later on into Xalan jar? Hopefully we will never forget it! >> >> Well, at a very least everything is under the ASL and in sync now... >> wouldn't Gump be able to spot the problem if we miss a cycle? > > BTW, I think it's a very bad idea to capsulate so many projects in their > jar. The current jar includes BCEL, CUP and jakarta-regex. Note that we > are use jakarta-regex twice?! I agree. We must make a xalan without bcel and jakarta-regex. It can also be a source of problems too. Best Regards, Antonio Gallardo
Re: extra bcel jar
Am Mo, den 29.03.2004 schrieb Gianugo Rabellino um 21:46: > Joerg Heinicke wrote: > > > On 29.03.2004 19:47, [EMAIL PROTECTED] wrote: > > > >> Remove the bcel classes from the xalan.jar and > >> create an extra jar for those. > > > > > > *Ouch*. If I understand this correctly we have to do it for every update > > on the Xalan jar until our continuations stuff goes into bcel that goes > > later on into Xalan jar? Hopefully we will never forget it! > > Well, at a very least everything is under the ASL and in sync now... > wouldn't Gump be able to spot the problem if we miss a cycle? BTW, I think it's a very bad idea to capsulate so many projects in their jar. The current jar includes BCEL, CUP and jakarta-regex. Note that we are use jakarta-regex twice?! Stephan.
Re: extra bcel jar
Joerg Heinicke wrote: On 29.03.2004 19:47, [EMAIL PROTECTED] wrote: Remove the bcel classes from the xalan.jar and create an extra jar for those. *Ouch*. If I understand this correctly we have to do it for every update on the Xalan jar until our continuations stuff goes into bcel that goes later on into Xalan jar? Hopefully we will never forget it! Well, at a very least everything is under the ASL and in sync now... wouldn't Gump be able to spot the problem if we miss a cycle? Ciao, -- Gianugo Rabellino Pro-netics s.r.l. - http://www.pro-netics.com Orixo, the XML business alliance - http://www.orixo.com (Blogging at: http://www.rabellino.it/blog/)
extra bcel jar (was: cvs commit)
On 29.03.2004 19:47, [EMAIL PROTECTED] wrote: Remove the bcel classes from the xalan.jar and create an extra jar for those. *Ouch*. If I understand this correctly we have to do it for every update on the Xalan jar until our continuations stuff goes into bcel that goes later on into Xalan jar? Hopefully we will never forget it! Joerg
