Eclipse Community Forums: Remote Application Platform (RAP) » updated rap from cvs and now get error with deploying in jboss

Home » Eclipse Projects » Remote Application Platform (RAP) » updated rap from cvs and now get error with deploying in jboss

Show: Today's Messages :: Show Polls :: Message Navigator

updated rap from cvs and now get error with deploying in jboss [message #31477]

Wed, 06 June 2007 12:46

Markus rüger

Messages: 369
Registered: July 2009

Senior Member

Hello,

I update RAP from CVS and changed everything in my application to work
properly. In eclipse everything works fine and deployed in a standalone
tomcat everything works fine.
Now, I deploy my application to jboss (as I always did before), I now keep
gett ing the error below and my application does not start.

Any ideas?

Thanx,

Markus

!ENTRY org.eclipse.update.configurator 4 0 2007-06-06 15:38:25.770
!MESSAGE
!STACK 0
org.osgi.framework.BundleException: Exception in
org.eclipse.update.internal.configurator.ConfigurationActiva tor.start() of
bundle org.eclipse.update.configurator.
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.s tartActivator(BundleContextImpl.java:1018)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.s tart(BundleContextImpl.java:974)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWor ker(BundleHost.java:346)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.resu me(AbstractBundle.java:350)
at
org.eclipse.osgi.framework.internal.core.Framework.resumeBun dle(Framework.java:1118)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.r esumeBundles(StartLevelManager.java:634)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.i ncFWSL(StartLevelManager.java:508)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:282)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.d ispatchEvent(StartLevelManager.java:468)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve nt(EventManager.java:195)
at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread .run(EventManager.java:297)
Caused by: org.apache.xerces.parsers.ObjectFactory$ConfigurationError:
Provider org.apache.xerces.parsers.XIncludeAwareParserConfiguration could
not be instantiated: org.apache.xerces.impl.dv.DVFactoryException: DTD
factory class org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend
from DTDDVFactory.
at org.apache.xerces.parsers.ObjectFactory.newInstance(Unknown Source)
at org.apache.xerces.parsers.ObjectFactory.createObject(Unknown Source)
at org.apache.xerces.parsers.ObjectFactory.createObject(Unknown Source)
at org.apache.xerces.parsers.SAXParser.<init>(Unknown Source)
at org.apache.xerces.parsers.SAXParser.<init>(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.<init>(Unknown
Source)
at org.apache.xerces.jaxp.SAXParserImpl.<init>(Unknown Source)
at org.apache.xerces.jaxp.SAXParserFactoryImpl.newSAXParser(Unk nown Source)
at
org.eclipse.update.internal.configurator.ConfigurationParser . <init>(ConfigurationParser.java:49)
at
org.eclipse.update.internal.configurator.PlatformConfigurati on.loadConfig(PlatformConfiguration.java:1061)
at
org.eclipse.update.internal.configurator.PlatformConfigurati on.initializeCurrent(PlatformConfiguration.java:734)
at
org.eclipse.update.internal.configurator.PlatformConfigurati on. <init>(PlatformConfiguration.java:103)
at
org.eclipse.update.internal.configurator.PlatformConfigurati on.startup(PlatformConfiguration.java:688)
at
org.eclipse.update.internal.configurator.ConfigurationActiva tor.getPlatformConfiguration(ConfigurationActivator.java:380 )
at
org.eclipse.update.internal.configurator.ConfigurationActiva tor.initialize(ConfigurationActivator.java:109)
at
org.eclipse.update.internal.configurator.ConfigurationActiva tor.start(ConfigurationActivator.java:69)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$2 .run(BundleContextImpl.java:999)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.s tartActivator(BundleContextImpl.java:993)
... 10 more
Root exception:
org.apache.xerces.parsers.ObjectFactory$ConfigurationError: Provider
org.apache.xerces.parsers.XIncludeAwareParserConfiguration could not be
instantiated: org.apache.xerces.impl.dv.DVFactoryException: DTD factory
class org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
DTDDVFactory.
at org.apache.xerces.parsers.ObjectFactory.newInstance(Unknown Source)
at org.apache.xerces.parsers.ObjectFactory.createObject(Unknown Source)
at org.apache.xerces.parsers.ObjectFactory.createObject(Unknown Source)
at org.apache.xerces.parsers.SAXParser.<init>(Unknown Source)
at org.apache.xerces.parsers.SAXParser.<init>(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.<init>(Unknown
Source)
at org.apache.xerces.jaxp.SAXParserImpl.<init>(Unknown Source)
at org.apache.xerces.jaxp.SAXParserFactoryImpl.newSAXParser(Unk nown Source)
at
org.eclipse.update.internal.configurator.ConfigurationParser . <init>(ConfigurationParser.java:49)
at
org.eclipse.update.internal.configurator.PlatformConfigurati on.loadConfig(PlatformConfiguration.java:1061)
at
org.eclipse.update.internal.configurator.PlatformConfigurati on.initializeCurrent(PlatformConfiguration.java:734)
at
org.eclipse.update.internal.configurator.PlatformConfigurati on. <init>(PlatformConfiguration.java:103)
at
org.eclipse.update.internal.configurator.PlatformConfigurati on.startup(PlatformConfiguration.java:688)
at
org.eclipse.update.internal.configurator.ConfigurationActiva tor.getPlatformConfiguration(ConfigurationActivator.java:380 )
at
org.eclipse.update.internal.configurator.ConfigurationActiva tor.initialize(ConfigurationActivator.java:109)
at
org.eclipse.update.internal.configurator.ConfigurationActiva tor.start(ConfigurationActivator.java:69)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$2 .run(BundleContextImpl.java:999)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.s tartActivator(BundleContextImpl.java:993)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.s tart(BundleContextImpl.java:974)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWor ker(BundleHost.java:346)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.resu me(AbstractBundle.java:350)
at
org.eclipse.osgi.framework.internal.core.Framework.resumeBun dle(Framework.java:1118)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.r esumeBundles(StartLevelManager.java:634)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.i ncFWSL(StartLevelManager.java:508)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:282)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.d ispatchEvent(StartLevelManager.java:468)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve nt(EventManager.java:195)
at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread .run(EventManager.java:297)

Report message to a moderator

Re: updated rap from cvs and now get error with deploying in jboss [message #31550 is a reply to message #31477]

Wed, 06 June 2007 14:07

Eclipse User

Originally posted by: fappel.innoopract.com

Hi,

that's strange since as far as I know the servlet engine of JBoss is also a
Tomcat. Maybe the old OSGi instance didn't shut down properly. But that's
just a wild guess...

Ciao
Frank

"Markus Kr

Report message to a moderator

Re: updated rap from cvs and now get error with deploying in jboss [message #32425 is a reply to message #31550]

Tue, 12 June 2007 13:09

Markus rüger

Messages: 369
Registered: July 2009

Senior Member

Hi,

that was not the problem :-( and I couldn't figure it out yet.

Is it possible to exclude the org.eclipse.update.configurator from the
deployment, or is it definitely needed?
I tried to exclude it from the Demo, but the I get the errors I attached.

The osgi status looks like this:

Framework is launched.

id State Bundle
0 ACTIVE org.eclipse.osgi_3.3.0.v20070530
1 ACTIVE org.eclipse.core.commands_3.3.0.I20070523-1500
2 ACTIVE org.eclipse.core.contenttype_3.2.100.v20070319
3 ACTIVE org.eclipse.core.expressions_3.3.0.v20070531-1300
4 ACTIVE org.eclipse.core.jobs_3.3.0.v20070423
5 ACTIVE org.eclipse.core.runtime_3.3.100.v20070530
6 ACTIVE org.eclipse.equinox.app_1.0.0.v20070423
7 ACTIVE org.eclipse.equinox.common_3.3.0.v20070426
8 INSTALLED org.eclipse.equinox.http.registry_1.0.0.200706121448
9 INSTALLED
org.eclipse.equinox.http.servletbridge_1.0.0.200706121448
10 INSTALLED org.eclipse.equinox.http.servlet_1.0.0.200706121448
11 ACTIVE org.eclipse.equinox.preferences_3.2.100.v20070522
12 ACTIVE org.eclipse.equinox.registry_3.3.0.v20070522
13 ACTIVE org.eclipse.osgi.services_3.1.200.v20070531
14 INSTALLED org.eclipse.rap.demo_1.0.0.200706121448
15 INSTALLED org.eclipse.rap.jface_1.0.0.200706121448
16 INSTALLED org.eclipse.rap.rwt_1.0.0.200706121448
17 INSTALLED org.eclipse.rap.ui.workbench_1.0.0.200706121448
18 INSTALLED org.eclipse.rap.w4t_1.0.0.200706121448

If I include the org.eclipse.update.configurator everthing works well...

Any idea???

Regards,

Markus

"Frank Appel" <fappel@innoopract.com> schrieb im Newsbeitrag
news:f46f2v$1rp$1@build.eclipse.org...
> Hi,
>
> that's strange since as far as I know the servlet engine of JBoss is also
> a
> Tomcat. Maybe the old OSGi instance didn't shut down properly. But that's
> just a wild guess...
>
>
> Ciao
> Frank
>
>
> "Markus Kr