Announcement Announcement Module
Collapse
No announcement yet.
Possible Supplier/Conflicts ? hu? Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Possible Supplier/Conflicts ? hu?

    hello,

    maybe somebody could point me in the right direction because i absolutely dont know where to start to resolve this

    thx
    m

    Caused by: com.springsource.platform.osgi.framework.UnableToS atisfyBundleDependenciesException: Unable to satisfy dependencies of bundle 'org.faces.web' at version '1.0.0': Cannot resolve: org.faces.web
    Resolver report:
    Bundle: org.faces.web_1.0.0 - Uses Conflict: Import-Package: org.apache.myfaces.shared_orchestra.renderkit.html ; version="[1.2.0.SNAPSHOT,1.2.0.SNAPSHOT]"
    Possible Supplier: org.apache.myfaces.orchestra.myfaces-orchestra-core_1.2.0.SNAPSHOT - Export-Package: org.apache.myfaces.shared_orchestra.renderkit.html ; version="1.2.0.SNAPSHOT"
    Possible Conflicts: javax.faces.render,javax.faces,javax.faces.context ,org.apache.commons.logging,org.apache.myfaces.sha red_orchestra.renderkit,org.apache.myfaces.shared_ orchestra.config,javax.faces.component.html,javax. faces.convert,javax.faces.event,javax.faces.compon ent,javax.faces.application,org.apache.myfaces.sha red_orchestra.util,org.apache.myfaces.shared_orche stra.component,javax.faces.model,org.apache.myface s.shared_orchestra.renderkit.html.util

    at com.springsource.platform.osgi.framework.equinox.E quinoxBundleInstaller.satisfyConstraints(EquinoxBu ndleInstaller.java:339)
    at com.springsource.platform.deployer.app.legacy.Lega cyApplication.deploy(LegacyApplication.java:77)
    at com.springsource.platform.deployer.core.internal.S tandardApplicationDeployer.deploy(StandardApplicat ionDeployer.java:390)
    ... 33 more

  • #2
    Possible Supplier/Conflicts ? hu?

    This is a complicated one - it seems that an import from your app is conflicting with one from the myfaces-orchestra bundle.

    If possible, could you create a JIRA issue, attach your application and any bundles you installed into bundles/usr?

    Regards,

    Rob

    Comment


    • #3
      Possible Supplier/Conflicts ? hu?

      hi rob,

      thanks. i think that the problem has to do with the enforcement of a certain javax.faces version from spring web bundle (javax.faces.application;version="[1.1.5, 2.0.0)") from within the import header. because this would conflict with bundle export-package headers that have uses (uses:= directive) javax.faces packages without a version attribute. for an example see the facelets bundle

      Export-Package: com.sun.facelets;version="1.1.14";uses:="com.sun.f acel
      ets.compiler,javax.el,javax.faces,javax.faces.appl ication,javax.faces
      .component,javax.faces.context",com.sun.facelets.c ompiler;version="1.
      1.14";uses:="com.sun.facelets,com.sun.facelets.el, com.sun.facelets.ta
      g,javax.el,javax.faces,javax.faces.component,javax .faces.context,java
      x.faces.el,javax.faces.event,javax.faces.render,ja vax.xml.parsers,org
      .xml.sax

      if you either remove the uses directive or add a (matching) version attribute the bunlde could be resolved. i think this is a problem because the maven bnd plugin does not add this version attribute automatically. ( you could configure it to omit it but this weakens the class compatibility check constraints )

      thx
      m

      Comment

      Working...
      X