I'm pretty sure the artifacts are not different, having done a 'compare' of the POMs in eclipse.

I don't know what an OSGi is, can you tell me how to check whether i have one?

Jeff Caldwell wrote:
Anyone else see this too?  I've tried both approaches and have the same results.

The only thing I can think is that there is not an OSGi running when we start jetty with "mvn jetty:run". Or perhaps the artifacts are actually different when running from command line as opposed to running via the eclipse plug-in for maven?

On Tue, Jul 15, 2008 at 09:25:56PM +0100, Ken Starks wrote:
It depends which way I do things, but I am still having
problems with 'Your first Cocoon 2.2 Application'
because the Java Bean doesn't work.

But while experimenting with the Eclipse plugin
'Maven Integration for Eclipse' as a way of
generating the block, I suddenly found that the
Java-Bean did work.

Can anyone explain this behaviour, in terms that a
non-java-speaker might understand?

+++++++++++++++++++++++++++++++++++++++++++++++++

Details:

Method One: (don't work)
++++++++++++++++++

a. In the shell,
--------------
mvn archetype:generate -DarchetypeCatalog=http://cocoon.apache.org

<snip the details, I chose an artifactId of myBlock1>

cd myBlock1
mvn eclipse:eclipse
mvn jetty:run

b. Browser
-----------
Going to http://localhost:8888/myBlock1/spring-bean,

 <spring>#message</spring>


Method two (do work!)
++++++++++=+++++

a. in Eclipse
------------
(with 'Maven integration for eclipse' plugin
from update site:-
http://m2eclipse.sonatype.org/update-dev/ )

Menubar --.New --> Maven --> Maven Project
--> NEXT

un-check 'Use default Workspace location'
browse to your usual 'GettingStartedApp' directory
--> Next

Nexus Indexer. select artifact Id:-
cocoon-22-archetype-block
--> Finish

<snip, to fill in details. this time I chose 'myBlock2 >


Cocoon then creates and compiles the block

b. In the shell,
--------------


cd myBlock2
mvn jetty:run

c. Browser
-----------
Going to http://localhost:8888/myBlock2/spring-bean,

 <spring>This is a message coming from a Spring bean.</spring>



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


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

Reply via email to