Hi,
The following resolve fail is occuring in my enRoute application bndrun, but I think this service
should be provided by felx scr (2.1.14)
Resolution failed. Capabilities satisfying the following requirements could not
be found:
[<>]
? osgi.identity:
Hi Tim,
On 6/03/2019 8:41 pm, Tim Ward wrote:
Hi Paul,
Firstly - this sounds like something for the Bndtools list rather than the OSGi
developer list, in that your asking a question about the Bndtools M2E
integration, rather than a question about OSGi enRoute.
Not sure I understand this
With about 30 modules in an enRoute project it is spending a long time in "Checking index project
APP for rebuild"
APP is the name of the project application.
Is this normal or have I missed a setting somewhere?
Eclipse 2018-12, bndtools 4.3.0.DEV
Paul Fraser
Hi,
Thanks to Ray for fixing the Jetty metadata problem and Carsten for pointing
out it's release.
Also to whoever upgraded felix scr to 2.1.14.
For some reason the debug problem with source code has gone away and enRoute is defaulting to the
latest versions of jetty and scr.
My system now
Hi,
What needs to be done to upgrade enRoute to use felix scr 2.1.14 and
felix.jetty 4.0.8 as defaults?
Paul Fraser
___
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
On 3/03/2019 7:59 pm, Carsten Ziegeler via osgi-dev wrote:
Hi
have a look at
http://repo1.maven.org/maven2/org/apache/felix/org.apache.felix.http.jetty/4.0.8/
It's released since some days
Thanks Carsten,
It does not show up in a maven central search, only 4.0.6, that's why I was not
Hi,
My code runs OK in a bnd workspace using R6 and bndtools 4.2 and it HAS (at the moment) to use
org.apache.felix.jetty 4.0.6 .
This setup resolves and runs OK with the missing metadata in 4.0.6.
This setup has the problem with Felix SCR not removing prototype references on shutdown using
On 16/01/2019 10:51 pm, Tim Ward wrote:
Is there a bug repot filed for this bug? Otherwise we should do that.
https://issues.apache.org/jira/browse/FELIX-6029
It would appear that http.jetty-4.08 fixes this but I cannot find v4.08.
Where should I look?
Thanks
Paul Fraser
Thomas,
Thank goodness someone else has experienced this. I thought it was my problem
only.
I mentioned this on this list previously but so far no response.
Paul
On 2/02/2019 3:54 am, Thomas Driessen via osgi-dev wrote:
Hi,
now that I'm using the enroute maven workspace I stumbled upon
Hi Thomas,
I have been going through the same trauma as you with a fond attachment to the bnd workspace and a
dislike of maven.
I think you also have an interest in Vaadin. Vaadin has been the catalyst for me having to get to
know and use the new enRoute.
The ease of using Vaadin addons and
leading up to it.
Best Regards,
Tim
On 30 Jan 2019, at 06:04, Paul F Fraser via osgi-dev
wrote:
Hi,
Now heavily into new enRoute, I am getting quite regularly (multiple) NPEs
during build. Does not seem to affect runtime.
Is this a normal situation or should I look for a problem in my code? Any
wrote:
Hi Paul,
If I follow the Download links from there I end up at the actual page that contains the specs:
https://www.osgi.org/release-7-1/
That page contains both the PDFs as well as the online ones...
Best regards,
David
On Wed, 30 Jan 2019 at 00:00, Paul F Fraser via osgi-dev
Hi,
Now heavily into new enRoute, I am getting quite regularly (multiple) NPEs during build. Does not
seem to affect runtime.
Is this a normal situation or should I look for a problem in my code? Any clues?
Paul Fraser
___
OSGi Developer Mail
Hi,
Who or how do I tell someone that the page https://www.osgi.org/developer/specifications/ needs
links to the online spec.
The bugs and issues area seems difficult to use without further study.
A low friction way to report these, relatively minor, but annoying aspects of the search for
correctly?
Paul
On 24/01/2019 8:39 pm, Paul F Fraser via osgi-dev wrote:
One query, I am finding in my system, after running resolve, the app sometimes needs to be saved
manually after the resolve other times it is saved auto.
Is this normal?
Paul
Thanks, Ray,
Things are starting to look promising :-)
One query, I am finding in my system, after running resolve, the app sometimes needs to be saved
manually after the resolve other times it is saved auto.
Is this normal?
Paul
On 22/01/2019 3:16 pm, Raymond Auge wrote:
_clientBuilder_
On 21/01/2019 7:57 pm, Tim Ward wrote:
As a separate question - is there a reason that you are trying to use the
Apache HttpClient? OSGi enRoute makes use of the JAX-RS Whiteboard which
includes a simple way to access the JAX-RS specification client implementation.
If it’s possible for you to
Hi,
Not sure if the problem is due to me, but I have been having major problems with the bare project
archetype.
Most of the errors I was getting made mention of not being able to find my bundles in the sonartype
repo.
Removing the sonartype repo from the eclipse maven repos and relying
Vaadin Flow bundle is using the
HttpService? It would be better and easier for them to use the Http Whiteboard than to use the
old HttpService to provide content…
Best Regards,
Tim
On 16 Jan 2019, at 04:45, Paul F Fraser via osgi-dev <mailto:osgi-dev@mail.osgi.org>> wrote:
Hi,
Hi,
When attempting to create a ds-component for a Vaadin Flow bundle in enRoute I have run up against
some problems reconciling the 2 different approaches.
Adding appropriate parts of the vaadin pom to the enRoute pom causes problems between enRoute
osgi-api pom and the osgi bundles used by
On 22/08/2018 5:40 AM, Paul F Fraser via osgi-dev wrote:
On 21/08/2018 10:00 PM, Tim Ward via osgi-dev wrote:
Have you looked at what the OSC project does? It uses Vaadin, and uses the ViewProvider interface
to provide view instances. These automatically have a detach listener added on creation
On 21/08/2018 10:00 PM, Tim Ward via osgi-dev wrote:
Have you looked at what the OSC project does? It uses Vaadin, and uses the ViewProvider interface
to provide view instances. These automatically have a detach listener added on creation so that
they get correctly disposed when their parent
Somewhere in an Eclipsecon video or some other source I came across some info on the new logging
setup which I cannot find now. It might have been David and Carsten, but not sure.
The spec will be most valuable once I understand what is going on!
Anyway, to the point, is there an approach
Tim,
Would this problem be related?
"Error: Could not find or load main class aQute.launcher.Launcher"
Also is the enRoute documentation still to be followed as is, for instance settings.xml and the cli
archetype commands?
Paul
On 3/07/2018 7:05 PM, Tim Ward via osgi-dev wrote:
Hi all,
e best learning method.
Thanks,
Paul
On 2 Jul 2018, at 10:47, Paul F Fraser via osgi-dev <mailto:osgi-dev@mail.osgi.org>> wrote:
Thanks to the clues obtained from code in the OpenSecurityController project I am making some
serious progress in handling the Vaadin OSGi situation.
The one
Thanks to the clues obtained from code in the OpenSecurityController project I am making some
serious progress in handling the Vaadin OSGi situation.
The one sticking point now is related to creating the instances of PROTOTYPE
services.
In the code below, when the component is activated the
Tim,
Thanks for the pointer to OpenSecurityController. It covers many aspects of the service model not
well explained anywhere else that I have been able to find.
A couple of questions...
The MainUI references all of the ComponentServiceObjects used in the project.
Could you suggest how
There has been some discussion in the bndtools list about handling 3rd part non
OSGi jars.
How can this be done in the new maven enRoute, if possible?
Paul Fraser
___
OSGi Developer Mail List
osgi-dev@mail.osgi.org
At last I have a working vaadin UI in the new enRoute environment.
https://github.com/QNENet/vaadin-osgi-enRoute
The code is based on work by Mirjan Merruko of Vaadin in preparation for possible inclusion in an
upcoming Vaadin release.
I have no yet tried any themes other than the default
After researching the situation with Vaadin and OSGi I have decided to ask for help from anyone
interested in the subject
I have created a Github repo with a readme that explains the problems and added 2 videos, first
video is an intro to the new enRoute and the other a demo of the Vaadin
A few questions about work environment.
Build automatically.. On or Off
Bndtools perspective.. Y or N
Paul
___
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
Vaadin instructions for OSGi-fying a Vaadin application is at
https://vaadin.com/docs/v8/framework/advanced/advanced-osgi.html
The reactor pom seems to handle most of the info suggested by Vaadin to be
placed in a bnd file.
Bundle-Name: ${project.name}
Bundle-Version: ${project.version}
I added slf4j as a managed dependency in the reactor and logback disappeared
from the index.
Removed it and logback was back.
Searched my workspace and only found logback mysteriously appearing in the the
app index.
Where should I look to find where logback is introduced?
Paul Fraser
Any opinions on how we should refer to the two versions?
Perhaps "enRoute" for the new and "Classic enRoute" for the original.
Or enroute1 and enRoute2?
Or is there a formal naming?
Paul Fraser
___
OSGi Developer Mail List
osgi-dev@mail.osgi.org
Just before giving up on the new enRoute system I decided to go back to the start and follow the
quickstart tutorial exactly as outlined in the documents.
I had tried to be too clever and use the bare project...wrong.
Using the full project artifact solved all of the problems. I deleted my .m2
On further investigation
It is not related to dependencies in the reactor. It happens in modules as well.
jsoup seems ok
vaadin server 8.4.3 causes errors
vaadin osgi integration bundle 8.4.3 causes errors
all other vaadin bundles seem ok.
Paul
On 18/06/2018 7:05 PM, Paul F Fraser via osgi-dev
frameworks, and therefore require indexes. You
can see that they create indexes because they enable the
bnd-indexer-maven-plugin.
Best Regards,
Tim
On 18 Jun 2018, at 06:15, Paul F Fraser via osgi-dev
wrote:
Is it intended that all modules listed in the reactor are indexed.
In my case
Is it intended that all modules listed in the reactor are indexed.
In my case for some reason, only those referenced in the application start
module(?) are indexed.
Paul Fraser
___
OSGi Developer Mail List
osgi-dev@mail.osgi.org
Hi,
Building with (new) enRoute, all is well until I add a Vaadin dependency.
Video of problem https://youtu.be/MQX8ICmUHdc
Part of error report
The default package '.' is not permitted by the Import-Package syntax.
This can be caused by compile errors in Eclipse because Eclipse creates
When creating new maven modules the default module package is set as
org. + the artifactId
Could this be changed to use
groupId + artifactId instead?
Or is there a reason for not doing this?
Paul Fraser
___
OSGi Developer Mail List
Hi Christian,
Thanks for confirmation.
Paul
On 10/06/2018 5:18 PM, Christian Schneider wrote:
Type bundle never makes sense for maven dependencies. It is just a setting the maven-bundle-plugin
uses while creating the bundle.
I also had lots of issues with this as m2e like to set the type
The problem I was having was with a maven central artifact that was classified as
"bundle".
Maven build was reporting it as not found so the build failed and of course
indexes not updated.
Change it to "jar" and everything works beautifully.
I have no idea if the change to jar will cause any
Probably an obvious answer, but how are jar dependencies added to the
repository from maven central?
If I add a dependency which is in maven central the maven build does not find
it.
The microservice tutorial says:-
By adding the following dependencies inside the||section of the
enRoute app module has a standalone repo called repo01.
I cannot find where the relationship between rep01 and target/index.xml is
established.
Any clues?
Paul
___
OSGi Developer Mail List
osgi-dev@mail.osgi.org
Hi,
After many hours immersing myself in youtube maven videos and working through the new enRoute
documentation I am slowly gaining an appreciation for the techniques involved.
The problem at the moment is handling the indexing and setting up the bndrun
files.
When working through the
On 18/05/2018 5:20 PM, Tim Ward wrote:
My guess is that you either haven’t done a pull of master, or that you have the old R7 branch
(used to do the initial R7 development) checked out.
Hi Tim,
Your guess is 100% accurate.
I thought I was smart and would work on the R7 branch. :-[
Paul
On 17/05/2018 2:08 AM, BJ Hargrave via osgi-dev wrote:
I made a PR to change to change to 4.0.0 from snapshot.
--
The enRoute tutorial commands do not work for me with a fresh download from
github.
mvn verify and this command fail, even with the -SNAPSHOT removed from the end.
|mvn -s
On 8/05/2018 8:08 PM, Tim Ward via osgi-dev wrote:
The enRoute project has now been updated to use the released R7 API as well as released versions
of Declarative Services, Config Admin, Http Whiteboard, JPA Service, Transaction Control, and
Configurator.
The one remaining snapshot
On 15/05/2018 6:43 PM, Tim Ward wrote:
The correct link is
https://github.com/osgi/osgi.enroute/blob/deprecated/osgi.enroute.pom.distro/distro-pom.xml
This does not work for me and the link to the distro pom is dead.
Is it still possible to alter the distro now that we have the new enRoute?
/osgi.enroute.pom.distro/distro-pom.xml)
Kind regards,
Peter Kriens
On 1 Dec 2017, at 07:32, Paul F Fraser via osgi-dev <osgi-dev@mail.osgi.org
<mailto:osgi-dev@mail.osgi.org>> wrote:
Hi,
The jetty bundles in the current distro (the one I have) are version 3.1 which
imports jetty 9.2.10.
The
Hi,
Webjars, a whole new world to me.
Can they be used in an OSGi container without OSGi manifest headers, or has OSGi missed the boat in
this technology?
Most, if not all webjars, contain no OSGi metadata.
Paul Fraser
___
OSGi Developer Mail
The beta4 release (today) has issue 455 as a known limitation. Someone might be
listening.
I have added a comment and nice to see Timothy J has also commented.
Paul
On 22/03/2018 11:07 PM, Thomas Driessen via osgi-dev wrote:
Hi,
as some people already wrote about Vaadin in OSGi applications
On 19/01/2018 2:15 AM, Thomas Driessen wrote:
Hello,
just for other people that are trying to get Vaadin 8 to work within an OSGi
environment:
Hi Thomas,
Good to hear that you are on the way.
Are you now using all Vaadin OSGi bundles and none of the enRoute bundles?
Are you developing in
Forwarded with permission--
Forwarded Message
Subject:Fwd: [osgi-dev] Vaadin 8.2 in OSGi: ClassNotFound
Date: Tue, 16 Jan 2018 22:24:18 +0100
From: Pierre De Rop
To: Paul F Fraser
Hello Paul;
I'm Pierre, one of
On 17/01/2018 1:52 AM, Thomas Driessen via osgi-dev wrote:
I also asked this question in the Vaadin forum. I just thought that maybe another OSGi developer
already had the same problems and am therefore posting this question here too:
I just tried to run a simple Hello World Vaadin app in an
"Off the Mark" was not the term I intended for getting going in 2018, after checking it's meaning "a
long way from an intended target".
Oh well it can only get better.
Paul
___
OSGi Developer Mail List
osgi-dev@mail.osgi.org
Hi,
Might be of interest to the OSGi community.
I have just published 2 medium articles about my project. I have mentioned in one of the articles
that my system is comprised 100% of OSGi modules.
https://twitter.com/qnenet/status/947580369779548160 and
for something more fully written up.
I hope this helps,
Tim
On 15 Dec 2017, at 04:26, Paul F Fraser via osgi-dev <osgi-dev@mail.osgi.org>
wrote:
Hi,
I have been dragged, kicking and screaming into the bnd/maven world. Putting it
off any longer is now, not an option.
Running eclipse
Hi,
I have been dragged, kicking and screaming into the bnd/maven world. Putting it off any longer is
now, not an option.
Running eclipse Oxygen Sept 2017 with bndtools 3.5
Venturing into the enRoute "Tutorial to work with Maven Repositories" the question arises, how
current is the
Hi,
The jetty bundles in the current distro (the one I have) are version 3.1 which
imports jetty 9.2.10.
The latest felix bundle is 3.4.6 which imports jetty 9.3.9.
What needs to be done to upgrade the distro or how can I force the resolver to ignore the old
version and work from a version
60 matches
Mail list logo