Re: [jira] Created: (OWB-231) exception using abstract decorators

Spec. says that if Decorator class not @Dependent, unportable behavior occurs. Also it says that @Dependent scoped beans does not require to define default constructor. But what occurs if Decorator is an abstract class? It must define default parameter otherwise it can not be subclassed and instan

Re: [jira] Created: (OWB-231) exception using abstract decorators

I think that this is related with Decorator class has not a default constructor. What is your Decorator bean you are talking about? Does it contain default no param constructor? Thanks; --Gurkan 2010/1/15 Eric Covener (JIRA) > exception using abstract decorators >

Re: [jira] Updated: (OWB-151) @Dependent beans not interceptable

>>>Is this something we should ask about on weld-dev? That will be great! Also, I tried to use EJB level interceptors on ManagedBeans in Weld. It seems that, It does not support it. Thanks; 2010/1/15 Joseph Bergmark > I tried Decorators on Depdenent scoped beans on Weld 1.1.0SP1 today and had

Re: Interceptor API changes

Great! Currently we use 1.1 interceptor specification. But we need to update name of the cdi. Then, http://issues.apache.org/jira/browse/GERONIMO-5007 can be closed. Thanks; --Gurkan 2010/1/14 David Blevins > Heads up on some spec jar changes... > > I've started to run the various geronimo-fo

[jira] Created: (OWB-231) exception using abstract decorators

exception using abstract decorators --- Key: OWB-231 URL: https://issues.apache.org/jira/browse/OWB-231 Project: OpenWebBeans Issue Type: Bug Components: Interceptor and Decorators Affects Versio

Re: [jira] Updated: (OWB-151) @Dependent beans not interceptable

I tried Decorators on Depdenent scoped beans on Weld 1.1.0SP1 today and had the same result: 1) Changes made to the public field were not reflected in calls to methods that used that field 2) Non-default @Inject constructors caused them to fail to create the proxy (and basically blow up with an ex

Interceptor API changes

Heads up on some spec jar changes... I've started to run the various geronimo-foo_spec jars through the Java EE 6 TCK to ensure the signatures are correct. Once of the adjustments is that the javax.interceptor.Interceptor class no longer is marked as @Stereotype (also not @Inherited and on

Re: Comments on dependencies

On Thu, Jan 14, 2010 at 7:31 PM, David Ezzio wrote: > Hi Gurkan, > > Comments inline. > > David > > Gurkan Erdogdu wrote: >> >> Hi David; >> >> Thanks for comments. >> > M2_REPO/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar -- not needed for > compilation >> >> webbeans-impl's pom.xml  does

Re: Comments on dependencies

Hi Gurkan, Comments inline. David Gurkan Erdogdu wrote: Hi David; Thanks for comments. M2_REPO/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar -- not needed for compilation webbeans-impl's pom.xml does not contain this. Where is the location of this dependency, which pom? I don't pretend

Re: Questions on using OWB to implement JSR 299 and JSR 330 for another app server

Hi Mark, Thanks for this brief exposition and the answers to some of my questions. David Mark Struberg wrote: Hi David! To explain this a bit more general: OpenWebBeans has 3 different layers 1st layer is webbeans-impl aka our owb-core. This has almost no non-SE dependency (only one is th

Re: [jira] Updated: (OWB-151) @Dependent beans not interceptable

as far as I've read in the interceptor spec, there is NO interception for fields at all! Have I missed something? LieGrue, strub --- On Thu, 1/14/10, Gurkan Erdogdu wrote: > From: Gurkan Erdogdu > Subject: Re: [jira] Updated: (OWB-151) @Dependent beans not interceptable > To: dev@openwebbean

Re: [jira] Updated: (OWB-151) @Dependent beans not interceptable

I have tried interceptors on @Dependent bean on Jboss RI (Weld). I guess that their implementation also uses Proxy approach (BeanManager# getReference returns proxy instance). I have also tried to use not default constructor stuff. It throws exception. Their implementation is also problematic when

Re: [TOMAHAWK] CDI contributions to tomahawk?

Hey Mark, On Thu, Jan 14, 2010 at 1:41 PM, Mark Struberg wrote: > Hi folks! > > I'm working on the Apache Implementation of JSR-299 OpenWebBeans and I'm > looking forward to add more support for JSF-2 via providing portable CDI > extensions. > > I already implemented an Extension for the javax.

[TOMAHAWK] CDI contributions to tomahawk?

Hi folks! I'm working on the Apache Implementation of JSR-299 OpenWebBeans and I'm looking forward to add more support for JSF-2 via providing portable CDI extensions. I already implemented an Extension for the javax.faces.beans.ViewScoped in our openwebbeans-jsf module, but honestly think tha

Re: Comments on dependencies

find -name '*.java' -type f -exec grep -q 'import javassist.' {} \; -print ./webbeans-jms/src/main/java/org/apache/webbeans/jms/util/JmsUtil.java ./webbeans-jms/src/main/java/org/apache/webbeans/jms/util/JmsProxyHandler.java ./webbeans-impl/src/main/java/org/apache/webbeans/intercept/InterceptorH

Re: Comments on dependencies

David, regarding javassist: We use javassist for 2 concerns: 1.) scanning the classpath for managed beans. This part is completely encapsulated via the MetaDataDiscoveryService SPI. You could easily use your own classpath scanning library and simply set it via openwebbeans.properties. The cur

Re: Comments on dependencies

On Wed, Jan 13, 2010 at 9:37 PM, Gurkan Erdogdu wrote: > Hi David; > > Thanks for comments. > M2_REPO/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar -- not needed for compilation > webbeans-impl's pom.xml  does not contain this. Where is the location of this > dependency, which pom? inher