On Thursday, July 18, 2002, at 08:07 am, Carsten Ziegeler wrote:
> Torsten Curdt wrote:
>
>> This is what I found out:
>>
>> cocoon2 HEAD seems to work out-of-the-box with xerces 2.0.2 for:
>>
>> resin 2.1.2, jdk 1.3.1_02, linux
>> tomcat 4.1.7b2, jdk
Torsten Curdt wrote:
> This is what I found out:
>
> cocoon2 HEAD seems to work out-of-the-box with xerces 2.0.2 for:
>
> resin 2.1.2, jdk 1.3.1_02, linux
> tomcat 4.1.7b2, jdk 1.3.1_02, linux
> resin 2.1.2, jdk 1.3.1, win2k
>
> but fails on
>
> tomcat 4.0.4b2, j
This is what I found out:
cocoon2 HEAD seems to work out-of-the-box with xerces 2.0.2 for:
resin 2.1.2, jdk 1.3.1_02, linux
tomcat 4.1.7b2, jdk 1.3.1_02, linux
resin 2.1.2, jdk 1.3.1, win2k
but fails on
tomcat 4.0.4b2, jdk 1.3.1_02, linux
tomcat 4.0.4, jdk 1.3.1_02, linux
with
> On Saturday 13 July 2002 18:19, Joerg Heinicke wrote:
> > I added xerces-2.0.2.jar to the xml-cocoon2\lib\core\ and changed the
> > jars.xml. (The same for Xalan, FOP and Lucene.) Subsequently I built th
> e
> > webapp and had no problem. I tested Xalan, Xerces and
>
>
>> Or maybe in this case its no big deal.
>>
>>
>
>at least that's what I hoped...
>
>I don't have a strong opinion upgrading the 2.0.x tree either because we are
>using HEAD but I thought when we ship a new stable release we should also
>ship the latest stable releases we can find. So f
> >just for hsqldb specifically?
>
> Dunno about the rest. I speak about what I know something about.
> HSQLDB is not really suitable for
> a production system (very slow) so its mostly used in Cocoon for
> development and for the examples. 2.1 is
> the development edition of cocoon. Because t
Torsten Curdt wrote:
>On Sunday 14 July 2002 15:45, Andrew C. Oliver wrote:
>
>
[ ] hsqldb 1.61 -> 1.70RC6j
+0, I want to wait for final release.
>>>+0
>>>
>>>
>>But as I said earlier, it would be fine/make sense to do this in the 2.1
>>branch I think.
>>
On Sunday 14 July 2002 15:45, Andrew C. Oliver wrote:
> >>[ ] hsqldb 1.61 -> 1.70RC6j
> >>
> >>+0, I want to wait for final release.
> >
> >+0
>
> But as I said earlier, it would be fine/make sense to do this in the 2.1
> branch I think.
just for hsqldb specifically?
--
Torsten
-
>
>
>>>
>>>
>>[ ] hsqldb 1.61 -> 1.70RC6j
>>
>>+0, I want to wait for final release.
>>
>>
>
>+0
>
But as I said earlier, it would be fine/make sense to do this in the 2.1
branch I think.
>
>-
>To unsubscribe, e-mail:
f it works.
if some people can confirm it works +0.5
> > [ ] xerces 2.0.0-> xerces 2.0.2
>
> +0, don't know.
+1, finally the AttributesImpl got fixed
> > [ ] batik-all 1.5b2 -> batik 1.5b3
>
> +1, provided all samples still work.
+0
> > any
On Saturday 13 July 2002 18:19, Joerg Heinicke wrote:
> I added xerces-2.0.2.jar to the xml-cocoon2\lib\core\ and changed the
> jars.xml. (The same for Xalan, FOP and Lucene.) Subsequently I built the
> webapp and had no problem. I tested Xalan, Xerces and FOP. We use
> current Lucene
On Saturday 13 July 2002 16:18, Joerg Heinicke wrote:
> I built my own version using Xerces 2.0.2 and had no problems.
...for it worked with resin - but not with tomcat
--
Torsten
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
On Saturday 13 July 2002 16:11, John Morrison wrote:
> I can get it to work with TC 4.0.4-b3, need to replace the version
> of xerces in common/lib with the newer one. Downloading 4.0.4 as I
> type. I'll try it in there too. The only other TC I know about is
> 4.1.7-beta.
hm... replace the tom
no code change)
+1, should not contain significant differences.
> [ ] fop 0.20.3 -> fop 0.20.4(sight change for logging)
+0.5, why not if it works.
> [ ] xerces 2.0.0-> xerces 2.0.2
+0, don't know.
> [ ] batik-
://localhost:8080/cocoon/search/welcome?
Yep :) Never tried it before :)
So, what should be put in the release...
[ ] lucene 1.2-rc2 -> lucene 1.2(no code change)
[ ] fop 0.20.3 -> fop 0.20.4(sight change for logging)
> From: John Morrison [mailto:[EMAIL PROTECTED]]
>
> > From: Joerg Heinicke [mailto:[EMAIL PROTECTED]]
> >
> > I built my own version using Xerces 2.0.2 and had no problems.
>
> Did you need to move/copy into the servlet engine or did you manage
> to mak
I added xerces-2.0.2.jar to the xml-cocoon2\lib\core\ and changed the
jars.xml. (The same for Xalan, FOP and Lucene.) Subsequently I built the
webapp and had no problem. I tested Xalan, Xerces and FOP. We use
current Lucene since a few weeks within a project (with Cocoon 2.0.1).
Joerg
John
> From: Joerg Heinicke [mailto:[EMAIL PROTECTED]]
>
> I built my own version using Xerces 2.0.2 and had no problems.
Did you need to move/copy into the servlet engine or did you manage
to make it run solely within the webapp?
> What about the current release versions of Lucene
I built my own version using Xerces 2.0.2 and had no problems.
What about the current release versions of Lucene 1.2 and Fop 0.20.4?
Joerg
Torsten Curdt wrote:
> Shouldn't we ship with the latest xerces release?
>
> I was desperatly trying to upgrade everything correctly to h
#x27;t we ship with the latest xerces release?
>
> I was desperatly trying to upgrade everything correctly to have
> it shipped
> with the upcoming release but failed. Couldn't figure out what's
> wrong (see
> thread xerces 2.0.2)
>
> Anyone else a try?
&g
Shouldn't we ship with the latest xerces release?
I was desperatly trying to upgrade everything correctly to have it shipped
with the upcoming release but failed. Couldn't figure out what's wrong (see
thread xerces 2.0.2)
Anyone else a try?
I also asked dims who did it last
> It turns out that resin 2.1.0 does just fine with the same .war file on the
> same machine :-/
>
> I'll try a another machine tomorrow...
...it seem to work only with resin (tried a different machine) :-/
Can anyone please confirm the following procedure to update to lastest
xerces-xalan-xm
> > I am a bit stumped... anyone an idea? I don't know where to start
> > debugging actually...
>
> Look at
> org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1126)
>
> } finally {
> if (ctxMap != null) ctxMap.clear();
> try{
>
Torsten Curdt wrote:
> I was trying to upgrade HEAD to xerces 2.0.2 but I am getting a very strange
> error :-/ (with catalina 4.0.4-b2-01)
>
> Cocoon servlet threw an Exception while trying to close stream.
> java.io.IOException: Cannot find message asso
I was trying to upgrade HEAD to xerces 2.0.2 but I am getting a very strange
error :-/ (with catalina 4.0.4-b2-01)
Cocoon servlet threw an Exception while trying to close stream.
java.io.IOException: Cannot find message associated with key
'responseStream.suspended'
On Tuesday 02 July 2002 17:05, Torsten Curdt wrote:
> ...any reasons out there not to upgrade (at least HEAD) to xerces 2.0.2?
> Earlier version have an ugly bug in the AttributesImpl...
>
> If there are no objections I'll commit the xerces 2.0.2 release version..
since noon
> From: Torsten Curdt [mailto:[EMAIL PROTECTED]]
>
> ...any reasons out there not to upgrade (at least HEAD) to xerces
2.0.2?
> Earlier version have an ugly bug in the AttributesImpl...
>
> If there are no objections I'll commit the xerces 2.0.2 release
version..
Go
...any reasons out there not to upgrade (at least HEAD) to xerces 2.0.2?
Earlier version have an ugly bug in the AttributesImpl...
If there are no objections I'll commit the xerces 2.0.2 release version..
--
Torsten
---
28 matches
Mail list logo
