Hi Petri,

FYI:

https://issues.apache.org/jira/browse/KARAF-2114
https://issues.apache.org/jira/browse/KARAF-2115

I gonna fix these issues, it will be included in next Karaf 2.3.1 and 3.0.0.

Thanks again for your report !

Regards
JB

On 01/08/2013 08:50 AM, PJR69 wrote:
Ok, finally I manage to resolve this!!!

The issue lies with using a child-instance and incomplete configuration for pax 
mvn url resolver.

Specifically, this property:
org.ops4j.pax.url.mvn.defaultRepositories=file:${karaf.home}/${karaf.default.repository}@snapshots,\
     file:${karaf.home}/local-repo@snapshots

in the org.ops4j.pax.url.mvn.cfg-file inside the child-instance etc-folder.

I fixed this by modifying the above line to read:
org.ops4j.pax.url.mvn.defaultRepositories=file:${karaf.home}/${karaf.default.repository}@snapshots,\
     file:${karaf.home}/local-repo@snapshots, 
file:${karaf.base}/${karaf.default.repository}@snapshots

So, it seems that the KAR-deployer does unpack the files into the system-folder 
of the child-instance, BUT the mvn-url resolve doesn’t see that system-folder! 
It only sees the system-folder of the root instance!

Once I modified the line as shown above and restart the child instance, my 
KAR-deployment started working just fine!!!

Furthermore: This fix:
#
# Settings for the OSGi 4.3 Weaving
# By default, we will not weave any classes. Change this setting to include 
classes
# that you application needs to have woven.
#
org.apache.aries.proxy.weaving.enabled=none
# Classes not to weave - Aries default + Xerces which is known to have issues.
org.apache.aries.proxy.weaving.disabled=org.objectweb.asm.*,org.slf4j.*,org.apache.log4j.*,javax.*,org.apache.xerces.*

appears only at the root-instance system.properties. If I create a 
child-instance, the system.properties-file generated there doesn’t include the 
above lines.

So maybe fix these on the next release?


-          Petri


From: jbonofre [via Karaf] [mailto:[email protected]]
Sent: 30. joulukuuta 2012 12:56
To: Riipinen Petri
Subject: Re: Difference in KAR-deployment between Windows and Linux

Thanks for the details. I gonna test it.

Regards
JB

On 12/30/2012 10:29 AM, PJR69 wrote:

I'm using the latest published version, 2.3.0.

If it helps, I can create a test-KAR for you once I get back to office on
7th of Jan. I can just include for example joda-time.jar into the KAR, that
is enough to demonstrate the issue.

Note that I'm using child instances and NOT the root instance, so maybe
there is a difference?

What I'm doing is this:
- Download Karaf 2.3.0 on a computer connected to internet.
- Create a child instance called "template"
- Start & connect to child instance and then add features to it, like CXF,
Camel and ActiveMQ.
- Then I shutdown the whole thing.
- Then I zip the Karaf folder and move it to internal computer without any
internet connection and unpack it there.
- Then I start the root instance, and clone the template to "prod1" and then
start it.
- And then I deploy the KAR-file into this prod1-instance. And as I said,
the jar-files inside the KAR do get unpacked into the prod1-instance system
folder, but the won't get activated, that's the problem. If I just deploy
all the bundles separately into the deploy-folder, everything works, but
that's not the way I'd like to make the deployment.



--
View this message in context: 
http://karaf.922171.n3.nabble.com/Difference-in-KAR-deployment-between-Windows-and-Linux-tp4027093p4027161.html
Sent from the Karaf - User mailing list archive at Nabble.com.


--
Jean-Baptiste Onofré
[hidden email]</user/SendEmail.jtp?type=node&node=4027162&i=0>
http://blog.nanthrax.net
Talend - http://www.talend.com

________________________________
If you reply to this email, your message will be added to the discussion below:
http://karaf.922171.n3.nabble.com/Difference-in-KAR-deployment-between-Windows-and-Linux-tp4027093p4027162.html
To start a new topic under Karaf - User, email 
[email protected]<mailto:[email protected]>
To unsubscribe from Karaf - User, click 
here<http://karaf.922171.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=930749&code=cGV0cmkucmlpcGluZW5AaW5zdGEuZml8OTMwNzQ5fDU5NTY5OTMzOA==>.
NAML<http://karaf.922171.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>




--
View this message in context: 
http://karaf.922171.n3.nabble.com/Difference-in-KAR-deployment-between-Windows-and-Linux-tp4027093p4027223.html
Sent from the Karaf - User mailing list archive at Nabble.com.


--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com

Reply via email to