absolutely. check out AutoLinkResolver to get started.-IgorOn 3/2/06, Thomas Singer <[EMAIL PROTECTED]> wrote:
Igor, thanks for clarification. Is it possible to plug-in an own"link-resolver", which manages the path-correction in the area?
--Best regards,Thomas SingerPS: I'm not THE SmartCVS/SVN gu
Igor, thanks for clarification. Is it possible to plug-in an own
"link-resolver", which manages the path-correction in the area?
--
Best regards,
Thomas Singer
PS: I'm not THE SmartCVS/SVN guy - we are two, Marc Strapetz and me. But
unfortunately experience in developing desktop applications
ok i got the links figured out. this is a bit tricky so walk with me. resolves links /relative/ to the package of the current templateyou have two linkswhen the index page loads wicket will resolve the links thus:page package: com.foo.website.pages1->com.foo.website.pages.Index2->com.foo.website.pa
OK, you are right, having the PageTemplate class in a different package than
the Index class and having the PageTemplate.html in the same directory as
the Index.html markup is not that easy do achieve on deploying. Looks like
in my case I need to keep my IResourceStreamLocator instance for the
lol, just noticed you are the smartsvn/cvs guy. great products. used them both in the past. props. :)-IgorOn 3/2/06, Igor Vaynberg <
[EMAIL PROTECTED]> wrote:havent taken a look at the links issue yet, one thing at a time.
-IgorOn 3/2/06,
Thomas Singer <[EMAIL PROTECTED]
> wrote:OK, at the moment
havent taken a look at the links issue yet, one thing at a time.-IgorOn 3/2/06, Thomas Singer <[EMAIL PROTECTED]
> wrote:OK, at the moment I have code to find the markups in the pages/ dir, but it
also should be possible to copy them into the packages while deploying.But does this solve the problem
OK, at the moment I have code to find the markups in the pages/ dir, but it
also should be possible to copy them into the packages while deploying.
But does this solve the problems with the *links* shown in my example?
--
Best regards,
Thomas Singer
Igor Vaynberg schrieb:
still tricky
notic
still trickynotice that your Index.html is in pages dir and so is your PageTemplate.html, but the corresponding classes are in two different packages: com.foo.website.pages.Index.html and com.foo.website.templates.PageTemplate
so somehow you need to handle that mapping. which you in fact can, you
Would it be possible for wicket to handle such a after-deploy-structure
without major head-aches:
+---graphics
| logo.gif
|
\---WEB-INF
| web.xml
|
+---classes
| +---com
| | \---foo
| | \---website
| | | FooWebApplication.class
if you don't want to make components for youre image or other resource tags.Then the only thing i can think of is that you put all youre pages in the doc rootand then all youre other stuff in images above that so
Page.htmlgraphics/style/The big problem with this at runtime is that youre wic
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 wa
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 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/wic
or even better prepare a unit test case which I can copy/add to the
existing once.
Juergen
On 3/1/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> 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 y
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 a
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 Ab
On 3/1/06, Thomas Singer <[EMAIL PROTECTED]> wrote:
I've converted my tiny project to Wicket 1.2, but encounter the sameproblems as with Wicket 1.1.1.One difference I noticed between yours and mine (which was based off the quickstart) is that I have my wicket servlet mapped to /app and not /
This w
Hi,
I took a look at your project, but I am definitely not the right guy to
ask about this. I have no experience with what you're trying to do.
Good luck!
Dave
On Tue, 2006-02-28 at 21:50 +0100, Thomas Singer wrote:
> Hi David and others,
>
> I've converted my tiny project to Wicket 1.2, bu
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" dire
19 matches
Mail list logo
