Hi all againThis time my problem is with my implementation of Navomatic.I had a menu with several elements, and it worked as described in the Navomatic example. Today I added a new element to the menu, with the same syntax that all other entries have, but Wicket is not rendering the new element
Hi Rui,
Do you have the files ListarProverbios.html and ListarProverbios.java
present in the same directory as the Menu.html and Menu.java?
I think both of them are needed for wicket:link to do the magic it does.
Cumprimentos,
Dave
Rui Pacheco wrote:
Hi all again
This time my problem is
DaveNo I don't, but then again, neither are any of the other links, and they work like a charm.Menu.html is included in all the pages that it calls, so in theory it is next to the other pages, at least when the application is running.
On 5/3/06, Dave Schoorl [EMAIL PROTECTED] wrote:
Hi Rui,Do you
Well, thats funny. I experimented a bit with the navomatic application
of wicket-examples and when I removed the page3.class file from the
classpath, the link to page3 showed the same behaviour as you described.
And in the log the following message was shown: WARN -
AutoLinkResolver
About the Menu.html being included in all the pages, I was just repeating what Navomatic does. Nevermind that.The thing is, all links work and used to work without those classes in the package. That one link, that I added today, doesn't work.
I see nothing on Tomcat's logs. I am using RC3, Java 5,
hmm, so you dont have ListarAbreviaturas.java and ListarAbreviaturas.html in the same package? where does the first link take you then?-IgorOn 5/3/06,
Rui Pacheco [EMAIL PROTECTED] wrote:
About the Menu.html being included in all the pages, I was just repeating what Navomatic does. Nevermind
I know all the links take me to the correct pages, except for the link I added today, which is not rendered by Wicket.On 5/3/06, Igor Vaynberg
[EMAIL PROTECTED] wrote:hmm, so you dont have
ListarAbreviaturas.java and ListarAbreviaturas.html in the same package? where does the first link take you
you didnt answer my questiondo you have those files in the same package and if not what pages do you end up at?-IgorOn 5/3/06, Rui Pacheco
[EMAIL PROTECTED] wrote:
I know all the links take me to the correct pages, except for the link I added today, which is not rendered by Wicket.
On 5/3/06,
I do not have those pages in the same package as the menu. And the pages I end up at are the ones the menu points to, ie, the correct ones.I'm sending you the packages personally as this is the internet and I dont want my source code floating around :)
And I won't make this an habit, too.On
hmm, nothing really jumps out at me. i guess you will have to walk the code in WicketLinkTagHandler to see why its not doing its magic.-IgorOn 5/3/06,
Rui Pacheco [EMAIL PROTECTED] wrote:
I do not have those pages in the same package as the menu. And the pages I end up at are the ones the menu
One final question: was it suppose to work with the pages in a different package or not? By your reply I take it that it should work.On 5/3/06, Igor Vaynberg
[EMAIL PROTECTED] wrote:
hmm, nothing really jumps out at me. i guess you will have to walk the code in WicketLinkTagHandler to see why its
autolinker looks for pages in the same package as the page it is on i believe. so since your menu is a panel and you are including it in a basepage i believe it should work as long as the pages are in the same package as the page that contains the menu panel.
-IgorOn 5/3/06, Rui Pacheco [EMAIL
Thanks for the answer.On 5/3/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
autolinker looks for pages in the same package as the page it is on i believe. so since your menu is a panel and you are including it in a basepage i believe it should work as long as the pages are in the same package as the
13 matches
Mail list logo
