Is there a way to compress all the cocoon jars into
one jar so I can just drop in my application server like a golf ball and all
cocoon deployments will have access to it ?
-- Robert
Robert,
I'm not sure I've understood your question, but I like to give it a try.
When you build Cocoon, it produces a WAR file, you just:
1) put the WAR under the webapps of your servlet container
2) re-start the container
The you can deploy your Cocoon app under the mount directory, hence
Robert Simmons wrote:
Having Hello-World up in 12 hours is not exactly a steep request.
I'm a cocoon developer and committer. I think I know what I'm saying.
Base Cocoon is not difficult. But given the current documentation and
examples, even only understanding what a base Cocoon usage is...
Ya I know that. I'm not talking about the prebuilt, distributed web
application. I am trying to develop a strategy for other users to be able to
use cocoon from within JBoss without having to leap through 15 hoops. So I
basically want a way I can build cocoon libs and then in each war file I make
Robert,
well, if I were you I'd tweak the build.xml to tailor it to your needs, and just tell
the readers to:
1) replace the native build.xml with yours
2) run it
3) deploy the resulting WAR.
I have no idea of alternative approaches... sorry :(
Regards,
Robert,
I've taken a look at your code and I'm tinkering with the idea of re-write it using
Cocoon... could you be of assistance today ?
BTW, there is any other poster who'd like to replicate this example in Cocoon ?
Regards,
-
Luca
Hi,
Just to go more deeply into Cocoon's comprehension, I've yesterday built a
little example with the load of two differents stylesheets
(participantsFR.xsl and participantsEN.xsl) depending of the value of a
parameter passed in HTTP Request, and with the help of this mailing-list,
I've achieved
Hmm one question though. This huge manifest attribute called
Cocoon-Libs. Where is it used in the application? Can I leave it out ?
- Original Message -
From: Luca Morandini [EMAIL PROTECTED]
To: Cocoon-users [EMAIL PROTECTED]
Sent: Sunday, January 26, 2003 10:45 AM
Subject: RE:
Hmm well that is what im getting to .. im pretty much on today tinkering with
cocoon trying to get a build that will be a bit more deployable to the newb.
What i want is for readers of my book (which Im writing on SERVER side issues
(as in EJB) to be able to download everything and run the sucker.
Ok I yanked the manifest file from WEB-INF and it all still seems to work,
though I don't know about in the full cocoon deployment. Is there any JUnit
built into this sucker?
-- Robert
- Original Message -
From: Robert Simmons [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
-Original Message-
From: Robert Simmons [mailto:[EMAIL PROTECTED]]
Sent: Sunday, January 26, 2003 1:23 PM
To: [EMAIL PROTECTED]
Subject: Re: Single JAR with all the libs?
Ok I yanked the manifest file from WEB-INF and it all still seems to work,
though I don't know about in the
Robert,
I've developed a tentative Cocoon implemtation of your sample.
1) I've defined a suitable selector in order to switch to different contents according
to its value:
map:selector name=command-selector
src=org.apache.cocoon.selection.RequestParameterSelector
If i understand you correct, you simply want to avoid deploying
several cocoon-based webapps all containing tons of the same
jar files ?
And in order to keep your customers happy, you want to simplify
the deployment by bundling all cocoon jars into one big jar,
deploying this golfball.jar
I do all my database work in the EJBs on the server side using JDO. JDO is
basically god for persisting Java objects. =)
I can probably figure out how to connect the suckers. In fact if I'm not too
far off I can drop them in the container and just grab an initial context.
However what I'm trying
Robert,
I think I misunderstood you.
Did you want the same approach (servlets + EJB + XSL) to work In Cocoon ? It could be
done, it's only a configuration problem... but
what's the point ?
I mean, if you want to show how Cocoon could help developing apps you should go the
Cocoon way a
dont forget that this is jsut a very small part of the application and a
refactoring usign the sitemap is a good thing. But yes, the data will be
retrieved from EJBs as that is my specialty and what has proven to be ubver
powerful in the server side. Client side I think cocooncould lay all others
-Original Message-
From: Robert Simmons [mailto:[EMAIL PROTECTED]]
Sent: Sunday, January 26, 2003 2:35 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Smileys Cocoon sample... the sequel
dont forget that this is jsut a very small part of the application and a
refactoring
hi johannes,
I think you should be matching the request parameter(s) via the respective
matcher, i.e. RequestParameterMatcher. the default (WildcardURI) matcher
most probably only matches on the URI.
so (from the top of my head) it would be something like:
!--php try--
map:pipeline
map:match
Ahh, perhaps I'm not making myself clear. Enterprise programmers have a sort
of different view of server and client side. To us, anything requesting
services of an EJB that isn't an EJB itself is a client. My vision is the
following
EJBs implementing complex logic in a distributed manner. These
-Original Message-
From: Robert Simmons [mailto:[EMAIL PROTECTED]]
Sent: Sunday, January 26, 2003 7:55 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Smileys Cocoon sample... the sequel
I do all my database work in the EJBs on the server side using JDO. JDO is
basically
Actually there is another option. Package all of the jars into a jar so that
the contents of that jar are all of the files. Then alter the manifest of the
containing jar (cocoon-all.jar) and add a Class-Path attribute with the names
of each of the sub jars. Now putting the cocoon-all.jar in the
Incidentally you should probably index that jar since it will have lots of
classes and make the classloader throw fits trying to find things.
Performance wise its best to index.
- Original Message -
From: Robert Simmons [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL
What is this file for and can it be omitted from
the package? If it cant be omitted is it something that the user should be
editing?
-- Robert
Given the recent discussion about the difficulty
getting into cocoon, I am wondering if we should start an initiative to make a
maintenance release for cocoon that would have a focus on usability for new
users. The following is a list of features I propose for this release.
1) A binary
Attached is an incomplete attempt at building the jar. I don't have time to
figure out how to convert the fileset into the space delimited list of files
needed for the classpath attribute.
-- Robert
- Original Message -
From: Robert Simmons [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent:
One other feature would be more extensive
documentation in the API. To see what I mean, look at the class level
documentation on LinkSerializer. Hrmm ... I still don't know what it does.
Perhaps its time to bust people's chops to document things.
What I meant about the component
Greetings,
Is there a uri for a sitemap schema that users can
use to validate the sitemap during development ? If so, Id like to have it.
TIA
-- Robert
On Saturday 25 January 2003 21:05, Jeff Turner wrote:
On Sat, Jan 25, 2003 at 06:22:10PM +0800, Niclas Hedhman wrote:
In fact, I think Cocoon is so powerful, that it has kind of grown out of
its servlet image. It should traverse to the next level (or two), and
has its own deployment system.
On Saturday 25 January 2003 21:05, Jeff Turner wrote:
On Sat, Jan 25, 2003 at 06:22:10PM +0800, Niclas Hedhman wrote:
In fact, I think Cocoon is so powerful, that it has kind of
grown out of
its servlet image. It should traverse to the next level (or
two), and
has its own deployment
First of all, I generally agree with you Robert.
1. Cocoon is overly daunting at first sight.
2. MS get you going much faster.
3. Separation between User and Developer must be stronger.
4. Point-Click deployment tools should become a priority.
There are a few things I don't agree with;
1. I
In light of this ginormous thread, do we need more newbie guides to
getting started with Cocoon? Obviously the CTWIG or whatever is out of
date, so perhaps there's a demand for something like a Busy Developer's
Guide to getting started with Cocoon? I'd be more that willing to write
stuff up that
Hi Carsten,
Hope you could spare some time to explain on the solution 2 you have
suggested...
Thanks again
- Original Message -
From: Richard Reyes [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, January 24,
Hy;
I want to use the RequestParam action to pass a parameter into
an aggregation. In parallel the parts of the agregation shall
be assembled from the match parameters {1} {2} ...
My original sitemap leads to an Resource not found error:
snip .../
map:actions
map:action name=request
stop-lurking
Hussayn is absolutely right here - there is a huge case that has
built
up over the last year for givinga "newbie-friendly" face to
Cocoon.
We can go on for hours (and have, before) about power and
scalability and performance and XSLT issues etc etc etc BUT
all of those things
We might consider smacking the developers around to start commenting
things. Pretend you are writing generator for the first time and you are looking
at the API documentation for documentation on what the parameters are to the
AbstractGenerator.setup() method. After you are done looking at
Dear listmembers,
maybe its answer is easy but I couldn't find an answer in the archieves.
I need to dynamically set the transformer source based on a parameter set
inside the Generator.
Thats what my matcher should look like:
map:match=articleid_*
Imho, yeah the CTWIG is helpful as a starting point for a
newbie. The other tutorial that I thought that was helpful was
from the www.cocooncenter.de topic auto-mount, except that it
needs a litle change instead of WildcardURIMatcherFactory it
should use WildcardURIMatcher on the sitemap.xmap.
37 matches
Mail list logo
