Problem with JBoss 7.2.0-Alpha1-SNAPSHOT on Windows

[pkilian]

After the fix of https://issues.jboss.org/browse/AS7-5779 I updated  to the latest master and have a different problem now:

13:04:41,139 ERROR [org.eclipse.rap.rwt.osgi] (Thread-63) Unable to start RWT application.: org.apache.felix.log.LogException: java.lang.RuntimeException: org.osgi.service.http.NamespaceException: JBAS011964: Invalid resource name: C:\java\jboss-as-7.2.0.Alpha1-SNAPSHOT\standalone\data\osgi-store\bundle-19\rwtcontext_26139062_10836077/rwt-resources

    at org.eclipse.rap.rwt.osgi.internal.ApplicationReferenceImpl.registerResourceDirectory(ApplicationReferenceImpl.java:194)

    at org.eclipse.rap.rwt.osgi.internal.ApplicationReferenceImpl.startRWTApplication(ApplicationReferenceImpl.java:79)

    at org.eclipse.rap.rwt.osgi.internal.ApplicationReferenceImpl.start(ApplicationReferenceImpl.java:63)

    at org.eclipse.rap.rwt.osgi.internal.ApplicationLauncherImpl.doLaunch(ApplicationLauncherImpl.java:103)

    at org.eclipse.rap.rwt.osgi.internal.ApplicationLauncherImpl.launch(ApplicationLauncherImpl.java:85)

    at org.eclipse.rap.rwt.osgi.internal.ApplicationLauncherImpl.launch(ApplicationLauncherImpl.java:162)

    at org.eclipse.rap.rwt.osgi.internal.ApplicationLauncherImpl.launchWithConfiguration(ApplicationLauncherImpl.java:149)

    at org.eclipse.rap.rwt.osgi.internal.ApplicationLauncherImpl.addConfiguration(ApplicationLauncherImpl.java:64)

    at org.eclipse.rap.rwt.osgi.internal.ApplicationConfigurationTracker.addingService(ApplicationConfigurationTracker.java:35)

    at org.eclipse.rap.rwt.osgi.internal.ApplicationConfigurationTracker.addingService(ApplicationConfigurationTracker.java:1)

    at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896) [jbosgi-resolver-api-3.0.0.Final.jar:3.0.0.Final]

    at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261) [jbosgi-resolver-api-3.0.0.Final.jar:3.0.0.Final]

    at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:233) [jbosgi-resolver-api-3.0.0.Final.jar:3.0.0.Final]

    at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:840) [jbosgi-resolver-api-3.0.0.Final.jar:3.0.0.Final]

    at org.jboss.osgi.framework.internal.FrameworkEventsPlugin.fireServiceEvent(FrameworkEventsPlugin.java:519) [jbosgi-framework-core-2.0.1.Final.jar:2.0.1.Final]

    at org.jboss.osgi.framework.internal.ServiceManagerPlugin.registerService(ServiceManagerPlugin.java:157) [jbosgi-framework-core-2.0.1.Final.jar:2.0.1.Final]

    at org.jboss.osgi.framework.internal.AbstractBundleContext.registerService(AbstractBundleContext.java:305) [jbosgi-framework-core-2.0.1.Final.jar:2.0.1.Final]

    at org.apache.aries.blueprint.container.BlueprintContainerImpl.registerService(BlueprintContainerImpl.java:394)

    at org.apache.aries.blueprint.container.ServiceRecipe.register(ServiceRecipe.java:188)

    at org.apache.aries.blueprint.container.BlueprintContainerImpl.registerServices(BlueprintContainerImpl.java:652)

    at org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:325)

    at org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:228)

    at org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)

    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [rt.jar:1.6.0_24]

    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_24]

    at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_24]

    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) [rt.jar:1.6.0_24]

    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206) [rt.jar:1.6.0_24]

    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_24]

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_24]

    at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_24]

Caused by: org.apache.felix.log.LogException: org.osgi.service.http.NamespaceException: JBAS011964: Invalid resource name: C:\java\jboss-as-7.2.0.Alpha1-SNAPSHOT\standalone\data\osgi-store\bundle-19\rwtcontext_26139062_10836077/rwt-resources

    at org.jboss.as.osgi.httpservice.HttpServiceImpl.registerResources(HttpServiceImpl.java:109)

    at org.eclipse.rap.rwt.osgi.internal.ApplicationReferenceImpl.registerResourceDirectory(ApplicationReferenceImpl.java:190)

    ... 30 more

I thing this problem is a Windows only problem.

[thomas.diesler]

Please monitor https://issues.jboss.org/browse/AS7-5883

What is the client of the HttpService doing to come up with this resource name?

So far I'd agree with the HttpService that this is an invalid name. Perhaps we have a bug in the framework such that it returns an invalid resource name instead of a valid one according to HttpService.registerResources(java.lang.String alias, java.lang.String name, HttpContext context)

[pkilian]

The client calls BundleContext.getDataFile() to get the path and extends it with "/rwt-resources".

I use the same simple example as in https://issues.jboss.org/browse/AS7-5779, if it helps i can attach also the sources.