We successfully deployed cocoon 2.0.4 on WebLogic7.0SP1 as a war file.
With a previous version of either WL or cocoon it does not seem to work.
Christoph
-Original Message-
From: Xiaonan Zheng [mailto:[EMAIL PROTECTED]]
Sent: 15 January 2003 15:49
To: [EMAIL PROTECTED]
Subject: deploy
About the app servers.
Have experience with two different ones:
1) JBoss: No problem, runs out of the box.
2) Weblogic: Quite straightforward in general (it becomes a lot easier if
you deploy exploded), but there are some issues with some specific
features (eg the JSPGenerator)
Christoph
Hi, we have the problem as well.
Unfortunatly, the request dispatcher way does not work either, even if we
try to customise it specifically for Weblogic Request dispatcher (the
customisation is needed, as the WL request dispatcher requires WL specific
wrapper classes, but due to the great avalon
Tried that as well to workaround the problem with weblogic jsp engine .
however, that way does not seem to be straightforward either. There seem to
be conflicts between the weblogic internal classloader and jasper
(classloader exceptions when trying to use jasper as jsp engine). Have not
Or write a custom generator. We have a custom writer transforming certain
JAVA classes to SAX events and use it in a generator
like
myJAVA = getSomehowTheJAVA();
contentHandler.startDocument();
XMLSaxWriter writer;
// generate the actual xml
writer = new XMLSaxWriter(contentHandler);
You can configure the NullLogger (see in avalon framework), if this is what
you want to do.
-Original Message-
From: Uwe Gerger [mailto:[EMAIL PROTECTED]
Sent: 26 February 2003 14:01
To: [EMAIL PROTECTED]
Subject: Cocoon2: Logger required?
Hello,
can I configure Cocoon2 so that it
You can try two things to rule out problems which existed with wl6.1 (I
don't know whether they were actually solved in SP3):
- try deploy exploded (i.e. unjar the cocoon war before placing it in the
applications dir)
- rename all libraries in cocoon lib directory to contain not more than one
.
Girish
Schaper, Christoph wrote:
You can try two things to rule out problems which existed with wl6.1 (I
don't know whether they were actually solved in SP3):
- try deploy exploded (i.e. unjar the cocoon war before placing it in the
applications dir)
- rename all libraries in cocoon lib directory
This is a known problem with cocoon and WL 7. We did quite a lot of research
to get JSPs working with Cocoon and WL7 (as well with the help of BEA
support), finally with no succes. You can not used the jasper JSP engine
(classcastexceptions from the WL class loader), and you cannot use the WL
one
Use xerces, its supports full w3c schema
-Original Message-
From: Bruno Dumon [mailto:[EMAIL PROTECTED]
Sent: 02 April 2003 13:32
To: [EMAIL PROTECTED]
Subject: Re: SAX Validation
On Wed, 2003-04-02 at 13:17, [EMAIL PROTECTED] wrote:
Hello all,
Does anybody know if its possible in
Just guessing: You are on Unix and you don't have the display variable set
when you run cocoon?
If this is the case, either point the display variable to your X environment
or, if you don't have one search in the cocoon docu for headless.
Christoph
-Original Message-
From: Irving
We got a very similar looking problem with a different jdk and different app
server (but as well cocoon 2.0.4). Difference was that the exception was not
in endElement but in comment.
We never really traced it down.
I happended only on one certain page, and after we restructured it a bit the
12 matches
Mail list logo
