Re: Site migration setup

t 1:26 PM, Romain Manni-Bucau wrote: > > Le jeu. 5 août 2021 à 20:54, David Jencks a > écrit : > >> What process updates the content? >> > > We have an asf.yaml but didnt see it used fast enough so pushed directly in > main branch the html files. > > >

Re: Site migration setup

? David Jencks > On Aug 5, 2021, at 6:31 AM, Romain Manni-Bucau wrote: > > Hi all, > > AFAIK we migrated our site to https://github.com/apache/openwebbeans-site > > It is ok until we want to publish the content. Until now we were publishing > it to subfolders directly (

Re: Jakarta EE 9 Support

difficulty for developers and probably users. Although I haven’t been active here for years I might even vote. thanks David Jencks > On Jun 7, 2020, at 10:46 AM, Gurkan Erdogdu wrote: > >> >> Tomcat works with branches since years without any issue. >> All projects we

Re: svn commit: r1622766 - /openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/config/BeansDeployer.java

I didn't look at the context, but your commit comment suggests that perhaps the previous throw should also be changed to DeploymentException? If not a comment why the DefinitionException is correct might be appropriate. sorry I'm too lazy to look into this further myself…. thanks da

Re: heavy cleanup

Quite a while back I set up a project at geronimo specs for the 1.1 spec classes, are there changes in any of the classes? thanks david jencks On Nov 25, 2012, at 11:36 AM, Mark Struberg wrote: > I again found a heavy bug which is caused by things like > > > //X TODO this

Re: Eclipse/Checkstyle errors

My opinion as a pretty much completely inactive contributor to OWB is that it would be better to have the test classes follow the same style rules as the main code, but I'm not prepared to help fix it. thanks david jencks On Sep 15, 2012, at 11:09 AM, Thomas Andraschko wrote: > I use

Re: [DISCUSS] implement a hierarchic BeanManager?

and install it with WebBeansFinder.setSingletonService(INSTANCE);. Then you need in the app server infrastructure to notify the singleton service when you enter and leave a context such as web app or ejb module. thanks david jencks On Feb 14, 2012, at 6:16 AM, Joseph Bergmark wrote: > I agree, at the v

Re: [VOTE] drop outdated (and unused) openwebbeans-openejb plugin

+1 drop it david jencks On Dec 27, 2011, at 11:08 AM, Mark Struberg wrote: > Hi! > > I was made aware by David that our openwebbeans-openejb plugin is > > > a.) not needed anymore because the OpenEJB project maintains a much deeper > integration already > b.)

Re: [DISCUSS] CDI-1.1 roadmap

ed in the spec itself. thanks david jencks On Oct 5, 2011, at 1:39 PM, David Jencks wrote: > I created GERONIMO-6182 and set up a geronimo specs project for the cdi 1.1 > spec by copying the 1.0 spec project. > > https://svn.apache.org/repos/asf/geronimo/specs/trunk/geronimo-jcdi_1

Re: [DISCUSS] CDI-1.1 roadmap

I created GERONIMO-6182 and set up a geronimo specs project for the cdi 1.1 spec by copying the 1.0 spec project. https://svn.apache.org/repos/asf/geronimo/specs/trunk/geronimo-jcdi_1.1_spec I'll do my best to apply patches attached to the jira promptly. thanks david jencks On Oct 5, 201

[jira] [Commented] (OWB-582) Support for Java 1.5 (needed for WebSphere 6.1)

[ https://issues.apache.org/jira/browse/OWB-582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079218#comment-13079218 ] David Jencks commented on OWB-582: -- This breaks the geronimo integration and requires u

Re: Snapshots

result in only the first few modules of a broken build getting deployed, but I'm OK with that happening occasionally. thanks david jencks On Jun 22, 2011, at 4:26 PM, Joseph Bergmark wrote: > I set up the Hudson builds for both OpenWebBeans-trunk > and OpenWebBeans_1.0.x. I suspect I

[jira] [Resolved] (OWB-588) PrincipalBean is misspelled

[ https://issues.apache.org/jira/browse/OWB-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved OWB-588. -- Resolution: Fixed rev 1138270 > PrincipalBean is misspel

[jira] [Created] (OWB-588) PrincipalBean is misspelled

Reporter: David Jencks Assignee: David Jencks Fix For: 1.1.1 PrinicipalBean??? Opening a jira since someone might be using the badly spelled version -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software

[jira] [Commented] (OWB-579) check for non-proxyiable methods should exclude synthetic methods

[ https://issues.apache.org/jira/browse/OWB-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052279#comment-13052279 ] David Jencks commented on OWB-579: -- rev 1137824 fixes two interceptor method checks a

[jira] [Commented] (OWB-585) ProcessSessionBean doesn't deal with generic type quite right (CDITCK-215)

[ https://issues.apache.org/jira/browse/OWB-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13048262#comment-13048262 ] David Jencks commented on OWB-585: -- This has to do with org.jboss.js

[jira] [Resolved] (OWB-585) ProcessSessionBean doesn't deal with generic type quite right (CDITCK-215)

[ https://issues.apache.org/jira/browse/OWB-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved OWB-585. -- Resolution: Fixed rev 1134736 > ProcessSessionBean doesn't deal with generic type quite right

[jira] [Created] (OWB-585) ProcessSessionBean doesn't deal with generic type quite right (CDITCK-215)

Beans Issue Type: Bug Components: Events Affects Versions: 1.1.1 Reporter: David Jencks Assignee: David Jencks Fix For: 1.1.1 As discussed in CDITCK-215, there's something odd in ProcessSessionBean: ProcessSessionBean extends ProcessManagedB

Re: Observer method resolution

My fix is in rev 1134736. Jira is down at the moment, I'll open an issue for it when it comes back. Review/comments very welcome :-) thanks david jencks On Jun 11, 2011, at 9:54 AM, David Jencks wrote: > I think I have a solution for this... more soon. > > david jencks >

Re: Observer method resolution

I think I have a solution for this... more soon. david jencks On Jun 10, 2011, at 2:27 PM, David Blevins wrote: > Looks like this is something we have to fix. See the little example I posted > here: > > > https://issues.jboss.org/browse/CDITCK-215?focusedCommentI

[jira] [Resolved] (OWB-584) check for declared name consistency for specializes beans is wrong

[ https://issues.apache.org/jira/browse/OWB-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved OWB-584. -- Resolution: Invalid Both problems are caused by an error in openejb. > check for declared n

[jira] [Created] (OWB-584) check for declared name consistency for specializes beans is wrong

Components: Inheritance, Specialization Affects Versions: 1.1.1 Reporter: David Jencks Assignee: David Jencks tck tests org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise have 3 out of 7 failures caused by this code from

[jira] [Commented] (OWB-581) Decorator interface check needs configurable exclusions

[ https://issues.apache.org/jira/browse/OWB-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044628#comment-13044628 ] David Jencks commented on OWB-581: -- The added interface causes tons more problems.

[jira] [Commented] (OWB-579) check for non-proxyiable methods should exclude synthetic methods

[ https://issues.apache.org/jira/browse/OWB-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044626#comment-13044626 ] David Jencks commented on OWB-579: -- I found a lot more instances where synthetic fields

Re: Yet another proxy/weaving problem

sure what this means but I'm wondering if it would be possible to mark this interface synthetic and have the relevant parts of OWB ignore synthetic interfaces rather than explicitly configuring it to ignore this particular interface? thanks david jencks On Jun 2, 2011, at 11:53 PM, David Jen

[jira] [Resolved] (OWB-581) Decorator interface check needs configurable exclusions

[ https://issues.apache.org/jira/browse/OWB-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved OWB-581. -- Resolution: Fixed Fix Version/s: 1.1.1 rev 1131302. This works, if you have a better idea comment

[jira] [Created] (OWB-581) Decorator interface check needs configurable exclusions

Affects Versions: 1.1.1 Reporter: David Jencks Assignee: David Jencks Aries proxy weaving code adds an interface to every class and so does Cobertura for code coverage. This breaks the implemented interface checks for decorators.Gurkan suggested using the spi

[jira] [Commented] (OWB-579) check for non-proxyiable methods should exclude synthetic methods

[ https://issues.apache.org/jira/browse/OWB-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044159#comment-13044159 ] David Jencks commented on OWB-579: -- After some more input from the aries folks

Yet another proxy/weaving problem

t add this interface? I don't think the jdk proxying code needs to add interfaces.... thanks david jencks

[jira] [Commented] (OWB-579) check for non-proxyiable methods should exclude synthetic methods

[ https://issues.apache.org/jira/browse/OWB-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043233#comment-13043233 ] David Jencks commented on OWB-579: -- revert the change in rev 1130915, cf ARIES-668 whe

[jira] [Commented] (OWB-579) check for non-proxyiable methods should exclude synthetic methods

[ https://issues.apache.org/jira/browse/OWB-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043009#comment-13043009 ] David Jencks commented on OWB-579: -- The original user supplied class doesn't h

[jira] [Resolved] (OWB-579) check for non-proxyiable methods should exclude synthetic methods

[ https://issues.apache.org/jira/browse/OWB-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved OWB-579. -- Resolution: Fixed Fix Version/s: 1.1.1 rev 1130394 also mentions the final methods that can'

[jira] [Created] (OWB-579) check for non-proxyiable methods should exclude synthetic methods

Components: Core Affects Versions: 1.1.1 Reporter: David Jencks Assignee: David Jencks Aries trunk has some weaving code that adds some final synthetic methods to just about every class. AFAICT javassist can still proxy these classes but OWB check for

[jira] [Resolved] (OWB-578) Allow DI for OpenWebBeansConfiguration properties

[ https://issues.apache.org/jira/browse/OWB-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved OWB-578. -- Resolution: Fixed Fix Version/s: 1.1.1 fixed in rev 1129986 > Allow DI

[jira] [Created] (OWB-578) Allow DI for OpenWebBeansConfiguration properties

Versions: 1.1.1 Reporter: David Jencks Assignee: David Jencks I've again run into an osgi situation where no properties files for OWB configuration are visible. I think this is going to be a normal situation in OSGI environments. I'm going to add another cons

Re: svn commit: r1081681 - in /openwebbeans/trunk: webbeans-impl/src/main/java/org/apache/webbeans/corespi/ webbeans-impl/src/main/java/org/apache/webbeans/corespi/security/ webbeans-impl/src/main/res

w imo the whole SecurityManager stuff is broken by design, ever was... dunno about SecurityManager, but I think there's some sense in the Permission based security model and doPrivileged. On the other hand I haven't really tried to do much in an environment where codebase-relate

Re: svn commit: r1081681 - in /openwebbeans/trunk: webbeans-impl/src/main/java/org/apache/webbeans/corespi/ webbeans-impl/src/main/java/org/apache/webbeans/corespi/security/ webbeans-impl/src/main/res

e to be very careful not to pass the instance around in such a way as to make it accessible from outside owb. hopefully I've misunderstood... thanks david jencks On Mar 15, 2011, at 1:27 AM, strub...@apache.org wrote: > Author: struberg > Date: Tue Mar 15 08:27:37 2011 > Ne

Re: TCK working again

will actually be used by OWB when using the class, so there isn't much extra overhead for classes that are actually CDI beans. If we can avoid looking at classes that aren't CDI beans I think we will have done well enough. thanks david jencks On Mar 5, 2011, at 2:43 AM, Mark Struberg wr

Re: TCK working again

pojo beans can be defined lazily on first (dynamic) use. david jencks On Mar 4, 2011, at 4:57 AM, Mark Struberg wrote: > hi! > > I've now fixed the DefinitionUtil#isPurePojoBean and a few other things which > means the TCK is now working again. > > > @djencks: I fear w

[jira] Updated: (OWB-526) remove usage of java.net.URLs from ScannerService and drop scannotation

[ https://issues.apache.org/jira/browse/OWB-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated OWB-526: - Attachment: OsgiMetaDataScannerService.java.mine This is an xbean-based scanner that only finds classes

[jira] Commented: (OWB-538) introduce proprietary configuration option to ignore not explicitly marked (via annotation or registered by extension) Dependent beans

[ https://issues.apache.org/jira/browse/OWB-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000586#comment-13000586 ] David Jencks commented on OWB-538: -- Maybe I've forgotten too much jcdi the last

[jira] Commented: (OWB-538) introduce proprietary configuration option to ignore not explicitly marked (via annotation or registered by extension) Dependent beans

[ https://issues.apache.org/jira/browse/OWB-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000493#comment-13000493 ] David Jencks commented on OWB-538: -- I think the real problem here is that owb curre

[jira] Commented: (OWB-527) JspFactory.getDefaultFactory() is synchronized, We can cache the return value to improve performance

[ https://issues.apache.org/jira/browse/OWB-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999064#comment-12999064 ] David Jencks commented on OWB-527: -- I'm looking at trunk code

[jira] Commented: (OWB-496) Don't replace the ProxyFactory classloaderProvider without the intention to do so

[ https://issues.apache.org/jira/browse/OWB-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997613#comment-12997613 ] David Jencks commented on OWB-496: -- I don't think anyone has tried to explain

Re: Problem with serializing ResourceProxyHandler

ng to ResourceinjectionService, but Mark didn't like that idea. I still do not understand any circumstance in which the existing code would be useful compared with the above. thanks david jencks On Jan 11, 2011, at 2:42 PM, Gerhard wrote: > hi david, > > please provide more details b

Re: svn commit: r1057407 - in /openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans: component/BuildInOwbBean.java proxy/JavassistProxyFactory.java

on info in every BuildinOwbBean which is also wasteful. I would suggest either putting the configuration map into a service in WebBeansContext or simply parsing it in a static method each time a built in bean is created and passing in the type from the subclass constructor. thanks david jencks

Re: Problem with serializing ResourceProxyHandler

useful to support their use as a default implementation. thanks david jencks On Jan 10, 2011, at 4:43 AM, Gerhard wrote: > hi, > > @ResourceInjectionService: > the current trunk breaks backward compatibility with existing owb plugins. > instead of c&p the default implementation

Can we avoid loading all the classes during startup?

bean class is needed immediately. I wonder if it might not be needed immediately for beans with no annotations. Thoughts or advice? thanks david jencks

Re: Next steps with WebBeansContext?

has passed TCK 1.0.4 CR2 with WebProfile. This appears to work in geronimo also many thanks david jencks > > Thanks; > > --Gurkan > > > > - Original Message > From: David Jencks > To: dev@openwebbeans.apache.org > Sent: Sat, January 8, 2011 10:1

Re: Next steps with WebBeansContext?

with rev 1056785 all the standalone tck tests are passing for me so I think we only have the ProcessProducerMethod/Field tests to worry about as far as tck compliance. thanks david jencks On Jan 8, 2011, at 10:43 AM, David Jencks wrote: > I guess as a side effect of these changes in the l

Re: Next steps with WebBeansContext?

I guess as a side effect of these changes in the last day when I run mvn clean install -Ptck locally I've gone from 23 to 1 failing test. I suspect something in the app environment wasn't getting cleaned up appropriately. thanks david jencks On Jan 8, 2011, at 3:25 AM, Mark Stru

Re: svn commit: r1056287 - in /openwebbeans/trunk: webbeans-el10/src/main/java/org/apache/webbeans/el10/ webbeans-impl/src/main/java/org/apache/webbeans/el/ webbeans-impl/src/main/java/org/apache/webb

Before concealing the use of WebBeansContext.getInstance() with this annotation I'd like to see a comment explaining why this is the only way to get the WebBeansContext. thanks david jencks On Jan 7, 2011, at 4:38 AM, gerdo...@apache.org wrote: > @Override > -@Suppr

Re: Can somebody deploy a new snapshot version?

oops, meant to do this yesterday after my commit. Uploading now after locally reverting Gurkan's rev 1056287 which broke the build (seems to be missing a new class) thanks david jencks On Jan 7, 2011, at 4:26 AM, Rick McGuire wrote: > The Geronimo build currently depends on recent ch

Re: Does it needed to deploy single annotated Type if there's no annotation in the impl Class ?

th some details? thanks david jencks On Jan 6, 2011, at 10:08 PM, Shawn Jiang wrote: > I met some CNF problem when running full profile Geronimo TCK. I traced > the problem and found even there's no annoation at all in implClass. > deploySingleAnnoatedType() will still get executed an

[jira] Commented: (OWB-496) Don't replace the ProxyFactory classloaderProvider without the intention to do so

[ https://issues.apache.org/jira/browse/OWB-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978444#action_12978444 ] David Jencks commented on OWB-496: -- I don't understand why you are pursuing this

Re: Yan:: Re: Release 1.1.0

ade to the meaning of the events and the tests are appropriate for a 1.0.x tck. I'm curious what you think. thanks david jencks On Jan 5, 2011, at 11:16 AM, Gurkan Erdogdu wrote: > Hello David > i will look at owb-493 you mentioned. i assume that this is the single failed > tes

Re: Release 1.1.0

se look at your JIRA tasks and close them if no need to stay as open. I don't seem to be able to close issues, just resolve them. thanks david jencks > - Please look at Unscheduled tasks and put them in 1.0.1 or 1.1.0 > > Thanks; > > --Gurkan > > >

[jira] Commented: (OWB-493) ProcessProducerMethod and ProcessProducerField type parameters are reversed in filtering (?) CDITCK-168

[ https://issues.apache.org/jira/browse/OWB-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976635#action_12976635 ] David Jencks commented on OWB-493: -- More info: T - The class of the return type of

Re: Next steps with WebBeansContext?

Some of these ideas are implemented in the patch attached to https://issues.apache.org/jira/browse/OWB-511 thanks david jencks On Dec 31, 2010, at 12:02 PM, David Jencks wrote: > I looked at the WebBeansContext recently and was a little surprised at what > it does and doesn't do.

Re: Problem with serializing ResourceProxyHandler

I put an implementation of the delegation idea in https://issues.apache.org/jira/browse/OWB-511 along with a proposal for making WebBeansContext more useful (IMO). thanks david jencks On Dec 29, 2010, at 4:12 PM, David Jencks wrote: > > On Dec 29, 2010, at 12:24 AM, Mark Struberg

[jira] Updated: (OWB-511) Delegate actualInstance serialization behavior in ResourceProxyHandler

[ https://issues.apache.org/jira/browse/OWB-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated OWB-511: - Attachment: OWB-511.diff proposal for delegating resource serialization and making WebBeansContext more

[jira] Created: (OWB-511) Delegate actualInstance serialization behavior in ResourceProxyHandler

: Bug Components: Core Affects Versions: 1.1.0 Reporter: David Jencks Assignee: Gurkan Erdogdu Fix For: 1.1.0 I suggested this on the dev list, here's a patch to show what I have in mind more definitely. This also includes part of the propos

Next steps with WebBeansContext?

text. Some make sense like ConversationManager where there is no interface and no subclasses, but some are specific implementations of service interfaces such as JndiService and ScannerService where IMO the Default* implementations are unlikely to be used in most integration contexts. thoughts? thanks david jencks

Re: Problem with serializing ResourceProxyHandler

ourceInjectionService? Then I can do the "always lookup in jndi" approach in geronimo and you can avoid it in OWB. thanks david jencks > > LieGrue, > strub > > > > [1] > > --- On Tue, 12/28/10, David Jencks wrote: > >> From: David Jencks

[jira] Resolved: (OWB-510) return null instead of an unusable proxy if a resource is missing

[ https://issues.apache.org/jira/browse/OWB-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved OWB-510. -- Resolution: Fixed fixed in rev 1053774 > return null instead of an unusable proxy if a resource

[jira] Created: (OWB-510) return null instead of an unusable proxy if a resource is missing

Components: Core Affects Versions: 1.1.0 Reporter: David Jencks Assignee: Gurkan Erdogdu Fix For: 1.1.0 Currently if the ResourceInjectionService returns null for a resource we build a proxy that is guaranteed to never work. I think this is really

Re: Problem with serializing ResourceProxyHandler

ResourceSerializationService which if supplied does the serialization. Or we could delegate all the serialization to a ResourceSerializationService so I can implement something that works for geronimo without disturbing the current special-casing of corba stubs. Hoping you can clarify in a way

Re: Problem with serializing ResourceProxyHandler

And another thing... ResourceProxyHandler will have problems if the serializing and deserializing OWB instances differ on whether FailoverService is present. We should write a token to indicate whether FailoverService was used to serialize and use it in deserialization. thanks david jencks

Problem with serializing ResourceProxyHandler

53011) but IMO serializing random objects rather than getting them from the bean is a bad idea. Even with this I get a tck failure trying to deserialze an EntityManagerFactory. thanks david jencks

[jira] Resolved: (OWB-509) Unwrap InvocationTargetException in ResourceProxyHandler.invokie

[ https://issues.apache.org/jira/browse/OWB-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved OWB-509. -- Resolution: Fixed rev 1053011 also includes minor cleanup. The serialization behavior is still causing

[jira] Created: (OWB-509) Unwrap InvocationTargetException in ResourceProxyHandler.invokie

Components: Core Affects Versions: 1.1.0 Reporter: David Jencks Assignee: Gurkan Erdogdu Fix For: 1.1.0 ResourceProxyHandler doesn't unwrap InvocationTargetException, and nothing else knows how either. This messes up some tck tests that test fo

Is there a reason to produce non-working proxies from a ResourceBean?

n NPE if the resource can't be found clearly indicating that there's a problem before the unfortunate user tries to use the proxy. Is there a reason for the current behavior or would this change be fine? thanks david jencks proposed patch: Index: webbeans-impl/src/main/java/org/

[jira] Commented: (OWB-493) ProcessProducerMethod and ProcessProducerField type parameters are reversed in filtering (?) CDITCK-168

[ https://issues.apache.org/jira/browse/OWB-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975071#action_12975071 ] David Jencks commented on OWB-493: -- The javadoc for ProcessProducerMethod

[jira] Commented: (OWB-493) ProcessProducerMethod and ProcessProducerField type parameters are reversed in filtering (?) CDITCK-168

[ https://issues.apache.org/jira/browse/OWB-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974991#action_12974991 ] David Jencks commented on OWB-493: -- I think there is a problem in OWB with the current

[jira] Commented: (OWB-493) ProcessProducerMethod and ProcessProducerField type parameters are reversed in filtering (?) CDITCK-168

[ https://issues.apache.org/jira/browse/OWB-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973126#action_12973126 ] David Jencks commented on OWB-493: -- the tck 1.0.4-SNAPSHOT has changed the test back

geronimo/owb cdi tck status

I have a little bit of evidence that there will be a problem when we run against the full server because I think the test harness is generating invalid ears: the war has a manifest class-path entry that is supposed to point to a jar with all the classes in it, but it appears to be wrong. thanks david jencks

Re: Yan:: svn commit: r1049215 - in /openwebbeans/trunk/webbeans-impl/src: main/java/org/apache/webbeans/event/NotificationManager.java test/java/org/apache/webbeans/newtests/portable/events/extension

other appropriate action with Pete or other CDI EG representative? I don't understand what course of action you want to follow. Is it to fail the most recent tck and ignore the problem? thanks david jencks On Dec 14, 2010, at 1:14 PM, Mark Struberg wrote: > David, as clarified by th

Re: Yan:: svn commit: r1049215 - in /openwebbeans/trunk/webbeans-impl/src: main/java/org/apache/webbeans/event/NotificationManager.java test/java/org/apache/webbeans/newtests/portable/events/extension

rest in passing the tck. thanks david jencks On Dec 14, 2010, at 12:50 PM, Gurkan Erdogdu wrote: > As pete mail, javadoc is correct therefore i reverted change before. If > javadoc is correct those tck tests must be excluded. our code is correct > because it is aligned with published

[jira] Commented: (OWB-490) ProcessObserverMethod Type parameters are inverted (CDITCK-174)

[ https://issues.apache.org/jira/browse/OWB-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971371#action_12971371 ] David Jencks commented on OWB-490: -- I reapplied rev 1034955 in rev 1049215 as the 1.0.2

[jira] Commented: (OWB-490) ProcessObserverMethod Type parameters are inverted (CDITCK-174)

[ https://issues.apache.org/jira/browse/OWB-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971357#action_12971357 ] David Jencks commented on OWB-490: -- Gurkan reverted rev 1034955 in rev 1038667 and 103

[jira] Commented: (OWB-493) ProcessProducerMethod and ProcessProducerField type parameters are reversed in filtering (?) CDITCK-168

[ https://issues.apache.org/jira/browse/OWB-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971351#action_12971351 ] David Jencks commented on OWB-493: -- I'm seeing these errors in the recently relea

[jira] Commented: (OWB-490) ProcessObserverMethod Type parameters are inverted (CDITCK-174)

[ https://issues.apache.org/jira/browse/OWB-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971346#action_12971346 ] David Jencks commented on OWB-490: -- There's a new 1.0.2.SP1 cdi tck available

Re: Is EL in jsp supported at all?

On Dec 13, 2010, at 12:48 AM, Mark Struberg wrote: > Which jasper do you use btw? The tomcat-7 jasper I looked 6 months ago was > pretty broken... Does it work now? AFAICT, it works fine now for normal jsps. I haven't had a chance to dig in and see what is happening here. d

Re: Is EL in jsp supported at all?

This property is set for this sample in geronimo, and the code in WebContainerLifecycle that adds an OwbELResolver is getting executed. I guess I'll have to look inside jasper to see what is going on. thanks david jencks On Dec 9, 2010, at 2:16 PM, Joseph Bergmark wrote: > There is

Is EL in jsp supported at all?

ding or creating an ExpressionBean. Am I doing something obviously stupid? Is there an example of EL + OWB + jsp working? thanks david jencks

Re: Yan:: svn commit: r1042754 - /openwebbeans/trunk/webbeans-jsf/src/main/resources/META-INF/faces-config.xml

k for jsf pages. So far I still think the OwbApplicationFactory doesn't do anything useful, but I'm keeping an open mind until I have more evidence. thanks david jencks On Dec 8, 2010, at 11:37 AM, Gurkan Erdogdu wrote: > David, > > This is for JSF pages not an ordinary JS

Re: Yan:: svn commit: r1042754 - /openwebbeans/trunk/webbeans-jsf/src/main/resources/META-INF/faces-config.xml

Type(Counter.class).getCount() == 2; assert getInstanceByType(Counter.class).getDestroy() == 2; } with the obvious corresponding changes in Counter and Game. thanks david jencks On Dec 7, 2010, at 9:49 AM, David Jencks wrote: > I'm investigating this further. I don't see

Re: Yan:: svn commit: r1042754 - /openwebbeans/trunk/webbeans-jsf/src/main/resources/META-INF/faces-config.xml

I'm investigating this further. I don't see any jcdi tck failures in geronimo with my patch so I'd like to determine if the requirements in 6.4.3 are actually tested. thanks david jencks On Dec 7, 2010, at 5:27 AM, Gurkan Erdogdu wrote: > David, >

Re: Proxy problems

vasisst. Are you saying that if I say tomorrow removed javassist in favor of proxy creation that did not require exposing server classes to applications that would not be acceptable for the next OWB release? If so, why? Hoping you can clarify what you mean, david jencks > > Regards

Proxy problems

jdk classes. Is there any good reason to use javassist rather than something else? thanks david jencks

Re: Yan:: svn commit: r1042754 - /openwebbeans/trunk/webbeans-jsf/src/main/resources/META-INF/faces-config.xml

would like to know about it. Since I don't see any spec support for this I wonder if installing it automatically results in portable apps. thanks david jencks On Dec 6, 2010, at 12:24 PM, Gurkan Erdogdu wrote: > Hi David > we designed owb as a plugin way. When he wants to add jsf

[jira] Commented: (OWB-505) OwbApplicationFactory should not be installed by default

[ https://issues.apache.org/jira/browse/OWB-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967465#action_12967465 ] David Jencks commented on OWB-505: -- rev 1042754. Not resolving for easier re

[jira] Created: (OWB-505) OwbApplicationFactory should not be installed by default

: Core Affects Versions: 1.1.0 Reporter: David Jencks Assignee: Gurkan Erdogdu Fix For: 1.1.0 Although OwbApplicationFactory is convenient, there's nothing in the spec that indicates that something like it should be installed by default. Currently ger

[jira] Resolved: (OWB-504) OwbApplicationFactory getWrapped should return wrapped application factory

[ https://issues.apache.org/jira/browse/OWB-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved OWB-504. -- Resolution: Fixed rev 1042752 > OwbApplicationFactory getWrapped should return wrapped applicat

[jira] Created: (OWB-504) OwbApplicationFactory getWrapped should return wrapped application factory

Issue Type: Bug Components: Core Affects Versions: 1.1.0 Reporter: David Jencks Assignee: Gurkan Erdogdu Fix For: 1.1.0 getWrapped currently delegates to the wrapped ApplicationFactory -- This message is automatically generated by JIRA. - You can

Re: [jira] Commented: (OWB-502) Only cache the ContextService once, in the SingletonService

which should be even faster than the TCCL cache I removed. thanks again david jencks On Nov 30, 2010, at 12:23 AM, Gurkan Erdogdu (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/OWB-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focused

[jira] Commented: (OWB-502) Only cache the ContextService once, in the SingletonService

[ https://issues.apache.org/jira/browse/OWB-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965037#action_12965037 ] David Jencks commented on OWB-502: -- Fixed in rev 1040364. > Only cache the Context

[jira] Created: (OWB-502) Only cache the ContextService once, in the SingletonService

Components: Core Affects Versions: 1.0.1 Reporter: David Jencks Assignee: Gurkan Erdogdu Fix For: 1.0.1 Currently the ContextService is cached once in the SingletonService, which can be replaced in environments that don't use enough classloaders to distin

[jira] Commented: (OWB-498) Java EE Resource Injections for CDI Interceptors & Decorators

[ https://issues.apache.org/jira/browse/OWB-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935477#action_12935477 ] David Jencks commented on OWB-498: -- I think there is at least a strong possibility that

[jira] Commented: (OWB-497) Don't break deployment if java can't read all the annotations

[ https://issues.apache.org/jira/browse/OWB-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934669#action_12934669 ] David Jencks commented on OWB-497: -- rev 1037951 fixes the two places I've had prob

  1   2   >