You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by "brian.diekelman" <de...@gmail.com> on 2008/06/05 01:53:46 UTC
IE7 Javascript Bug: WICKET-1646
I wanted to bring some visibility to an issue with 1.3.4/1.4-M before 1.3.4
goes final:
https://issues.apache.org/jira/browse/WICKET-1646
The patch to use the native XMLHttpRequest object on IE7 is breaking on any
DoD computer with Standard Desktop Configuration enabled (basically just
locked down security settings). This will also probably break any computer
in a large corporate setting that has a similarly strict configuration.
I wanted to bring this up because I heard Frank Bille say Wicket 1.3.4 was
probably going to be released this week and I wanted to see if we could get
this addressed before then. Please check my comments on the Jira ticket for
my suggested fix.
Thanks,
- Brian
--
View this message in context: http://www.nabble.com/IE7-Javascript-Bug%3A-WICKET-1646-tp17659227p17659227.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.
Re: Error in current trunk 1.4
Posted by "brian.diekelman" <de...@gmail.com>.
And along those lines, shouldn't the CI server freak out when it tries to
build from trunk and tests fail?
Also, anyone know why this is listed as a response to my WICKET-1646
message?
jwcarman wrote:
>
> On Sat, Jun 7, 2008 at 3:39 AM, Stefan Lindner <li...@visionet.de>
> wrote:
>> Yes! Of course some tests fail during maven build but that is not unusual
>> for trunk.
>
> Checking in broken code should be unusual, especially for trunk. I
> can see where you would do so on a branch or something, but the trunk
> should remain buildable at all times.
>
>
--
View this message in context: http://www.nabble.com/IE7-Javascript-Bug%3A-WICKET-1646-tp17659227p17711368.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.
Re: Error in current trunk 1.4
Posted by James Carman <ja...@carmanconsulting.com>.
On Sat, Jun 7, 2008 at 3:39 AM, Stefan Lindner <li...@visionet.de> wrote:
> Yes! Of course some tests fail during maven build but that is not unusual for trunk.
Checking in broken code should be unusual, especially for trunk. I
can see where you would do so on a branch or something, but the trunk
should remain buildable at all times.
Re: Error in current trunk 1.4
Posted by Stefan Lindner <li...@visionet.de>.
I use Java 1.5.0_15 and Maven 2.0.9. I checked out the current wicket trunk (http://svn.apache.org/repos/asf/wicket/trunk) into a fresh new directory. I build wicket with
mvn -Prelease install
And I see the following
INFO - Application - [WicketTester$DummyWebApplication] destroy: Wicket JMX initializer
INFO - Application - [WicketTester$DummyWebApplication] destroy: Wicket JMX initializer
ERROR - Initializer - WicketTester$DummyWebApplication-3:type=Application
javax.management.InstanceNotFoundException: WicketTester$DummyWebApplication-3:type=Application
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1010)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.unregisterMBean(DefaultMBeanServerInterceptor.java:354)
at com.sun.jmx.mbeanserver.JmxMBeanServer.unregisterMBean(JmxMBeanServer.java:527)
at org.apache.wicket.jmx.Initializer.destroy(Initializer.java:75)
at org.apache.wicket.Application.callDestroyers(Application.java:789)
at org.apache.wicket.Application.internalDestroy(Application.java:909)
at org.apache.wicket.protocol.http.WebApplication.internalDestroy(WebApplication.java:499)
at org.apache.wicket.protocol.http.MockWebApplication.destroy(MockWebApplication.java:683)
at org.apache.wicket.examples.hangman.WordGeneratorTest.tearDown(WordGeneratorTest.java:60)
at junit.framework.TestCase.runBare(TestCase.java:130)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.maven.surefire.battery.JUnitBattery.executeJUnit(JUnitBattery.java:242)
at org.apache.maven.surefire.battery.JUnitBattery.execute(JUnitBattery.java:216)
at org.apache.maven.surefire.Surefire.executeBattery(Surefire.java:215)
at org.apache.maven.surefire.Surefire.run(Surefire.java:163)
at org.apache.maven.surefire.Surefire.run(Surefire.java:87)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.maven.surefire.SurefireBooter.runTestsInProcess(SurefireBooter.java:313)
at org.apache.maven.surefire.SurefireBooter.run(SurefireBooter.java:221)
at org.apache.maven.test.SurefirePlugin.execute(SurefirePlugin.java:371)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
ERROR - Initializer - WicketTester$DummyWebApplication-3:type=Application,name=ApplicationSettings
javax.management.InstanceNotFoundException: WicketTester$DummyWebApplication-3:type=Application,name=ApplicationSettings
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1010)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.unregisterMBean(DefaultMBeanServerInterceptor.java:354)
at com.sun.jmx.mbeanserver.JmxMBeanServer.unregisterMBean(JmxMBeanServer.java:527)
at org.apache.wicket.jmx.Initializer.destroy(Initializer.java:75)
at org.apache.wicket.Application.callDestroyers(Application.java:789)
at org.apache.wicket.Application.internalDestroy(Application.java:909)
at org.apache.wicket.protocol.http.WebApplication.internalDestroy(WebApplication.java:499)
at org.apache.wicket.protocol.http.MockWebApplication.destroy(MockWebApplication.java:683)
at org.apache.wicket.examples.hangman.WordGeneratorTest.tearDown(WordGeneratorTest.java:60)
at junit.framework.TestCase.runBare(TestCase.java:130)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.maven.surefire.battery.JUnitBattery.executeJUnit(JUnitBattery.java:242)
at org.apache.maven.surefire.battery.JUnitBattery.execute(JUnitBattery.java:216)
at org.apache.maven.surefire.Surefire.executeBattery(Surefire.java:215)
at org.apache.maven.surefire.Surefire.run(Surefire.java:163)
at org.apache.maven.surefire.Surefire.run(Surefire.java:87)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.maven.surefire.SurefireBooter.runTestsInProcess(SurefireBooter.java:313)
at org.apache.maven.surefire.SurefireBooter.run(SurefireBooter.java:221)
at org.apache.maven.test.SurefirePlugin.execute(SurefirePlugin.java:371)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
ERROR - Initializer - WicketTester$DummyWebApplication-3:type=Application,name=DebugSettings
javax.management.InstanceNotFoundException: WicketTester$DummyWebApplication-3:type=Application,name=DebugSettings
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1010)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.unregisterMBean(DefaultMBeanServerInterceptor.java:354)
at com.sun.jmx.mbeanserver.JmxMBeanServer.unregisterMBean(JmxMBeanServer.java:527)
at org.apache.wicket.jmx.Initializer.destroy(Initializer.java:75)
at org.apache.wicket.Application.callDestroyers(Application.java:789)
at org.apache.wicket.Application.internalDestroy(Application.java:909)
at org.apache.wicket.protocol.http.WebApplication.internalDestroy(WebApplication.java:499)
at org.apache.wicket.protocol.http.MockWebApplication.destroy(MockWebApplication.java:683)
at org.apache.wicket.examples.hangman.WordGeneratorTest.tearDown(WordGeneratorTest.java:60)
at junit.framework.TestCase.runBare(TestCase.java:130)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
-----Ursprüngliche Nachricht-----
Von: Johan Compagner [mailto:jcompagner@gmail.com]
Gesendet: Sonntag, 8. Juni 2008 14:30
An: dev@wicket.apache.org
Betreff: Re: Error in current trunk 1.4
Test all work.. You are building and testing with java 6?
It shoukd be done with 5 for now
On 6/7/08, Stefan Lindner <li...@visionet.de> wrote:
> Yes! Of course some tests fail during maven build but that is not
> unusual for trunk.
>
> -----Ursprüngliche Nachricht-----
> Von: Johan Compagner [mailto:jcompagner@gmail.com]
> Gesendet: Samstag, 7. Juni 2008 00:50
> An: dev@wicket.apache.org
> Betreff: Re: Error in current trunk 1.4
>
> so you have an exception purely at runtime but it compiles correct?
>
> On Fri, Jun 6, 2008 at 10:17 PM, Stefan Lindner <li...@visionet.de> wrote:
>
>> The class AutoLinkResolver has an inner interface in line 510
>>
>> private static interface ITagReferenceResolver
>>
>> this leads to the following exception when an application is deployed:
>>
>> ERROR [[/Test]] Exception starting filter Test
>> java.lang.NoClassDefFoundError:
>> org/apache/wicket/markup/resolver/AutoLinkResolver$ITagReferenceResolver
>> at
>> org.apache.wicket.protocol.http.WebApplication.internalInit(WebApplic
>> a
>> ti
>> on.java:529)
>> at
>> org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:5
>> 5
>> 8)
>>
>> When I make the interface public the applicatioin gets deployed
>> correctly.
>>
>> Shall I report a bug or is this already solved by a developer?
>>
>> Stefan
>>
>
Re: Error in current trunk 1.4
Posted by Stefan Lindner <li...@visionet.de>.
I don't want to create too much noise on this list. I will cuntinue to
use 1.4M2 so the developers might have the patience to solve real
problems.
Stefan
Re: Error in current trunk 1.4
Posted by Johan Compagner <jc...@gmail.com>.
Test all work.. You are building and testing with java 6?
It shoukd be done with 5 for now
On 6/7/08, Stefan Lindner <li...@visionet.de> wrote:
> Yes! Of course some tests fail during maven build but that is not unusual
> for trunk.
>
> -----Ursprüngliche Nachricht-----
> Von: Johan Compagner [mailto:jcompagner@gmail.com]
> Gesendet: Samstag, 7. Juni 2008 00:50
> An: dev@wicket.apache.org
> Betreff: Re: Error in current trunk 1.4
>
> so you have an exception purely at runtime but it compiles correct?
>
> On Fri, Jun 6, 2008 at 10:17 PM, Stefan Lindner <li...@visionet.de> wrote:
>
>> The class AutoLinkResolver has an inner interface in line 510
>>
>> private static interface ITagReferenceResolver
>>
>> this leads to the following exception when an application is deployed:
>>
>> ERROR [[/Test]] Exception starting filter Test
>> java.lang.NoClassDefFoundError:
>> org/apache/wicket/markup/resolver/AutoLinkResolver$ITagReferenceResolver
>> at
>> org.apache.wicket.protocol.http.WebApplication.internalInit(WebApplica
>> ti
>> on.java:529)
>> at
>> org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:55
>> 8)
>>
>> When I make the interface public the applicatioin gets deployed
>> correctly.
>>
>> Shall I report a bug or is this already solved by a developer?
>>
>> Stefan
>>
>
AW: Error in current trunk 1.4
Posted by Stefan Lindner <li...@visionet.de>.
Yes! Of course some tests fail during maven build but that is not unusual for trunk.
-----Ursprüngliche Nachricht-----
Von: Johan Compagner [mailto:jcompagner@gmail.com]
Gesendet: Samstag, 7. Juni 2008 00:50
An: dev@wicket.apache.org
Betreff: Re: Error in current trunk 1.4
so you have an exception purely at runtime but it compiles correct?
On Fri, Jun 6, 2008 at 10:17 PM, Stefan Lindner <li...@visionet.de> wrote:
> The class AutoLinkResolver has an inner interface in line 510
>
> private static interface ITagReferenceResolver
>
> this leads to the following exception when an application is deployed:
>
> ERROR [[/Test]] Exception starting filter Test
> java.lang.NoClassDefFoundError:
> org/apache/wicket/markup/resolver/AutoLinkResolver$ITagReferenceResolver
> at
> org.apache.wicket.protocol.http.WebApplication.internalInit(WebApplica
> ti
> on.java:529)
> at
> org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:55
> 8)
>
> When I make the interface public the applicatioin gets deployed
> correctly.
>
> Shall I report a bug or is this already solved by a developer?
>
> Stefan
>
Re: Error in current trunk 1.4
Posted by Johan Compagner <jc...@gmail.com>.
so you have an exception purely at runtime but it compiles correct?
On Fri, Jun 6, 2008 at 10:17 PM, Stefan Lindner <li...@visionet.de> wrote:
> The class AutoLinkResolver has an inner interface in line 510
>
> private static interface ITagReferenceResolver
>
> this leads to the following exception when an application is deployed:
>
> ERROR [[/Test]] Exception starting filter Test
> java.lang.NoClassDefFoundError:
> org/apache/wicket/markup/resolver/AutoLinkResolver$ITagReferenceResolver
> at
> org.apache.wicket.protocol.http.WebApplication.internalInit(WebApplicati
> on.java:529)
> at
> org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:558)
>
> When I make the interface public the applicatioin gets deployed
> correctly.
>
> Shall I report a bug or is this already solved by a developer?
>
> Stefan
>
Error in current trunk 1.4
Posted by Stefan Lindner <li...@visionet.de>.
The class AutoLinkResolver has an inner interface in line 510
private static interface ITagReferenceResolver
this leads to the following exception when an application is deployed:
ERROR [[/Test]] Exception starting filter Test
java.lang.NoClassDefFoundError:
org/apache/wicket/markup/resolver/AutoLinkResolver$ITagReferenceResolver
at
org.apache.wicket.protocol.http.WebApplication.internalInit(WebApplicati
on.java:529)
at
org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:558)
When I make the interface public the applicatioin gets deployed
correctly.
Shall I report a bug or is this already solved by a developer?
Stefan