You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bval.apache.org by "Donald Woods (JIRA)" <ji...@apache.org> on 2010/07/09 20:48:50 UTC
[jira] Reopened: (BVAL-77) bval-guice needs the optional
bval-xstream module
[ https://issues.apache.org/jira/browse/BVAL-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods reopened BVAL-77:
------------------------------
Problem is actual caused by BVAL-75, in that method signatures were changed to return XMLMetaBeanManager, which now causes bval-xstream to be required, which we don't want.
> bval-guice needs the optional bval-xstream module
> -------------------------------------------------
>
> Key: BVAL-77
> URL: https://issues.apache.org/jira/browse/BVAL-77
> Project: BeanValidation
> Issue Type: Bug
> Components: build
> Affects Versions: 0.2-incubating
> Reporter: Donald Woods
> Assignee: Donald Woods
> Fix For: 0.2-incubating
>
>
> After recent changes in BVAL-75 (seem unrelated though....) the bval-guice module junits failed due to -
> Error injecting constructor, java.lang.NoClassDefFoundError: org/apache/bval/xml/XMLMetaBeanManager
> at org.apache.bval.guice.ValidatorProvider.<init>(ValidatorProvider.java:45)
> while locating org.apache.bval.guice.ValidatorProvider
> while locating javax.validation.Validator
> for field at org.apache.bval.guice.ValidateMethodInterceptor.validator(ValidateMethodInterceptor.java:53)
> at org.apache.bval.guice.ValidationModule.configure(ValidationModule.java:60)
> which is now in the optional bval-xstream module.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.