You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bval.apache.org by "Roman Stumm (JIRA)" <ji...@apache.org> on 2010/06/18 08:09:23 UTC

[jira] Work started: (BVAL-69) make dependency to com.thoughtworks.xstream of bval-core optional or obsolete

     [ https://issues.apache.org/jira/browse/BVAL-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on BVAL-69 started by Roman Stumm.

> make dependency to com.thoughtworks.xstream of bval-core optional or obsolete
> -----------------------------------------------------------------------------
>
>                 Key: BVAL-69
>                 URL: https://issues.apache.org/jira/browse/BVAL-69
>             Project: BeanValidation
>          Issue Type: Improvement
>          Components: jsr303
>    Affects Versions: 0.2-incubating
>            Reporter: Roman Stumm
>            Assignee: Roman Stumm
>
> currently bval-core needs xstream to compile, although xstream is NOT used to marshal XML when working with bval-jsr303 xml-descriptors. Only proprietary xml-support in bval-core uses xstream.
> To minimize the number of different XML-frameworks (bval-jsr303 has a dependency to jaxb, which is OK, because this is part of the JDK) and to minimize the number of dependencies in general, we should refactor the core-classes to get rid of the mandatory xstream dependency.
> A first simple way would be to remove all XStream annotation in org.apache.bval.xml and instead use the programmatic API of XStream to define the mapping and move the xstream-dependent code to a new optional mvn-module.
> Another way could be to change the code from using XStream to using jaxb or to remove the code (if we do not want to keep the proprietary functionality, which is not required for the jsr303 features)
> Any other ideas??

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.