[ https://issues.jboss.org/browse/AS7-4568?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on AS7-4568: ---------------------------------- Can you describe exactly what it is you tried, what the expected result is, and what the actual result is? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-4568?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on AS7-4568: ---------------------------------- How did you add the dependency? Did you use the {{MANIFEST.MF}} "Dependency:" mechanism or {{jboss-deployment-structure.xml}}? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-4568?page=com.atlassian.jira.plugin.s... ] Christoph Thelen commented on AS7-4568: --------------------------------------- Initially we used the manifest entry. We have an ear with several included wars. We tried adding the dependency in the ear and the war manifests. Neither worked. Additionally placing the primefaces.jar in the war/WEB-INF/libs was successful, but like the original reporter we'd like to put it in a module. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-4568?page=com.atlassian.jira.plugin.s... ] Christoph Thelen commented on AS7-4568: --------------------------------------- Unfortunately this doesn't work, I still can't use the primefaces tags and features. As I said in the first comment the {{jboss-deployment-structure.xml}} solution works fine for us. If the current behavior is the way module loading is designed I would suggest explicitly mentioning the META-INF import for service descriptors in the documentation for the deployment structure file (at least I didn't find a mention of it there). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-4568?page=com.atlassian.jira.plugin.s... ] Gernot P commented on AS7-4568: ------------------------------- Does the "service" option ("Dependencies: org.primefaces services") really import the whole META-INF directory structure, or only the serviceloader specific parts? Because there's a lot of other stuff in primfaces.jar/META-INF -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-4568?page=com.atlassian.jira.plugin.s... ] Christoph Thelen edited comment on AS7-4568 at 5/25/12 6:40 AM: ---------------------------------------------------------------- The manifest was in standalone/deployments/my.ear/META-INF and contained {noformat} Manifest-Version: 1.0 Dependencies: org.primefaces services {noformat} I also tried putting this manifest in the .../my.ear/mywar1.war/META-INF directories. As I said we now use the deployment structure file. My main issue (and probably the original reason for this ticket) here is, that component librarys like Primefaces need the special import handling if they are bound as module. was (Author: cth): The manifest was in standalone/deployments/my.ear/META-INF and contained {noformat} Manifest-Version: 1.0 Dependencies: org.primefaces services {noformat} I also tried putting this manifest in the .../my.ear/mywar1.war/META-INF direstories. As I said we now use the deployment structure file. My main issue (and probably the original reason for this ticket) here is, that component librarys like Primefaces need the special import handling if they are bound as module. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira