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 little.
This is why I thought useful re-factoring your sample using the sitemap... did you
need something else, or what ?
Regards,
---------------------------------------------
Luca Morandini
GIS Consultant
[EMAIL PROTECTED]
http://utenti.tripod.it/lmorandini/index.html
---------------------------------------------
> -----Original Message-----
> From: Robert Simmons [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, January 26, 2003 1:55 PM
> 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 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 to envision is my reader deploying this and shot of
> reproducing the build file or telling my users to unpack the cocoon war, I
> don't know what to do exactly. If there was one jar they could include, it
> would be perfect. I envision a user being able to download a jar file that
> has every one of the classes all jared into one cocoon-all.jar and then
> dropping it as one unit in their WEB-INF/lib directory but I'm not sure how
> to accomplish that. I would also need to know if the path to the cocoon
> properties file and the xconf files are hardcoded as I would like to file
> them away too. but now I'm talking about developing on cocoon and that's what
> I was trying to avoid. Sigh.
>
> -- Robert.
>
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
