Hi, Many thanks for all of your thoughts on this. I have chosen to go with having a common project as a jar and setting up maven to build this project first and use it as a dependency for the other two. This means i'll be able to put the various entities in there that are shared between both web applications. I am not *too* concerned about live class reloading if it's only for the shared JAR since it will contain mainly only entities and it doesn't take long whilst developing to just hit "run" again if I can't figure out a better way. I would imagine these entities will remain relatively static throughout the restructing as they are mapped to database tables using hibernate and everything currently works, they are just going to be moved.
Another factor in deciding to use this approach is that I have been told we are having one side of the website launch before the other and this division of the projects into separate web apps makes it slightly easier. I'm looking at the documentation at he moment for how to create a jar file for tapestry to use and I intend to use the documentation here: https://tapestry.apache.org/component-libraries.html I did spot that it says clearly at the top: "This page has not yet been fully updated for Tapestry 5.4. Things are different and simpler in 5.4 than in previous releases." but i'm going to have to just run with it and find out what those changes are as I go along. I think long term, having them split into two webapps that just share the same model (the database and various entities) makes most sense. In the meantime, whilst making this decision I have been working on the front end, but after a while of reading up I am thinking (for us) this is the best solution. Any light on what the documentation is hinting at with the updates for that page would be fantastic if anyone has any ideas. Thanks, Steve On 4 August 2015 at 15:40, Thiago H de Paula Figueiredo <thiag...@gmail.com> wrote: > On Tue, 04 Aug 2015 10:27:01 -0300, Svein-Erik Løken <sv...@jacilla.no> > wrote: > > >> 4) You can't use Tapestry's Live Class Reloading on any class in the >>> >> common >>> >> JAR (e.g. Tapestry IOC service implementation classes). >>> > >>> > I think 4) is the biggest downside in a multi-module project. Do you >>> > think Tapestry can do a Live Class Reloading of the common JAR included >>> > with contributeCoreLibComponentClasses? >>> >>> If this is about Eclipse (I'm not sure about other IDEs, since I haven't >>> used any besides Eclipse for many years), if you have all the projects >>> open at the same time, you can use live class reloading on all of them at >>> the same, and I do this all the time. >>> >>> >> Really! I am using IntelliJ IDEA Ultimate and NEED this functionality. >> Today I need to recompile all maven projects and restart jetty for every >> change to components and JavaScript modules (all resources) in the common >> JAR. >> > > If you're including your common project as a JAR in the classpath of your > main project, live class reloading will never work. On the other hand, if > you include your common project's target folder (where the .class files are > generated) in the classpath of your main project, it should work. I'm sure > there's a way of doing that in IDEA. There has to be one. IDEA would suck > if there wasn't, and apparently IDEA is the opposite of suck. :) > > -- > Thiago H. de Paula Figueiredo > Tapestry, Java and Hibernate consultant and developer > http://machina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
