RE: cocoon portability

[Geoff Howard]

Jetty now ships with 2.1, so it works there.  Cocoon is just a webapp, so if
you
mean portability to other containers, there should only be isolated issues.
If you
mean ripping your code out of cocoon, then Peter's advice is what you need.
Of course,
if you use helper classes with your xsp's you could also reuse some logic
there.

The other issue to consider is SAX.  A lot of your code is going to be
centered around
SAX.  At the moment, I'm not aware of many other SAX pipeline webapps
involving java.
And when I say many, it's only there to keep me from being called an idiot
if I say
"any".

Geoff

> -Original Message-
> From: Tellis George [mailto:[EMAIL PROTECTED]]
> Sent: Friday, January 31, 2003 11:30 AM
> To: [EMAIL PROTECTED]
> Subject: cocoon portability
>
>
> Hi,
>
> How easy is it to configure cocoon to work with other app servers such as
> weblogic, jetty, sun one etc...?
>
> Basically after I gave them a presentation, my management is keen
> on cocoon
> but they insist that I show them that there is a way to
> transition smoothly
> to  alternatives to tomcat if required.
>
> Also they want to know how much of the effort of setting up a
> cocoon can be
> reused if we decide not to go with cocoon. I suppose the business
> logic can
> be reused and possible the stylesheets but I am not sure.
>
> Any advise will be great !!
>
> Regards
> Tellis
>
>
>
>
> _
> It's fast, it's easy and it's free. Get MSN Messenger today!
> http://messenger.msn.co.uk
>
>
> -
> Please check that your question  has not already been answered in the
> FAQ before posting. 
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail:   <[EMAIL PROTECTED]>
>
>
>


-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

RE: cocoon portability

[Schaper, Christoph]

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

-Original Message-
From: Tellis George [mailto:[EMAIL PROTECTED]]
Sent: 31 January 2003 17:30
To: [EMAIL PROTECTED]
Subject: cocoon portability


Hi,

How easy is it to configure cocoon to work with other app servers such as 
weblogic, jetty, sun one etc...?

Basically after I gave them a presentation, my management is keen on cocoon 
but they insist that I show them that there is a way to transition smoothly 
to  alternatives to tomcat if required.

Also they want to know how much of the effort of setting up a cocoon can be 
reused if we decide not to go with cocoon. I suppose the business logic can 
be reused and possible the stylesheets but I am not sure.

Any advise will be great !!

Regards
Tellis




_
It's fast, it's easy and it's free. Get MSN Messenger today! 
http://messenger.msn.co.uk


-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Any e-mail message from the European Central Bank (ECB) is sent in good faith but 
shall neither be binding nor construed as constituting a commitment by the ECB except 
where provided for in a written agreement.
This e-mail is intended only for the use of the recipient(s) named above. Any 
unauthorised disclosure, use or dissemination, either in whole or in part, is 
prohibited.
If you have received this e-mail in error, please notify the sender immediately via 
e-mail and delete this e-mail from your system.


-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

RE: cocoon portability

[Hunsberger, Peter]

> Also they want to know how much of the effort of setting up a cocoon can
be 
> reused if we decide not to go with cocoon. I suppose the business logic
can 
> be reused and possible the stylesheets but I am not sure.

If you stay away from XSP then much of what you do can be reused.  If you're
careful all your XSLT are portable.  Similarly, Cocoon is a big servlet: if
you're careful (extend a common base class that of your own) actions and
generators can be maybe 80% reusable, though you'll have to write a lot of
code to move them anywhere:  Basically, you'd have to implement your own
servlet that probably made hard coded assumptions about resource names. It
would call your generators to pass the output on to an XML transform.  From
there you'd call your actions, again with a bunch of stuff hard coded. I
can't imagine actually wanting to ever do this, but much of our code has
been written with this possibility in mind.  Now that Cocoon is more
accepted here this requirement may go away for us in the future :-)


-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>