cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Fagerstrom <dani...@nada.kth.se>
Subject Re: [2.2] Debugging and inplace editing
Date Thu, 14 Dec 2006 11:52:31 GMT
Philipp Zerelles skrev:
> Daniel Fagerstrom wrote:
>   
>> If you use the trunk in Eclipse with the Eclipse-Jetty plugin, it 
>> already works in the way you ask for. To make it work you need to ensure 
>> that the main webapp has a project dependency on the my-block in Eclipse 
>> (e.g. by running mvn eclipse:eclipse from a top level pom). If it has 
>> Eclipse will have put the contents of my-block/src/main/resources/ on 
>> the classpath used in the main webapp. And the deployer part of Cocoon 
>> that is executed during startup will read the COB-INFs directly from 
>> classpath in the case where there is a file protocol at the classpath. 
>> Only jars are unpacked.
>>
>> See http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=116326232408386&w=2

>> for details about the implementation.
>>     
>
> What Eclipse-Jetty plugin do you use? I tried the jetty-launcher plugin, but it does
not support Jetty 6.
> Do you use Jetty 5.1 then?
>   
Yes, I use the jetty-launcher plugin with Jetty 5.1. Jetty 5.1 supports 
Servlet 1.4 which is the same as Cocoon 2.2 supports, so Jetty 5.1 is 
enough for testing purposes.

/Daniel


Mime
View raw message