4:12 p.m.
WRT webbeans-ri-trunk
My IntelliJ IDEA outlook looks broken.
Looking at the WebBeansBootstrapDeployer it cannot link to parts of
JBoss Deployers,
although they are in the Libraries.
Anyone using IDEA and seeing the same problems after re-running "mvn
idea:idea"?
btw: Pete, why is deployers module depending on ejb module (in pom.xml)?
deployer shouldn't depend on anything, as it runtime delegates things.
6:12 p.m.
New subject: [webbeans-dev] Web Beans SE Documentation and Swing Example
Hi,
I have added some documentation for SE. It doesn't yet include any of
the threading/shutdown manager stuff, and I've got a little TODO in
there. Can anyone tell me, does the Interceptor/decorator stuff make use
of any EE features, or will it probably work out of the box in SE? I
just haven't got round to trying yet.
I've also checked in a Swing version of the number guess example at
webbeans/examples/trunk/se/number-guess.
Finally, I'm /experimenting/ with enabling and using Request, Session
and Conversation scopes/contexts in SE. If you're interested in seeing
the working code I've got the changes to core, SE and the number guess
example ready to check in to separate branches. Happy to discuss this
further if anyone is interested/curious.
Cheers,
Pete.
3:27 p.m.
New subject: [webbeans-dev] Web Beans SE Documentation and Swing Example
On 11 Apr 2009, at 00:12, Peter Royle wrote:
Hi,
I have added some documentation for SE. It doesn't yet include any of
the threading/shutdown manager stuff, and I've got a little TODO in
there.
Looks really good :-)
Can anyone tell me, does the Interceptor/decorator stuff make use
of any EE features, or will it probably work out of the box in SE?
Currently where Interceptors/Decorators live (EJB/299/???) is open - I
think they make sense in SE, but I don't know how where they will be
implemented yet. NB We haven't impld them in WB core for this reason...
I
just haven't got round to trying yet.
I've also checked in a Swing version of the number guess example at
webbeans/examples/trunk/se/number-guess.
I tried to run it - but I'm missing the key thing - a readme or
tutorial on how to run it ;-) We should definitely put a little newbie
tutorial in the docs...
Finally, I'm /experimenting/ with enabling and using Request, Session
and Conversation scopes/contexts in SE. If you're interested in seeing
the working code I've got the changes to core, SE and the number guess
example ready to check in to separate branches. Happy to discuss this
further if anyone is interested/curious.
Perhaps send a patch out for review (or attach to a JIRA issue?)
Cheers,
Pete.
_______________________________________________
webbeans-dev mailing list
webbeans-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/webbeans-dev
--
Pete Muir
http://www.seamframework.org
http://in.relation.to/Bloggers/Pete
2 a.m.
New subject: [webbeans-dev] Web Beans SE Documentation and Swing Example
Hi Pete,
Cheers for your thoughts. I'll remove the TODO from the docs then and
create a JIRA instead.
I'll add a readme for the Number Guess SE example and put it in the docs
as you suggest. For the record, the easiest way to run it at the moment
is to load it into and IDE and run the
org.jboss.webbeans.environment.se.StartMain main class.
And good idea I'll submit some patch sets to Jira soonish.
Cheers,
Pete.
On Tue, 2009-04-14 at 21:27 +0100, Pete Muir wrote:
On 11 Apr 2009, at 00:12, Peter Royle wrote:
> Hi,
>
> I have added some documentation for SE. It doesn't yet include any of
> the threading/shutdown manager stuff, and I've got a little TODO in
> there.
Looks really good :-)
> Can anyone tell me, does the Interceptor/decorator stuff make use
> of any EE features, or will it probably work out of the box in SE?
Currently where Interceptors/Decorators live (EJB/299/???) is open - I
think they make sense in SE, but I don't know how where they will be
implemented yet. NB We haven't impld them in WB core for this reason...
> I
> just haven't got round to trying yet.
>
> I've also checked in a Swing version of the number guess example at
> webbeans/examples/trunk/se/number-guess.
I tried to run it - but I'm missing the key thing - a readme or
tutorial on how to run it ;-) We should definitely put a little newbie
tutorial in the docs...
>
>
> Finally, I'm /experimenting/ with enabling and using Request, Session
> and Conversation scopes/contexts in SE. If you're interested in seeing
> the working code I've got the changes to core, SE and the number guess
> example ready to check in to separate branches. Happy to discuss this
> further if anyone is interested/curious.
Perhaps send a patch out for review (or attach to a JIRA issue?)
>
>
> Cheers,
>
> Pete.
>
>
>
>
> _______________________________________________
> webbeans-dev mailing list
> webbeans-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/webbeans-dev
--
Pete Muir
http://www.seamframework.org
http://in.relation.to/Bloggers/Pete
7:14 a.m.
New subject: [webbeans-dev] Web Beans SE Documentation and Swing Example
On 15 Apr 2009, at 08:00, Peter Royle wrote:
Hi Pete,
Cheers for your thoughts. I'll remove the TODO from the docs then and
create a JIRA instead.
I'll add a readme for the Number Guess SE example and put it in the
docs
as you suggest. For the record, the easiest way to run it at the
moment
is to load it into and IDE and run the
org.jboss.webbeans.environment.se.StartMain main class.
Great, I also made maven add the relevant MANIFEST entry, and added a -
Drun target so you can just do mvn -Drun to launch the app :-)
I made a few small changes to naming for consistency...
And good idea I'll submit some patch sets to Jira soonish.
Cheers,
Pete.
On Tue, 2009-04-14 at 21:27 +0100, Pete Muir wrote:
> On 11 Apr 2009, at 00:12, Peter Royle wrote:
>
>> Hi,
>>
>> I have added some documentation for SE. It doesn't yet include any
>> of
>> the threading/shutdown manager stuff, and I've got a little TODO in
>> there.
>
> Looks really good :-)
>
>> Can anyone tell me, does the Interceptor/decorator stuff make use
>> of any EE features, or will it probably work out of the box in SE?
>
> Currently where Interceptors/Decorators live (EJB/299/???) is open
> - I
> think they make sense in SE, but I don't know how where they will be
> implemented yet. NB We haven't impld them in WB core for this
> reason...
>
>
>> I
>> just haven't got round to trying yet.
>>
>> I've also checked in a Swing version of the number guess example at
>> webbeans/examples/trunk/se/number-guess.
>
> I tried to run it - but I'm missing the key thing - a readme or
> tutorial on how to run it ;-) We should definitely put a little
> newbie
> tutorial in the docs...
>
>>
>>
>> Finally, I'm /experimenting/ with enabling and using Request,
>> Session
>> and Conversation scopes/contexts in SE. If you're interested in
>> seeing
>> the working code I've got the changes to core, SE and the number
>> guess
>> example ready to check in to separate branches. Happy to discuss
>> this
>> further if anyone is interested/curious.
>
> Perhaps send a patch out for review (or attach to a JIRA issue?)
>
>>
>>
>> Cheers,
>>
>> Pete.
>>
>>
>>
>>
>> _______________________________________________
>> webbeans-dev mailing list
>> webbeans-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/webbeans-dev
>
> --
> Pete Muir
> http://www.seamframework.org
> http://in.relation.to/Bloggers/Pete
>
_______________________________________________
webbeans-dev mailing list
webbeans-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/webbeans-dev
--
Pete Muir
http://www.seamframework.org
http://in.relation.to/Bloggers/Pete
2:25 p.m.
New subject: [webbeans-dev] Web Beans SE Documentation and Swing Example
On 15/04/2009, at 1:14 PM, Pete Muir wrote:
Great, I also made maven add the relevant MANIFEST entry, and added
a -Drun target so you can just do mvn -Drun to launch the app :-)
Smooth :)
I made a few small changes to naming for consistency...
>
>
> And good idea I'll submit some patch sets to Jira soonish.
>
> Cheers,
>
> Pete.
>
> On Tue, 2009-04-14 at 21:27 +0100, Pete Muir wrote:
>> On 11 Apr 2009, at 00:12, Peter Royle wrote:
>>
>>> Hi,
>>>
>>> I have added some documentation for SE. It doesn't yet include
>>> any of
>>> the threading/shutdown manager stuff, and I've got a little TODO in
>>> there.
>>
>> Looks really good :-)
>>
>>> Can anyone tell me, does the Interceptor/decorator stuff make use
>>> of any EE features, or will it probably work out of the box in SE?
>>
>> Currently where Interceptors/Decorators live (EJB/299/???) is
>> open - I
>> think they make sense in SE, but I don't know how where they will be
>> implemented yet. NB We haven't impld them in WB core for this
>> reason...
>>
>>
>>> I
>>> just haven't got round to trying yet.
>>>
>>> I've also checked in a Swing version of the number guess example at
>>> webbeans/examples/trunk/se/number-guess.
>>
>> I tried to run it - but I'm missing the key thing - a readme or
>> tutorial on how to run it ;-) We should definitely put a little
>> newbie
>> tutorial in the docs...
>>
>>>
>>>
>>> Finally, I'm /experimenting/ with enabling and using Request,
>>> Session
>>> and Conversation scopes/contexts in SE. If you're interested in
>>> seeing
>>> the working code I've got the changes to core, SE and the number
>>> guess
>>> example ready to check in to separate branches. Happy to discuss
>>> this
>>> further if anyone is interested/curious.
>>
>> Perhaps send a patch out for review (or attach to a JIRA issue?)
>>
>>>
>>>
>>> Cheers,
>>>
>>> Pete.
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> webbeans-dev mailing list
>>> webbeans-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/webbeans-dev
>>
>> --
>> Pete Muir
>> http://www.seamframework.org
>> http://in.relation.to/Bloggers/Pete
>>
>
>
> _______________________________________________
> webbeans-dev mailing list
> webbeans-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/webbeans-dev
--
Pete Muir
http://www.seamframework.org
http://in.relation.to/Bloggers/Pete
1:34 a.m.
New subject: [webbeans-dev] Request, Conversation and Session Scopes in Web Beans SE
[apologies if this is a double post - I sent one 8 hours ago but haven't
heard anything from the list]
Hi,
As mentioned previously, I've been doing some experimenting with using
the above contexts in Web Beans within the Java SE environment. Here are
some patches, diffed from the root webbeans directory, which will add
support for these contexts to the Web Beans SE Module project, plus
modify the Swing SE Numberguess example to use these scopes.
The key points are:
NUMBERGUESS
- A Session is pretty much the whole lifespan of the application, since
it's single-user.
- A Conversation is a single instance of the game, until it is either
won or lost.
- A Request is a single button click, and is mostly present to support
Conversations using the existing paradigms.
- The Game class is now Conversation scoped. No restart() necessary, the
NumberGuessFrame simply ends the current conversation when the game is
over and starts a new one.
- This allows the @Random number to be injected directly into Game for
each fresh conversation (rather than injecting the generator and hanging
on to it)
- NumberGuessFrame injects the current conversation and conversation
manager, as well as the JavaSELifecycle, all of which it uses to manage
the various contexts (Request, Session and Conversation)
- You can see these contexts being started and stopped during the
start(), guessButtonActionPerformed() and replayButtonActionPerformed()
methods.
WEB BEANS SE MODULE
- JavaSELifecycle added to help client apps and frameworks manage
lifecycle in SE. This would eventually end up in the SPI perhaps, or as
a better abstraction of an existing SPI interface.
- JavaSEConversationManager is copied from ServletConversationManager
and much of the common code should probably be pushed into an abstract
class.
- WebBeansBootstrap now registers everything except
ServletConversationManager and HttpSessionManager when in SE mode. It
also registers the new JavaSEConversationManager.
I would like to clean up the syntax for starting requests because it's
obviously pretty ugly and verbose right now. Maybe some kind of
annotation and interceptor pair perhaps? And possibly some
Swing-specific helpers to make it easy to attach the Request context to
a button click? Making this sort of stuff more transparent is my next
goal.
Let me know what you think, anyone. Cheers.
Pete.
>
>
> Finally, I'm /experimenting/ with enabling and using Request, Session
> and Conversation scopes/contexts in SE. If you're interested in seeing
> the working code I've got the changes to core, SE and the number guess
> example ready to check in to separate branches. Happy to discuss this
> further if anyone is interested/curious.
Perhaps send a patch out for review (or attach to a JIRA issue?)
>
>
> Cheers,
>
> Pete.
>
>
>
>
> _______________________________________________
> webbeans-dev mailing list
> webbeans-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/webbeans-dev
--
Pete Muir
http://www.seamframework.org
http://in.relation.to/Bloggers/Pete
5:56 a.m.
New subject: [webbeans-dev] Request, Conversation and Session Scopes in Web Beans SE
Hi Pete
On 1 May 2009, at 07:34, Peter Royle wrote:
[apologies if this is a double post - I sent one 8 hours ago but
haven't
heard anything from the list]
lists.jboss.org was having some problems, now all fixed.
Hi,
As mentioned previously, I've been doing some experimenting with using
the above contexts in Web Beans within the Java SE environment. Here
are
some patches, diffed from the root webbeans directory, which will add
support for these contexts to the Web Beans SE Module project, plus
modify the Swing SE Numberguess example to use these scopes.
The key points are:
NUMBERGUESS
- A Session is pretty much the whole lifespan of the application,
since
it's single-user.
- A Conversation is a single instance of the game, until it is either
won or lost.
- A Request is a single button click, and is mostly present to support
Conversations using the existing paradigms.
- The Game class is now Conversation scoped. No restart() necessary,
the
NumberGuessFrame simply ends the current conversation when the game is
over and starts a new one.
- This allows the @Random number to be injected directly into Game for
each fresh conversation (rather than injecting the generator and
hanging
on to it)
- NumberGuessFrame injects the current conversation and conversation
manager, as well as the JavaSELifecycle, all of which it uses to
manage
the various contexts (Request, Session and Conversation)
- You can see these contexts being started and stopped during the
start(), guessButtonActionPerformed() and
replayButtonActionPerformed()
methods.
Looks good, though I think we shouldn't have session or request in
here (just conversation and application)
WEB BEANS SE MODULE
- JavaSELifecycle added to help client apps and frameworks manage
lifecycle in SE. This would eventually end up in the SPI perhaps, or
as
a better abstraction of an existing SPI interface.
Yes, I need to finish the lifeycle SPI stuff, I got the idea straight
now :-)
- JavaSEConversationManager is copied from ServletConversationManager
and much of the common code should probably be pushed into an abstract
class.
- WebBeansBootstrap now registers everything except
ServletConversationManager and HttpSessionManager when in SE mode. It
also registers the new JavaSEConversationManager.
My idea is that lifecycle just has methods to do the relevant things
here, and you don't need to worry about things like conversation
manager...
Let me do this work (will be the week after next I think), and then we
can review?
I would like to clean up the syntax for starting requests because it's
obviously pretty ugly and verbose right now. Maybe some kind of
annotation and interceptor pair perhaps? And possibly some
Swing-specific helpers to make it easy to attach the Request context
to
a button click? Making this sort of stuff more transparent is my next
goal.
Let me know what you think, anyone. Cheers.
Pete.
>>
>>
>> Finally, I'm /experimenting/ with enabling and using Request,
>> Session
>> and Conversation scopes/contexts in SE. If you're interested in
>> seeing
>> the working code I've got the changes to core, SE and the number
>> guess
>> example ready to check in to separate branches. Happy to discuss
>> this
>> further if anyone is interested/curious.
>
> Perhaps send a patch out for review (or attach to a JIRA issue?)
>
>>
>>
>> Cheers,
>>
>> Pete.
>>
>>
>>
>>
>> _______________________________________________
>> webbeans-dev mailing list
>> webbeans-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/webbeans-dev
>
> --
> Pete Muir
> http://www.seamframework.org
> http://in.relation.to/Bloggers/Pete
>
<se-contexts.diff>
--
Pete Muir
http://www.seamframework.org
http://in.relation.to/Bloggers/Pete
4:03 p.m.
New subject: [webbeans-dev] Request, Conversation and Session Scopes in Web Beans SE
Hi,
Looks good, though I think we shouldn't have session or request
in
here (just conversation and application)
I can certainly see the benefits of not having to worry about Request
and Session scopes for standalone desktop apps.
There were 2 main reasons I chose to include Request and Session though:
- Primarily for applications other than standalone desktop apps which
happen to have multiple user support and/or are server based, but no
HTTP/Servlet based front-end. For example a Trading platform using FIX
protocol. This almost makes me think that non Servlet scopes belong in a
separate extension - something that could be used in conjunction with
EJB Lite. Thinking aloud a bit there.
- Secondarily, it made it easier to implement Conversation, which uses
those two scopes in the existing implementation.
What are your thoughts on these?
Yes, I need to finish the lifeycle SPI stuff, I got the idea straight
now :-)
My idea is that lifecycle just has methods to do the relevant things
here, and you don't need to worry about things like conversation
manager...
Let me do this work (will be the week after next I think), and then we
can review?
Sounds good!
> I would like to clean up the syntax for starting requests
because it's
> obviously pretty ugly and verbose right now. Maybe some kind of
> annotation and interceptor pair perhaps? And possibly some
> Swing-specific helpers to make it easy to attach the Request context
> to
> a button click? Making this sort of stuff more transparent is my next
> goal.
I guess, as hinted above, probably doing away with Request and Session
scope, or somehow making it completely transparent at least is the way
forward here. Agree?
Cheers,
Pete.
>
> Let me know what you think, anyone. Cheers.
>
>
> Pete.
>
>
>>>
>>>
>>> Finally, I'm /experimenting/ with enabling and using Request,
>>> Session
>>> and Conversation scopes/contexts in SE. If you're interested in
>>> seeing
>>> the working code I've got the changes to core, SE and the number
>>> guess
>>> example ready to check in to separate branches. Happy to discuss
>>> this
>>> further if anyone is interested/curious.
>>
>> Perhaps send a patch out for review (or attach to a JIRA issue?)
>>
>>>
>>>
>>> Cheers,
>>>
>>> Pete.
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> webbeans-dev mailing list
>>> webbeans-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/webbeans-dev
>>
>> --
>> Pete Muir
>> http://www.seamframework.org
>> http://in.relation.to/Bloggers/Pete
>>
> <se-contexts.diff>
--
Pete Muir
http://www.seamframework.org
http://in.relation.to/Bloggers/Pete
5:13 a.m.
New subject: [webbeans-dev] Request, Conversation and Session Scopes in Web Beans SE
On 6 May 2009, at 22:03, Peter Royle wrote:
Hi,
> Looks good, though I think we shouldn't have session or request in
> here (just conversation and application)
I can certainly see the benefits of not having to worry about Request
and Session scopes for standalone desktop apps.
There were 2 main reasons I chose to include Request and Session
though:
- Primarily for applications other than standalone desktop apps which
happen to have multiple user support and/or are server based, but no
HTTP/Servlet based front-end. For example a Trading platform using FIX
protocol. This almost makes me think that non Servlet scopes belong
in a
separate extension - something that could be used in conjunction with
EJB Lite. Thinking aloud a bit there.
- Secondarily, it made it easier to implement Conversation, which uses
those two scopes in the existing implementation.
I'm no expert on desktop apps, but I can see that session might make
sense here - do you have multiple users logged in at the same time?
With conversation - we can code around this I think...
What are your thoughts on these?
> Yes, I need to finish the lifeycle SPI stuff, I got the idea straight
> now :-)
> My idea is that lifecycle just has methods to do the relevant things
> here, and you don't need to worry about things like conversation
> manager...
>
> Let me do this work (will be the week after next I think), and then
> we
> can review?
Sounds good!
>> I would like to clean up the syntax for starting requests because
>> it's
>> obviously pretty ugly and verbose right now. Maybe some kind of
>> annotation and interceptor pair perhaps? And possibly some
>> Swing-specific helpers to make it easy to attach the Request context
>> to
>> a button click? Making this sort of stuff more transparent is my
>> next
>> goal.
I guess, as hinted above, probably doing away with Request and Session
scope, or somehow making it completely transparent at least is the way
forward here. Agree?
Yes
Cheers,
Pete.
>>
>> Let me know what you think, anyone. Cheers.
>>
>>
>> Pete.
>>
>>
>>>>
>>>>
>>>> Finally, I'm /experimenting/ with enabling and using Request,
>>>> Session
>>>> and Conversation scopes/contexts in SE. If you're interested in
>>>> seeing
>>>> the working code I've got the changes to core, SE and the number
>>>> guess
>>>> example ready to check in to separate branches. Happy to discuss
>>>> this
>>>> further if anyone is interested/curious.
>>>
>>> Perhaps send a patch out for review (or attach to a JIRA issue?)
>>>
>>>>
>>>>
>>>> Cheers,
>>>>
>>>> Pete.
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> webbeans-dev mailing list
>>>> webbeans-dev(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/webbeans-dev
>>>
>>> --
>>> Pete Muir
>>> http://www.seamframework.org
>>> http://in.relation.to/Bloggers/Pete
>>>
>> <se-contexts.diff>
>
> --
> Pete Muir
> http://www.seamframework.org
> http://in.relation.to/Bloggers/Pete
>
--
Pete Muir
http://www.seamframework.org
http://in.relation.to/Bloggers/Pete
3:03 p.m.
New subject: [webbeans-dev] Request, Conversation and Session Scopes in Web Beans SE
> - Primarily for applications other than standalone desktop apps
which
> happen to have multiple user support and/or are server based, but no
> HTTP/Servlet based front-end. For example a Trading platform using FIX
> protocol. This almost makes me think that non Servlet scopes belong
> in a
> separate extension - something that could be used in conjunction with
> EJB Lite. Thinking aloud a bit there.
I'm no expert on desktop apps, but I can see that session might make
sense here - do you have multiple users logged in at the same time?
Yeah let me try to explain myself a bit more clearly.
So for a standalone desktop app there would only be one user at any
given time. In which case, having to deal with session scope and even
request scope seems a bit naff. But as the Numberguess example shows
there's potential value in having conversation scope and application
scope.
But take as an example a trading platform which runs as a service in a
dark room somewhere with a purely message based interface (eg: FIX
protocol). This is obviously not a desktop app, nor does it have any
servlet or web based functionality. However it will still have the
notion of multiple users logging in concurrently, sending through
requests and probably long running conversations as well, for things
like trade negotiations. So in this case we could make use of all 3
scopes (session, conversation and request).
Pretty straightforward, I think we're all agreed so far. So finally ...
Imagine implementing a swing based front-end to this trading platform as
a desktop app. If you as a developer are provided with a conversation
scope to code against on both the server and client side, is that a good
thing, or could things start to get a bit confusing? If you could align
the conversations easily between the client and server I think it would
be a good thing. At the very least, on the client side you could make
your conversationId conversation scoped ;).
Thoughts?
Pete.
With conversation - we can code around this I think...
>
>
> What are your thoughts on these?
>
>
>> Yes, I need to finish the lifeycle SPI stuff, I got the idea straight
>> now :-)
>> My idea is that lifecycle just has methods to do the relevant things
>> here, and you don't need to worry about things like conversation
>> manager...
>>
>> Let me do this work (will be the week after next I think), and then
>> we
>> can review?
>
> Sounds good!
>
>>> I would like to clean up the syntax for starting requests because
>>> it's
>>> obviously pretty ugly and verbose right now. Maybe some kind of
>>> annotation and interceptor pair perhaps? And possibly some
>>> Swing-specific helpers to make it easy to attach the Request context
>>> to
>>> a button click? Making this sort of stuff more transparent is my
>>> next
>>> goal.
>
> I guess, as hinted above, probably doing away with Request and Session
> scope, or somehow making it completely transparent at least is the way
> forward here. Agree?
Yes
>
>
> Cheers,
>
> Pete.
>
>>>
>>> Let me know what you think, anyone. Cheers.
>>>
>>>
>>> Pete.
>>>
>>>
>>>>>
>>>>>
>>>>> Finally, I'm /experimenting/ with enabling and using Request,
>>>>> Session
>>>>> and Conversation scopes/contexts in SE. If you're interested in
>>>>> seeing
>>>>> the working code I've got the changes to core, SE and the
number
>>>>> guess
>>>>> example ready to check in to separate branches. Happy to discuss
>>>>> this
>>>>> further if anyone is interested/curious.
>>>>
>>>> Perhaps send a patch out for review (or attach to a JIRA issue?)
>>>>
>>>>>
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Pete.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> webbeans-dev mailing list
>>>>> webbeans-dev(a)lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/webbeans-dev
>>>>
>>>> --
>>>> Pete Muir
>>>> http://www.seamframework.org
>>>> http://in.relation.to/Bloggers/Pete
>>>>
>>> <se-contexts.diff>
>>
>> --
>> Pete Muir
>> http://www.seamframework.org
>> http://in.relation.to/Bloggers/Pete
>>
>
>
--
Pete Muir
http://www.seamframework.org
http://in.relation.to/Bloggers/Pete
6:29 a.m.
New subject: [webbeans-dev] Re: wb-ri-int & idea
The reason is this in deployer/pom.xml
<!-- Test dependencies -->
<dependency>
<groupId>org.jboss.deployers</groupId>
<artifactId>jboss-deployers-vfs</artifactId>
<type>test-jar</type>
<scope>test</scope>
<!--
<exclusions>
<exclusion>
<groupId>org.jboss.deployers</groupId>
<artifactId>jboss-deployers-impl</artifactId>
</exclusion>
<exclusion>
<groupId>org.jboss.deployers</groupId>
<artifactId>jboss-deployers-spi</artifactId>
</exclusion>
<exclusion>
<groupId>org.jboss.microcontainer</groupId>
<artifactId>jboss-kernel</artifactId>
</exclusion>
<exclusion>
<groupId>org.jboss.cl</groupId>
<artifactId>jboss-classloading</artifactId>
</exclusion>
</exclusions>
-->
</dependency>
If I comment that exclusion out, all is fine.
Pete, this is something you added (r83706)
"Depend on released deployers now test jar is available, don't export
any deps from pom"
Why?
Ales Justin wrote:
WRT webbeans-ri-trunk
My IntelliJ IDEA outlook looks broken.
Looking at the WebBeansBootstrapDeployer it cannot link to parts of
JBoss Deployers,
although they are in the Libraries.
Anyone using IDEA and seeing the same problems after re-running "mvn
idea:idea"?
btw: Pete, why is deployers module depending on ejb module (in pom.xml)?
deployer shouldn't depend on anything, as it runtime delegates things.
6:34 a.m.
New subject: [webbeans-dev] Re: wb-ri-int & idea
If I comment that exclusions out, all is fine.
Pete, this is something you added (r83706)
"Depend on released deployers now test jar is available, don't export
any deps from pom"
Why?
Eh, that's not the right revision.
It's the latest, r86882.
Which is something you probably just copied from older mc module?
If yes, I wonder why it worked before ...
If no, the same previous why stands. :-)
Ales Justin wrote:
> WRT webbeans-ri-trunk
>
> My IntelliJ IDEA outlook looks broken.
>
> Looking at the WebBeansBootstrapDeployer it cannot link to parts of
> JBoss Deployers,
> although they are in the Libraries.
>
> Anyone using IDEA and seeing the same problems after re-running "mvn
> idea:idea"?
>
> btw: Pete, why is deployers module depending on ejb module (in pom.xml)?
> deployer shouldn't depend on anything, as it runtime delegates things.
>
6:49 a.m.
New subject: [webbeans-dev] Re: wb-ri-int & idea
On 11 Apr 2009, at 12:34, Ales Justin wrote:
> If I comment that exclusions out, all is fine.
> Pete, this is something you added (r83706)
> "Depend on released deployers now test jar is available, don't
> export any deps from pom"
> Why?
Eh, that's not the right revision.
It's the latest, r86882.
Which is something you probably just copied from older mc module?
If yes, I wonder why it worked before ...
If no, the same previous why stands. :-)
Probably a bug, can you fix it?
> Ales Justin wrote:
>> WRT webbeans-ri-trunk
>>
>> My IntelliJ IDEA outlook looks broken.
>>
>> Looking at the WebBeansBootstrapDeployer it cannot link to parts
>> of JBoss Deployers,
>> although they are in the Libraries.
>>
>> Anyone using IDEA and seeing the same problems after re-running
>> "mvn idea:idea"?
>>
>> btw: Pete, why is deployers module depending on ejb module (in
>> pom.xml)?
>> deployer shouldn't depend on anything, as it runtime delegates
>> things.
Agreed, not needed - if you remove, just verify the webbeans.deployer
zip is still built correctly...
>>
>>
--
Pete Muir
http://www.seamframework.org
http://in.relation.to/Bloggers/Pete
7 a.m.
New subject: [webbeans-dev] Re: wb-ri-int & idea
Pete Muir wrote:
On 11 Apr 2009, at 12:34, Ales Justin wrote:
>> If I comment that exclusions out, all is fine.
>> Pete, this is something you added (r83706)
>> "Depend on released deployers now test jar is available, don't export
>> any deps from pom"
>> Why?
>
> Eh, that's not the right revision.
> It's the latest, r86882.
>
> Which is something you probably just copied from older mc module?
> If yes, I wonder why it worked before ...
> If no, the same previous why stands. :-)
Probably a bug, can you fix it?
I removed the exclusions and it works now.
Already committed on Saturday. ;-)
The only funny thing left for me now is
how jboss-reflect-2.0.0.GA creeps in (it should be 2.0.2.GA).
The "mvn dependency:tree" doesn't show it anywhere.
btw: I implemented WBINT-3 ;-)
7:45 a.m.
New subject: [webbeans-dev] Re: wb-ri-int & idea
Since late Saturday when I updated my SVN working copies, I have no
longer been able to run JBoss AS 5.0.1 with Web Beans (or
webbeans-ri-int). Everyday I rebuild every project for Web Beans and
the JBoss integration and re-install to JBoss AS, but I always get this
same exception regarding JBossEjb:
2009-04-14 14:40:22,822 ERROR
[org.jboss.kernel.plugins.dependency.AbstractKernelController] (main)
Error installing to Real:
name=vfsfile:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/webbeans.deployer/
state=PreReal mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: Error deploying:
vfsfile:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/webbeans.deployer/
at
org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:136)
at
org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployerWithInput.deploy(AbstractRealDeployerWithInput.java:125)
at
org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployerWithInput.internalDeploy(AbstractRealDeployerWithInput.java:102)
at
org.jboss.deployers.spi.deployer.helpers.AbstractComponentDeployer.internalDeploy(AbstractComponentDeployer.java:78)
at
org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at
org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:698)
at
org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:297)
at
org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205)
at
org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405)
at org.jboss.Main.boot(Main.java:209)
at org.jboss.Main$1.run(Main.java:547)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.IllegalArgumentException: Exception loading class
for ScopeKey addition.
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.addBeanComponent(BeanMetaDataFactoryVisitor.java:67)
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:126)
... 23 more
Caused by: java.lang.ClassNotFoundException:
org.jboss.webbeans.integration.util.JBossEjb from
BaseClassLoader@1ec3adc{VFSClassLoaderPolicy@c7f06{name=vfsfile:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/webbeans.deployer/
domain=ClassLoaderDomain@135b1f3{name=DefaultDomain parentPolicy=BEFORE
parent=org.jboss.system.NoAnnotationURLClassLoader@8a0d5d}
roots=[MemoryContextHandler@6782626[path=
context=vfsmemory://3j011-56yegj-ftikzfq0-1-ftikzwzk-e
real=vfsmemory://3j011-56yegj-ftikzfq0-1-ftikzwzk-e],
DelegatingHandler(a)11204174[path=webbeans.deployer/webbeans-jboss-int-deployer.jar
context=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/
real=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/webbeans.deployer/webbeans-jboss-int-deployer.jar],
DelegatingHandler(a)1090100[path=webbeans.deployer/jsr299-api.jar
context=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/
real=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/webbeans.deployer/jsr299-api.jar],
DelegatingHandler(a)605017[path=webbeans.deployer/webbeans-logging.jar
context=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/
real=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/webbeans.deployer/webbeans-logging.jar],
DelegatingHandler(a)1535180[path=webbeans.deployer/webbeans-api.jar
context=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/
real=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/webbeans.deployer/webbeans-api.jar],
DelegatingHandler(a)31979889[path=webbeans.deployer/webbeans-spi.jar
context=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/
real=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/webbeans.deployer/webbeans-spi.jar]]
delegates=null exported=[, org.jboss.webbeans.integration.deployer.cl,
org.jboss.webbeans.servlet.api.helpers, javax.annotation,
org.jboss.webbeans.integration.deployer.metadata,
META-INF.maven.org.jboss.webbeans.webbeans-api, org.jboss.webbeans.bootstrap.spi,
org.jboss.webbeans.servlet.api, org.jboss.webbeans.context.api, org.jboss.webbeans.ws.spi,
javax.inject.manager, javax.interceptor,
META-INF.maven.org.jboss.webbeans.webbeans-logging, org.jboss.webbeans.ejb.api,
org.jboss.webbeans.transaction.spi, org.jboss.webbeans.ejb.spi.helpers, javax.event,
org.jboss.webbeans.persistence.spi.helpers, META-INF.maven.org.jboss.webbeans.jsr299-api,
org.jboss.webbeans.conversation, org.jboss.webbeans.bootstrap.api.helpers,
org.jboss.webbeans.resources.spi.helpers, org.jboss.webbeans.messaging.spi,
org.jboss.webbeans.ejb.spi, org.jboss.webbeans.integration.deployer.ext,
org.jboss.webbeans.ws.spi.helpers, org.jboss.webbeans.manager.api,
org.jboss.webbeans.context.api.helpers, org.jboss.webbeans.bootstrap.api,
org.jboss.webbeans.bootstrap.spi.helpers, META-INF, org.jboss.webbeans.persistence.spi,
javax.context, org.jboss.webbeans.log, javax.webbeans,
META-INF.maven.org.jboss.webbeans.webbeans-spi,
META-INF.maven.org.jboss.webbeans.integration.webbeans-jboss-int-deployer,
org.jboss.webbeans.integration.deployer.env, org.jboss.webbeans.resources.spi,
javax.decorator, org.jboss.webbeans.messaging.spi.helpers,
org.jboss.webbeans.integration.deployer, javax.inject] <IMPORT-ALL>NON_EMPTY}}
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:422)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.addBeanComponent(BeanMetaDataFactoryVisitor.java:63)
... 24 more
2009-04-14 14:40:29,347 ERROR
[org.jboss.system.server.profileservice.ProfileServiceBootstrap] (main)
Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS
ERRORS FOR DETAILS):
On Tue, 2009-04-14 at 14:00 +0200, Ales Justin wrote:
> Pete Muir wrote:
>
> On 11 Apr 2009, at 12:34, Ales Justin wrote:
>
>>> If I comment that exclusions out, all is fine.
>>> Pete, this is something you added (r83706)
>>> "Depend on released deployers now test jar is available, don't
export
>>> any deps from pom"
>>> Why?
>>
>> Eh, that's not the right revision.
>> It's the latest, r86882.
>>
>> Which is something you probably just copied from older mc module?
>> If yes, I wonder why it worked before ...
>> If no, the same previous why stands. :-)
>
> Probably a bug, can you fix it?
I removed the exclusions and it works now.
Already committed on Saturday. ;-)
The only funny thing left for me now is
how jboss-reflect-2.0.0.GA creeps in (it should be 2.0.2.GA).
The "mvn dependency:tree" doesn't show it anywhere.
btw: I implemented WBINT-3 ;-)
_______________________________________________
webbeans-dev mailing list
webbeans-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/webbeans-dev
7:58 a.m.
New subject: [webbeans-dev] Re: wb-ri-int & idea
It might be from my removed deployer --> ejb module dependency.
As I see now assembly.xml in deployer module refs ejb's artifact.
Pete?
David Allen wrote:
Since late Saturday when I updated my SVN working copies, I have no
longer been able to run JBoss AS 5.0.1 with Web Beans (or
webbeans-ri-int). Everyday I rebuild every project for Web Beans and
the JBoss integration and re-install to JBoss AS, but I always get this
same exception regarding JBossEjb:
2009-04-14 14:40:22,822 ERROR
[org.jboss.kernel.plugins.dependency.AbstractKernelController] (main)
Error installing to Real:
name=vfsfile:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/webbeans.deployer/
state=PreReal mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: Error deploying:
vfsfile:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/webbeans.deployer/
at
org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:136)
at
org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployerWithInput.deploy(AbstractRealDeployerWithInput.java:125)
at
org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployerWithInput.internalDeploy(AbstractRealDeployerWithInput.java:102)
at
org.jboss.deployers.spi.deployer.helpers.AbstractComponentDeployer.internalDeploy(AbstractComponentDeployer.java:78)
at
org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at
org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:698)
at
org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:297)
at
org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205)
at
org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405)
at org.jboss.Main.boot(Main.java:209)
at org.jboss.Main$1.run(Main.java:547)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.IllegalArgumentException: Exception loading class
for ScopeKey addition.
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.addBeanComponent(BeanMetaDataFactoryVisitor.java:67)
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:126)
... 23 more
Caused by: java.lang.ClassNotFoundException:
org.jboss.webbeans.integration.util.JBossEjb from
BaseClassLoader@1ec3adc{VFSClassLoaderPolicy@c7f06{name=vfsfile:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/webbeans.deployer/
domain=ClassLoaderDomain@135b1f3{name=DefaultDomain parentPolicy=BEFORE
parent=org.jboss.system.NoAnnotationURLClassLoader@8a0d5d}
roots=[MemoryContextHandler@6782626[path=
context=vfsmemory://3j011-56yegj-ftikzfq0-1-ftikzwzk-e
real=vfsmemory://3j011-56yegj-ftikzfq0-1-ftikzwzk-e],
DelegatingHandler(a)11204174[path=webbeans.deployer/webbeans-jboss-int-deployer.jar
context=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/
real=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/webbeans.deployer/webbeans-jboss-int-deployer.jar],
DelegatingHandler(a)1090100[path=webbeans.deployer/jsr299-api.jar
context=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/
real=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/webbeans.deployer/jsr299-api.jar],
DelegatingHandle
r(a)605017[path=webbeans.deployer/webbeans-logging.jar
context=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/
real=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/webbeans.deployer/webbeans-logging.jar],
DelegatingHandler(a)1535180[path=webbeans.deployer/webbeans-api.jar
context=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/
real=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/webbeans.deployer/webbeans-api.jar],
DelegatingHandler(a)31979889[path=webbeans.deployer/webbeans-spi.jar
context=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/
real=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/webbeans.deployer/webbeans-spi.jar]]
delegates=null exported=[, org.jboss.webbeans.integration.deployer.cl,
org.jboss.webbeans.servlet.api.helpers, javax.annotation,
org.jboss.webbeans.integration.deployer.metadata,
META-INF.maven.org.jboss.webbeans.webbeans-api,
org.jboss.webbeans.bootstrap.spi, org.jboss.webbeans.servlet.api,
org.jboss.webbeans.context.api, org.jboss.webbeans.ws.spi, javax.inject.manager,
javax.interceptor, META-INF.maven.org.jboss.webbeans.webbeans-logging,
org.jboss.webbeans.ejb.api, org.jboss.webbeans.transaction.spi,
org.jboss.webbeans.ejb.spi.helpers, javax.event,
org.jboss.webbeans.persistence.spi.helpers, META-INF.maven.org.jboss.webbeans.jsr299-api,
org.jboss.webbeans.conversation, org.jboss.webbeans.bootstrap.api.helpers,
org.jboss.webbeans.resources.spi.helpers, org.jboss.webbeans.messaging.spi,
org.jboss.webbeans.ejb.spi, org.jboss.webbeans.integration.deployer.ext,
org.jboss.webbeans.ws.spi.helpers, org.jboss.webbeans.manager.api,
org.jboss.webbeans.context.api.helpers, org.jboss.webbeans.bootstrap.api,
org.jboss.webbeans.bootstrap.spi.helpers, META-INF, org.jboss.webbeans.persistence.spi,
javax.context, org.jboss.webbeans.log, javax.webbeans,
META-INF.maven.org.jboss.webbeans.webbeans-spi, META-INF.mav
en.org.jboss.webbeans.integration.webbeans-jboss-int-deployer,
org.jboss.webbeans.integration.deployer.env, org.jboss.webbeans.resources.spi,
javax.decorator, org.jboss.webbeans.messaging.spi.helpers,
org.jboss.webbeans.integration.deployer, javax.inject] <IMPORT-ALL>NON_EMPTY}}
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:422)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.addBeanComponent(BeanMetaDataFactoryVisitor.java:63)
... 24 more
2009-04-14 14:40:29,347 ERROR
[org.jboss.system.server.profileservice.ProfileServiceBootstrap] (main)
Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS
ERRORS FOR DETAILS):
On Tue, 2009-04-14 at 14:00 +0200, Ales Justin wrote:
>> Pete Muir wrote:
>>
>> On 11 Apr 2009, at 12:34, Ales Justin wrote:
>>
>>>> If I comment that exclusions out, all is fine.
>>>> Pete, this is something you added (r83706)
>>>> "Depend on released deployers now test jar is available, don't
export
>>>> any deps from pom"
>>>> Why?
>>> Eh, that's not the right revision.
>>> It's the latest, r86882.
>>>
>>> Which is something you probably just copied from older mc module?
>>> If yes, I wonder why it worked before ...
>>> If no, the same previous why stands. :-)
>> Probably a bug, can you fix it?
> I removed the exclusions and it works now.
> Already committed on Saturday. ;-)
>
> The only funny thing left for me now is
> how jboss-reflect-2.0.0.GA creeps in (it should be 2.0.2.GA).
>
> The "mvn dependency:tree" doesn't show it anywhere.
>
> btw: I implemented WBINT-3 ;-)
> _______________________________________________
> webbeans-dev mailing list
> webbeans-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/webbeans-dev
8:31 a.m.
New subject: [webbeans-dev] Re: wb-ri-int & idea
Exactly :-)
I restored the dep from deployer -> ejb as a runtime dep.
On 14 Apr 2009, at 13:58, Ales Justin wrote:
It might be from my removed deployer --> ejb module dependency.
As I see now assembly.xml in deployer module refs ejb's artifact.
Pete?
David Allen wrote:
> Since late Saturday when I updated my SVN working copies, I have no
> longer been able to run JBoss AS 5.0.1 with Web Beans (or
> webbeans-ri-int). Everyday I rebuild every project for Web Beans and
> the JBoss integration and re-install to JBoss AS, but I always get
> this
> same exception regarding JBossEjb:
> 2009-04-14 14:40:22,822 ERROR
> [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main)
> Error installing to Real:
> name=vfsfile:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/
> deployers/webbeans.deployer/ state=PreReal mode=Manual
> requiredState=Real
> org.jboss.deployers.spi.DeploymentException: Error deploying:
> vfsfile:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/
> deployers/webbeans.deployer/
> at
> org
> .jboss
> .deployers
> .spi
> .DeploymentException
> .rethrowAsDeploymentException(DeploymentException.java:49)
> at
> org
> .jboss
> .deployers
> .vfs
> .deployer
> .kernel
> .BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:
> 136)
> at
> org
> .jboss
> .deployers
> .spi
> .deployer
> .helpers
> .AbstractRealDeployerWithInput
> .deploy(AbstractRealDeployerWithInput.java:125)
> at
> org
> .jboss
> .deployers
> .spi
> .deployer
> .helpers
> .AbstractRealDeployerWithInput
> .internalDeploy(AbstractRealDeployerWithInput.java:102)
> at
> org
> .jboss
> .deployers
> .spi
> .deployer
> .helpers
> .AbstractComponentDeployer
> .internalDeploy(AbstractComponentDeployer.java:78)
> at
> org
> .jboss
> .deployers
> .spi
> .deployer
> .helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
> at
> org
> .jboss
> .deployers
> .plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
> at
> org
> .jboss
> .deployers
> .plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
> at
> org
> .jboss
> .deployers
> .plugins
> .deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:
> 1157)
> at
> org
> .jboss
> .deployers
> .plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
> at
> org
> .jboss
> .dependency
> .plugins
> .AbstractControllerContext.install(AbstractControllerContext.java:
> 348)
> at
> org
> .jboss
> .dependency
> .plugins.AbstractController.install(AbstractController.java:1598)
> at
> org
> .jboss
> .dependency
> .plugins.AbstractController.incrementState(AbstractController.java:
> 934)
> at
> org
> .jboss
> .dependency
> .plugins.AbstractController.resolveContexts(AbstractController.java:
> 1062)
> at
> org
> .jboss
> .dependency
> .plugins.AbstractController.resolveContexts(AbstractController.java:
> 984)
> at
> org
> .jboss
> .dependency
> .plugins.AbstractController.change(AbstractController.java:822)
> at
> org
> .jboss
> .dependency
> .plugins.AbstractController.change(AbstractController.java:553)
> at
> org
> .jboss
> .deployers
> .plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
> at
> org
> .jboss
> .deployers
> .plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:698)
> at
> org
> .jboss
> .system
> .server
> .profileservice
> .ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:
> 297)
> at
> org
> .jboss
> .system
> .server
> .profileservice
> .ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205)
> at
> org
> .jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:
> 405)
> at org.jboss.Main.boot(Main.java:209)
> at org.jboss.Main$1.run(Main.java:547)
> at java.lang.Thread.run(Thread.java:619)
> Caused by: java.lang.IllegalArgumentException: Exception loading
> class
> for ScopeKey addition.
> at
> org
> .jboss
> .deployers
> .vfs
> .deployer
> .kernel
> .BeanMetaDataFactoryVisitor
> .addBeanComponent(BeanMetaDataFactoryVisitor.java:67)
> at
> org
> .jboss
> .deployers
> .vfs
> .deployer
> .kernel
> .BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:
> 126)
> ... 23 more
> Caused by: java.lang.ClassNotFoundException:
> org.jboss.webbeans.integration.util.JBossEjb from
> BaseClassLoader@1ec3adc{VFSClassLoaderPolicy@c7f06{name=vfsfile:/
> home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/
> webbeans.deployer/
> domain=ClassLoaderDomain@135b1f3{name=DefaultDomain
> parentPolicy=BEFORE
> parent=org.jboss.system.NoAnnotationURLClassLoader@8a0d5d}
> roots=[MemoryContextHandler@6782626[path= context=vfsmemory://
> 3j011-56yegj-ftikzfq0-1-ftikzwzk-e real=vfsmemory://3j011-56yegj-
> ftikzfq0-1-ftikzwzk-e],
> DelegatingHandler(a)11204174[path=webbeans.deployer/webbeans-jboss-
> int-deployer.jar context=file:/home/dallen/JBossServer/
> jboss-5.0.1.GA/server/default/deployers/ real=file:/home/dallen/
> JBossServer/jboss-5.0.1.GA/server/default/deployers/
> webbeans.deployer/webbeans-jboss-int-deployer.jar],
> DelegatingHandler(a)1090100[path=webbeans.deployer/jsr299-api.jar
> context=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/
> deployers/ real=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/
> default/deployers/webbeans.deployer/jsr299-api.jar], DelegatingHandle
r(a)605017[path=webbeans.deployer/webbeans-logging.jar context=file:/
home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/
real=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/
deployers/webbeans.deployer/webbeans-logging.jar],
DelegatingHandler(a)1535180[path=webbeans.deployer/webbeans-api.jar
context=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/
deployers/ real=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/
default/deployers/webbeans.deployer/webbeans-api.jar],
DelegatingHandler(a)31979889[path=webbeans.deployer/webbeans-spi.jar
context=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/
deployers/ real=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/
default/deployers/webbeans.deployer/webbeans-spi.jar]]
delegates=null exported=[,
org.jboss.webbeans.integration.deployer.cl,
org.jboss.webbeans.servlet.api.helpers, javax.annotation,
org.jboss.webbeans.integration.deployer.metadata, META-
INF.maven.org.jboss.webbeans.webbeans-api,
org.jboss.webbeans.bootstrap.spi, org.jboss.webbeans.servlet.api,
org.jboss.webbeans.context.api, org.jboss.webbeans.ws.spi,
javax.inject.manager, javax.interceptor, META-
INF.maven.org.jboss.webbeans.webbeans-logging,
org.jboss.webbeans.ejb.api, org.jboss.webbeans.transaction.spi,
org.jboss.webbeans.ejb.spi.helpers, javax.event,
org.jboss.webbeans.persistence.spi.helpers, META-
INF.maven.org.jboss.webbeans.jsr299-api,
org.jboss.webbeans.conversation,
org.jboss.webbeans.bootstrap.api.helpers,
org.jboss.webbeans.resources.spi.helpers,
org.jboss.webbeans.messaging.spi, org.jboss.webbeans.ejb.spi,
org.jboss.webbeans.integration.deployer.ext,
org.jboss.webbeans.ws.spi.helpers, org.jboss.webbeans.manager.api,
org.jboss.webbeans.context.api.helpers,
org.jboss.webbeans.bootstrap.api,
org.jboss.webbeans.bootstrap.spi.helpers, META-INF,
org.jboss.webbeans.persistence.spi, javax.context,
org.jboss.webbeans.log, javax.webbeans, META-
INF.maven.org.jboss.webbeans.webbeans-spi, META-INF.mav
en.org.jboss.webbeans.integration.webbeans-jboss-int-deployer,
org.jboss.webbeans.integration.deployer.env,
org.jboss.webbeans.resources.spi, javax.decorator,
org.jboss.webbeans.messaging.spi.helpers,
org.jboss.webbeans.integration.deployer, javax.inject] <IMPORT-
ALL>NON_EMPTY}}
> at
> org
> .jboss
> .classloader
> .spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:422)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
> at
> org
> .jboss
> .deployers
> .vfs
> .deployer
> .kernel
> .BeanMetaDataFactoryVisitor
> .addBeanComponent(BeanMetaDataFactoryVisitor.java:63)
> ... 24 more
> 2009-04-14 14:40:29,347 ERROR
> [org.jboss.system.server.profileservice.ProfileServiceBootstrap]
> (main)
> Failed to load profile: Summary of incomplete deployments (SEE
> PREVIOUS
> ERRORS FOR DETAILS):
> On Tue, 2009-04-14 at 14:00 +0200, Ales Justin wrote:
>>> Pete Muir wrote:
>>>
>>> On 11 Apr 2009, at 12:34, Ales Justin wrote:
>>>
>>>>> If I comment that exclusions out, all is fine.
>>>>> Pete, this is something you added (r83706)
>>>>> "Depend on released deployers now test jar is available,
don't
>>>>> export any deps from pom"
>>>>> Why?
>>>> Eh, that's not the right revision.
>>>> It's the latest, r86882.
>>>>
>>>> Which is something you probably just copied from older mc module?
>>>> If yes, I wonder why it worked before ...
>>>> If no, the same previous why stands. :-)
>>> Probably a bug, can you fix it?
>> I removed the exclusions and it works now.
>> Already committed on Saturday. ;-)
>>
>> The only funny thing left for me now is
>> how jboss-reflect-2.0.0.GA creeps in (it should be 2.0.2.GA).
>>
>> The "mvn dependency:tree" doesn't show it anywhere.
>>
>> btw: I implemented WBINT-3 ;-)
>> _______________________________________________
>> webbeans-dev mailing list
>> webbeans-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/webbeans-dev
_______________________________________________
webbeans-dev mailing list
webbeans-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/webbeans-dev
--
Pete Muir
http://www.seamframework.org
http://in.relation.to/Bloggers/Pete
9:07 a.m.
New subject: [webbeans-dev] Re: wb-ri-int & idea
On Tue, 2009-04-14 at 14:31 +0100, Pete Muir wrote:
Exactly :-)
I restored the dep from deployer -> ejb as a runtime dep.
OK. Looks like this works now.
On 14 Apr 2009, at 13:58, Ales Justin wrote:
> It might be from my removed deployer --> ejb module dependency.
> As I see now assembly.xml in deployer module refs ejb's artifact.
>
> Pete?
>
> David Allen wrote:
>> Since late Saturday when I updated my SVN working copies, I have no
>> longer been able to run JBoss AS 5.0.1 with Web Beans (or
>> webbeans-ri-int). Everyday I rebuild every project for Web Beans and
>> the JBoss integration and re-install to JBoss AS, but I always get
>> this
>> same exception regarding JBossEjb:
>> 2009-04-14 14:40:22,822 ERROR
>> [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main)
>> Error installing to Real:
>> name=vfsfile:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/
>> deployers/webbeans.deployer/ state=PreReal mode=Manual
>> requiredState=Real
>> org.jboss.deployers.spi.DeploymentException: Error deploying:
>> vfsfile:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/
>> deployers/webbeans.deployer/
>> at
>> org
>> .jboss
>> .deployers
>> .spi
>> .DeploymentException
>> .rethrowAsDeploymentException(DeploymentException.java:49)
>> at
>> org
>> .jboss
>> .deployers
>> .vfs
>> .deployer
>> .kernel
>> .BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:
>> 136)
>> at
>> org
>> .jboss
>> .deployers
>> .spi
>> .deployer
>> .helpers
>> .AbstractRealDeployerWithInput
>> .deploy(AbstractRealDeployerWithInput.java:125)
>> at
>> org
>> .jboss
>> .deployers
>> .spi
>> .deployer
>> .helpers
>> .AbstractRealDeployerWithInput
>> .internalDeploy(AbstractRealDeployerWithInput.java:102)
>> at
>> org
>> .jboss
>> .deployers
>> .spi
>> .deployer
>> .helpers
>> .AbstractComponentDeployer
>> .internalDeploy(AbstractComponentDeployer.java:78)
>> at
>> org
>> .jboss
>> .deployers
>> .spi
>> .deployer
>> .helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
>> at
>> org
>> .jboss
>> .deployers
>> .plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
>> at
>> org
>> .jboss
>> .deployers
>> .plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
>> at
>> org
>> .jboss
>> .deployers
>> .plugins
>> .deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:
>> 1157)
>> at
>> org
>> .jboss
>> .deployers
>> .plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
>> at
>> org
>> .jboss
>> .dependency
>> .plugins
>> .AbstractControllerContext.install(AbstractControllerContext.java:
>> 348)
>> at
>> org
>> .jboss
>> .dependency
>> .plugins.AbstractController.install(AbstractController.java:1598)
>> at
>> org
>> .jboss
>> .dependency
>> .plugins.AbstractController.incrementState(AbstractController.java:
>> 934)
>> at
>> org
>> .jboss
>> .dependency
>> .plugins.AbstractController.resolveContexts(AbstractController.java:
>> 1062)
>> at
>> org
>> .jboss
>> .dependency
>> .plugins.AbstractController.resolveContexts(AbstractController.java:
>> 984)
>> at
>> org
>> .jboss
>> .dependency
>> .plugins.AbstractController.change(AbstractController.java:822)
>> at
>> org
>> .jboss
>> .dependency
>> .plugins.AbstractController.change(AbstractController.java:553)
>> at
>> org
>> .jboss
>> .deployers
>> .plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
>> at
>> org
>> .jboss
>> .deployers
>> .plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:698)
>> at
>> org
>> .jboss
>> .system
>> .server
>> .profileservice
>> .ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:
>> 297)
>> at
>> org
>> .jboss
>> .system
>> .server
>> .profileservice
>> .ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205)
>> at
>> org
>> .jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:
>> 405)
>> at org.jboss.Main.boot(Main.java:209)
>> at org.jboss.Main$1.run(Main.java:547)
>> at java.lang.Thread.run(Thread.java:619)
>> Caused by: java.lang.IllegalArgumentException: Exception loading
>> class
>> for ScopeKey addition.
>> at
>> org
>> .jboss
>> .deployers
>> .vfs
>> .deployer
>> .kernel
>> .BeanMetaDataFactoryVisitor
>> .addBeanComponent(BeanMetaDataFactoryVisitor.java:67)
>> at
>> org
>> .jboss
>> .deployers
>> .vfs
>> .deployer
>> .kernel
>> .BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:
>> 126)
>> ... 23 more
>> Caused by: java.lang.ClassNotFoundException:
>> org.jboss.webbeans.integration.util.JBossEjb from
>> BaseClassLoader@1ec3adc{VFSClassLoaderPolicy@c7f06{name=vfsfile:/
>> home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/
>> webbeans.deployer/
>> domain=ClassLoaderDomain@135b1f3{name=DefaultDomain
>> parentPolicy=BEFORE
>> parent=org.jboss.system.NoAnnotationURLClassLoader@8a0d5d}
>> roots=[MemoryContextHandler@6782626[path= context=vfsmemory://
>> 3j011-56yegj-ftikzfq0-1-ftikzwzk-e real=vfsmemory://3j011-56yegj-
>> ftikzfq0-1-ftikzwzk-e],
>> DelegatingHandler(a)11204174[path=webbeans.deployer/webbeans-jboss-
>> int-deployer.jar context=file:/home/dallen/JBossServer/
>> jboss-5.0.1.GA/server/default/deployers/ real=file:/home/dallen/
>> JBossServer/jboss-5.0.1.GA/server/default/deployers/
>> webbeans.deployer/webbeans-jboss-int-deployer.jar],
>> DelegatingHandler(a)1090100[path=webbeans.deployer/jsr299-api.jar
>> context=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/
>> deployers/ real=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/
>> default/deployers/webbeans.deployer/jsr299-api.jar], DelegatingHandle
> r(a)605017[path=webbeans.deployer/webbeans-logging.jar context=file:/
> home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deployers/
> real=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/
> deployers/webbeans.deployer/webbeans-logging.jar],
> DelegatingHandler(a)1535180[path=webbeans.deployer/webbeans-api.jar
> context=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/
> deployers/ real=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/
> default/deployers/webbeans.deployer/webbeans-api.jar],
> DelegatingHandler(a)31979889[path=webbeans.deployer/webbeans-spi.jar
> context=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/
> deployers/ real=file:/home/dallen/JBossServer/jboss-5.0.1.GA/server/
> default/deployers/webbeans.deployer/webbeans-spi.jar]]
> delegates=null exported=[,
> org.jboss.webbeans.integration.deployer.cl,
> org.jboss.webbeans.servlet.api.helpers, javax.annotation,
> org.jboss.webbeans.integration.deployer.metadata, META-
> INF.maven.org.jboss.webbeans.webbeans-api,
> org.jboss.webbeans.bootstrap.spi, org.jboss.webbeans.servlet.api,
> org.jboss.webbeans.context.api, org.jboss.webbeans.ws.spi,
> javax.inject.manager, javax.interceptor, META-
> INF.maven.org.jboss.webbeans.webbeans-logging,
> org.jboss.webbeans.ejb.api, org.jboss.webbeans.transaction.spi,
> org.jboss.webbeans.ejb.spi.helpers, javax.event,
> org.jboss.webbeans.persistence.spi.helpers, META-
> INF.maven.org.jboss.webbeans.jsr299-api,
> org.jboss.webbeans.conversation,
> org.jboss.webbeans.bootstrap.api.helpers,
> org.jboss.webbeans.resources.spi.helpers,
> org.jboss.webbeans.messaging.spi, org.jboss.webbeans.ejb.spi,
> org.jboss.webbeans.integration.deployer.ext,
> org.jboss.webbeans.ws.spi.helpers, org.jboss.webbeans.manager.api,
> org.jboss.webbeans.context.api.helpers,
> org.jboss.webbeans.bootstrap.api,
> org.jboss.webbeans.bootstrap.spi.helpers, META-INF,
> org.jboss.webbeans.persistence.spi, javax.context,
> org.jboss.webbeans.log, javax.webbeans, META-
> INF.maven.org.jboss.webbeans.webbeans-spi, META-INF.mav
> en.org.jboss.webbeans.integration.webbeans-jboss-int-deployer,
> org.jboss.webbeans.integration.deployer.env,
> org.jboss.webbeans.resources.spi, javax.decorator,
> org.jboss.webbeans.messaging.spi.helpers,
> org.jboss.webbeans.integration.deployer, javax.inject] <IMPORT-
> ALL>NON_EMPTY}}
>> at
>> org
>> .jboss
>> .classloader
>> .spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:422)
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>> at
>> org
>> .jboss
>> .deployers
>> .vfs
>> .deployer
>> .kernel
>> .BeanMetaDataFactoryVisitor
>> .addBeanComponent(BeanMetaDataFactoryVisitor.java:63)
>> ... 24 more
>> 2009-04-14 14:40:29,347 ERROR
>> [org.jboss.system.server.profileservice.ProfileServiceBootstrap]
>> (main)
>> Failed to load profile: Summary of incomplete deployments (SEE
>> PREVIOUS
>> ERRORS FOR DETAILS):
>> On Tue, 2009-04-14 at 14:00 +0200, Ales Justin wrote:
>>>> Pete Muir wrote:
>>>>
>>>> On 11 Apr 2009, at 12:34, Ales Justin wrote:
>>>>
>>>>>> If I comment that exclusions out, all is fine.
>>>>>> Pete, this is something you added (r83706)
>>>>>> "Depend on released deployers now test jar is available,
don't
>>>>>> export any deps from pom"
>>>>>> Why?
>>>>> Eh, that's not the right revision.
>>>>> It's the latest, r86882.
>>>>>
>>>>> Which is something you probably just copied from older mc module?
>>>>> If yes, I wonder why it worked before ...
>>>>> If no, the same previous why stands. :-)
>>>> Probably a bug, can you fix it?
>>> I removed the exclusions and it works now.
>>> Already committed on Saturday. ;-)
>>>
>>> The only funny thing left for me now is
>>> how jboss-reflect-2.0.0.GA creeps in (it should be 2.0.2.GA).
>>>
>>> The "mvn dependency:tree" doesn't show it anywhere.
>>>
>>> btw: I implemented WBINT-3 ;-)
>>> _______________________________________________
>>> webbeans-dev mailing list
>>> webbeans-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/webbeans-dev
> _______________________________________________
> webbeans-dev mailing list
> webbeans-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/webbeans-dev
--
Pete Muir
http://www.seamframework.org
http://in.relation.to/Bloggers/Pete
5990
days inactive
6017
days old
18 comments
6 participants
participants (6)
-
Ales Justin -
David Allen -
Howard Moon -
Pete Muir -
Pete Muir -
Peter Royle