Yes, you’re right. The servlet is actually not a component, it is registered manually on behalf of the Application service. It was a remnant.
I’ve fixed it.
Kind regards,
Peter Kriens
> On 7 jun. 2016, at 01:44, Paul F Fraser <pa...@a2zliving.com> wrote:
>
> Hi Peter,
>
> In VaadinOSGiServlet this property has no effect,
> HttpWhiteboardConstants.HTTP_WHITEBOARD_SERVLET_PATTERN +
> "=/foo",
>
> The setting in ClickMeApp @Component(name =
> "osgi.enroute.examples.vaadin.clickme", property = "alias=/poo") is the
> effective setting.
> In this case /poo works and the whiteboard constant is ignored.
>
> Paul
>
>
> On 7/06/2016 9:08 AM, Paul F Fraser wrote:
>> Brilliant, Thanks Peter,
>>
>> It works, now I need to get my head into all that is going on.
>> From first glance at the code it seems that this example covers a very wide
>> range of EnRoute techniques.
>>
>> Paul
>>
>>
>> On 6/06/2016 11:47 PM, Peter Kriens wrote:
>>> These are always the questions that are hard to resist :-(
>>>
>>> I’ve created a simple proof of concept to show how you could use [Vaadin
>>> with OSGi][1]. Vaadin is one of those (in my opinion horrid) pieces of
>>> software that can’t resist the temptation to use statics, singletons,
>>> global variables, and strings instead of classes :-(
>>>
>>> In my opinion good software is _instance_ based and OSGi is a prime
>>> example. So it took me a few hours but I figured out how I could trick
>>> Vaadin in letting the service create the instance of the UI and not through
>>> newInstance().
>>>
>>> The provided repo has a readme. Let me know how it works and I am of course
>>> very interested in PRs since this is a quick POC and not the usual quality.
>>>
>>> Quick note. The Vaadin dependencies use the new Maven Bnd Repository plugin
>>> in 3.2. Look at cnf/vaadin.bnd for the specific info.
>>>
>>> Kind regards,
>>>
>>> Peter Kriens
>>>
>>>
>>> [1]: https://github.com/osgi/osgi.enroute.examples.vaadin
>>> <https://github.com/osgi/osgi.enroute.examples.vaadin>
>>>
>>>
>>>
>>>
>>>
>>>
>>>> On 6 jun. 2016, at 02:43, Paul F Fraser <pa...@a2zliving.com
>>>> <mailto:pa...@a2zliving.com>> wrote:
>>>>
>>>> Hi David,
>>>>
>>>> On 6/06/2016 9:54 AM, David Leangen wrote:
>>>>> Hard to provide much useful information if I don’t yet completely
>>>>> understand what you are up to. :-)
>>>>>
>>>>> Are you able to share some code?
>>>> As soon as I "understand what I am up to" I will have some code to share
>>>> :-)
>>>> There is so much in EnRoute that provides functionality, in a tidy
>>>> environment, that it takes considerable time to investigate and avoid
>>>> rewriting what is already there.
>>>> For instance, I am checking out the web simple provider and web security
>>>> bundles in the osgi-bundles repository to understand servlet handling.
>>>> The "service catalog" whiteboard service does not have any documentation
>>>> yet on the EnRoute site.
>>>>
>>>> Much of my previous understanding of OSGi, Bnd and Bndtools has been
>>>> totally reset by the approach taken in EnRoute.
>>>> The video http://enroute.osgi.org/videos/chuck-boecking-persistence.html
>>>> <http://enroute.osgi.org/videos/chuck-boecking-persistence.html> has been
>>>> very valuable, thanks Chuck.
>>>>
>>>> Paul
>>>> _______________________________________________
>>>> OSGi Developer Mail List
>>>> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>
>>>> https://mail.osgi.org/mailman/listinfo/osgi-dev
>>>> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
>>>
>>>
>>> _______________________________________________
>>> OSGi Developer Mail List
>>> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>
>>> https://mail.osgi.org/mailman/listinfo/osgi-dev
>>> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
>>
>>
>> _______________________________________________
>> OSGi Developer Mail List
>> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>
>> https://mail.osgi.org/mailman/listinfo/osgi-dev
>> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
> _______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org
> https://mail.osgi.org/mailman/listinfo/osgi-dev
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
