Re: [osgi-dev] Hi

As soon as a bundle accesses resources of another bundle these classes are instantiated. A bundle that is uninstalled can only be completely purged once the last class of that bundle is garbage collected. Refreshing the bundles that used the uninstalled bundle normally fix this but you also need

[osgi-dev] Reference Filters

Hi, A previous discussion in this list @Component public class Component { @Reference(target = "(alias = ${alias})" public void bindService(Service service) } and the solution proposed was to use .target as a property. Are there any code examples available that provide more info on this

[osgi-dev] Couple of doubts

Hi All, I am on Enroute/Eclipse/Bndtools. * I have a .provider and .api in my project (along with other bundles). I do not want to install this provider bundle during run. It should not be installed/active. By default this is going into installed/active mode. Note that this bundle is

[osgi-dev] Hi

Hi All, I am on Enroute/Eclipse/Bndtools. I INSTALL a certain bundle and then go on to UNINSTALL. But still, the bundle seem to exist (may be in the cache) as I am able to execute functions in this uninstalled bundle. How do I eliminate this bundle's presence completely? Thanks, Manoj The

Re: [osgi-dev] Integration with Karaf

> For anybody else confused by this thread, there are now two Tim Wards > apparently! Ahh! Now I understand!! :-) Hehehe. Thanks for pointing this out. The disadvantage of “David” is that there are too many of us. But I have an unusual last name, so at least there are not two of me

Re: [osgi-dev] Basic feedback on JAX-RS whiteboard spec

Also, thank you for reading the RFC and providing feedback! I will make sure to clarify the rules around pre and post match filters. Regards, Tim > On 10 Nov 2016, at 18:39, BJ Hargrave wrote: > > As stated in the front matter of the RFC, you should provide feedback to

Re: [osgi-dev] Basic feedback on JAX-RS whiteboard spec

As stated in the front matter of the RFC, you should provide feedback to the OSGi public bugzilla system at https://osgi.org/bugzilla/.   Thanks,   --BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848

Re: [osgi-dev] Enroute Rest

You must be doing something weird since CORS is only an issue when the browser gets an index.html file from a different server than the server serving the REST call. That is of course fine but that is a relatively advanced use case that requires you to understand CORS and its security

[osgi-dev] Basic feedback on JAX-RS whiteboard spec

Hi, Sorry if it is not the right place to provide the feedback, I just wanted to share some basic feedback. - The text is written well and is easy to understand - May be worth distinguishing between PreMatch and PostMatch filters - the former are run before a resource method has been found -

Re: [osgi-dev] Why is 'start' an error for fragments?

> On 10 Nov 2016, at 16:51, Benson Margulies wrote: > > On Thu, Nov 10, 2016 at 11:16 AM, BJ Hargrave > wrote: >> Not really. Fragments are not bundle in that they do not have a class loader >> or a separate activation

Re: [osgi-dev] Why is 'start' an error for fragments?

On Thu, Nov 10, 2016 at 11:16 AM, BJ Hargrave wrote: > Not really. Fragments are not bundle in that they do not have a class loader > or a separate activation life. They can be attached to zero or more host > bundles (non-fragment bundles). So to start them is not possible.

Re: [osgi-dev] JAX-RS Whiteboard spec link

Hi David Thanks, downloaded it, Cheers, Sergey On 10/11/16 16:33, David Bosschaert wrote: Hi Sergey, It doesn't exist yet as a spec. The latest documentation that for it is in RFC 217 here: https://github.com/osgi/design/tree/master/rfcs/rfc0217 Cheers, David On 10 November 2016 at 16:26,

Re: [osgi-dev] osgi-dev Digest, Vol 121, Issue 20

> On 10 Nov 2016, at 16:07, Christian Schneider wrote: > > Hi Neil, > > that sounds very good. I was not aware of the Endpoint publishing. I will > test the interoperability as soon as I can. > I will also look into making CXF-DOSGi implement the spec as well as

Re: [osgi-dev] JAX-RS Whiteboard spec link

Hi Sergey, It doesn't exist yet as a spec. The latest documentation that for it is in RFC 217 here: https://github.com/osgi/design/tree/master/rfcs/rfc0217 Cheers, David On 10 November 2016 at 16:26, Sergey Beryozkin wrote: > Hi All > > Where can I find a link to the

[osgi-dev] JAX-RS Whiteboard spec link

Hi All Where can I find a link to the JAX-RS whiteboard spec text ? Thanks, Sergey ___ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev

Re: [osgi-dev] Why is 'start' an error for fragments?

Not really. Fragments are not bundle in that they do not have a class loader or a separate activation life. They can be attached to zero or more host bundles (non-fragment bundles). So to start them is not possible. To make it a no-op will break an invariant: After callings start, the bundle must

Re: [osgi-dev] Why is 'start' an error for fragments?

There was early on, but I admit I forgot the good reason it is an error vs. a no-op. Regardless, it will be difficult to change now because others may be depending on the current behavior. I suggest you avoid checking headers though: boolean isFragment =

Re: [osgi-dev] osgi-dev Digest, Vol 121, Issue 20

Hi Neil, that sounds very good. I was not aware of the Endpoint publishing. I will test the interoperability as soon as I can. I will also look into making CXF-DOSGi implement the spec as well as possible so we get away a bit from the proprietary configs. Anyway it is really good that we

[osgi-dev] Why is 'start' an error for fragments?

Has there ever been consideration of making 'start' be a harmless no-op for fragment bundles? I keep having to write code to check the headers and avoid the call to start on fragments. ___ OSGi Developer Mail List osgi-dev@mail.osgi.org

Re: [osgi-dev] osgi-dev Digest, Vol 121, Issue 20

> On 10 Nov 2016, at 15:31, Christian Schneider wrote: > > On 10.11.2016 15:16, Timothy Ward wrote: >> >> This is where your argument has problems, RSA simply does not equal REST. >> RESTful services follow API design principles which are heavily connected to >>

Re: [osgi-dev] osgi-dev Digest, Vol 121, Issue 20

On 10.11.2016 15:16, Timothy Ward wrote: This is where your argument has problems, RSA simply does not equal REST. RESTful services follow API design principles which are heavily connected to HTTP, and to the incoming and outgoing wire formats. If I have a REST API used by my “one page web

Re: [osgi-dev] osgi-dev Digest, Vol 121, Issue 20

Hi Christian > On 10 Nov 2016, at 12:17, Christian Schneider wrote: > > I think we were simply talking about different things. I’m not sure that we are - I’m talking about when RSA is an appropriate choice, and how to provide advice in a relatively vendor-neutral way

Re: [osgi-dev] Integration with Karaf

On 10/11/2016 11:05, Tim Ward wrote: On 10/11/2016 10:26, Tim Verbelen wrote: Hi Tim, If you want to use some of the eclipse equinox bundles (such as org.eclipse.equinox.coordinator), you are kind of bound to the equinox framework since they depend on the org.eclipse.osgi.util package that

Re: [osgi-dev] RS/RSA for exposing JAX-RS resources

Thank you both for your reply and I am sorry I was not clear in the link that I wanted but I got it. Thanks, David On Thu, Nov 10, 2016 at 6:57 AM, Timothy Ward wrote: > Actually I believe the prototype of the reference implementation is > currently here

Re: [osgi-dev] RS/RSA for exposing JAX-RS resources

Actually I believe the prototype of the reference implementation is currently here https://github.com/csierra/osgi-jaxrs-extracted but it will be moved into Apache Aries at some point soon. It’s nice to know that Amdatu is planning to offer a

Re: [osgi-dev] RS/RSA for exposing JAX-RS resources

https://bitbucket.org/amdatu/amdatu-remoteservices On Thu, Nov 10, 2016 at 12:50 PM David Daniel wrote: > Is there a link to the code where the refernce implementation is being > kept. I would love to take a look at it. > > Thanks David > > On Thu, Nov 10, 2016 at

Re: [osgi-dev] RS/RSA for exposing JAX-RS resources

Is there a link to the code where the refernce implementation is being kept. I would love to take a look at it. Thanks David On Thu, Nov 10, 2016 at 3:08 AM, Tim Ward wrote: > I'll be there, and am happy to talk with you about it. These talks will > likely both be about

Re: [osgi-dev] osgi-dev Digest, Vol 121, Issue 20

I think the wheels came off a while ago when ppl started promoting RSA for publishing JAX-RS services because this is supported by an extension of a RSA implementation ;) On Thu, Nov 10, 2016 at 12:31 PM Timothy Ward wrote: > Add the property service.exported.interfaces=*

Re: [osgi-dev] Enroute Rest

Hi All, I am getting the following error when I run my App which is based on getUpper() QS tutorial (REST API) No 'Access-Control-Allow-Origin' header is present on the requested resource. Can we get this enabled from the REST HTTP Server side or is there any other better solution to get

Re: [osgi-dev] osgi-dev Digest, Vol 121, Issue 20

> Add the property service.exported.interfaces=* and some provider specific > properties to your OSGi service. And this is where the wheels come off. This statement is *wrong*. if you *have* to add some provider specific properties then this is no longer RSA, but some implementation specific

Re: [osgi-dev] Integration with Karaf

On 10/11/2016 10:31, Neil Bartlett wrote: For anybody else confused by this thread, there are now two Tim Wards apparently! Oh yes, I had spotted that there was one already here, and had intended to say "this is a different one" in my first post to the list, but forgot to do so - sorry for

Re: [osgi-dev] Integration with Karaf

On 10/11/2016 10:26, Tim Verbelen wrote: Hi Tim, If you want to use some of the eclipse equinox bundles (such as org.eclipse.equinox.coordinator), you are kind of bound to the equinox framework since they depend on the org.eclipse.osgi.util package that is provided by the equinox framework.

Re: [osgi-dev] osgi-dev Digest, Vol 121, Issue 20

Hi Christian, > Unfortunately it is not really possible to describe a practical example for > RSA without implementation specific details. I disagree with this statement. It’s perfectly possible to discuss the RSA architecture, and then to provide an example which uses one of the

Re: [osgi-dev] Integration with Karaf

Hi Tim, If you want to use some of the eclipse equinox bundles (such as org.eclipse.equinox.coordinator), you are kind of bound to the equinox framework since they depend on the org.eclipse.osgi.util package that is provided by the equinox framework. If you do want to run these on a

Re: [osgi-dev] Integration with Karaf

On 10.11.2016 10:55, Tim Ward wrote: Insofar as I understand any of what is going on, which is not very much, this sounds plausible - there does look like a bizarre mixture of equinox and felix components (although one of my colleagues says "that's not a problem as they all just implement

Re: [osgi-dev] Integration with Karaf

You asked how to solve the problem, I'm just answering. If you don't want to depend on Equinox framework, do not deploy bundles that do depend on it ;-) In this case, osgi.enroute.configurer.simple.provider depends on the equinox coordinator which depends on org.eclipse.equinox.util package

Re: [osgi-dev] osgi-dev Digest, Vol 121, Issue 20

I agree. The problem is sometimes to distinguish between explaining how to use RSA in general which I think is appropriate here and featuring the individual impl which might not. Unfortunately it is not really possible to describe a practical example for RSA without implementation specific

Re: [osgi-dev] Integration with Karaf

On 10/11/2016 09:44, Christian Schneider wrote: It looks like you are installing a lot of bundles that are already present in apache karaf. These can conflict with the ones already present. The actual resolve problems you get are because you are missing some equinox bundles the bundle you try

Re: [osgi-dev] osgi-dev Digest, Vol 121, Issue 20

-dev@mail.osgi.org> > https://mail.osgi.org/mailman/listinfo/osgi-dev > > The information contained in this electronic message and any attachments to > this message are intended for the exclusive use of the addressee(s) and may > contain proprietary, confidential or privileged informat

Re: [osgi-dev] Integration with Karaf

On 10/11/2016 09:43, Guillaume Nodet wrote: It seems you have a strong dependency on the Equinox OSGi framework. In Karaf, run the "framework equinox ;shutdown --reboot --force " commands and see if this is better. Thanks, but we are specifically and deliberately wanting to use Felix, and I

Re: [osgi-dev] Integration with Karaf

It looks like you are installing a lot of bundles that are already present in apache karaf. These can conflict with the ones already present. The actual resolve problems you get are because you are missing some equinox bundles the bundle you try to install need. Installing these will not fully

Re: [osgi-dev] Integration with Karaf

It seems you have a strong dependency on the Equinox OSGi framework. In Karaf, run the "framework equinox ; shutdown --reboot --force " commands and see if this is better. 2016-11-10 10:32 GMT+01:00 Tim Ward : > So, I've gone through the enRoute tutorials, which worked fine,

[osgi-dev] Integration with Karaf

So, I've gone through the enRoute tutorials, which worked fine, then tried writing some code of my own, which worked fine, then tried deploying it to Karaf, attempting to following the instructions in http://enroute.osgi.org/appnotes/bndtools-and-karaf.html and it doesn't work, and after

Re: [osgi-dev] RS/RSA for exposing JAX-RS resources

I'll be there, and am happy to talk with you about it. These talks will likely both be about the upcoming JAX-RS whiteboard specification from OSGi Enterprise R7 - Liferay are building the reference implementation for it. Tim Sent from my iPhone > On 10 Nov 2016, at 08:01, Bernd Eckenfels

Re: [osgi-dev] RS/RSA for exposing JAX-RS resources

Hello, Just noticed at the modconf2016 in Darmstadt (literary event next Tuesday) there is also a Workshop on this topic: https://web.liferay.com/de/web/events2016/modconf [ I will be at the conference as well, so maybe we can meet and greet? ] Modular Rest APIs using JAX-RS in OSGi