Where to put HTML files?

[Gonzalo Aguilar Delgado-4]

Hi,

I'm just wondering were to put html pages. Currently I using the same
path as
.java files. I created two compilation units, one for java and one for
resources.
After compiling both units are joined and put into the same folder.

But this is tricky to handle as sources are compiled into jar and to
modify an html
I have to process the .jar or just recompile.

Is there any other way to organize thinks so resources got out the .jar?

Thank you!

[Pieter Degraeuwe]

IMHO, I think it is not a good idea to pull them too far from eachother. It
is actually a good thing that classes and their corresponding markup is
packaged together.
If the markup changes, your classes will change as well. (Otherwise, you
probably add to much 'styling' in your markup; use css instead)

On Thu, Oct 29, 2009 at 10:01 AM, Gonzalo Aguilar Delgado <
gaguilar@...> wrote:

> Hi,
>
> I'm just wondering were to put html pages. Currently I using the same
> path as
> .java files. I created two compilation units, one for java and one for
> resources.
> After compiling both units are joined and put into the same folder.
>
> But this is tricky to handle as sources are compiled into jar and to
> modify an html
> I have to process the .jar or just recompile.
>
> Is there any other way to organize thinks so resources got out the .jar?
>
> Thank you!
>

--
Pieter Degraeuwe
Systemworks bvba
Belgiëlaan 61
9070 Destelbergen
GSM: +32 (0)485/68.60.85
Email: pieter.degraeuwe@...
visit us at http://www.systemworks.be

[martin-g]

Check the sources of:
http://wicketstuff.org/wicket14/customresourceloading/

El jue, 29-10-2009 a las 10:06 +0100, Pieter Degraeuwe escribió:

> IMHO, I think it is not a good idea to pull them too far from eachother. It
> is actually a good thing that classes and their corresponding markup is
> packaged together.
> If the markup changes, your classes will change as well. (Otherwise, you
> probably add to much 'styling' in your markup; use css instead)
>
> On Thu, Oct 29, 2009 at 10:01 AM, Gonzalo Aguilar Delgado <
> gaguilar@...> wrote:
>
> > Hi,
> >
> > I'm just wondering were to put html pages. Currently I using the same
> > path as
> > .java files. I created two compilation units, one for java and one for
> > resources.
> > After compiling both units are joined and put into the same folder.
> >
> > But this is tricky to handle as sources are compiled into jar and to
> > modify an html
> > I have to process the .jar or just recompile.
> >
> > Is there any other way to organize thinks so resources got out the .jar?
> >
> > Thank you!
> >
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Olivier Bourgeois-2]

You can also override the template loader for the application. That's what
I've done and our templates and properties are in a different project than
the application. I also have two differents SVN repos.

The pros :

- you have instant template/properties reloading in development mode without
redeploying or complex IDE setup.
- you can edit, tag and release the templates without repackaging the war.

The cons :

- you have a more complex project setup : two projects in eclipse, two
folders.
- you don't have the templates near the classes and you cannot use tools
like wicket-bench for error detection (eg component id mispelling).

[Martijn Dashorst]

On Thu, Oct 29, 2009 at 2:20 PM, Olivier Bourgeois
<olivier.bourgeois.pro@...> wrote:
> The pros :
>
> - you have instant template/properties reloading in development mode without
> redeploying or complex IDE setup.

This is something that the quickstart
(http://wicket.apache.org/quickstart.html) already provides, no need
for complex setups having to keep directory structures in sync, or
having to debug a custom resource resolver, or finding out why the
templates don't match your java code ("Oh shouldn't I have updated
production with the new templates?")

Martijn

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Gonzalo Aguilar Delgado-4]

Thank you a lot to all for your commentaries...

Everything exposed here seems to help me in one way or another.

I will run a test for best approach and after decide the best way for
me.

Thank you again!


El jue, 29-10-2009 a las 14:27 +0100, Martijn Dashorst escribió:

> On Thu, Oct 29, 2009 at 2:20 PM, Olivier Bourgeois
> <olivier.bourgeois.pro@...> wrote:
> > The pros :
> >
> > - you have instant template/properties reloading in development mode without
> > redeploying or complex IDE setup.
>
> This is something that the quickstart
> (http://wicket.apache.org/quickstart.html) already provides, no need
> for complex setups having to keep directory structures in sync, or
> having to debug a custom resource resolver, or finding out why the
> templates don't match your java code ("Oh shouldn't I have updated
> production with the new templates?")
>
> Martijn
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>