Created: (FELIX-2481) Renaming a package via refactoring should update any workspace package exports/imports

     [
https://issues.apache.org/jira/browse...nels:all-tabpanel
]

David Savage resolved FELIX-1346.

Add refactoring support for moving and renaming bundle activator -
automatically update sigil.properties to match updates

     [
https://issues.apache.org/jira/browse...nels:all-tabpanel
]

David Bosschaert updated DOSGI-38:

hello,

i am very new to osgi so maybe my issue is something trivial, but i did
not find solution for it while googling.

i have basic webapp that works fine if i install there felix osgi log
implementation and other felix bundles. i decided to try to code my own
implementation of osgi log service. i think i did all correctly, but
when i try to start my webapp with my implementation of log service, i
get this error:

ERROR: Error starting
jndi:/localhost/webapp/WEB-INF/bundles/commons-logservice-osgi-1.0-SNAPSHOT.jar
(org.osgi.framework.BundleException: Unresolved constraint in bundle
cz.startnet.commons-logservice-osgi [2]: package;
(&(package=org.osgi.framework)(version>=1.5.0)))
org.osgi.framework.BundleException: Unresolved constraint in bundle
cz.startnet.commons-logservice-osgi [2]: package;
(&(package=org.osgi.framework)(version>=1.5.0))
        at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3299)
        at org.apache.felix.framework.Felix.startBundle(Felix.java:1657)
        at
org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1128)
        at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
        at java.lang.Thread.run(Thread.java:619)

manifest of commons-logservice-osgi contains this (and ofc other lines):
Export-Package: cz.startnet.commons.org.osgi.service.log,org.osgi.serv
 ice.log;uses:="org.osgi.framework";version="1.3"
Import-Package: cz.startnet.commons.org.osgi.service.log,org.osgi.fram
 ework;version="1.5",org.osgi.service.log;version="1.3"

manifest was generated by maven-bundle-plugin.

this is structure of my webapp:

target/
|-- bundles
|   |-- commons-logservice-osgi-1.0-SNAPSHOT.jar
|   |-- org.apache.felix.http.bridge-2.0.4.jar
|   `-- org.apache.felix.webconsole-3.0.0.jar
|-- classes
|   `-- cz
|       `-- startnet
|           `-- webapp
|               |-- FrameworkService.class
|               |-- ProvisionActivator.class
|               `-- StartupListener.class
|-- felix-cache
|   |-- bundle0
|   |   `-- bundle.id
|   |-- bundle1
|   |   |-- bundle.id
|   |   |-- bundle.lastmodified
|   |   |-- bundle.location
|   |   |-- bundle.startlevel
|   |   |-- bundle.state
|   |   `-- version0.0
|   |       |-- bundle.jar
|   |       |-- bundle.jar-embedded
|   |       |   |-- commons-fileupload-1.1.1.jar
|   |       |   |-- commons-io-1.4.jar
|   |       |   `-- json-20070829.jar
|   |       `-- revision.location
|   |-- bundle2
|   |   |-- bundle.id
|   |   |-- bundle.lastmodified
|   |   |-- bundle.location
|   |   |-- bundle.startlevel
|   |   |-- bundle.state
|   |   `-- version0.0
|   |       |-- bundle.jar
|   |       `-- revision.location
|   `-- bundle3
|       |-- bundle.id
|       |-- bundle.lastmodified
|       |-- bundle.location
|       |-- bundle.startlevel
|       |-- bundle.state
|       `-- version0.0
|           |-- bundle.jar
|           `-- revision.location
|-- maven-archiver
|   `-- pom.properties
|-- war
|   `-- work
|       `-- webapp-cache.xml
|-- webapp
|   |-- META-INF
|   |   `-- context.xml
|   `-- WEB-INF
|       |-- bundles
|       |   |-- commons-logservice-osgi-1.0-SNAPSHOT.jar
|       |   |-- org.apache.felix.http.bridge-2.0.4.jar
|       |   `-- org.apache.felix.webconsole-3.0.0.jar
|       |-- classes
|       |   `-- cz
|       |       `-- startnet
|       |           `-- webapp
|       |               |-- FrameworkService.class
|       |               |-- ProvisionActivator.class
|       |               `-- StartupListener.class
|       |-- framework.properties
|       |-- lib
|       |   |-- org.apache.felix.framework-2.0.5.jar
|       |   |-- org.apache.felix.http.proxy-2.0.4.jar
|       |   |-- org.osgi.compendium-4.2.0.jar
|       |   `-- org.osgi.core-4.2.0.jar
|       `-- web.xml
`-- webapp.war

26 directories, 47 files


anyone knows what i am doing wrong that commons-logservice-osgi cannot
be started? thx for any hints.

Miroslav

Wrong error message on a missing package

Karaf feature validate plugin should take the osgi system package into
consideration

I am trying simple osgi bundle which has every dependency embedded 
inside my bundle. By default, bundle-plugin creates several entries in 
Import-Package and Export-Package . I want to get rid of them 
completely. I tried several ways . If I try giving empty Import-Package 
, it fails at build. I tried blank _exportcontents, does not work too !

Any clue ?

Common ORM layer/package

Pig needs to support keywords in the package name

I want to specify the package name and class name of the generated java
bean class

Add RPC Payloads and Better Histograms to Stats Package

Wrong import package version for javax.servlet

vs2008 project files are missing in the download-package

Have package naming more closely follow Appendix D.5.1 of JAXB 2.0/2.2
specification

Could not package plugin when build sample javaee5\bank

Label interfaces for audience and stability in org.apache.pig.backend
package

current use of generics on the model package seems to cause issues in
Scala-land when trying to use the model objects to build up routes

If I have a package { "foo": ensure => installed; require =>
something
} in a module, AND I also have a Package { require =>
Class['yum::client']} in site.pp, what happens in the module? Does the
package in the module require both 'something' and the yum::client
class, or does the fact I specified a package{} with a require in the
module mean that only the yum::client class is required?

Doug.

On 6/25/2010 12:03 AM, Bill Weiss wrote:
 My problem is, in this case, there are machines that need X but not
 Y, Y but not X, X and Y, or neither.  I can obviously write all of
 those cases out separately, but that means duplication of code for
 setting up the parts of X and Y that aren't dependant.

 Custom facts are probably the best way for me to do this, but I'd
 love to hear that there's a simpler way.


If you can decide in your node source (site.pp or external) which 
components are needed, this is very easy:


   node a { include X }
   node b { include Y }
   node c { include X,Y }
   node d { }


If you **cannot** decide in your node source, you're probably doing 
something wrong[1] and need to explain your problem better.



Best Regards, David

[1] I know, converting legacy systems is a pain, but IMHO you're still 
better off doing a manual survey and nailing it down instead of trying 
to make automatic decisions that'll backfire down the road.


        FB-Nr.: FN 309285 g          FB-Gericht: LG Korneuburg

I use it at my job at kaChing. Generally it is just fine for the job,
doing what you'd expect.

My criticisms are that it is very thin on documentation (javadoc),
which may have been improved, and I don't like how it makes every zk
exception into a RuntimeException.

But I'm thumbs up.

.. Adam

On Mon, Jul 12, 2010 at 4:10 PM, Jun Rao <jun### @gmail.com> wrote:
 Hi,

 ZkClient (http://github.com/sgroschupf/zkclient) provides a nice
wrapper
 around the ZooKeeper client and handles things like retry during
 ConnectionLoss events, and auto reconnect. Does anyone (other than
Katta)
 use it? Would people recommend using it? Thanks,

 Jun