You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org> on 2010/03/17 22:53:27 UTC
[jira] Created: (MYFACES-2613) ExternalSpecifications has an import
from javax.validation api, and this one should be optional
ExternalSpecifications has an import from javax.validation api, and this one should be optional
-----------------------------------------------------------------------------------------------
Key: MYFACES-2613
URL: https://issues.apache.org/jira/browse/MYFACES-2613
Project: MyFaces Core
Issue Type: Bug
Components: JSR-314
Affects Versions: 2.0.0-beta-3
Reporter: Leonardo Uribe
Assignee: Leonardo Uribe
In a environment without javax.validation api, if bean validation is used, a ClassNotFoundException is thrown because ExternalSpecifications has an import from javax.validation api. The solution is create another class that has this only import, so ExternalSpecifications could be loaded on the classpath without the presence of javax.validation api.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (MYFACES-2613) ExternalSpecifications has an
import from javax.validation api, and this one should be optional
Posted by "Jakob Korherr (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/MYFACES-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jakob Korherr reopened MYFACES-2613:
------------------------------------
Assignee: Jakob Korherr (was: Leonardo Uribe)
_ExternalSpecifications is also present in javax.faces.component package, so the changes have to be applied here too!
> ExternalSpecifications has an import from javax.validation api, and this one should be optional
> -----------------------------------------------------------------------------------------------
>
> Key: MYFACES-2613
> URL: https://issues.apache.org/jira/browse/MYFACES-2613
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-314
> Affects Versions: 2.0.0-beta-3
> Reporter: Leonardo Uribe
> Assignee: Jakob Korherr
> Fix For: 2.0.0-beta-3
>
>
> In a environment without javax.validation api, if bean validation is used, a ClassNotFoundException is thrown because ExternalSpecifications has an import from javax.validation api. The solution is create another class that has this only import, so ExternalSpecifications could be loaded on the classpath without the presence of javax.validation api.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2613) ExternalSpecifications has an
import from javax.validation api, and this one should be optional
Posted by "Jakob Korherr (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/MYFACES-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846691#action_12846691 ]
Jakob Korherr commented on MYFACES-2613:
----------------------------------------
We should really try to get rid of the redundancy here!
> ExternalSpecifications has an import from javax.validation api, and this one should be optional
> -----------------------------------------------------------------------------------------------
>
> Key: MYFACES-2613
> URL: https://issues.apache.org/jira/browse/MYFACES-2613
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-314
> Affects Versions: 2.0.0-beta-3
> Reporter: Leonardo Uribe
> Assignee: Jakob Korherr
> Fix For: 2.0.0-beta-3
>
>
> In a environment without javax.validation api, if bean validation is used, a ClassNotFoundException is thrown because ExternalSpecifications has an import from javax.validation api. The solution is create another class that has this only import, so ExternalSpecifications could be loaded on the classpath without the presence of javax.validation api.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MYFACES-2613) ExternalSpecifications has an
import from javax.validation api, and this one should be optional
Posted by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/MYFACES-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leonardo Uribe resolved MYFACES-2613.
-------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0-beta-3
> ExternalSpecifications has an import from javax.validation api, and this one should be optional
> -----------------------------------------------------------------------------------------------
>
> Key: MYFACES-2613
> URL: https://issues.apache.org/jira/browse/MYFACES-2613
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-314
> Affects Versions: 2.0.0-beta-3
> Reporter: Leonardo Uribe
> Assignee: Leonardo Uribe
> Fix For: 2.0.0-beta-3
>
>
> In a environment without javax.validation api, if bean validation is used, a ClassNotFoundException is thrown because ExternalSpecifications has an import from javax.validation api. The solution is create another class that has this only import, so ExternalSpecifications could be loaded on the classpath without the presence of javax.validation api.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MYFACES-2613) ExternalSpecifications has an
import from javax.validation api, and this one should be optional
Posted by "Jakob Korherr (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/MYFACES-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jakob Korherr resolved MYFACES-2613.
------------------------------------
Resolution: Fixed
> ExternalSpecifications has an import from javax.validation api, and this one should be optional
> -----------------------------------------------------------------------------------------------
>
> Key: MYFACES-2613
> URL: https://issues.apache.org/jira/browse/MYFACES-2613
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-314
> Affects Versions: 2.0.0-beta-3
> Reporter: Leonardo Uribe
> Assignee: Jakob Korherr
> Fix For: 2.0.0-beta-3
>
>
> In a environment without javax.validation api, if bean validation is used, a ClassNotFoundException is thrown because ExternalSpecifications has an import from javax.validation api. The solution is create another class that has this only import, so ExternalSpecifications could be loaded on the classpath without the presence of javax.validation api.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.