You are viewing a plain text version of this content. The canonical link for it is here.
Posted to adffaces-issues@incubator.apache.org by "Gary Kind (JIRA)" <ad...@incubator.apache.org> on 2006/09/18 20:51:19 UTC
[jira] Created: (ADFFACES-183)
org.apache.myfaces.trinidad.model.XMLMenuModel$MenuContentHandler file was
not put in META-INF/services directory
org.apache.myfaces.trinidad.model.XMLMenuModel$MenuContentHandler file was not put in META-INF/services directory
-----------------------------------------------------------------------------------------------------------------
Key: ADFFACES-183
URL: http://issues.apache.org/jira/browse/ADFFACES-183
Project: MyFaces ADF-Faces
Issue Type: Bug
Reporter: Gary Kind
Attachments: trunk.patch
In order for the XMLMenuModel (on the API side) to use and call into the MenuContentHandlerImpl ( on the trinidadinternal side) the file listed in the summary, org.apache.myfaces.trinidad.model.XMLMenuModel$MenuContentHandler, must be present in the META-INF/services directory of the api jar file (or any jar file in the Classpath, as per the Services API). Currently, it is not present and the XMLMenuModel will not work without it. This can be worked around by putting this file in any jar file that is in the user's Classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (ADFFACES-183)
org.apache.myfaces.trinidad.model.XMLMenuModel$MenuContentHandler file was
not put in META-INF/services directory
Posted by "Gary Kind (JIRA)" <ad...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/ADFFACES-183?page=all ]
Gary Kind updated ADFFACES-183:
-------------------------------
Attachment: trunk.patch
> org.apache.myfaces.trinidad.model.XMLMenuModel$MenuContentHandler file was not put in META-INF/services directory
> -----------------------------------------------------------------------------------------------------------------
>
> Key: ADFFACES-183
> URL: http://issues.apache.org/jira/browse/ADFFACES-183
> Project: MyFaces ADF-Faces
> Issue Type: Bug
> Reporter: Gary Kind
> Attachments: trunk.patch
>
>
> In order for the XMLMenuModel (on the API side) to use and call into the MenuContentHandlerImpl ( on the trinidadinternal side) the file listed in the summary, org.apache.myfaces.trinidad.model.XMLMenuModel$MenuContentHandler, must be present in the META-INF/services directory of the api jar file (or any jar file in the Classpath, as per the Services API). Currently, it is not present and the XMLMenuModel will not work without it. This can be worked around by putting this file in any jar file that is in the user's Classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (ADFFACES-183)
org.apache.myfaces.trinidad.model.XMLMenuModel$MenuContentHandler file was
not put in META-INF/services directory
Posted by "Adam Winer (JIRA)" <ad...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/ADFFACES-183?page=all ]
Adam Winer resolved ADFFACES-183.
---------------------------------
Resolution: Fixed
Fixed - put the services file in the impl jar, not the api.
> org.apache.myfaces.trinidad.model.XMLMenuModel$MenuContentHandler file was not put in META-INF/services directory
> -----------------------------------------------------------------------------------------------------------------
>
> Key: ADFFACES-183
> URL: http://issues.apache.org/jira/browse/ADFFACES-183
> Project: MyFaces ADF-Faces
> Issue Type: Bug
> Reporter: Gary Kind
> Attachments: trunk.patch
>
>
> In order for the XMLMenuModel (on the API side) to use and call into the MenuContentHandlerImpl ( on the trinidadinternal side) the file listed in the summary, org.apache.myfaces.trinidad.model.XMLMenuModel$MenuContentHandler, must be present in the META-INF/services directory of the api jar file (or any jar file in the Classpath, as per the Services API). Currently, it is not present and the XMLMenuModel will not work without it. This can be worked around by putting this file in any jar file that is in the user's Classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (ADFFACES-183)
org.apache.myfaces.trinidad.model.XMLMenuModel$MenuContentHandler file was
not put in META-INF/services directory
Posted by "Matthias Weßendorf (JIRA)" <ad...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/ADFFACES-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias Weßendorf updated ADFFACES-183:
----------------------------------------
Fix Version/s: 1.0.0-incubating-core
Affects Version/s: 1.0.0-incubating-core
> org.apache.myfaces.trinidad.model.XMLMenuModel$MenuContentHandler file was not put in META-INF/services directory
> -----------------------------------------------------------------------------------------------------------------
>
> Key: ADFFACES-183
> URL: https://issues.apache.org/jira/browse/ADFFACES-183
> Project: MyFaces ADF-Faces
> Issue Type: Bug
> Affects Versions: 1.0.0-incubating-core
> Reporter: Gary Kind
> Fix For: 1.0.0-incubating-core
>
> Attachments: trunk.patch
>
>
> In order for the XMLMenuModel (on the API side) to use and call into the MenuContentHandlerImpl ( on the trinidadinternal side) the file listed in the summary, org.apache.myfaces.trinidad.model.XMLMenuModel$MenuContentHandler, must be present in the META-INF/services directory of the api jar file (or any jar file in the Classpath, as per the Services API). Currently, it is not present and the XMLMenuModel will not work without it. This can be worked around by putting this file in any jar file that is in the user's Classpath.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.