[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008789#comment-13008789
]
Scott O'Bryan commented on PORTLETBRIDGE-199:
---------------------------------------------
I'm fine with this in principal, but it's important to keep the API of the
bridge as lean as possible. This belongs in the impl or in an external
utilities project. The PortletBridge's sole purpose should be to facilitate
running a JSF application in a portal and I don't see how this API accomplishes
that.
> Proposal for 3.0 API: BridgeUtil.getClassPathResourceAsString(String
> resourcePath)
> ----------------------------------------------------------------------------------
>
> Key: PORTLETBRIDGE-199
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-199
> Project: MyFaces Portlet Bridge
> Issue Type: New Feature
> Components: General
> Affects Versions: 3.0.0
> Reporter: Neil Griffin
> Assignee: Michael Freedman
>
> Proposal is to introduce a utility method that can load the contents of
> classpath resources (like META-INF/services/filename) into a String.
> This will help the API with discovery of the implementation of
> BridgeFactoryFinder specified in PORTLETBRIDGE-189
> See the following class for more details:
> http://svn.portletfaces.org/svn/portletfaces/bridge/portletfaces-bridge-api/trunk/src/main/java/org/portletfaces/bridge/BridgeUtil.java
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
