I have a similar problem:
A css style sheet is added to the app like so:
getSharedResources().add("css_table", new
ContextRelativeResource("css/table.css"));
and this css file contains image references like so:
div.tabpanel div.tab-row li {
float: left;
background: url(".
Thanks Martin, that helps. Forgive my naivety, but why do I have the option
of adding CSS via the Java code? Surely it's better to follow convention and
add it into the appropriate .war directory?
...and if I could do the Columbo, "Just one more thing", thing. Why am I
getting two tags in my app?
Martin Grigorov-4 wrote
>
>
>>If you provide components library then you need to distribute the
>>resources too, not just the classes.
>>Shared resources is more for delivering dynamically generated content.
>>A content that is different depending on some external condition
>>(request parameter,
UPDATE:
I created a new TestBasePage and a new class that extends TestBasePage. The
markup for TestBasePage has the same mark up as that in my
application's BasePage class. When I tested the rendered html it still has
two tags. I then added the tag to the child class of
TestBasePage and then
Hi,
I have a class that extends AjaxTabbedPanel, it displays a busy indicator
while the ajax call is running (see code below). This all works fine during
these ajax calls; so a busy indicator is displayed and the tab that has been
selected is displayed correctly in the view. However, if the page
Ah yes sorry, the all important version number. It's Wicket 1.5.
Yes, I *believe* the busy indicator isn't related.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Class-that-extends-AjaxTabbedPanel-does-not-remember-selected-panel-on-page-refresh-tp4650642p4650
I can't see any difference between the two...
One thing I have noticed, is that the page's constructor is run when I
refresh the page. Would that have anything to do with it? The page is
defined in the web application class:
mount("/home", HomePage.class);
--
View this message in context:
lol. Yes we are indeed tinkering with the custom request mappers. I removed
some code from the code sample above thinking at the time that it wasn't
relevant. Here's the full code (not sure if it helps with the investigation
of the problem or not but since you mentioned it I'll include it anyway):
BTW. The application has been ported from Wicket 1.4 to 1.5, and it did this
in 1.4 too. So maybe the request mapping stuff isn't an issue...
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Class-that-extends-AjaxTabbedPanel-does-not-remember-selected-panel-on-pag
Good shout Martin that is the problem. I changed it to the following and now
it's working:
mountPage("/home", HomePage.class);
You know what's coming next don't you...I've now changed the behavior of the
url so it's now:
http://localhost:8080/myApp/home?3
Am I stuck with this or is there
OK thanks Martin. I'll have to raise this as an issue with my management, as
it may have knock on affects. It's a shame the state has to be maintained by
parameters in the url.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Class-that-extends-AjaxTabbedPanel-does-
I think I did suggest something, "It's a shame the state has to be
maintained by parameters in the url". You are the people responsible for the
Wicket code I'm a customer...oh how annoying customers can be ;-)
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Class-
Lucky for us there are plenty of others who would charge us the same :-)
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Class-that-extends-AjaxTabbedPanel-does-not-remember-selected-panel-on-page-refresh-tp4650642p4650720.html
Sent from the Users forum mailing list
13 matches
Mail list logo
