Wnlab

User Tools

Site Tools

You are here: start » giraffplus » 3rdparty
Trace:
giraffplus:3rdparty

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
giraffplus:3rdparty [2013-07-18 12:13] – [Problems You May Discover Running Your Bundle in Apache Felix] filippogiraffplus:3rdparty [2013-07-18 12:17] (current) – [If You Have the Following Execution Errors when Starting Your Bundle] filippo
Line 145: Line 145:
 Notice the unresolved constraint above. This is something which will need to be added to your POM as an imported package. Change your pom.xml file, add the package to the Import-Package statement, re-build your bundle JAR, and then try again. Notice the unresolved constraint above. This is something which will need to be added to your POM as an imported package. Change your pom.xml file, add the package to the Import-Package statement, re-build your bundle JAR, and then try again.
  
-===== If You Have the Following Execution Errors when Starting Your Bundle ===== +===== Other Hints and Tricks =====
- +
->> Provider for javax.xml.transform.TransformerFactory cannot be found +
- +
->> Provider for javax.xml.parsers.SAXParserFactory cannot be found +
- +
->> com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl cannot be cast to javax.xml.transform.sax.SAXTransformerFactory +
- +
->> loader constraint violation: when resolving method "javax.xml.transform.sax.SAXResult.<init>(Lorg/xml/sax/ContentHandler;)V" the class loader (instance of org/apache/felix/framework/searchpolicy/ModuleImpl$ModuleClassLoader) of the current class, com/searchtechnologies/aspire/framework/SimpleDigester, and the class loader (instance of <bootloader>) for resolved class, javax/xml/transform/sax/SAXResult, have different Class objects for the type org/xml/sax/ContentHandler used in the signature +
- +
->> Caused by: javax.xml.transform.TransformerException: Source object passed to ''{0}'' has no contents. at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transformIdentity(Unknown Source) +
- +
->> Class not found:  x.y.z.CLASS +
- +
->> Unable to load class +
- +
-If you have thes execution errors when starting your bundle, add the following to your <Import-Package> description: +
- +
-  javax.xml.parsers,javax.xml.transform,javax.xml.transform.sax,org.xml.sax,javax.xml.transform.dom,javax.xml.namespace,org.xml.sax.ext, +
- +
-NOTE:  These should be included even if the maven-bundle-plugin reports warnings that they're not needed. +
- +
-== Version Errors == +
- +
-For a currently unknown reason, Maven sometimes adds a "version" to the packaged imports when it builds the bundle. You'll typically notice this when your bundle fails to load with the following exception: +
- +
-  com.searchtechnologies.aspire.services.AspireException: Unable to install bundle file:/C:/Users/sdenny/.m2/repository/com/searchtechnologies/aspire-fast-qpl/1.2-SNAPSHOT/aspire-fast-qpl-1.2-SNAPSHOT.JAR from repository MavenRepository[C:\Users\sdenny/.m2/repository]. +
-        at com.searchtechnologies.aspire.application.ComponentBundleInfo.load(ComponentBundleInfo.java:156) +
-        at com.searchtechnologies.aspire.application.RepositoryManager.load(RepositoryManager.java:170) +
-        at com.searchtechnologies.aspire.application.AspireApplicationImpl.loadFactoryBundle(AspireApplicationImpl.java:394) +
-        at com.searchtechnologies.aspire.application.ComponentManagerImpl.registerComponents(ComponentManagerImpl.java:238) +
-        . +
-        . +
-        at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) +
-        at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) +
-       '''Caused by: org.osgi.framework.BundleException: Unresolved constraint in bundle com.searchtechnologies.aspire-fast-qpl [24]: Unable to resolve 24.0: missing requirement [24.0] osgi.wiring.package; (&(osgi.wiring.package=groovy.lang)(version>=2.0.0))''' +
-   +
-        at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:3826) +
-        at org.apache.felix.framework.Felix.startBundle(Felix.java:1868) +
-        at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:944) +
-        at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:931) +
-        at com.searchtechnologies.aspire.application.ComponentBundleInfo.load(ComponentBundleInfo.java:152) +
-        ... 42 more +
- +
-If you examine the bundle (using winrar or similar)and look in the ''META-INF/MANIFEST.MF'' file, you'll see the imports have a version specified: +
- +
-  Import-Package: com.searchtechnologies.aspire.services,com.searchtechnologies.aspire.services.xml,'''groovy.lang;version="2.0"''',javax.xml.parsers,javax.xml.transform,javax.xml.transform.dom,javax.xml.transform.sax,javax.xml.transform.stream,org.osgi.framework,org.osgi.service.log,org.osgi.util.tracker,org.w3c.dom,org.w3c.dom.bootstrap,org.w3c.dom.ls,org.xml.sax,org.xml.sax.ext,org.xml.sax.helpers +
- +
-Unless the packages were exported with this version, then the import cannot find them. In Aspire we don't add versions to exported packages, so the easiest way to work around this issue is to suppress the addition of the version number to the import. This can be done by specifying the import in the following manner: +
- +
-  <Import-Package> +
-    groovy.lang''';version=!''', +
- +
-== Other Hints and Tricks ==+
  
 If you make changes to the framework, you'll likely need to re-run "mvn install" on the framework before those changes will be visible in your project. If you make changes to the framework, you'll likely need to re-run "mvn install" on the framework before those changes will be visible in your project.
Line 204: Line 151:
 You can find more information here:  You can find more information here: 
  
-: http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html+http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html
  
 Also, check out the BND documentation page for additional options (Maven bundle plugin is based on BND, so the syntax for specifying imports/exports is the same): Also, check out the BND documentation page for additional options (Maven bundle plugin is based on BND, so the syntax for specifying imports/exports is the same):
  
-: http://www.aqute.biz/Bnd/Bnd+http://www.aqute.biz/Bnd/Bnd
  
 Specifically, look at the "Import Package" section: Specifically, look at the "Import Package" section:
  
-: http://www.aqute.biz/Bnd/Format#import-package+http://www.aqute.biz/Bnd/Format#import-package
  
-== APPENDIX:  Packages provided by the System Bundle ==+===== APPENDIX:  Packages provided by the System Bundle =====
  
 Note that you will need to import these with &lt;Import-Package&gt; if you use them, or if any of your 3rd party JARs use them. Note that you will need to import these with &lt;Import-Package&gt; if you use them, or if any of your 3rd party JARs use them.
  
-<pre>+<code>
 javax.accessibility,version=1.6.0 javax.accessibility,version=1.6.0
 javax.activation,version=1.6.0 javax.activation,version=1.6.0
Line 383: Line 330:
 org.xml.sax.ext,version=1.6.0 org.xml.sax.ext,version=1.6.0
 org.xml.sax.helpers,version=1.6.0 org.xml.sax.helpers,version=1.6.0
-</pre> +</code>
- +
-[[Category:Component Development Topics]]+
giraffplus/3rdparty.1374149626.txt.gz · Last modified: 2013-07-18 12:13 by filippo
Donate Powered by PHP Valid HTML5 Valid CSS Run on Debian Driven by DokuWiki