hmm

worked on it yesterday evening, think i managed to make resources in
META-INF/context.xml working

can you give more details on your config please?

*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*




2012/10/8 andymil <[email protected]>

> Hello,
>
> Although I'm able to successfully deploy Jasper Report Server .war file on
> Tomcat 7, it fails when I try to do the same on TomEE (either version, I
> tried 1.1 and 1.5). It fails also when I attempt to deploy it on Tomcat 7
> along with OpenEJB .war. Here's the error I'm getting in all cases:
>
> INFO: Configuring enterprise application:
> C:\Java\apache-tomee-webprofile-1.5.1\webapps\jasperserver
> Oct 8, 2012 9:49:36 AM org.apache.tomee.catalina.TomcatWebAppBuilder
> startInternal
> SEVERE: Unable to deploy collapsed ear in war
>
> StandardEngine[Catalina].StandardHost[localhost].StandardContext[/jasperserver]
> org.apache.openejb.OpenEJBException: No provider available for resource-ref
> 'null' of type 'com.jaspersoft.jasperserver.remote.services.JobsService'
> for
> 'localhost/jasperserver'.
>         at
>
> org.apache.openejb.config.AutoConfig.autoCreateResource(AutoConfig.java:1770)
>         at
> org.apache.openejb.config.AutoConfig.getResourceId(AutoConfig.java:1763)
>         at
> org.apache.openejb.config.AutoConfig.getResourceId(AutoConfig.java:1714)
>         at
> org.apache.openejb.config.AutoConfig.processJndiRefs(AutoConfig.java:728)
>         at org.apache.openejb.config.AutoConfig.deploy(AutoConfig.java:702)
>         at org.apache.openejb.config.AutoConfig.deploy(AutoConfig.java:195)
>         at
>
> org.apache.openejb.config.ConfigurationFactory$Chain.deploy(ConfigurationFactory.java:363)
>         at
>
> org.apache.openejb.config.ConfigurationFactory.configureApplication(ConfigurationFactory.java:850)
>         at
>
> org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBuilder.java:825)
>         at
>
> org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(TomcatWebAppBuilder.java:780)
>         at
>
> org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:118)
>         at
>
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
>         at
>
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
>         at
>
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5173)
>         at
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>         at
>
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
>         at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
>         at
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:618)
>         at
>
> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1100)
>         at
>
> org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1618)
>         at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>         at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>         at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>         at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>         at java.lang.Thread.run(Thread.java:662)
>
> so it looks like on TomEE the TomcatWebAppBuilder is responsible for
> deploying web apps, but for some reason it is not working the way the
> regular Tomcat does in this scenario...
>
> any help is greatly appreciated!
>
>
>
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/Unable-to-deploy-Jasper-Reports-Server-on-TomEE-tp4657878.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>

Reply via email to