You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "Francesco Chicchiriccò (JIRA)" <ji...@apache.org> on 2014/06/23 17:43:24 UTC
[jira] [Updated] (SYNCOPE-514) Core doesn't deploy on Glassfish
[ https://issues.apache.org/jira/browse/SYNCOPE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Chicchiriccò updated SYNCOPE-514:
-------------------------------------------
Description:
Now, trying to deploy the core on Glassfish 4 the result is:
[17:07:50.688][info][talledLocalContainer] remote failure: Error occurred during deployment: Exception while loading the app : java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'validator' defined in file [/tmp/trunk/core/target/syncope-core-test/WEB-INF/classes/persistenceContext.xml]: Invocation of init method failed; nested exception is java.lang.AbstractMethodError: org.apache.bval.jsr303.ConfigurationImpl.getDefaultParameterNameProvider()Ljavax/validation/ParameterNameProvider;. Please see server.log for more details.
I have been able to deploy it deleting bval dependencies and replacing them with hibernate-validator libraries.
Considering that SYNCOPE-46 suggests to replace BVal with Hibernate Validator, what do you think to replace it now?
was:
Now, trying to deploy the core on Glassfish 4 the result is:
[17:07:50.688][info][talledLocalContainer] remote failure: Error occurred during deployment: Exception while loading the app : java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'validator' defined in file [/tmp/trunk/core/target/syncope-core-test/WEB-INF/classes/persistenceContext.xml]: Invocation of init method failed; nested exception is java.lang.AbstractMethodError: org.apache.bval.jsr303.ConfigurationImpl.getDefaultParameterNameProvider()Ljavax/validation/ParameterNameProvider;. Please see server.log for more details.
I have been able to deploy it deleting bval dependencies and replacing them with hibernate-validator libraries.
Considering that <a href="https://issues.apache.org/jira/browse/SYNCOPE-461">SYNCOPE-461</a> issue suggests to replace the bval libreries, what do you think to replace it now?
Environment: Glassfish 4
Fix Version/s: 1.2.0
> Core doesn't deploy on Glassfish
> --------------------------------
>
> Key: SYNCOPE-514
> URL: https://issues.apache.org/jira/browse/SYNCOPE-514
> Project: Syncope
> Issue Type: Bug
> Components: core
> Affects Versions: 1.2.0
> Environment: Glassfish 4
> Reporter: Massimiliano Perrone
> Assignee: Massimiliano Perrone
> Fix For: 1.2.0
>
>
> Now, trying to deploy the core on Glassfish 4 the result is:
> [17:07:50.688][info][talledLocalContainer] remote failure: Error occurred during deployment: Exception while loading the app : java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'validator' defined in file [/tmp/trunk/core/target/syncope-core-test/WEB-INF/classes/persistenceContext.xml]: Invocation of init method failed; nested exception is java.lang.AbstractMethodError: org.apache.bval.jsr303.ConfigurationImpl.getDefaultParameterNameProvider()Ljavax/validation/ParameterNameProvider;. Please see server.log for more details.
> I have been able to deploy it deleting bval dependencies and replacing them with hibernate-validator libraries.
> Considering that SYNCOPE-46 suggests to replace BVal with Hibernate Validator, what do you think to replace it now?
--
This message was sent by Atlassian JIRA
(v6.2#6252)