[
https://issues.apache.org/jira/browse/DOSGI-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469625#comment-13469625
]
Tomasz Kleszczynski edited comment on DOSGI-69 at 2/15/13 9:03 PM:
-------------------------------------------------------------------
I took a look one more time and found problem with test failure.
It was caused by wrong version in import of package
org.springframework.beans.factory.xml. It was [2.5.6,3) instead of [3,4) -
project now use spring-beans in version 3.0.6.RELEASE. This wrong version was
computed because maven plugin used to generate OSGi manifest uses spring-beans
in version 2.5.6.SEC01 (dependency of spring-osgi-core 1.2.1 defined in pom)
which wasn't good because now project uses spring framework in version
3.0.6.RELEASE.
I prepared second patch with explicit dependency to spring-beans in version
used in project and now version of package
org.springframework.beans.factory.xml in MANIFEST.MF is computed properly and
tests complete without failures.
Following is some log from system test which shows that spring-beans in version
3.0.6.RELEASE is used:
[ StreamUtils] -
file:/C:/java/workspace/cxf-dosgi/distribution/multi-bundle/target/cxf-dosgi-ri-multibundle-distribution-1.3.1-dir/apache-cxf-dosgi-ri-1.3.1/dosgi_bundles/spring-beans-3.0.6.RELEASE.jar
: downloading...
[ StreamUtils] -
file:/C:/java/workspace/cxf-dosgi/distribution/multi-bundle/target/cxf-dosgi-ri-multibundle-distribution-1.3.1-dir/apache-cxf-dosgi-ri-1.3.1/dosgi_bundles/spring-beans-3.0.6.RELEASE.jar
: 556590 bytes @ [ 55659kBps ]
was (Author: tkleszczynski):
I take a look one more time and found problem with test failure.
It was caused by wrong version in import of package
org.springframework.beans.factory.xml. It was [2.5.6,3) instead of [3,4) -
project now use spring-beans in version 3.0.6.RELEASE. This wrong version was
computed because maven plugin used to generate OSGi manifest uses spring-beans
in version 2.5.6.SEC01 (dependency of spring-osgi-core 1.2.1 defined in pom)
which wasn't good because now project uses spring framework in version
3.0.6.RELEASE.
I prepared second patch with explicit dependency to spring-beans in version
used in project and now version of package
org.springframework.beans.factory.xml in MANIFEST.MF is computed properly and
tests completes without failures.
Following is some log from system test which shows that spring-beans in version
3.0.6.RELEASE is used:
[ StreamUtils] -
file:/C:/java/workspace/cxf-dosgi/distribution/multi-bundle/target/cxf-dosgi-ri-multibundle-distribution-1.3.1-dir/apache-cxf-dosgi-ri-1.3.1/dosgi_bundles/spring-beans-3.0.6.RELEASE.jar
: downloading...
[ StreamUtils] -
file:/C:/java/workspace/cxf-dosgi/distribution/multi-bundle/target/cxf-dosgi-ri-multibundle-distribution-1.3.1-dir/apache-cxf-dosgi-ri-1.3.1/dosgi_bundles/spring-beans-3.0.6.RELEASE.jar
: 556590 bytes @ [ 55659kBps ]
> CXF-DOSGi requires internet access when reading XML
> ---------------------------------------------------
>
> Key: DOSGI-69
> URL: https://issues.apache.org/jira/browse/DOSGI-69
> Project: CXF Distributed OSGi
> Issue Type: Bug
> Components: DSW
> Affects Versions: 1.1
> Reporter: David Bosschaert
> Assignee: David Bosschaert
> Fix For: 1.4
>
> Attachments: dosgi69.patch, DOSGI-69.patch, DOSGI-69.patch,
> dosgi69-withoutEmbeddedDependencies.patch
>
>
> When the DOSGi system parses XML (such as an intent map or
> remote-services.xml file) it tries to resolve the used XML schema's from the
> internet, even though they are part of the distribution. This shouldn't be
> happening.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
