You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Jakob Korherr (JIRA)" <de...@myfaces.apache.org> on 2011/02/22 10:56:38 UTC

[jira] Reopened: (MYFACES-3044) Resource jsf.js not found when using the OSGi bundle

     [ https://issues.apache.org/jira/browse/MYFACES-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jakob Korherr reopened MYFACES-3044:
------------------------------------

      Assignee:     (was: Leonardo Uribe)

I disagree that this is the expected behavior.

Users will use our OSGi-bundle also if ProjectStage==Development and not only in Production. So if we do not fix it, users would have to use ProjectStage==Production for development too and that's just wrong!

Also it should be really easy to fix. From the dev-list: add META-INF.internal-resources.javax.faces and META-INF.services to the exported packages in MANIFEST.MF.

> Resource jsf.js not found when using the OSGi bundle
> ----------------------------------------------------
>
>                 Key: MYFACES-3044
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3044
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions: 2.0.3
>            Reporter: Clovis
>
> First there is a
> WARNING: Resource referenced by resourceName jsf.js and libraryName javax.faces not found in call to ResourceHandler.createResource. It will be silenty ignored.
> and later a NullPointerException
> Using javax.faces.PROJECT_STAGE=Development, the class loader was trying to load META-INF/internal-resources/javax.faces/jsf-uncompressed-full.js (so I added the "package" META-INF.internal-resources.javax.faces to the list of exported packages of myfaces-bundle.jar). But then I changed it from Development to Production, and myfaces tried to load something else (and I decided to write a bug).

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira