Re: testng in eclipse -- can't debug from 'failed tests'

2010-02-24 Thread Gurkan Erdogdu
This might be an Eclipse related bug. Please try to run tests using Run/Debug Configuration. One thing, currently openwebbeans-tck/jsr299...xml does not include interceptors test. To include them please add to packages section. Thanks; --Gurkan 2010/2/25 Eric Covener > Hoping someone can get

[DISCUSSION] Performance of OWB

2010-02-24 Thread Gurkan Erdogdu
Hi; In fact, I have not done any performance related work on OWB so far. I just want to kick start a discussion on Performance Problems/Solutions of OWB. I will also create an JIRA issue. Mainly, performance problems occur resulting from; 1* Lots of proxy usage 2* Bean resolution algorithms used

[DISCUSSION] Using of Logginf in OWB

2010-02-24 Thread Gurkan Erdogdu
Hi; Last couple of days there were some good discussion on how to proceed with logging in OWB. There are some approaches: 1* Remove any hard log dependency library from classpath(For example : removing log4.jar from classpath) and use java logging. 2* Use some third-party facades, for example usi

Re: TCK Report Before M4

2010-02-24 Thread Gurkan Erdogdu
>>>Gurkan, thanks for the great work! We thanks to all, not just me :) >>>current OWB version is pretty stable Yes, but if we pass TCK fully that will be very cool! --Gurkan 2010/2/25 Mark Struberg > Gurkan, thanks for the great work! > > current OWB version is pretty stable (taking apart the

Re: TCK Report Before M4

2010-02-24 Thread Gurkan Erdogdu
Yes, I know Joe :) . That is great, thanks; --Gurkan 25 Şubat 2010 00:02 tarihinde Joseph Bergmark yazdı: > As I am sure you are already aware I've been working on some of the > Decorator based TCK tests. I've even opened at least one bug to find out > you fixed it a few hours beforehand :) >

Re: testng in eclipse -- can't debug from 'failed tests'

2010-02-24 Thread Joseph Bergmark
I've been running individual classes by going to either Debug or Run and then the "Run Configurations" (or equivalent debug configurations) and then typing in the class name beside the class radio button for a TestNG type. I haven't tried running a single class or method from inside the result tab

testng in eclipse -- can't debug from 'failed tests'

2010-02-24 Thread Eric Covener
Hoping someone can get me on the right track. I'm using eclipse 3.5.1 and latest testng. I can right-click the openwebbeans-tck/jsr299...xml and run with 33/549 failures. When i look in the testNG results tab, neither run or debug of individual failers responds at all in the GUI. I get a very un-g

Re: TCK Report Before M4

2010-02-24 Thread Joseph Bergmark
As I am sure you are already aware I've been working on some of the Decorator based TCK tests. I've even opened at least one bug to find out you fixed it a few hours beforehand :) Primarily I've been focused on: org.jboss.jsr299.tck.tests.decorators.invocation.DecoratorInvocationTests (opened OW

AW: TCK Report Before M4

2010-02-24 Thread Mark Struberg
Gurkan, thanks for the great work! current OWB version is pretty stable (taking apart the bug in the javassist library, which one can simply upgrade later by explicitly declaring a newer version in a custom project instead of taking the default version one gets as a transitive dependency. LieG

TCK Report Before M4

2010-02-24 Thread Gurkan Erdogdu
Hello folks; I have been working on standalone TCK (standalone means that not running in container but includes EJB tests using OpenEJB) for a long time and decreased the number of failed tests considerably. Some of those failed tests are related with CDI-TCK bug and reported to CDI-TCK team.

[jira] Created: (OWB-302) InjectionPoint injections (both method and field based) in Decorators result in null

2010-02-24 Thread Joe Bergmark (JIRA)
InjectionPoint injections (both method and field based) in Decorators result in null Key: OWB-302 URL: https://issues.apache.org/jira/browse/OWB-302 Project: OpenWeb

[jira] Commented: (OWB-300) Currently OWB requires log4j for logging. This patch provides a means of choosing other loggers.

2010-02-24 Thread James Carman (JIRA)
[ https://issues.apache.org/jira/browse/OWB-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837867#action_12837867 ] James Carman commented on OWB-300: -- I understand the whole idea about minimizing dependencies

[jira] Updated: (OWB-300) Currently OWB requires log4j for logging. This patch provides a means of choosing other loggers.

2010-02-24 Thread Paul J. Reder (JIRA)
[ https://issues.apache.org/jira/browse/OWB-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul J. Reder updated OWB-300: -- Description: Currently OWB requires (is dependent on) log4j for logging. This patch provides a means of ch

[jira] Commented: (OWB-300) Currently OWB requires log4j for logging. This patch provides a means of choosing other loggers.

2010-02-24 Thread Paul J. Reder (JIRA)
[ https://issues.apache.org/jira/browse/OWB-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837857#action_12837857 ] Paul J. Reder commented on OWB-300: --- SLF4J does appear to provide support for args and NLS b

[jira] Closed: (OWB-301) WebBeansDecorators getDecoratedTypes returns the types of the wrapped bean instead of its list of decorated types

2010-02-24 Thread Joe Bergmark (JIRA)
[ https://issues.apache.org/jira/browse/OWB-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bergmark closed OWB-301. Resolution: Fixed Fix Version/s: (was: 1.0.0) M4 Assignee: Gurkan Erdogd

[jira] Created: (OWB-301) WebBeansDecorators getDecoratedTypes returns the types of the wrapped bean instead of its list of decorated types

2010-02-24 Thread Joe Bergmark (JIRA)
WebBeansDecorators getDecoratedTypes returns the types of the wrapped bean instead of its list of decorated types - Key: OWB-301 URL: https://issues.ap

[jira] Resolved: (OWB-299) WebBeansUtil's checkDecoratorResolverParams does not always check that the annotations passed are qualifiers

2010-02-24 Thread Joe Bergmark (JIRA)
[ https://issues.apache.org/jira/browse/OWB-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bergmark resolved OWB-299. -- Resolution: Fixed Fix Version/s: (was: 1.0.0) M4 Integrated change to always

[jira] Commented: (OWB-300) Currently OWB requires log4j for logging. This patch provides a means of choosing other loggers.

2010-02-24 Thread Joe Bergmark (JIRA)
[ https://issues.apache.org/jira/browse/OWB-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837831#action_12837831 ] Joe Bergmark commented on OWB-300: -- Just wanted to provide some history on this. I believe t

[jira] Commented: (OWB-300) Currently OWB requires log4j for logging. This patch provides a means of choosing other loggers.

2010-02-24 Thread James Carman (JIRA)
[ https://issues.apache.org/jira/browse/OWB-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837814#action_12837814 ] James Carman commented on OWB-300: -- So, use SLF4J. Some folks don't like (including myself)

[jira] Commented: (OWB-300) Currently OWB requires log4j for logging. This patch provides a means of choosing other loggers.

2010-02-24 Thread Paul J. Reder (JIRA)
[ https://issues.apache.org/jira/browse/OWB-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837809#action_12837809 ] Paul J. Reder commented on OWB-300: --- I'm not an expert at Commons logging so I may have miss