[2.1.9] Upgrade: Handling of *.xroles files?

["Hochsteger Andreas (OI&T V)" <an...@oeamtc.at>]

Hi,

we are in the process of upgrading from Cocoon 2.1.7 directly to version
2.1.9.

I noticed some changes concerning resources which are now located inside JAR
files and not in the filesystem anymore.
It seems that the file cocoon.roles is now contained within the file
cocoon-2.1.9.jar.
What's the intended procedure now (concerning the build system) to make
custom components available to Cocoon - assuming the cocoon-2.1.9.jar file
should not be modified?

BTW, I used the description from
http://wiki.apache.org/cocoon/YourCocoonBasedProjectAnt16 to setup the build
system.

Thanks,

Andreas

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

general problem: xsp-generate v.s. transformations

[Christoph May <cm...@web.de>]

Hello Dear Experts,

I am using cocoon for some time now. And i run quite predictably into 
the always same problem:

IF i decide to use a map:generate(in the sitemap) with type="serverpages",
everything is well, execept one crucial thing: almost all processing has 
to happen using xsp,esql,xsp-input,... (which is very comfortable)
in this one and only first transformation (i.e.: generation). This way 
the separation of logic and appearance is very difficult to maintain.

If i decide to use map:generate with type="file" and session-,sql- and 
(if necessary) multiple xslt-transformations,
the separation of logic and design comes nearly for free and everything 
is quite easily readable. But now some logic-concerns
are very difficult to accomplish, which makes the code  difficult to 
read again.

And the biggest problem in this context: it is very time-consuming to 
switch between  both approaches.

To have a "serverpages"-transformation would solve the problem, but i 
had to find out, that this is the only generation
that does not come as a transformation. And to use xinclude as a trick 
to navigate around this, make the files very difficult to read.

My question now: Did i understand something wrong? Is there a third way? 
How can i maintain the separation of logic and appearance
with logic only really available  in the generation-step?

   Christoph May


Diese Mail wurde von DPAG IT-Service auf Viren untersucht.
Aus Rechts- und Sicherheitsgruenden ist die in dieser E-Mail gegebene
Information nicht rechtsverbindlich. Eine rechtsverbindliche Bestaetigung
reichen wir Ihnen gerne auf Anforderung in schriftlicher Form nach. Beachten
Sie bitte, dass jede Form der unautorisierten Nutzung, Veroeffentlichung,
Vervielfaeltigung oder Weitergabe des Inhalts dieser E-Mail 
nicht gestattet ist.Diese Nachricht ist ausschliesslich fuer den
bezeichneten Adressaten oder dessen Vertreter bestimmt. Sollten Sie nicht
der vorgesehene Adressat dieser E-Mail oder dessen Vertreter sein, so bitten
wir Sie, sich mit dem Absender der E-Mail in Verbindung zu setzen. 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org