Hi Johan,
Thank you very much for taking the time to take a look at my first steps
project.
you have really the most strange setup i have every seen.
everything is pretty much scrambled.
Well, as said before, I'm completely new to web-application development and
I try to set it up that way, that I can edit the HTML files with my favorite
HTML-editor (IDEA), which esp. can check the paths/image sizes and I can see
them in WYSIWYG-editors (DreamWeaver). To my understanding this only is
possible using relative paths.
<img src="graphics/logo.gif" width="90" height="100" alt="Logo"/>
that one tells me it sits in the WEBAPP root dir (so the dir just below youre
WEB-INF dir)
Interesting, what you are reading in that line. ;) I just want the logo.gif
to be in the subdirectory "graphics" of the current file (at design-time). I
don't care, where everything is put at the time of deploying.
<img src="/CONTEXT/graphics/logo.gif" width="90" height="100" alt="Logo"/>
and context is in youre place 'foo'
But logo.gif doesn't sit in that location. No it sits (looking at the root of
youre webapp in:
"/resources/pages/graphics/logo.gif"
OK, this one I understand. From the browser's point of view it should occur
at "/CONTEXT/graphics/logo.gif", when the path to the current page is, e.g.,
"/CONTEXT/index". I guess, you want me to say, that the graphics directory
should be at the same level as WEB-INF, because that's the standard way of
loading graphics at that path, isn't it?
<img src="graphics/logo.gif" wicket:id="logoimage" width="90" height="100"
alt="Logo"/>
and add a ImageLink or something like that to the page and make a
PackageResourceReference to youre logo.gif.
Well, that's something I want to avoid, because I don't want to add a
component for every graphic I add on the web-site. This seems to be too
error prone to me.
of if you really want youre images and pages in the webroot dir do make it so
that it matches the web app root
in youre case
I don't care where the files are located after deploying, I just want to
have them in a "nice structure" at design-time and want wicket to correct
the paths as required. Why I'm so "stubborn" with my design-time paths?
Because wicket advertises previewability at design-time (because the markup
still is valid HTML code) and I want to go a step further and also want to
use graphics, other resources and links at design-time.
If there should be a more difficult deployment process to copy image files
to a different path than the classes or markup-files, OK, that's fine, as
long as I get my design-time previewability. ;)
I hope, I could sketch my vision somehow understandable, although it might
sound weird to web-application experts.
--
Best regards,
Thomas Singer
_____________
smartcvs.com
smartsvn.com
Johan Compagner schrieb:
you have really the most strange setup i have every seen.
everything is pretty much scrambled.
I guess you want youre pages in the web-root and not in the classes yes?
If you want that then please set it up a bit different.
Because how do we expect to know where you pages are and what the root
is for you pages if you load them completely yourself from a totally
different
then wicket way location?
Just look at youre logo:
<img src="graphics/logo.gif" width="90" height="100" alt="Logo"/>
that one tells me it sits in the WEBAPP root dir (so the dir just below
youre WEB-INF dir)
and it is not a wicketised tag so wicket only makes it this:
<img src="/CONTEXT/graphics/logo.gif" width="90" height="100" alt="Logo"/>
and context is in youre place 'foo'
But logo.gif doesn't sit in that location. No it sits (looking at the
root of youre webapp in:
"/resources/pages/graphics/logo.gif"
so tell me in the current setup how do we ever know expect to know that??
you have 2 choices i think.
Move everything in the classes dir. And make a package resource out of
it then you need to do this:
<img src="graphics/logo.gif" wicket:id="logoimage" width="90"
height="100" alt="Logo"/>
and add a ImageLink or something like that to the page and make a
PackageResourceReference to youre logo.gif.
of if you really want youre images and pages in the webroot dir do make
it so that it matches the web app root
in youre case
/resources/pages should be the root of youre webapp.
johan
On 3/2/06, *Thomas Singer* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
wrote:
> you have a better chance of having people look at your code if
you post
> it with jetty and eclipse project files so that we can import it,
click
> run, and have a look. see quickstart for how its setup.
OK, I've got it up and running. Please download the bundle from
http://www.regnis.de/_wicket/wicket-link-test-060302.zip (3MB).
Thanks in
advance.
--
Best regards,
Thomas Singer
Igor Vaynberg schrieb:
> many committers dont have the time to setup deployment to tomcat, ide
> setup, etc.
>
> you have a better chance of having people look at your code if
you post
> it with jetty and eclipse project files so that we can import it,
click
> run, and have a look. see quickstart for how its setup.
>
> if you want you are more then welcome to post the bug report, but
you
> would probably benefit more from doing the above.
>
> -Igor
>
>
> On 3/1/06, * Thomas Singer* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> <mailto: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>>>
> wrote:
>
> Should I file a bug report because of the link problems?
>
> --
> Best regards,
> Thomas Singer
>
>
> Thomas Singer schrieb:
> > Hi David and others,
> >
> > I've converted my tiny project to Wicket 1.2, but
encounter the same
> > problems as with Wicket 1.1.1.
> > - the image on the first page is not found,
> > - clicking the About link shows the about page, but does not
> render the
> > links correctly (About is still a link).
> >
> > My "exploded" directory contains this structure:
> > +---META-INF
> > | context.xml
> > |
> > +---pages
> > | | Index.html
> > | | PageTemplate.html
> > | |
> > | +---about
> > | | Index.html
> > | |
> > | \---graphics
> > | logo.gif
> > |
> > \---WEB-INF
> > | web.xml
> > |
> > +---classes
> > | \---com
> > | \---foo
> > | \---website
> > | | FooWebApplication$1.class
> > | | FooWebApplication.class
> > | |
> > | +---pages
> > | | | Index.class
> > | | |
> > | | \---about
> > | | Index.class
> > | |
> > | \---templates
> > | PageTemplate.class
> > |
> > \---lib
> > commons-logging-1.0.4.jar
> > log4j-1.2.12.jar
> > wicket-1.2-20060227-0200.jar
> >
> > I'd really appreciate it, if someone please could take a
look at the
> > tiny project (http://regnis.de/_wicket/wicket-060228.zip
<http://regnis.de/_wicket/wicket-060228.zip>) and give a
> > hint about what's wrong and how to make it better. Thanks
in advance.
> >
> > --
> > Best regards,
> > Thomas Singer
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
that extends applications into web and mobile media. Attend the live
webcast
and join the prime developer group breaking into this new coding
territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
<http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642>
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
<mailto:Wicket-user@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wicket-user
<https://lists.sourceforge.net/lists/listinfo/wicket-user>
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
