On Tue, 24 Sep 2013 16:53:09 -0300, Daniel Jue wrote:
Thanks Thiago!! Good to hear from you.
Hello, Daniel! Nice to see you back at the mailing list. :)
One of my little concerns with the location of html and js files is that
the developer who's writing those doesn't want to have anything
Thanks Thiago!! Good to hear from you.
One of my little concerns with the location of html and js files is that
the developer who's writing those doesn't want to have anything to do with
Tapestry. He's a bit challenging to work with (in an old school, hand
crafted servlet kind of way), and I'm t
Thanks for the recommendation to peek into tapestry-security, I hadn't
thought to look there but I'm definitely looking for those types of
examples.
I'll definitely be using the MANIFEST.MF method of discovery, since the
core module will have no idea about the customer/dataset specific modules
unt
Ok, I made some progress in the meantime, preparing the code to be split up
for different and future customers. To me it looks like whatever I want to
be in the root of the web app, I just stick under
/src/main/resources/com/customer/app/ , based on how I see it being done
with tapestry bootstrap
For Tapestry 5.4, the location in the classpath you put assets may have
changed, but everything else didn't, so I see no reason for what you
describe not working. This isn't any different from what happens in
tapestry-security, for example. It includes pages, components, etc.
As long there'
Hi, I was reading over this older blog link
http://blog.tapestry5.de/index.php/2010/01/19/tapestry-ioc-modularization-of-web-applications-without-osgi/
now that I have to architect our app to work for other customers. We want
to keep the core parts together and refactor out the customer specific
