Actually, my below theory regarding the contribute's was incorrect - it
seems to be some kind of race condition with my service bindings.
If I do not eagerLoad any the services in my component library, LCR
works fine.
If I eagerLoad one of my component library services LCR intermittently
doe
After a couple of weeks working with eclipse+tomcat+live class reloading
working just fine I've managed to break it all.
I just included a JAR which is a component library I have written (with
its own Module). I used the guide
(http://tapestry.apache.org/component-libraries.html) to configure
kalle, one other tip for your document which was a bit of a gotcha today
(when adding a 2nd project):
Make sure 'Automatically compute' is checked on the 'Source path' page
of window>preferences>tomcat section.
This tip could go between point 6.3 and 6.4.
On 7/01/2012 3:24 PM, Kalle Korhonen
On Fri, Dec 23, 2011 at 1:23 PM, Paul Stanton wrote:
> That document is great, much better than what I could find last time around.
> The only step which I had to go searching elsewhere to solve was finding
> where the "DevLoader" was!
> I figured out (google) that the devloader package is actuall
Kalle,
I've figured out that it was the tapestry-test etc adding jetty etc to
my classpath.
After looking into it, I have a simple way to make sure your 'devLoader'
classpath is correct:
Method 1 - compare to target/[project]/WEB-INF/lib after a maven install
1. run maven install
2. browse
I think I may have one outstanding issue with this configuration
regarding classloaders...
ComponentResources cr = container.getComponentResources();
Component comp = cr.getEmbeddedComponent(zoneClientId);
log.debug(Zone.class.getName() + " == " +
comp.getClass().getName
I solved the problem ..
it seems my changes to the 'tomcat' settings for the project were not
persisting or changing the ".tomcatplugin" file which was still
referencing the old maven dependencies...
after simplifying the pom, deleting ".tomcatplugin" and re-applying the
settings in the "tom
Thanks Kalle,
That document is great, much better than what I could find last time around.
The only step which I had to go searching elsewhere to solve was finding
where the "DevLoader" was!
"7. Install devloader for Tomcat (for Tomcat 7.x use devloader from
version 3.3). Unzip and copy the
ading, it is a big convenience for
tapestry+openejb+tomcat+eclipse projects !
Nourredine.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/development-with-eclipse-tomcat-tp5096541p5096781.html
Sent from the Tapestry - User mailing list archive at Nabbl
On Thu, Dec 22, 2011 at 11:51 PM, Paul Stanton wrote:
> For productivity, live class reloading, the ability to step through code and
> being able to start and stop the container are all required.
> We ended up compiling into "webapp/WEB-INF/classes" and copying all
> dependencies into "webapp/WEB-
2011-12-23 08:51, Paul Stanton:
> Its been over 2 years since I started a new production tapestry
> application, and once again in the same server environment we need to do
> our development & testing in the environment familiar with the team: ie
> tomcat.
>
> For productivity, live class reloadin
Its been over 2 years since I started a new production tapestry
application, and once again in the same server environment we need to do
our development & testing in the environment familiar with the team: ie
tomcat.
For productivity, live class reloading, the ability to step through code
and
12 matches
Mail list logo
