on 7/2/01 11:30 AM, "Berin Loritsch" <[EMAIL PROTECTED]> wrote:
> Or the other way around. In the beginning, I will persue the path of least
> resistance. If it is easier to embed Turbine, I will go that route. If it
> is easier to embed Cocoon, then you get the idea. I need to wrap my head
> around the way Turbine works, so that will take me a few days.
Berin,
I think that you will find that merging the two together will be difficult
because both of them attempt to control the URI space.
If you take a few steps back and try to realize what Cocoon is actually
doing along side with what Turbine is actually doing, you will see that
Cocoon will play nicely with Turbine as the "View" portion of Turbine.
I just saw your other posting come by stating that you would like to use the
Services. In that case, you don't need anything more than to use the
TurbineConfig object to initialize Turbine with the right
TurbineResources.properties file and then go from there by using the
Services directly within your other code.
Thanks,
-jon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
