[
https://issues.apache.org/jira/browse/OWB-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12892180#action_12892180
]
Gerhard Petracek commented on OWB-425:
--
here i see up to 60 % for @RequestScoped and @Ses
[
https://issues.apache.org/jira/browse/OWB-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek updated OWB-425:
-
Attachment: OWB-425.patch
this patch improves the performance of the owb-el-resolver up to 40%
> im
improve performance of owb-el-resolver
--
Key: OWB-425
URL: https://issues.apache.org/jira/browse/OWB-425
Project: OpenWebBeans
Issue Type: Improvement
Components: Injection and Lookup
Affect
+1
On Sun, Jul 25, 2010 at 1:28 PM, Eric Covener wrote:
> How do people feel / who do we ask to turn on a CIA bot for commit
> messages in #openwebbeans?
>
> I am personally +1
>
> --
> Eric Covener
> cove...@gmail.com
>
[
https://issues.apache.org/jira/browse/OWB-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Covener reassigned OWB-422:
Assignee: Eric Covener (was: Gurkan Erdogdu)
> Support needed for PrePassivate, PostActivate, and Aro
How do people feel / who do we ask to turn on a CIA bot for commit
messages in #openwebbeans?
I am personally +1
--
Eric Covener
cove...@gmail.com
Paul, can you submit a followup patch to address a few issues inline below?
> + �...@aroundtimeout
> + public Object callAroundTimeouts(InvocationContext context) throws
> Exception
> + {
> + Object retVal = null;
> + InjectionTargetBean injectionTarget = (InjectionTargetBe
Hi!
+1 on improving our docu ;)
I usually run the TCK after big changes, but since dropping the EL listener was
almost a no-brainer (just used lazy init instead of it), I have to admit that I
didn't run it. Otoh such things like the change with caching the bean-proxy are
definitely not tested
On Sat, Jul 24, 2010 at 3:15 PM, Gurkan Erdogdu wrote:
> http://svn.apache.org/repos/asf/openwebbeans/trunk/readme/TCK_RUNNING.txt
>
Thanks Gurkan -- I ran standalone and got these results (twice) :
Tests run: 574, Failures: 10, Errors: 0, Skipped: 0, Time elapsed:
42.527 sec <<< FAILURE!
Results
