akochnev wrote:
> 
> Shymon,
>    I'm not sure what the solution to your problem is going to be. The
> reason
> why things worked in the original setup is that when you specify
> archiveClasses to false, when the app is deployed in Glassfish, it's
> deployed as an exploded war; thus, when you update the class files, T5 is
> able to automatically reload them.
> 
>    Now, when you add your library in a module, it doesn't make much sense
> to
> have it not be in a jar (hence, there is no "archiveClasses" option for
> that). T5 doesn't does not do live reloading of the contents of the jar
> file, and because java caches the index of the jar file, when you
> redeploy,
> you get the exception.
> 

Thanks for explanation.


akochnev wrote:
> 
>    Do you really have to restart tomcat or can you get away w/ just
> redeploying the app to Tomcat ?
> 

I use netbeans and for maven projects I don't have Deploy/Redeploy option. I
only have Run option
which, as I suppose, does deployment. So repeating Run option doesn't change
anything - every attempt throws exception. Even Clean and Build option
doesn't help, only Tomcat restart does.


akochnev wrote:
> 
>    Maybe one of the more experienced folks on the list can chime in on how
> best to handle the development workflow with a module that's still under
> development.
> 

Would be nice. For now I moved all components to main app ...components
package :(
But it is not what I want. So I consider to abandon maven. I will have some
extra config work 
in the begining, but at least there are no issues with jar dependencies.

But if somebody could help... :)

Shymon
-- 
View this message in context: 
http://www.nabble.com/Tapestry-5.0.15%2C-NetBeans-6.1-and-Hibernate-ClassNotFound-exception-tp19757952p20197738.html
Sent from the Tapestry - User mailing list archive at Nabble.com.


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

Reply via email to