Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » EclipseLink » ValidationException while deployment on Tomcat with enabled TomcatSecurity
icon5.gif  ValidationException while deployment on Tomcat with enabled TomcatSecurity [message #558812] Tue, 14 September 2010 10:15 Go to next message
Christoph Eickhoff is currently offline Christoph Eickhoff
Messages: 2
Registered: September 2010
Junior Member
We are using a Tomcat 5.5 on a Debian lenny system. The Tomcat installatiin has security turned on.

When we are deploying our web application onto the server, we get the following exception:

org.eclipse.persistence.exceptions.ValidationException
Exception Description: The mapping element [bordersRight] for the class [class de.unikassel.vinylit.client.datamodel.FacadeElement] has an unsupported collection type [class java.util.ArrayList]. Only Set, List, Map and Collection are supported.
at org.eclipse.persistence.exceptions.ValidationException.inval idCollectionTypeForRelationship(ValidationException.java:113 2)
at org.eclipse.persistence.internal.jpa.metadata.accessors.mapp ings.CollectionAccessor.process(CollectionAccessor.java:588)
at org.eclipse.persistence.internal.jpa.metadata.accessors.mapp ings.OneToManyAccessor.process(OneToManyAccessor.java:119)
at org.eclipse.persistence.internal.jpa.metadata.accessors.mapp ings.RelationshipAccessor.processRelationship(RelationshipAc cessor.java:625)
at org.eclipse.persistence.internal.jpa.metadata.MetadataProjec t.processRelationshipAccessors(MetadataProject.java:1239)
at org.eclipse.persistence.internal.jpa.metadata.MetadataProjec t.processStage3(MetadataProject.java:1528)
at org.eclipse.persistence.internal.jpa.metadata.MetadataProces sor.processORMMetadata(MetadataProcessor.java:475)
at org.eclipse.persistence.internal.jpa.deployment.PersistenceU nitProcessor.processORMetadata(PersistenceUnitProcessor.java :441)
at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl. predeploy(EntityManagerSetupImpl.java:959)
at org.eclipse.persistence.internal.jpa.deployment.JPAInitializ er.callPredeploy(JPAInitializer.java:88)
at org.eclipse.persistence.jpa.PersistenceProvider.createEntity ManagerFactory(PersistenceProvider.java:124)
at org.eclipse.persistence.jpa.PersistenceProvider.createEntity ManagerFactory(PersistenceProvider.java:65)
at javax.persistence.Persistence.createEntityManagerFactory(Unk nown Source)
at javax.persistence.Persistence.createEntityManagerFactory(Unk nown Source)
at de.unikassel.vinylit.server.DataExchangeServiceImpl.<init>(DataExchangeServiceImpl.java:39)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Nativ e Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Native ConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(De legatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:5 13)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at org.apache.catalina.core.StandardWrapper.loadServlet(Standar dWrapper.java:1089)
at org.apache.catalina.core.StandardWrapper.allocate(StandardWr apper.java:791)
at org.apache.catalina.core.StandardWrapperValve.invoke(Standar dWrapperValve.java:127)
at org.apache.catalina.core.StandardContextValve.invoke(Standar dContextValve.java:172)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHo stValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepo rtValve.java:117)
at org.apache.catalina.core.StandardEngineValve.invoke(Standard EngineValve.java:108)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAd apter.java:174)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler. java:200)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.ja va:283)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java :773)
at org.apache.jk.common.ChannelSocket.processConnection(Channel Socket.java:703)
at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(Ch annelSocket.java:895)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.ru n(ThreadPool.java:689)
at java.lang.Thread.run(Thread.java:619)



Using the same server with security turned off, everything works fine, no exceptions are thrown.
What do we do wrong?

Searching the web for this problem didn't yield to any solutions.
Hoping for help...

Christoph
Re: ValidationException while deployment on Tomcat with enabled TomcatSecurity [message #559418 is a reply to message #558812] Thu, 16 September 2010 11:02 Go to previous message
James Sutherland is currently offline James Sutherland
Messages: 1939
Registered: July 2009
Location: Ottawa, Canada
Senior Member

As the error states you need to use a collection interface not an impl.

Not sure why it is affect by security. We do allow impls when the fetch type is EAGER, so that may be related. But in general you should use the interface.


James : Wiki : Book : Blog : Twitter
Previous Topic:Eclipselink, JavaSE and multiple JDBC datastores
Next Topic:[SOLVED]Eclipselink crashing after throw a Database Excetion
Goto Forum:
  


Current Time: Wed Apr 16 09:48:23 EDT 2014

Powered by FUDForum. Page generated in 0.01689 seconds