[
https://issues.apache.org/jira/browse/EXTCDI-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033954#comment-13033954
]
Jakob Korherr commented on EXTCDI-178:
--------------------------------------
Thanks for taking care of this, guys.
Actually my first thought was that Mojarra may do a wrong bval availability
check, so that's great.
> however, we can add bv in any case.
I am not a fan of this. The archetype should be as simple as possible. However,
we could provide a bval archetype or a config property to enable it when the
archetype is generated, but not by default!
> archetype is broken for mojarra
> -------------------------------
>
> Key: EXTCDI-178
> URL: https://issues.apache.org/jira/browse/EXTCDI-178
> Project: MyFaces CODI
> Issue Type: Bug
> Reporter: Imre Osswald
> Assignee: Jakob Korherr
> Priority: Trivial
> Attachments: pom.xml.zip
>
>
> mvn clean jetty:run-exploded -PjettyConfig -Djsf=mojarra
> leads to an exception because the bean-validation impl. is missing and
> mojarra behaves differently.
> To reproduce:
> * Use the archetype (currently) #11
> * mvn clean jetty:run-exploded -PjettyConfig -Djsf=mojarra
> * Enter something into the input-field and submit the form.
> I've attached a pom that depends on org.apache.bval.bval-core and bval-jsr303
> in the mojarra profile (not sure if both are needed?)
> We should maybe also add a commented section, that has the dependencies for
> using bval/extval, so it is easy to add the Impl.
> Imre
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
