tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Miles, Eric (CONT)" <Eric.Mi...@capitalone.com>
Subject Re: Exclude certain aspects of TomEE?
Date Wed, 05 Feb 2014 14:30:38 GMT
Our problem with bval is that it's on 1.0 spec and we're using the 1.1
spec in our app.  How do I circumvent this issue:

SEVERE: Unable to deploy collapsed ear in war
StandardEngine[Catalina].StandardHost[localhost].StandardContext[/location-
web]
org.apache.openejb.OpenEJBException: Creating application failed:
/Users/ovh781/Workspaces/mobile-services/location-module/location-web/targe
t/apache-tomee/webapps/location-web:
javax.validation.spi.ConfigurationState.getParameterNameProvider()Ljavax/va
lidation/ParameterNameProvider;
	at 
org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.
java:897)
	at 
org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.
java:612)
	at 
org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBui
lder.java:1205)
	at 
org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(TomcatWebAppBu
ilder.java:1051)
	at 
org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListen
erSupport.java:127)
	at 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppo
rt.java:119)
	at 
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.jav
a:90)
	at 
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java
:5322)
	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:633)
	at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:983)
	at 
org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1660)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
	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.j
ava:895)
	at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:
918)
	at java.lang.Thread.run(Thread.java:680)


I attempted excluding the relevant bval libraries from tomee by using
<lib>remove:bval</lib> but that just caused other problems.

Also, you mentioned tomee-embeddedÅ I assumed I was using that by
leveraging the Maven plugin and not providing an install base for tomee.
Is there a different way?  Thanks again for any help.

Eric




On 2/4/14 4:52 PM, "Romain Manni-Bucau" <rmannibucau@gmail.com> wrote:

>Hi
>
>for jaxrs see conf/conf.d/cxf-rs.properties and add disabled = true.
>
>for bval it should use war impl first but still container API (by spec).
>
>Jersey and spring should work, if not just propose us a sample
>reproducing the issue.
>
>PS: using tomee-embedded can be interesting for you and would ease
>classpath handling IMO (depend a bit on your app)
>Romain Manni-Bucau
>Twitter: @rmannibucau
>Blog: http://rmannibucau.wordpress.com/
>LinkedIn: http://fr.linkedin.com/in/rmannibucau
>Github: https://github.com/rmannibucau
>
>
>
>2014-02-04 Miles, Eric (CONT) <Eric.Miles@capitalone.com>:
>> I'm really new to OpenEJB and the use of TomEE so please excuse this if
>>it's a dumb question, but I didn't find what I was looking for in the
>>documentation.
>>
>> We currently use Jetty for embedded integration testing with our Maven
>>build.  Our production deployments are to another, extremely expensive
>>application server so our use of Jetty is limited to only
>>development/integration testing.  We have a need to deploy other JEE
>>artifacts into Jetty (other wars and a few ears containing EJBs) and we
>>have done as much with the inclusion of ActiveMQ and other open source
>>options.  Rather than do all of this, we're looking at leveraging TomEE+
>>since this all comes baked in.  However, we're having difficulties
>>getting our stuff deployed due to conflicts.  Most of our artifacts are
>>Jersey2+Spring applications, leveraging things such JSR 349 with the
>>Hibernate Validator, etc.
>>
>> My question is, is it possible to turn off TomEE for certain things
>>like it's built in support for JAX-RS or bean validation?  Or is there a
>>way to tell TomEE to use the class/library in a war/ear over what is on
>>the container's class path?  If so, how is this accomplished?
>>
>> Thanks so much,
>> Eric
>> ________________________________________________________
>>
>> The information contained in this e-mail is confidential and/or
>>proprietary to Capital One and/or its affiliates. The information
>>transmitted herewith is intended only for use by the individual or
>>entity to which it is addressed.  If the reader of this message is not
>>the intended recipient, you are hereby notified that any review,
>>retransmission, dissemination, distribution, copying or other use of, or
>>taking of any action in reliance upon this information is strictly
>>prohibited. If you have received this communication in error, please
>>contact the sender and delete the material from your computer.

________________________________________________________

The information contained in this e-mail is confidential and/or proprietary to Capital One
and/or its affiliates. The information transmitted herewith is intended only for use by the
individual or entity to which it is addressed.  If the reader of this message is not the intended
recipient, you are hereby notified that any review, retransmission, dissemination, distribution,
copying or other use of, or taking of any action in reliance upon this information is strictly
prohibited. If you have received this communication in error, please contact the sender and
delete the material from your computer.


Mime
View raw message