scaffolding not working as expected

[solid]

I have resorted to using the jetty server adapter for eclipse-wtp. It is working. It should be noted that I am using the vanillla tomcat 6.0.20 from apache to produce the errors listed. It appears to be something related to the roo namespace declaration in the main template. I don't know why that would not be working but it is definitely reproducable with tomcat in eclipse.
Stefan/Ben is there anything I can send you to help you see what I am seeing?

[Stefan Schmidt]

Sorry you have so much trouble with Tomcat in your application. I have just tried it again twice (once on Mac OSX and once in a brand-new Ubuntu 9.10 VM) and both worked just fine. I used Sun JDK 1.6.

Also I am not aware of other users facing this problem, so I have to assume that the problem is related to your environment. Can you please let me know which Java and OS you are running? Also does this happen with all the sample scripts that Roo ships (clinic.roo, wedding.roo and vote.roo). If you just run the script in a new directory, and then run 'mvn tomcat:run' (no eclipse) - does it still fail?

Cheers,
Stefan

[solid]

no worries. Pioneers take the arrows, right? I'm just glad you are working through it with me.
I started tomcat at 17:32 EST
It is now 17:38 and tomcat is still not up. here is what is output at the console:

alter table visit add constraint FK6B04D4B6B108014 foreign key (pet) references pet
alter table visit add constraint FK6B04D4B6B10AD20 foreign key (vet) references abstract_person
schema export complete
Checking 0 named HQL queries
Checking 0 named SQL queries
Finished creating instance of bean 'entityManagerFactory'
Invoking afterPropertiesSet() on bean with name 'transactionManager'
Finished creating instance of bean 'transactionManager'
Creating shared instance of singleton bean 'org.springframework.transaction.config.internalTr ansactionAspect'
Creating instance of bean 'org.springframework.transaction.config.internalTr ansactionAspect'
Eagerly caching bean 'org.springframework.transaction.config.internalTr ansactionAspect' to allow for resolving potential
circular references
Invoking afterPropertiesSet() on bean with name 'org.springframework.transaction.config.internalTr ansactionAspect'
Finished creating instance of bean 'org.springframework.transaction.config.internalTr ansactionAspect'
Returning cached instance of singleton bean 'entityManagerFactory'
Published root WebApplicationContext as ServletContext attribute with name [org.springframework.web.context.WebApplicati
onContext.ROOT]
Root WebApplicationContext: initialization completed in 5703 ms
Initializing filter 'Spring OpenEntityManagerInViewFilter'
Filter 'Spring OpenEntityManagerInViewFilter' configured successfully
Initializing filter 'CharacterEncodingFilter'
Filter 'CharacterEncodingFilter' configured successfully
Initializing filter 'etagFilter'
Filter 'etagFilter' configured successfully
Initializing filter 'httpMethodFilter'
Filter 'httpMethodFilter' configured successfully
[INFO] org.tuckey.web.filters.urlrewrite.UrlRewriteFilter INFO: loaded (conf ok)
[INFO] Initializing Coyote HTTP/1.1 on http-8080
[INFO] Starting Coyote HTTP/1.1 on http-8080

[solid]

btw I am I used the clinic.roo script.

[solid]

java: java version "1.6.0_13"
Java(TM) SE Runtime Environment (build 1.6.0_13-b03)
Java HotSpot(TM) Client VM (build 11.3-b02, mixed mode, sharing)

OS: Win XP SP2 (but I have also experienced the same behavior on gentoo.)

[Stefan Schmidt]

I really have a hard time reproducing this. Can you do me a favor and package the project up in a war file and deploy that manually to a normal tomcat installation?

So you would run:

rm -rf * .*;roo script clinic.roo;mvn package;cp target/petclinic-0.1.0-SNAPSHOT.war /path/to/tomcat/webapps/petclinic.war

Cheers,
Stefan

[superkley]

hi,

recently i had the similar phenomenon on a friend's machine. the quick fix was to copy the tagx files to the target\classes\WEB-INF\tags folder. Try it. I have not analyzed this problem deeper. Something strange happens here.

Kley

[solid]

Today I discovered the problem (kindof). When tomcat is configured to "Serve modules without publishing" in eclipse, the tagx files cannot be found for some reason. I'm not sure why this is but when I unclick the serve without publishing option, suddenly all the tagx files begin working again. I'm not sure what the source of this is but at lease I know how to get the tag files working again.