Hi Simon,
Yes i solved this.
Frow what i've understand maybe i'm wrong the problem is that in the
config.ini file i had not put a line for the fragment bunldes of
logback.
As i had understand in past, it's not necessary because fragment
bundles should not be started, so i had not put a line for the fragment
bundle
in the config.ini file
Even if it's not right start a fragment bundle if i put a line like for
the following bundles:
osgi.bundles=org.eclipse.equinox.common@2:start,\
org.eclipse.update.configurator@start,\
ch.qos.logback.classic@4:start,\
ch.qos.logback.core@4:start,\
ch.qos.logback.slf4j@4:start,\ <- This is the fragment bunlde i've
put a line saying to start even if is not correct this seems to cause a
"correct resolution"
this solve the problem... probably is something related to equinox
internals resolution mechanism...
In that case i had not the line described the fragment bundle result in
a resolved state but it's not attached to it's host bundle.
Don't know if it could help Simon, but i had also other resolution
problems with the servlet bridge....
Another problem that i have is that when i start the servlet bridge is
a log entry from equinox about not resolving a bunlde that requires
javax.jms packages
but *the strange thing is that when the equinox container has finishe
the startup phase* if i do a "ss" command the bundles for which i i get
the error message is there
percfectly resolved and started so i 'm a bit confused on what was
happening. ( I had an exception but the bundles seems to be ok!! )
As for the case above, if i start the jms bundle with a line in the
config.ini file this solve the problem even if the javax.jms does not
need to be
start anywhere.
At the end i came up ( even if it's not the better solution ) to have a
config.ini file where i start all my bundles. This solve all the
problem above.
Andrea
Il 19/07/2010 17:20, Simon Kaegi ha scritto:
Very strange. Did you resolve this?
I know of several teams using SLF4J in a similar way with the
servletbridge although admittedly not currently with the orbit bundles.
Is is possible there is more than one fragment in your install or is
the logback bundle using incompatible "uses" contraints?
Can you provide any more info on what the host bundle thinks it's
importing/exporting?
-Simon
 Andrea
Zoppello ---07/14/2010 06:28:52 AM---Hi All, I'm having the following
errors with the orbit/slf4j bunldes when i try
Hi All,
I'm having the following errors with the orbit/slf4j bunldes when i try
to use
with equinox started by the "servlet bridge".
In this configuration the "fragment" bundles is not resolved and when
i
do a diag
i have the folllowing message:
update@plugins/ch.qos.logback.slf4j_0.9.19.v20100519-1910.jar [167]
Constraints from the fragment conflict with the host: Import-Package:
ch.qos.l
ogback.classic; version="0.9.19"
Constraints from the fragment conflict with the host: Import-Package:
ch.qos.l
ogback.classic.selector; version="0.9.19"
Constraints from the fragment conflict with the host: Import-Package:
ch.qos.l
ogback.classic.util; version="0.9.19"
Constraints from the fragment conflict with the host: Import-Package:
ch.qos.l
ogback.core; version="0.9.19"
Constraints from the fragment conflict with the host: Import-Package:
ch.qos.l
ogback.core.joran; version="0.9.19"
Constraints from the fragment conflict with the host: Import-Package:
ch.qos.l
ogback.core.joran.spi; version="0.9.19"
Constraints from the fragment conflict with the host: Import-Package:
ch.qos.l
ogback.core.util; version="0.9.19"
The strange thing is that when i use the same bundles with equinox
standalone container there is NO problem..
Any thoughts??
Andrea
--
*Andrea Zoppello*
Spagic Architect
Corso Stati Uniti, 23/C - 35127 Padova - Italy
Tel. +39-049.8283411
Mob. +39-345.4668537
andrea.zoppello@xxxxxx
www.spagoworld.org <http://www.spagoworld.org>
*Engineering Group*
IT Solution Architect
Research & Innovation Division
Architectures & Consulting
www.eng.it <http://www.eng.it>
Respect the environment. Please don't print this e-mail unless you
really need to.
The information transmitted is intended only for the person or entity
to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you
received this in error, please contact the sender and delete the
material from any computer.
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev
--
Andrea Zoppello
Spagic Architect
 |
Respect
the environment. Please don't print this e-mail unless you really need
to. |
The information transmitted is intended
only for the person or entity to which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance
upon, this information by persons or entities other than the intended
recipient is prohibited. If you received this in error, please contact
the sender and delete the material from any computer.
|
