Hi All,
I've committed an initial code for addressing [1], please review it
again now that it is in the code, if you have any additional comments
then let me know please, also, if someone would like to tune JavaDocs a
bit - please go ahead.
Thanks, Sergey
[1]
Hi Again
The other thing I've been thinking a lot about is whether it makes sense
to wait with introducing blueprint-web-osgi [2] to the trunk or wait
till some later time.
As I said earlier and as you can see from the patch it is a very light
weight module; what it does now I can easily do
Hi,
I really would like to see this being included in the next release.
It's one of those things I really have been missing in the past and
a lot of questions where being asked about a feature like this
for Pax-Web.
+1 (non-binding) for this.
regards, Achim
2013/10/21 Sergey Beryozkin
Hi Sergey,
I think I understand what you are proposing for [1]. A programmatic
API to create Blueprint Containers. Once you have such container, can
you then also programmatically add beans etc? In other words will you
be able to do via code all the things that you would normally do in a
Hi David
Thanks for the feedback,
On 08/10/13 09:34, David Bosschaert wrote:
Hi Sergey,
I think I understand what you are proposing for [1]. A programmatic
API to create Blueprint Containers. Once you have such container, can
you then also programmatically add beans etc? In other words will
Thanks Sergey,
sounds reasonable to me...
Cheers,
David
On 8 October 2013 11:01, Sergey Beryozkin sberyoz...@gmail.com wrote:
Hi David
Thanks for the feedback,
On 08/10/13 09:34, David Bosschaert wrote:
Hi Sergey,
I think I understand what you are proposing for [1]. A programmatic
API
Hi All,
I did some initial work on enhancing BlueprintExtender to make it easier
to deal with BlueprintContainers externally [1] and introducing a new
blueprint-web-osgi module [2].
I've commented at [1] [2] so hopefully the reason behind these minor
but also IMHO useful enhancements is
