Not a single line of code has been changed between the two versions. The
version with Wicket 1.2.5 jars displays property web pages using css files
in the css subdirectory of the web application root directory, and the
version with Wicket 1.2.6 jars cannot find the css files that are in the
same
servlet-mapping
servlet-namedmWicketApplication/servlet-name
url-pattern/app/*/url-pattern
/servlet-mapping
--
View this message in context:
http://www.nabble.com/from-1.2.5-to-1.2.6-tf3647980.html#a10203607
Sent from the Wicket - User mailing list
, but the /context/mapping/? did, so that is
the option we went with.
is that the problem? the browser thinks you are in /context/mapping while
your link assumes you are in /context ?
what is your servlet mapping?
-igor
On 4/26/07, dzenanr [EMAIL PROTECTED] wrote:
Not a single line of code
] was not found
The translated path is the correct one for the CSS file.
igor.vaynberg wrote:
is that the 1.2.6 or the 1.2.5 url?
-igor
On 4/26/07, dzenanr [EMAIL PROTECTED] wrote:
Yes, it seems that this is the problem:
http://localhost:8081/dmWicket/app?wicket:bookmarkablePage
a mounted page.
-igor
On 4/26/07, dzenanr [EMAIL PROTECTED] wrote:
Sorry,
It is the 1.2.6 url and the url is:
http://localhost:8081/dmWicket/app/?wicket:bookmarkablePage=:course.wicket.app.AboutPage
When the page is displayed there is no CSS formatting for the page. In
the
log
=screen
href=../css/box.css
/
notice the ../ in href. that should fix that.
also note that this isnt the greatest way to include css because it will
break if you use a mounted page.
-igor
On 4/26/07, dzenanr [EMAIL PROTECTED] wrote:
Sorry,
It is the 1.2.6 url and the url is:
http
:
link and import have not changed behavior
what has changed is that wicket now always appends a / after the servlet
mapping, where as before it only did so sometimes. so now it is more
consistent but is messing with your context path.
-igor
On 4/26/07, dzenanr [EMAIL PROTECTED] wrote
/app.css for you?
-igor
On 4/26/07, dzenanr [EMAIL PROTECTED] wrote:
Well, I changed imports to links and the same definition in both pages
works
well without using ../:
link rel=stylesheet type=text/css media=screen href=css/app.css
/
link rel=stylesheet type=text/css media
true
Is there a reason why Wicket does not process imports?
igor.vaynberg wrote:
so it was never the link element that was the problem, it was the @imports
because wicket doesnt process those.
-igor
On 4/26/07, dzenanr [EMAIL PROTECTED] wrote:
link rel=stylesheet type=text/css
I have replaced wicket jar files in my project from 1.2.5 to 1.2.6. CSS does
not work properly now. I have the css directory in the root directory of the
Eclipse. The following line in my html files produced the correct CSS
before:
link rel=stylesheet type=text/css media=screen href=css/box.css
the text area that has the same length vertically
and horizontally. I have tried with 96 instead of 64 (96 appears in the
generated HTML), but the page still looks the same.
Eelco Hillenius wrote:
Did you check the actual HTML that is generated?
Eelco
On 10/31/06, dzenanr [EMAIL PROTECTED
not display properly
the text area. I just do not know where to look for the problem, since the
page does not display the proper size of the text area, despite the new
numbers in the generated page.
igor.vaynberg wrote:
thats hardly a wicket issue
check your css
-igor
On 11/1/06, dzenanr
The same problem with Microsoft Explorer and Firefox.
I have cleaned all in Firefox. Still the same.
Eelco Hillenius wrote:
Very weird indeed. Did you try different browsers and cleaning up the
browser's cache?
Eelco
On 11/1/06, dzenanr [EMAIL PROTECTED] wrote:
CSS is simple
: #ffe4b5;
}
/* ===[ end ]=== */
Eelco Hillenius wrote:
What is the resulting markup of your whole page, and any css files you
use?
Eelco
On 11/1/06, dzenanr [EMAIL PROTECTED] wrote:
The same problem with Microsoft Explorer and Firefox.
I have cleaned all
;
}
.textfield {
margin:3px;
height:20px;
width:200px;
}
textarea {
margin:3px;
height:165px;
width:200px;
}
/* ===[ end ]=== */
dzenanr wrote:
?xml version
Actually the problem was a missing point in front of textarea within
form.css.
dzenanr wrote:
I have found the problem. It was CSS for a form - width 300px for the
fieldset.
Thank you for leading me towards the cause of the problem.
/* form.css */
/* ===[ begin
Hi all,
I determine the number of rows and columns for a text area using
AttributeModifier. Usually there are more columns than rows and they are
derived properly in my code. However, the text area is always displayed as a
square, as the number of rows determines, by error?, also the number of
17 matches
Mail list logo
