You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "sander hautvast (JIRA)" <ji...@apache.org> on 2009/07/16 18:45:14 UTC
[jira] Issue Comment Edited: (WICKET-2373) wicket markup gone
[ https://issues.apache.org/jira/browse/WICKET-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732013#action_12732013 ]
sander hautvast edited comment on WICKET-2373 at 7/16/09 9:43 AM:
------------------------------------------------------------------
ok, I educated myself a little
other developers built a small wicket application and called for my help when it didn't deploy on websphere. And I know a lot about websphere, and not much about wicket.
let me rephrase the problem:
<wicket:panel>
<label wicket:id="label">label</label>
<select wicket:id="value">
<option></option>
</select>
</wicket:panel>
works fine in jetty 6 on windows using sun jre 1.6
but fails to show in websphere 6.1 on aix
and I found out Tomcat 6 on windows using sun jre1.6 doesn't work either. The exact same behavior.
the mode for jetty doesn´t make a difference. but on Tomcat and Websphere the page won´t render in development mode.
in deployment mode the select is missing.
I think I pretty much ruled out the OS/JRE
My guess is that tomcat and websphere have something in common that jetty does not have.
That´s all I can give you. It would be too much of an effort right now to send some sample application to proove my point. I cannot send you the application itself
was (Author: shautvast):
ok, I educated myself a little
other developers built a small wicket application and called for my help when it didn't deploy on websphere. And I know a lot about websphere, and not much about wicket.
let me rephrase the problem:
<wicket:panel>
<label wicket:id="label">label</label>
<select wicket:id="value">
<option></option>
</select>
</wicket:panel>
works fine in jetty 6 on windows using sun jre 1.6
but fails to show in websphere 6.1 on aix
and I found out Tomcat 6 on windows using sun jre1.6 doesn't work either. The exact same behavior.
the mode for jetty doesn´t make a difference. but on Tomcat and Websphere the page won´t render in development mode.
in deployment mode the select is missing.
I think I pretty much ruled the OS/JRE
My guess is that tomcat and websphere have something in common that jetty does not have.
That´s all I can give you. It would be too much of an effort right now to send some sample application to proove my point. I cannot send you the application itself
> wicket markup gone
> ------------------
>
> Key: WICKET-2373
> URL: https://issues.apache.org/jira/browse/WICKET-2373
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4-RC5, 1.4-RC7
> Environment: WASWIN
> java version "1.5.0"
> Java(TM) 2 Runtime Environment, Standard Edition (build pwi32dev-20060511 (SR2))
> IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223-20060504 (JIT enabled)
> J9VM - 20060501_06428_lHdSMR
> JIT - 20060428_1800_r8
> GC - 20060501_AA)
> JCL - 20060511a
> WASAIX
> java version "1.5.0"
> Java(TM) 2 Runtime Environment, Standard Edition (build pap64devifx-20080906 (SR8a + IZ29767 + IZ30684 + IZ31214 + IZ31213))
> IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 AIX ppc64-64 j9vmap6423ifx-20080811 (JIT enabled)
> J9VM - 20080809_21892_BHdSMr
> JIT - 20080620_1845_r8
> GC - 200806_19)
> JCL - 20080906
> Reporter: sander hautvast
>
> we expect
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
> <html xmlns:wicket>
> <head>
> but get
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
> <html>
> <head>
> and any other wicket markup removed
> we run in websphere 6.1.0.21 on AIX 5.3
> websphere 6.1.0.21 on windows works fine (and several others like jetty on linux)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.