looking what we have today in standalone mode i think exceptions are
useless: people can (should) split their applications into packages
correctly IMHO. Managing classes and packages is (still IMHO) not
interesting for the same reason. For me include/exclude pattern like in
standalone should be eno
Started to type this in the previous email and wow did it get too long
In general I'm still not sure what kind of properties we might want to use to
configure all this. Here's a sample of the xml I imagine:
An include based approach:
org.superbiz
org.w
On Mar 24, 2011, at 11:07 AM, rni...@gmail.com wrote:
> Hi,
>
> Filtering urls/dependencies is probably faster than packages, no?
The straight "require xml files" is the fastest, definitely. With a class
matching pattern like ".*Bean" it would be even faster. I definitely like this
approach
Hi,
Filtering urls/dependencies is probably faster than packages, no?
However i think the ejb-jar approach could still be used/activated by
configuration, it is really a pretty nive feature but it can't be the default
one today, your proposal looks nice as the default behavior.
- Romain
-
Hi, David!
Don't you think that a big ugly warning at startup time with some tips to
the user on how to improve the performance can do the job? This way we keep
the "ejb-jar.xml" (I love this one!), the "go through all classes" and the
"by package" approaches.
[]s,
Thiago.
On Tue, Mar 22, 2011 at
Nevermind... I saw Jonathan's changes.
tkx,
Thiago.
On Wed, Mar 23, 2011 at 9:47 PM, Thiago Veronezi wrote:
> Hi Devs,
> It seems that the problem with the methods return type is fixed, but now we
> have a couple of new methods to implement on our "CdiPlugin.java". Please
> check if following ch
