Looking around found out that the problem was fixed on a newer version
of Spring, so I replaced the old version (2.51) with the latest one
(3.21) but now I get 3 more errors. Im trying to connect 2 cocoon blocks
com.spectron.website.webapp-logger.service and
com.spectron.website.webapp-home.ser
Ok, commented the OSGI stuff out (shouldnt it check if it is an OSGI
bundle before deploying as such?) and now is deploying but with a ton of
Spring errors:
10:04:24,163 DEBUG
[org.springframework.core.io.support.PathMatchingResourcePatternResolver] (MSC
service thread 1-2) Cannot search for
In every jar file :) But I don't think that such procedure will make your
app work. Apparently its not OSGi app :)
It looks to me that your jBoss is starting up in default OSGi mode or is
treating your war file as an OSGi bundle.
You can fix this:
1. either by removing OSGI-specific info in every
In every jar in the war archive? I hope not. Maybe another question:
I'm putting the war in the standalone/deployments directory so it gets
autodeployed. Is there a way to deploy in Jboss and tell it "It is a
war, not osgi bundle"?
On 3/8/2013 2:29 PM, gelo1234 wrote:
Hi Fawzib,
Looks like
Hi Fawzib,
Looks like you are trying to deploy spectron.war as an OSGi
bundle/application, so you need OSGi-compatible META-INF/MANIFEST
file in every .jar
Greetings,
Greg
2013/3/8 Fawzib Rojas
> Anyone tried running a cocoon 2.2 webapp (war) in JBoss 7? I have run a
> simple cocoon 2.2 app (
Anyone tried running a cocoon 2.2 webapp (war) in JBoss 7? I have run a
simple cocoon 2.2 app (just says Cocoon 2.2 runs!) in Glassfish and
Jetty8 but is giving me an error in JBoss 7.1.1
10:45:26,737 DEBUG
[org.jboss.osgi.framework.internal.AbstractFrameworkService] (MSC
service thread 1-1)
