[jboss-jira] [JBoss JIRA] Commented: (JBSEAM-358) Adding core.FacesMessages requires JSF libraries to compile component

[Gavin King (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBSEAM-358?page=comments#action_12343876 ] 
            
Gavin King commented on JBSEAM-358:
-----------------------------------

No, this is not the reason for it. FacesMessages is totally dependent to JSF for its functionality and even its API.

> Adding core.FacesMessages requires JSF libraries to compile component
> ---------------------------------------------------------------------
>
>                 Key: JBSEAM-358
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-358
>             Project: JBoss Seam
>          Issue Type: Bug
>            Reporter: Christian Bauer
>            Priority: Minor
>
> I have this in a Seam component:
>     // For error messages
>     @In(create=true)
>     private FacesMessages facesMessages;
> This is org.jboss.seam.core.FacesMessages. It doesn't extend anything from JSF but I still can't compile my Seam component without the JSF stubs on the classpath:
> /Users/turin/work/local/lab8/modules/beans/src/auction/beans/PlaceBidImpl.java
>     Error:Error:line (112)cannot access javax.faces.application.FacesMessage
> file javax/faces/application/FacesMessage.class not found
> This is inconvenient because this is the only JSF compile-time dependency in all of my Seam components and I have to add the JSF libs to my compile classpath just for this. I don't really know why this is required... because of the static methods in FacesMessages?
> In any case, it would be nice to be able to send JSF messages without binding the component to JSF and I initially thought that this was the usecase for core.FacesMessages in Seam.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira