[jira] [Assigned] (OWB-1215) Specializing more then one producer method not working
[
https://issues.apache.org/jira/browse/OWB-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg reassigned OWB-1215:
--
Assignee: Mark Struberg
> Specializing more then one producer method not working
> --
>
> Key: OWB-1215
> URL: https://issues.apache.org/jira/browse/OWB-1215
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Inheritance, Specialization
>Affects Versions: 2.0.0
>Reporter: Jan Krpata
>Assignee: Mark Struberg
>
> A have problem with specializing a producer method
> - https://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#specialize_producer_method
> I have class A with many @Produces methods.
> I have class B extends A, where I can override some producer methods (more
> then one and not all) from superclass. The other producer methods must be
> still enabled from superclass.
> Method WebBeansUtil.configureProducerMethodSpecializations throw
> WebBeansDeploymentException "Multiple specializations for the same producer
> method got detected for type".
> Example:
> {code:java}
> public class A {
> @Produces
> @OneProducesMethod
> public Boolean getX() { ...}
> @Produces
> @TwoProducesMethod
> public Boolean getY() { ...}
> @Produces
> @ThreeProducesMethod
> public Boolean getZ() { ...}
> }
> public class B extends A {
> @Produces
> @Specializes
> @OneProducesMethod
> public Boolean getX() { ...}
> @Produces
> @Specializes
> @TwoProducesMethod
> public Boolean getY() { ...}
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OWB-1213) producer of URI or other classes with private ct blow up with a NPE
[ https://issues.apache.org/jira/browse/OWB-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OWB-1213: --- Description: URI has a private ct, so it's not a valid bean type. Otoh one can easily a producer method returning an URI. Currently this blows up with a NPE because any type is also checked for self-injection. > producer of URI or other classes with private ct blow up with a NPE > --- > > Key: OWB-1213 > URL: https://issues.apache.org/jira/browse/OWB-1213 > Project: OpenWebBeans > Issue Type: Bug > Components: Core >Affects Versions: 2.0.0 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 2.0.1 > > > URI has a private ct, so it's not a valid bean type. > Otoh one can easily a producer method returning an URI. > Currently this blows up with a NPE because any type is also checked for > self-injection. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OWB-1213) producer of URI or other classes with private ct blow up with a NPE
Mark Struberg created OWB-1213: -- Summary: producer of URI or other classes with private ct blow up with a NPE Key: OWB-1213 URL: https://issues.apache.org/jira/browse/OWB-1213 Project: OpenWebBeans Issue Type: Bug Components: Core Affects Versions: 2.0.0 Reporter: Mark Struberg Fix For: 2.0.1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OWB-1213) producer of URI or other classes with private ct blow up with a NPE
[ https://issues.apache.org/jira/browse/OWB-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned OWB-1213: -- Assignee: Mark Struberg > producer of URI or other classes with private ct blow up with a NPE > --- > > Key: OWB-1213 > URL: https://issues.apache.org/jira/browse/OWB-1213 > Project: OpenWebBeans > Issue Type: Bug > Components: Core >Affects Versions: 2.0.0 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 2.0.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OWB-1209) Custom bean with isAlternative()=true should not be automatically enabled
[
https://issues.apache.org/jira/browse/OWB-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123312#comment-16123312
]
Mark Struberg commented on OWB-1209:
Oki, will review the spec again and keep you updated. Txs for the report in any
case!
> Custom bean with isAlternative()=true should not be automatically enabled
> -
>
> Key: OWB-1209
> URL: https://issues.apache.org/jira/browse/OWB-1209
> Project: OpenWebBeans
> Issue Type: Bug
>Reporter: Martin Kouba
>Assignee: Mark Struberg
>
> It seems that if you register a custom bean where {{isAlternative()}} returns
> true, the bean is automatically enabled. However, the container should use
> {{getBeanClass()}}, see also "Declaring selected alternatives for a bean
> archive":
> {quote}
> For a custom implementation of the Bean interface defined in The Bean
> interface, the container calls isAlternative() to determine whether the bean
> is an alternative, and getBeanClass() and getStereotypes() to determine
> whether an alternative is selected in a certain bean archive.
> {quote}
> Moreover, if I specify the bean class of a custom bean in the {{beans.xml}} I
> get :
> {noformat}
> Given alternative class : org.jboss.cdi.builtinbeans.IntegerEventBean is not
> annotated wih @Alternative or not an enabled bean
> {noformat}
> To reproduce, checkout https://github.com/mkouba/alternative-builtin-beans
> and modify
> https://github.com/mkouba/alternative-builtin-beans/blob/master/src/test/java/org/jboss/cdi/builtinbeans/BeansXml.java#L25
> to always return beans.xml with enablement. Then run:
> {noformat}
> mvn clean test -DcdiImpl=owb1
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OWB-1210) Providing an own alternative implementation of Provider might disable some Instance resolving
Mark Struberg created OWB-1210: -- Summary: Providing an own alternative implementation of Provider might disable some Instance resolving Key: OWB-1210 URL: https://issues.apache.org/jira/browse/OWB-1210 Project: OpenWebBeans Issue Type: Bug Affects Versions: 2.0.0 Reporter: Mark Struberg Assignee: Mark Struberg Fix For: 2.0.1 When a user creates a Bean which implements Provider for a certain Qualifier @X then this might break Instance injection for other Qualifiers. Detected by [~mkouba], txs! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OWB-1209) Custom bean with isAlternative()=true should not be automatically enabled
[
https://issues.apache.org/jira/browse/OWB-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-1209.
Resolution: Not A Problem
Assignee: Mark Struberg
In OWB we use the section 5 definition of BDA. Means a BDA is per Module
And for each Module we have a separate BeanManager.
Only active Beans make it to the list of available Beans for
BeanManager.getBeans();
If someone adds an Alternative Bean via an Extension then it's assumed that is
is active for this Module.
> Custom bean with isAlternative()=true should not be automatically enabled
> -
>
> Key: OWB-1209
> URL: https://issues.apache.org/jira/browse/OWB-1209
> Project: OpenWebBeans
> Issue Type: Bug
>Reporter: Martin Kouba
>Assignee: Mark Struberg
>
> It seems that if you register a custom bean where {{isAlternative()}} returns
> true, the bean is automatically enabled. However, the container should use
> {{getBeanClass()}}, see also "Declaring selected alternatives for a bean
> archive":
> {quote}
> For a custom implementation of the Bean interface defined in The Bean
> interface, the container calls isAlternative() to determine whether the bean
> is an alternative, and getBeanClass() and getStereotypes() to determine
> whether an alternative is selected in a certain bean archive.
> {quote}
> Moreover, if I specify the bean class of a custom bean in the {{beans.xml}} I
> get :
> {noformat}
> Given alternative class : org.jboss.cdi.builtinbeans.IntegerEventBean is not
> annotated wih @Alternative or not an enabled bean
> {noformat}
> To reproduce, checkout https://github.com/mkouba/alternative-builtin-beans
> and modify
> https://github.com/mkouba/alternative-builtin-beans/blob/master/src/test/java/org/jboss/cdi/builtinbeans/BeansXml.java#L25
> to always return beans.xml with enablement. Then run:
> {noformat}
> mvn clean test -DcdiImpl=owb1
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OWB-1205) We should not fire ProcessInjectionPoint for CDI Extension Observers
Mark Struberg created OWB-1205: -- Summary: We should not fire ProcessInjectionPoint for CDI Extension Observers Key: OWB-1205 URL: https://issues.apache.org/jira/browse/OWB-1205 Project: OpenWebBeans Issue Type: Bug Affects Versions: 2.0.0 Reporter: Mark Struberg Assignee: Mark Struberg Fix For: 2.0.1 We currently fire ProcessInjectionPoint for all InjectionPoints of Observers. We should omit those for lifecycle events in Extensions. Because at that time the Extensions are not yet booted and not even the BeanManager is up and running. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OWB-1198) Randomly broken Test in CDI TCK MessageDrivenBeanInterceptorInvocationTest
Mark Struberg created OWB-1198:
--
Summary: Randomly broken Test in CDI TCK
MessageDrivenBeanInterceptorInvocationTest
Key: OWB-1198
URL: https://issues.apache.org/jira/browse/OWB-1198
Project: OpenWebBeans
Issue Type: Bug
Environment: Linux, FC25, Java8
Reporter: Mark Struberg
{noformat}
[INFO] OpenEJB :: TCK :: Common ... SUCCESS [ 0.751 s]
[INFO] OpenEJB :: TCK :: CDI Embedded . FAILURE [04:12 min]
{noformat}
{noformat}
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
INFORMATION - Invoke DecoratorTypeParamInitializerTest.testDeploymentFails:
1.479/1.479 Failed tests: 1 (644)
INFORMATION - Stopping network services
INFORMATION - Stopping server services
INFORMATION - Destroying container system
INFORMATION - Scheduler OpenEJB-TimerService-Scheduler_$_OpenEJB shutting down.
INFORMATION - Scheduler OpenEJB-TimerService-Scheduler_$_OpenEJB paused.
INFORMATION - Scheduler unregistered from name
'quartz:type=QuartzScheduler,name=OpenEJB-TimerService-Scheduler,instance=OpenEJB'
in the local MBeanServer.
INFORMATION - Scheduler OpenEJB-TimerService-Scheduler_$_OpenEJB shutdown
complete.
INFORMATION - Closing DataSource: jdbc
INFORMATION - Closing DataSource: jdbcNonJta
INFORMATION - Stopping ResourceAdapter: Default JMS Resource Adapter
INFORMATION - Stopping ActiveMQ
INFORMATION - Apache ActiveMQ 5.14.3 (localhost,
ID:stehtnix-43855-1499679488155-0:1) is shutting down
INFORMATION - Connector tcp://localhost.localdomain:35107 stopped
INFORMATION - Connector vm://localhost stopped
INFORMATION - Apache ActiveMQ 5.14.3 (localhost,
ID:stehtnix-43855-1499679488155-0:1) uptime 4 minutes
INFORMATION - Apache ActiveMQ 5.14.3 (localhost,
ID:stehtnix-43855-1499679488155-0:1) is shutdown
INFORMATION - Stopped ActiveMQ broker
Tests run: 1479, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 250.712 sec
<<< FAILURE! - in TestSuite
testMessageDrivenBeanMethodIntercepted(org.jboss.cdi.tck.tests.interceptors.definition.enterprise.jms.MessageDrivenBeanInterceptorInvocationTest)
Time elapsed: 5.026 sec <<< FAILURE!
java.lang.AssertionError: expected [true] but found [false]
at org.testng.Assert.fail(Assert.java:94)
at org.testng.Assert.failNotEquals(Assert.java:494)
at org.testng.Assert.assertTrue(Assert.java:42)
at org.testng.Assert.assertTrue(Assert.java:52)
at
org.jboss.cdi.tck.tests.interceptors.definition.enterprise.jms.MessageDrivenBeanInterceptorInvocationTest.testMessageDrivenBeanMethodIntercepted(MessageDrivenBeanInterceptorInvocationTest.java:92)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OWB-1197) OwbSWClassLoader creates wrong URL
Mark Struberg created OWB-1197: -- Summary: OwbSWClassLoader creates wrong URL Key: OWB-1197 URL: https://issues.apache.org/jira/browse/OWB-1197 Project: OpenWebBeans Issue Type: Bug Components: Arquillian Reporter: Mark Struberg -return new URL(null, "archive:" + nodes.iterator().next()); +return new URL(null, "archive:" + nodes.iterator().next(), new ArchiveStreamHandler()); Otherwise we blow up with a MalformedURLException. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OWB-1197) OwbSWClassLoader creates wrong URL
[ https://issues.apache.org/jira/browse/OWB-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OWB-1197: --- Fix Version/s: 1.7.5 2.0.0 > OwbSWClassLoader creates wrong URL > -- > > Key: OWB-1197 > URL: https://issues.apache.org/jira/browse/OWB-1197 > Project: OpenWebBeans > Issue Type: Bug > Components: Arquillian >Reporter: Mark Struberg > Fix For: 2.0.0, 1.7.5 > > > -return new URL(null, "archive:" + nodes.iterator().next()); > +return new URL(null, "archive:" + nodes.iterator().next(), > new ArchiveStreamHandler()); > Otherwise we blow up with a MalformedURLException. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OWB-1197) OwbSWClassLoader creates wrong URL
[ https://issues.apache.org/jira/browse/OWB-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-1197. Resolution: Fixed Assignee: Mark Struberg > OwbSWClassLoader creates wrong URL > -- > > Key: OWB-1197 > URL: https://issues.apache.org/jira/browse/OWB-1197 > Project: OpenWebBeans > Issue Type: Bug > Components: Arquillian >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 2.0.0, 1.7.5 > > > -return new URL(null, "archive:" + nodes.iterator().next()); > +return new URL(null, "archive:" + nodes.iterator().next(), > new ArchiveStreamHandler()); > Otherwise we blow up with a MalformedURLException. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OWB-1179) OWB-Arquillian scanner doesn't ignore classes with ClassNotFound and NoClassDefFound
[ https://issues.apache.org/jira/browse/OWB-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-1179. Resolution: Fixed We now catch NoClassDefFound and LinkingErrors and log a warning about skipping class scanning for those cases. > OWB-Arquillian scanner doesn't ignore classes with ClassNotFound and > NoClassDefFound > > > Key: OWB-1179 > URL: https://issues.apache.org/jira/browse/OWB-1179 > Project: OpenWebBeans > Issue Type: Bug > Components: Arquillian >Affects Versions: 1.2.8, 1.7.3 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 2.0.0 > > > Came across a class which implements a Servlet Filter. > OWB blows up if the servlet spec api is not on the classpath. > Sometimes those classes are purely optional. > We should imo only log those problems and ignore the class where this > happens. > That is the same handling we do in the 'real' ScannerService as well. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OWB-1179) OWB-Arquillian scanner doesn't ignore classes with ClassNotFound and NoClassDefFound
[ https://issues.apache.org/jira/browse/OWB-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OWB-1179: --- Fix Version/s: 2.0.0 > OWB-Arquillian scanner doesn't ignore classes with ClassNotFound and > NoClassDefFound > > > Key: OWB-1179 > URL: https://issues.apache.org/jira/browse/OWB-1179 > Project: OpenWebBeans > Issue Type: Bug > Components: Arquillian >Affects Versions: 1.2.8, 1.7.3 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 2.0.0 > > > Came across a class which implements a Servlet Filter. > OWB blows up if the servlet spec api is not on the classpath. > Sometimes those classes are purely optional. > We should imo only log those problems and ignore the class where this > happens. > That is the same handling we do in the 'real' ScannerService as well. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OWB-1088) fix samples with java 8 and update to tomcat7/8
[ https://issues.apache.org/jira/browse/OWB-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OWB-1088: --- Fix Version/s: (was: 2.0.0) 2.0.1 > fix samples with java 8 and update to tomcat7/8 > --- > > Key: OWB-1088 > URL: https://issues.apache.org/jira/browse/OWB-1088 > Project: OpenWebBeans > Issue Type: Task > Components: Samples & Documentation >Affects Versions: 2.0.0 >Reporter: Reinhard Sandtner >Assignee: Reinhard Sandtner > Fix For: 2.0.1 > > > some of our samples are currently broken under java 8 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OWB-1195) do a codestyle analysis check and apply fidings before releasing OWB-2.0.0
[ https://issues.apache.org/jira/browse/OWB-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-1195. Resolution: Fixed > do a codestyle analysis check and apply fidings before releasing OWB-2.0.0 > -- > > Key: OWB-1195 > URL: https://issues.apache.org/jira/browse/OWB-1195 > Project: OpenWebBeans > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 2.0.0 > > > We should run the code analysis checks and Sonar and apply findings which > make sense. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OWB-1190) implement java-se support
[ https://issues.apache.org/jira/browse/OWB-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-1190. Resolution: Fixed > implement java-se support > - > > Key: OWB-1190 > URL: https://issues.apache.org/jira/browse/OWB-1190 > Project: OpenWebBeans > Issue Type: Sub-task > Components: Core >Reporter: Gerhard Petracek > Fix For: 2.0.0 > > > new parts: > * SeContainer > * SeContainerInitializer -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OWB-1185) implement Annotated#getAnnotations
[ https://issues.apache.org/jira/browse/OWB-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-1185. Resolution: Fixed Assignee: Mark Struberg > implement Annotated#getAnnotations > -- > > Key: OWB-1185 > URL: https://issues.apache.org/jira/browse/OWB-1185 > Project: OpenWebBeans > Issue Type: Sub-task > Components: Core >Reporter: Gerhard Petracek >Assignee: Mark Struberg > Fix For: 2.0.0 > > > + default implementations in: > * AnnotatedConstructor > * AnnotatedField > * AnnotatedMethod > * AnnotatedParameter > * AnnotatedType -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OWB-1187) implement configurators
[ https://issues.apache.org/jira/browse/OWB-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-1187. Resolution: Fixed Assignee: Mark Struberg > implement configurators > --- > > Key: OWB-1187 > URL: https://issues.apache.org/jira/browse/OWB-1187 > Project: OpenWebBeans > Issue Type: Sub-task >Reporter: Gerhard Petracek >Assignee: Mark Struberg > Fix For: 2.0.0 > > > new configurators: > * AnnotatedConstructorConfigurator > * AnnotatedFieldConfigurator > * AnnotatedMethodConfigurator > * AnnotatedParameterConfigurator > * AnnotatedTypeConfigurator > * BeanAttributesConfigurator > * BeanConfigurator > * InjectionPointConfigurator > * ObserverMethodConfigurator > * ProducerConfigurator -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OWB-1186) update logic for bootstrapping-events
[ https://issues.apache.org/jira/browse/OWB-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-1186. Resolution: Fixed Assignee: Mark Struberg > update logic for bootstrapping-events > - > > Key: OWB-1186 > URL: https://issues.apache.org/jira/browse/OWB-1186 > Project: OpenWebBeans > Issue Type: Sub-task >Reporter: Gerhard Petracek >Assignee: Mark Struberg > Fix For: 2.0.0 > > > new methods: > * AfterBeanDiscovery > ** #addBean() > ** #addObserverMethod() > * AfterTypeDiscovery > ** #addAnnotatedType(Class, String) > * BeforeBeanDiscovery > ** #addAnnotatedType(Class, String) > ** #configureQualifier(Class) > ** #configureInterceptorBinding(Class) > * ProcessAnnotatedType#configureAnnotatedType > * ProcessBeanAttributes > ** #configureBeanAttributes > ** #ignoreFinalMethods > * ProcessInjectionPoint > ** #configureInjectionPoint > * ProcessObserverMethod > ** #setObserverMethod > ** #configureObserverMethod > ** #veto > * ProcessProducer#configureProducer() > new events: > * ProcessSyntheticBean > * ProcessSyntheticObserverMethod -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OWB-1188) implement async events
[ https://issues.apache.org/jira/browse/OWB-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned OWB-1188: -- Assignee: Mark Struberg > implement async events > -- > > Key: OWB-1188 > URL: https://issues.apache.org/jira/browse/OWB-1188 > Project: OpenWebBeans > Issue Type: Sub-task > Components: Events >Reporter: Gerhard Petracek >Assignee: Mark Struberg > Fix For: 2.0.0 > > > new parts: > * Event#fireAsync > * @ObservesAsync > * ObserverMethod#isAsync -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OWB-1189) add new parts to the event-api
[ https://issues.apache.org/jira/browse/OWB-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-1189. Resolution: Fixed > add new parts to the event-api > -- > > Key: OWB-1189 > URL: https://issues.apache.org/jira/browse/OWB-1189 > Project: OpenWebBeans > Issue Type: Sub-task > Components: Events >Reporter: Gerhard Petracek >Assignee: Mark Struberg > Fix For: 2.0.0 > > > new parts: > * EventContext > * NotificationOptions/ImmutableNotificationOptions > * BeanManager#getEvent > * ObserverMethod#getPriority() > * ObserverMethod#notify > new event: > * BeforeDestroyed -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OWB-1188) implement async events
[ https://issues.apache.org/jira/browse/OWB-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-1188. Resolution: Fixed > implement async events > -- > > Key: OWB-1188 > URL: https://issues.apache.org/jira/browse/OWB-1188 > Project: OpenWebBeans > Issue Type: Sub-task > Components: Events >Reporter: Gerhard Petracek >Assignee: Mark Struberg > Fix For: 2.0.0 > > > new parts: > * Event#fireAsync > * @ObservesAsync > * ObserverMethod#isAsync -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OWB-1192) update logic for Instance
[ https://issues.apache.org/jira/browse/OWB-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-1192. Resolution: Fixed > update logic for Instance > - > > Key: OWB-1192 > URL: https://issues.apache.org/jira/browse/OWB-1192 > Project: OpenWebBeans > Issue Type: Sub-task > Components: Core >Reporter: Gerhard Petracek > Fix For: 2.0.0 > > > new parts: > * Instance > ** #stream > ** #isResolvable > * BeanManager#createInstance -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OWB-1191) implement api for manual request-context handling
[ https://issues.apache.org/jira/browse/OWB-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OWB-1191: --- Fix Version/s: (was: 2.0.0) 2.0.1 > implement api for manual request-context handling > - > > Key: OWB-1191 > URL: https://issues.apache.org/jira/browse/OWB-1191 > Project: OpenWebBeans > Issue Type: Sub-task > Components: Context and Scopes >Reporter: Gerhard Petracek > Fix For: 2.0.1 > > > new parts: > * ActivateRequestContext > * RequestContextController -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OWB-1193) implement InterceptionFactory
[ https://issues.apache.org/jira/browse/OWB-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-1193. Resolution: Fixed > implement InterceptionFactory > - > > Key: OWB-1193 > URL: https://issues.apache.org/jira/browse/OWB-1193 > Project: OpenWebBeans > Issue Type: Sub-task > Components: Interceptor and Decorators >Reporter: Gerhard Petracek > Fix For: 2.0.0 > > > basic logic as well as BeanManager#createInterceptionFactory -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OWB-1182) Implement the CDI-2.0 API
[ https://issues.apache.org/jira/browse/OWB-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-1182. Resolution: Fixed > Implement the CDI-2.0 API > - > > Key: OWB-1182 > URL: https://issues.apache.org/jira/browse/OWB-1182 > Project: OpenWebBeans > Issue Type: Task >Affects Versions: 2.0.0 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 2.0.0 > > > Upgrade the dependencies, etc for targeting CDI-2.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OWB-1182) Implement the CDI-2.0 API
[ https://issues.apache.org/jira/browse/OWB-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned OWB-1182: -- Assignee: Mark Struberg > Implement the CDI-2.0 API > - > > Key: OWB-1182 > URL: https://issues.apache.org/jira/browse/OWB-1182 > Project: OpenWebBeans > Issue Type: Task >Affects Versions: 2.0.0 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 2.0.0 > > > Upgrade the dependencies, etc for targeting CDI-2.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MEECROWAVE-29) tomcat 9.0.0.M22 upgrade
[ https://issues.apache.org/jira/browse/MEECROWAVE-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated MEECROWAVE-29: Summary: tomcat 9.0.0.M22 upgrade (was: tomcat 9.0.0.M21 upgrade) > tomcat 9.0.0.M22 upgrade > > > Key: MEECROWAVE-29 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-29 > Project: Meecrowave > Issue Type: Bug >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau > Fix For: 1.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MEECROWAVE-29) tomcat 9.0.0.M21 upgrade
[ https://issues.apache.org/jira/browse/MEECROWAVE-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated MEECROWAVE-29: Summary: tomcat 9.0.0.M21 upgrade (was: tomcat 9.0.0.M22 upgrade) > tomcat 9.0.0.M21 upgrade > > > Key: MEECROWAVE-29 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-29 > Project: Meecrowave > Issue Type: Bug >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau > Fix For: 1.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MEECROWAVE-48) OpenWebBeans 2 upgrade and CDI SE support
[ https://issues.apache.org/jira/browse/MEECROWAVE-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated MEECROWAVE-48: Fix Version/s: (was: 1.0.0) 2.0.0 > OpenWebBeans 2 upgrade and CDI SE support > - > > Key: MEECROWAVE-48 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-48 > Project: Meecrowave > Issue Type: Task >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau > Fix For: 2.0.0 > > > Part -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (MEECROWAVE-51) Upgrade dependency versions
[ https://issues.apache.org/jira/browse/MEECROWAVE-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved MEECROWAVE-51. - Resolution: Fixed > Upgrade dependency versions > --- > > Key: MEECROWAVE-51 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-51 > Project: Meecrowave > Issue Type: Bug >Affects Versions: 0.3.1 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.0.0 > > > We have some dependencies which might get updated > * commons-cli 1.3.1 -> 1.4 > * commons-lang4 3.5 -> 3.6 > * ziplock 7.0.1 -> 7.0.3 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (MEECROWAVE-52) Upgrade to OWB-1.7.4
[ https://issues.apache.org/jira/browse/MEECROWAVE-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved MEECROWAVE-52. - Resolution: Fixed > Upgrade to OWB-1.7.4 > > > Key: MEECROWAVE-52 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-52 > Project: Meecrowave > Issue Type: Task >Affects Versions: 0.3.1 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.0.0 > > > Upgrade to latest OWB version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (MEECROWAVE-49) Returning a binary leads to nullpointers
[
https://issues.apache.org/jira/browse/MEECROWAVE-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved MEECROWAVE-49.
-
Resolution: Fixed
> Returning a binary leads to nullpointers
>
>
> Key: MEECROWAVE-49
> URL: https://issues.apache.org/jira/browse/MEECROWAVE-49
> Project: Meecrowave
> Issue Type: Bug
>Affects Versions: 0.3.1
>Reporter: Mark Struberg
>Assignee: Mark Struberg
> Fix For: 1.0.0
>
>
> Currently Meecrowave tries to serve too much mime types via Johnzon. This
> leads to ugly NullPointerExceptions.
> Given the following REST endpoints:
> {code:java}
> @GET
> @Path("test4")
> @Produces(MediaType.APPLICATION_OCTET_STREAM)
> public Response testOctetStream() { ...}
> {code}
> or
> {code:java}
> @GET
> @Path("test5")
> @Produces(MediaType.APPLICATION_OCTET_STREAM)
> public byte[] testOctetStream() { ...}
> {code}
> We currently blow up with a NPE:
> {noformat}
> Caused by: java.lang.ClassCastException: [B cannot be cast to
> [Ljava.lang.Object;
> at org.apache.johnzon.jsonb.JohnsonJsonb.toJson(JohnsonJsonb.java:313)
> ~[johnzon-jsonb-1.1.1.jar:1.1.1]
> at
> org.apache.johnzon.jaxrs.jsonb.jaxrs.JsonbJaxrsProvider.writeTo(JsonbJaxrsProvider.java:152)
> ~[johnzon-jsonb-1.1.1.jar:1.1.1]
> at
> org.apache.cxf.jaxrs.utils.JAXRSUtils.writeMessageBody(JAXRSUtils.java:1386)
> ~[cxf-rt-frontend-jaxrs-3.1.11.jar:3.1.11]
> at
> org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor.serializeMessage(JAXRSOutInterceptor.java:244)
> ~[cxf-rt-frontend-jaxrs-3.1.11.jar:3.1.11]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (MEECROWAVE-52) Upgrade to OWB-1.7.4
Mark Struberg created MEECROWAVE-52: --- Summary: Upgrade to OWB-1.7.4 Key: MEECROWAVE-52 URL: https://issues.apache.org/jira/browse/MEECROWAVE-52 Project: Meecrowave Issue Type: Task Affects Versions: 0.3.1 Reporter: Mark Struberg Assignee: Mark Struberg Fix For: 1.0.0 Upgrade to latest OWB version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OWB-935) wrong result of javax.enterprise.inject.Instance in combination with alternatives
[
https://issues.apache.org/jira/browse/OWB-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg updated OWB-935:
--
Fix Version/s: (was: 1.7.4)
> wrong result of javax.enterprise.inject.Instance in combination with
> alternatives
> -
>
> Key: OWB-935
> URL: https://issues.apache.org/jira/browse/OWB-935
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Injection and Lookup
>Affects Versions: 1.2.2
>Reporter: Gerhard Petracek
>Assignee: Mark Struberg
> Fix For: 1.7.5
>
> Attachments: OWB-935.zip
>
>
> if the result of InjectionResolver#findByAlternatives is > 1 (for
> InstanceImpl#iterator) and there is one alternative-bean in the result, beans
> without alternative implementations aren't part of the result, because
> alternativeSet only contains alternative beans - see:
> {code}
> if (containsAlternative)
> {
> return alternativeSet;
> }
> return enableSet;
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[
https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg updated OWB-1074:
---
Fix Version/s: (was: 1.7.4)
> implement automatic supportsConversation() detection
>
>
> Key: OWB-1074
> URL: https://issues.apache.org/jira/browse/OWB-1074
> Project: OpenWebBeans
> Issue Type: Improvement
> Components: Context and Scopes
>Affects Versions: 1.5.0
>Reporter: Mark Struberg
> Fix For: 1.7.5
>
>
> Currently we rely on the user to define the configuration option in
> OpenWebBeansConfiguration
> {code}
> APPLICATION_SUPPORTS_CONVERSATION =
> "org.apache.webbeans.application.supportsConversation";
> {code}
> This is by default disabled in owb-impl (core) and gets enabled by adding the
> web or jsf plugins.
> We could improve this by not only allowing {{true}} or {{false}} but also
> with an {{auto}} mode.
> In this mode the BeanManager can walk through all registered beans and check
> whether there is a single @ConversationScoped bean. In that case we will
> automagically enable CDI conversations, otherwise OWB will dynamically
> disable conversation support and don't need to do all kinds of work in
> WebContextsService for example.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OWB-1078) create Dockerfiles for installing OpenWebBeans as Docker Image based on Tomcat8
[ https://issues.apache.org/jira/browse/OWB-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OWB-1078: --- Fix Version/s: (was: 1.7.4) > create Dockerfiles for installing OpenWebBeans as Docker Image based on > Tomcat8 > --- > > Key: OWB-1078 > URL: https://issues.apache.org/jira/browse/OWB-1078 > Project: OpenWebBeans > Issue Type: New Feature > Components: Samples & Documentation >Affects Versions: 1.5.0 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.7.5 > > > create Dockerfiles for installing OpenWebBeans as Docker Image based on > Tomcat8 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OWB-897) Interceptors do not work on processed injection targets
[
https://issues.apache.org/jira/browse/OWB-897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg updated OWB-897:
--
Fix Version/s: (was: 1.7.4)
> Interceptors do not work on processed injection targets
> ---
>
> Key: OWB-897
> URL: https://issues.apache.org/jira/browse/OWB-897
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Interceptor and Decorators
>Affects Versions: 1.2.0
>Reporter: Harald Wellmann
>Assignee: Romain Manni-Bucau
> Fix For: 1.7.5
>
>
> I have a portable extension which processes injection targets and replaces
> them with a custom implementation of
> javax.enterprise.inject.spi.InjectionTarget.
> This breaks interceptors on beans injected into beans which are processed
> injection targets. The injected contextual references are missing the
> expected proxy.
> The following code snippets look suspicious:
> org.apache.webbeans.component.InjectionTargetBean.defineBeanInterceptorStack():
> if (this instanceof InterceptedMarker && getInjectionTarget()
> instanceof InjectionTargetImpl) { ... }
> .
> This means that interceptors only get processed if the injection target is an
> instance of InjectionTargetImpl, which does not cover the case of a custom
> injection target provided by a portable extension.
> org.apache.webbeans.container.InjectionTargetFactoryImpl.createInjectionTarget(Bean):
> This method directly returns the injection target processed by the extension.
> This target should probably be wrapped by OWB's own implementation to make
> interceptors work.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (MEECROWAVE-51) Upgrade dependency versions
Mark Struberg created MEECROWAVE-51: --- Summary: Upgrade dependency versions Key: MEECROWAVE-51 URL: https://issues.apache.org/jira/browse/MEECROWAVE-51 Project: Meecrowave Issue Type: Bug Affects Versions: 0.3.1 Reporter: Mark Struberg Assignee: Mark Struberg Fix For: 1.0.0 We have some dependencies which might get updated * commons-cli 1.3.1 -> 1.4 * commons-lang4 3.5 -> 3.6 * ziplock 7.0.1 -> 7.0.3 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MEECROWAVE-45) support for owb2
[ https://issues.apache.org/jira/browse/MEECROWAVE-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated MEECROWAVE-45: Fix Version/s: (was: 1.0.0) 2.0.0 > support for owb2 > > > Key: MEECROWAVE-45 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-45 > Project: Meecrowave > Issue Type: Improvement >Affects Versions: 0.3.1 >Reporter: Gerhard Petracek >Assignee: Gerhard Petracek > Fix For: 2.0.0 > > Attachments: MEECROWAVE-45.patch > > > using meecrowave with owb2 results in a NullPointerException, because > webBeansContext is null (e.g. in #setFilter) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MEECROWAVE-49) Returning a binary leads to nullpointers
[
https://issues.apache.org/jira/browse/MEECROWAVE-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071783#comment-16071783
]
Mark Struberg commented on MEECROWAVE-49:
-
Since the spec api mime type check is broken, do we probably like to check them
in isWriteable?
> Returning a binary leads to nullpointers
>
>
> Key: MEECROWAVE-49
> URL: https://issues.apache.org/jira/browse/MEECROWAVE-49
> Project: Meecrowave
> Issue Type: Bug
>Affects Versions: 0.3.1
>Reporter: Mark Struberg
>Assignee: Mark Struberg
> Fix For: 0.4.0
>
>
> Currently Meecrowave tries to serve too much mime types via Johnzon. This
> leads to ugly NullPointerExceptions.
> Given the following REST endpoints:
> {code:java}
> @GET
> @Path("test4")
> @Produces(MediaType.APPLICATION_OCTET_STREAM)
> public Response testOctetStream() { ...}
> {code}
> or
> {code:java}
> @GET
> @Path("test5")
> @Produces(MediaType.APPLICATION_OCTET_STREAM)
> public byte[] testOctetStream() { ...}
> {code}
> We currently blow up with a NPE:
> {noformat}
> Caused by: java.lang.ClassCastException: [B cannot be cast to
> [Ljava.lang.Object;
> at org.apache.johnzon.jsonb.JohnsonJsonb.toJson(JohnsonJsonb.java:313)
> ~[johnzon-jsonb-1.1.1.jar:1.1.1]
> at
> org.apache.johnzon.jaxrs.jsonb.jaxrs.JsonbJaxrsProvider.writeTo(JsonbJaxrsProvider.java:152)
> ~[johnzon-jsonb-1.1.1.jar:1.1.1]
> at
> org.apache.cxf.jaxrs.utils.JAXRSUtils.writeMessageBody(JAXRSUtils.java:1386)
> ~[cxf-rt-frontend-jaxrs-3.1.11.jar:3.1.11]
> at
> org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor.serializeMessage(JAXRSOutInterceptor.java:244)
> ~[cxf-rt-frontend-jaxrs-3.1.11.jar:3.1.11]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MEECROWAVE-49) Returning a binary leads to nullpointers
[
https://issues.apache.org/jira/browse/MEECROWAVE-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071779#comment-16071779
]
Mark Struberg commented on MEECROWAVE-49:
-
Yes, will create a separate ticket for it.
The problem I see is that isWriteable does *not* get Response!
It seems that in case of returning a Response, CXF examines the content and
this is the type you get in isWritable. So even for
Response.ok("bla".getBytes()).build(); we are back to a byte[] in isWritable.
Not sure if this was that way ever since though...
> Returning a binary leads to nullpointers
>
>
> Key: MEECROWAVE-49
> URL: https://issues.apache.org/jira/browse/MEECROWAVE-49
> Project: Meecrowave
> Issue Type: Bug
>Affects Versions: 0.3.1
>Reporter: Mark Struberg
>Assignee: Mark Struberg
> Fix For: 0.4.0
>
>
> Currently Meecrowave tries to serve too much mime types via Johnzon. This
> leads to ugly NullPointerExceptions.
> Given the following REST endpoints:
> {code:java}
> @GET
> @Path("test4")
> @Produces(MediaType.APPLICATION_OCTET_STREAM)
> public Response testOctetStream() { ...}
> {code}
> or
> {code:java}
> @GET
> @Path("test5")
> @Produces(MediaType.APPLICATION_OCTET_STREAM)
> public byte[] testOctetStream() { ...}
> {code}
> We currently blow up with a NPE:
> {noformat}
> Caused by: java.lang.ClassCastException: [B cannot be cast to
> [Ljava.lang.Object;
> at org.apache.johnzon.jsonb.JohnsonJsonb.toJson(JohnsonJsonb.java:313)
> ~[johnzon-jsonb-1.1.1.jar:1.1.1]
> at
> org.apache.johnzon.jaxrs.jsonb.jaxrs.JsonbJaxrsProvider.writeTo(JsonbJaxrsProvider.java:152)
> ~[johnzon-jsonb-1.1.1.jar:1.1.1]
> at
> org.apache.cxf.jaxrs.utils.JAXRSUtils.writeMessageBody(JAXRSUtils.java:1386)
> ~[cxf-rt-frontend-jaxrs-3.1.11.jar:3.1.11]
> at
> org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor.serializeMessage(JAXRSOutInterceptor.java:244)
> ~[cxf-rt-frontend-jaxrs-3.1.11.jar:3.1.11]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MEECROWAVE-49) Returning a binary leads to nullpointers
[
https://issues.apache.org/jira/browse/MEECROWAVE-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071776#comment-16071776
]
Mark Struberg commented on MEECROWAVE-49:
-
Well, I already reported a bug in the spec. Everything */xxx is kind of a
wildcard for EVERYTHING.
*/*+json is like */* really :(
You might remember the discussion on the CXF list?
Anyway, the question now is: do we add Byte arrays ("[B") to the list of
ignored types? Or do we want to ignore every application/octet-stream content
via isWriteable in JsonbJaxRsProvider?
For now I'm gonna add a workaround to Meecrowave, but I will also create a
Johnzon ticket for handling it.
> Returning a binary leads to nullpointers
>
>
> Key: MEECROWAVE-49
> URL: https://issues.apache.org/jira/browse/MEECROWAVE-49
> Project: Meecrowave
> Issue Type: Bug
>Affects Versions: 0.3.1
>Reporter: Mark Struberg
>Assignee: Mark Struberg
> Fix For: 0.4.0
>
>
> Currently Meecrowave tries to serve too much mime types via Johnzon. This
> leads to ugly NullPointerExceptions.
> Given the following REST endpoints:
> {code:java}
> @GET
> @Path("test4")
> @Produces(MediaType.APPLICATION_OCTET_STREAM)
> public Response testOctetStream() { ...}
> {code}
> or
> {code:java}
> @GET
> @Path("test5")
> @Produces(MediaType.APPLICATION_OCTET_STREAM)
> public byte[] testOctetStream() { ...}
> {code}
> We currently blow up with a NPE:
> {noformat}
> Caused by: java.lang.ClassCastException: [B cannot be cast to
> [Ljava.lang.Object;
> at org.apache.johnzon.jsonb.JohnsonJsonb.toJson(JohnsonJsonb.java:313)
> ~[johnzon-jsonb-1.1.1.jar:1.1.1]
> at
> org.apache.johnzon.jaxrs.jsonb.jaxrs.JsonbJaxrsProvider.writeTo(JsonbJaxrsProvider.java:152)
> ~[johnzon-jsonb-1.1.1.jar:1.1.1]
> at
> org.apache.cxf.jaxrs.utils.JAXRSUtils.writeMessageBody(JAXRSUtils.java:1386)
> ~[cxf-rt-frontend-jaxrs-3.1.11.jar:3.1.11]
> at
> org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor.serializeMessage(JAXRSOutInterceptor.java:244)
> ~[cxf-rt-frontend-jaxrs-3.1.11.jar:3.1.11]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (MEECROWAVE-49) Returning a binary leads to nullpointers
[
https://issues.apache.org/jira/browse/MEECROWAVE-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071763#comment-16071763
]
Mark Struberg edited comment on MEECROWAVE-49 at 7/2/17 7:40 PM:
-
Managed to reproduce the problem. Setting a String to the response does work,
but a byte[] makes it blow up:
Works:
{code}
return Response.ok("byte array forever").build();
{code}
Fails with the Exception as above:
{code}
return Response.ok("byte array forever".getBytes()).build();
{code}
was (Author: struberg):
Managed to reproduce the problem. Setting a String to the response does work,
but a byte[] makes it blow up:
Works:
{source:java}
return Response.ok("byte array forever").build();
{source}
Fails with the Exception as above:
{source:java}
return Response.ok("byte array forever".getBytes()).build();
{source}
> Returning a binary leads to nullpointers
>
>
> Key: MEECROWAVE-49
> URL: https://issues.apache.org/jira/browse/MEECROWAVE-49
> Project: Meecrowave
> Issue Type: Bug
>Affects Versions: 0.3.1
>Reporter: Mark Struberg
>Assignee: Mark Struberg
> Fix For: 0.4.0
>
>
> Currently Meecrowave tries to serve too much mime types via Johnzon. This
> leads to ugly NullPointerExceptions.
> Given the following REST endpoints:
> {code:java}
> @GET
> @Path("test4")
> @Produces(MediaType.APPLICATION_OCTET_STREAM)
> public Response testOctetStream() { ...}
> {code}
> or
> {code:java}
> @GET
> @Path("test5")
> @Produces(MediaType.APPLICATION_OCTET_STREAM)
> public byte[] testOctetStream() { ...}
> {code}
> We currently blow up with a NPE:
> {noformat}
> Caused by: java.lang.ClassCastException: [B cannot be cast to
> [Ljava.lang.Object;
> at org.apache.johnzon.jsonb.JohnsonJsonb.toJson(JohnsonJsonb.java:313)
> ~[johnzon-jsonb-1.1.1.jar:1.1.1]
> at
> org.apache.johnzon.jaxrs.jsonb.jaxrs.JsonbJaxrsProvider.writeTo(JsonbJaxrsProvider.java:152)
> ~[johnzon-jsonb-1.1.1.jar:1.1.1]
> at
> org.apache.cxf.jaxrs.utils.JAXRSUtils.writeMessageBody(JAXRSUtils.java:1386)
> ~[cxf-rt-frontend-jaxrs-3.1.11.jar:3.1.11]
> at
> org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor.serializeMessage(JAXRSOutInterceptor.java:244)
> ~[cxf-rt-frontend-jaxrs-3.1.11.jar:3.1.11]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MEECROWAVE-49) Returning a binary leads to nullpointers
[
https://issues.apache.org/jira/browse/MEECROWAVE-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071763#comment-16071763
]
Mark Struberg commented on MEECROWAVE-49:
-
Managed to reproduce the problem. Setting a String to the response does work,
but a byte[] makes it blow up:
Works:
{source:java}
return Response.ok("byte array forever").build();
{source}
Fails with the Exception as above:
{source:java}
return Response.ok("byte array forever".getBytes()).build();
{source}
> Returning a binary leads to nullpointers
>
>
> Key: MEECROWAVE-49
> URL: https://issues.apache.org/jira/browse/MEECROWAVE-49
> Project: Meecrowave
> Issue Type: Bug
>Affects Versions: 0.3.1
>Reporter: Mark Struberg
>Assignee: Mark Struberg
> Fix For: 0.4.0
>
>
> Currently Meecrowave tries to serve too much mime types via Johnzon. This
> leads to ugly NullPointerExceptions.
> Given the following REST endpoints:
> {code:java}
> @GET
> @Path("test4")
> @Produces(MediaType.APPLICATION_OCTET_STREAM)
> public Response testOctetStream() { ...}
> {code}
> or
> {code:java}
> @GET
> @Path("test5")
> @Produces(MediaType.APPLICATION_OCTET_STREAM)
> public byte[] testOctetStream() { ...}
> {code}
> We currently blow up with a NPE:
> {noformat}
> Caused by: java.lang.ClassCastException: [B cannot be cast to
> [Ljava.lang.Object;
> at org.apache.johnzon.jsonb.JohnsonJsonb.toJson(JohnsonJsonb.java:313)
> ~[johnzon-jsonb-1.1.1.jar:1.1.1]
> at
> org.apache.johnzon.jaxrs.jsonb.jaxrs.JsonbJaxrsProvider.writeTo(JsonbJaxrsProvider.java:152)
> ~[johnzon-jsonb-1.1.1.jar:1.1.1]
> at
> org.apache.cxf.jaxrs.utils.JAXRSUtils.writeMessageBody(JAXRSUtils.java:1386)
> ~[cxf-rt-frontend-jaxrs-3.1.11.jar:3.1.11]
> at
> org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor.serializeMessage(JAXRSOutInterceptor.java:244)
> ~[cxf-rt-frontend-jaxrs-3.1.11.jar:3.1.11]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (MEECROWAVE-49) Returning a binary leads to nullpointers
Mark Struberg created MEECROWAVE-49:
---
Summary: Returning a binary leads to nullpointers
Key: MEECROWAVE-49
URL: https://issues.apache.org/jira/browse/MEECROWAVE-49
Project: Meecrowave
Issue Type: Bug
Affects Versions: 0.3.1
Reporter: Mark Struberg
Assignee: Mark Struberg
Fix For: 0.4.0
Currently Meecrowave tries to serve ALL mime types via Johnzon. This leads to
ugly NullPointerExceptions.
Given the following REST endpoints:
{code:java}
@GET
@Path("test4")
@Produces(MediaType.APPLICATION_OCTET_STREAM)
public Response testOctetStream() { ...}
{code}
or
{code:java}
@GET
@Path("test5")
@Produces(MediaType.APPLICATION_OCTET_STREAM)
public byte[] testOctetStream() { ...}
{code}
We currently blow up with a NPE:
{noformat}
Caused by: java.lang.ClassCastException: [B cannot be cast to
[Ljava.lang.Object;
at org.apache.johnzon.jsonb.JohnsonJsonb.toJson(JohnsonJsonb.java:313)
~[johnzon-jsonb-1.1.1.jar:1.1.1]
at
org.apache.johnzon.jaxrs.jsonb.jaxrs.JsonbJaxrsProvider.writeTo(JsonbJaxrsProvider.java:152)
~[johnzon-jsonb-1.1.1.jar:1.1.1]
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.writeMessageBody(JAXRSUtils.java:1386)
~[cxf-rt-frontend-jaxrs-3.1.11.jar:3.1.11]
at
org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor.serializeMessage(JAXRSOutInterceptor.java:244)
~[cxf-rt-frontend-jaxrs-3.1.11.jar:3.1.11]
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MEECROWAVE-48) OpenWebBeans 2 upgrade and CDI SE support
[ https://issues.apache.org/jira/browse/MEECROWAVE-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071595#comment-16071595 ] Mark Struberg commented on MEECROWAVE-48: - Romain, I fear that upgrade is a bit too eager. I'd love to ship a 0.3.2 or 0.4 before moving to CDI 2.0. We already have people who use this in production, so we need a branch for the CDI-1.2 version as well. Gonna move back to CDI-1.2 and we will keep this until after the release, ok? > OpenWebBeans 2 upgrade and CDI SE support > - > > Key: MEECROWAVE-48 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-48 > Project: Meecrowave > Issue Type: Task >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau > Fix For: 0.3.2 > > > Part -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (MEECROWAVE-41) make meecrowave:bundle pick up content from src/main/meecrowave/conf/*
[ https://issues.apache.org/jira/browse/MEECROWAVE-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved MEECROWAVE-41. - Resolution: Fixed > make meecrowave:bundle pick up content from src/main/meecrowave/conf/* > -- > > Key: MEECROWAVE-41 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-41 > Project: Meecrowave > Issue Type: New Feature >Affects Versions: 0.3.1 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 0.4.0 > > > Currently files in src/main/meecrowave/conf etc get ignored during > meecrowave:bundle. > We should just copy over all those files. > If certain files like log4j2.xml and meecrowave.properties does not exist in > the source folder then we generate sensible default ones. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MEECROWAVE-41) make meecrowave:bundle pick up content from src/main/meecrowave/conf/*
[ https://issues.apache.org/jira/browse/MEECROWAVE-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated MEECROWAVE-41: Summary: make meecrowave:bundle pick up content from src/main/meecrowave/conf/* (was: make meecrowave:bundle pick up content from src/meecrowave/*) > make meecrowave:bundle pick up content from src/main/meecrowave/conf/* > -- > > Key: MEECROWAVE-41 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-41 > Project: Meecrowave > Issue Type: New Feature >Affects Versions: 0.3.1 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 0.4.0 > > > Currently files in src/meecrowave/conf etc get ignored during > meecrowave:bundle. > We should just copy over all those files. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MEECROWAVE-41) make meecrowave:bundle pick up content from src/meecrowave/*
Mark Struberg created MEECROWAVE-41: --- Summary: make meecrowave:bundle pick up content from src/meecrowave/* Key: MEECROWAVE-41 URL: https://issues.apache.org/jira/browse/MEECROWAVE-41 Project: Meecrowave Issue Type: New Feature Affects Versions: 0.3.1 Reporter: Mark Struberg Assignee: Mark Struberg Fix For: 4.0 Currently files in src/meecrowave/conf etc get ignored during meecrowave:bundle. We should just copy over all those files. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OWB-1195) do a codestyle analysis check and apply fidings before releasing OWB-2.0.0
Mark Struberg created OWB-1195: -- Summary: do a codestyle analysis check and apply fidings before releasing OWB-2.0.0 Key: OWB-1195 URL: https://issues.apache.org/jira/browse/OWB-1195 Project: OpenWebBeans Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Mark Struberg Assignee: Mark Struberg Fix For: 2.0.0 We should run the code analysis checks and Sonar and apply findings which make sense. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MEECROWAVE-39) detect getJaxrsMapping automatically based on Application and @ApplicationPath
Mark Struberg created MEECROWAVE-39: --- Summary: detect getJaxrsMapping automatically based on Application and @ApplicationPath Key: MEECROWAVE-39 URL: https://issues.apache.org/jira/browse/MEECROWAVE-39 Project: Meecrowave Issue Type: New Feature Reporter: Mark Struberg Currently the jaxrs mapping is set to /* even if a more specific @ApplicationPath is set. That makes it hard to serve additional content. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OWB-1189) add new parts to the event-api
[ https://issues.apache.org/jira/browse/OWB-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned OWB-1189: -- Assignee: Mark Struberg > add new parts to the event-api > -- > > Key: OWB-1189 > URL: https://issues.apache.org/jira/browse/OWB-1189 > Project: OpenWebBeans > Issue Type: Sub-task > Components: Events >Reporter: Gerhard Petracek >Assignee: Mark Struberg > Fix For: 2.0.0 > > > new parts: > * EventContext > * NotificationOptions/ImmutableNotificationOptions > * BeanManager#getEvent > * ObserverMethod#getPriority() > * ObserverMethod#notify > new event: > * BeforeDestroyed -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (OWB-1184) arquillian connector doesn't support BDAs
[ https://issues.apache.org/jira/browse/OWB-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-1184. Resolution: Fixed > arquillian connector doesn't support BDAs > - > > Key: OWB-1184 > URL: https://issues.apache.org/jira/browse/OWB-1184 > Project: OpenWebBeans > Issue Type: Bug > Components: Arquillian >Affects Versions: 2.0.0 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 2.0.0 > > > Currently we only implement the ScannerService in our Arquillian Connector. > For testing in some TCK tests we also need to support BDA information > and the BdaScannerService. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (OWB-1183) OWB-Arquillian does not supports implicit bean discovery mode
[ https://issues.apache.org/jira/browse/OWB-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-1183. Resolution: Fixed Fix Version/s: (was: 1.7.4) Implemented in 2.0.0 > OWB-Arquillian does not supports implicit bean discovery mode > - > > Key: OWB-1183 > URL: https://issues.apache.org/jira/browse/OWB-1183 > Project: OpenWebBeans > Issue Type: Bug > Components: Arquillian >Affects Versions: 1.7.3 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 2.0.0-alpha-1 > > > Currently the owb-arquillian-standalone only picks up classes in an Archive > if there is also a META-INF/beans.xml file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OWB-1183) OWB-Arquillian does not supports implicit bean discovery mode
Mark Struberg created OWB-1183: -- Summary: OWB-Arquillian does not supports implicit bean discovery mode Key: OWB-1183 URL: https://issues.apache.org/jira/browse/OWB-1183 Project: OpenWebBeans Issue Type: Bug Components: Arquillian Affects Versions: 1.7.3 Reporter: Mark Struberg Assignee: Mark Struberg Fix For: 1.7.4, 2.0.0-alpha-1 Currently the owb-arquillian-standalone only picks up classes in an Archive if there is also a META-INF/beans.xml file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OWB-1182) CDI-2.0 project setup
Mark Struberg created OWB-1182: -- Summary: CDI-2.0 project setup Key: OWB-1182 URL: https://issues.apache.org/jira/browse/OWB-1182 Project: OpenWebBeans Issue Type: Task Affects Versions: 2.0.0-alpha-1 Reporter: Mark Struberg Fix For: 2.0.0-alpha-1 Upgrade the dependencies, etc for targeting CDI-2.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (OWB-1177) producer should check runtime instance for Serializable constraint and not returned type
[ https://issues.apache.org/jira/browse/OWB-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed OWB-1177. -- > producer should check runtime instance for Serializable constraint and not > returned type > > > Key: OWB-1177 > URL: https://issues.apache.org/jira/browse/OWB-1177 > Project: OpenWebBeans > Issue Type: Bug >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau > Fix For: 1.7.3 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (OWB-1175) Duplicate registration of ServletContextBean
[
https://issues.apache.org/jira/browse/OWB-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg closed OWB-1175.
--
> Duplicate registration of ServletContextBean
>
>
> Key: OWB-1175
> URL: https://issues.apache.org/jira/browse/OWB-1175
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Web
>Affects Versions: 1.7.2
>Reporter: Benjamin Mueller
>Assignee: Mark Struberg
> Fix For: 1.7.3
>
> Attachments: test.zip
>
>
> After updating to 1.7.2 (from 1.6.3) my application on Tomcat 8 stopped
> working.
> It configures both the WebBeansConfigurationListener and
> WebBeansConfigurationFilter in web.xml
> {code:xml}
>
>
> org.apache.webbeans.servlet.WebBeansConfigurationListener
>
>
> WebBeansConfigurationFilter
>
> org.apache.webbeans.servlet.WebBeansConfigurationFilter
>
>
> WebBeansConfigurationFilter
> /*
> FORWARD
>
> {code}
> I need this setup to handle requests being forwarded by a different webapp
> (with cross-context).
> When starting, Open-Webbeans fails now with:
> {noformat}
> SCHWERWIEGEND: Exception starting filter WebBeansConfigurationFilter
> org.apache.webbeans.exception.DuplicateDefinitionException:
> PassivationCapable bean id is not unique: SERVLET_CONTEXT#interface
> javax.servlet.ServletContext#@javax.enterprise.inject.Default(),@javax.enterprise.inject.Any(),
> bean:ServletContext, WebBeansType:SERVLET_CONTEXT, Name:null, API
> Types:[java.lang.Object,javax.servlet.ServletContext],
> Qualifiers:[javax.enterprise.inject.Default,javax.enterprise.inject.Any]
> at
> org.apache.webbeans.container.BeanManagerImpl.addPassivationInfo(BeanManagerImpl.java:411)
> at
> org.apache.webbeans.container.BeanManagerImpl.addInternalBean(BeanManagerImpl.java:365)
> at
> org.apache.webbeans.web.lifecycle.WebContainerLifecycle.startApplication(WebContainerLifecycle.java:90)
> at
> org.apache.webbeans.servlet.WebBeansConfigurationFilter.init(WebBeansConfigurationFilter.java:90)
> {noformat}
> This is probably due to WebContainerLifecycle#startApplication, which does
> not first check if it is already started before it adds the
> ServletContextBean (again) in contrast to AbstractLifecycle#startApplication
> (bootstrapApplication).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (OWB-1178) Upgrade Arquillian to 1.1.13 and ShrinkWrap to 1.2.6
[ https://issues.apache.org/jira/browse/OWB-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed OWB-1178. -- > Upgrade Arquillian to 1.1.13 and ShrinkWrap to 1.2.6 > > > Key: OWB-1178 > URL: https://issues.apache.org/jira/browse/OWB-1178 > Project: OpenWebBeans > Issue Type: Task > Components: Arquillian >Affects Versions: 1.7.2 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.7.3 > > > 1.1.13.Final seems finally work well again. Thus we should update to this > Arquillian version. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (OWB-1169) Invalid OSGI version ranges
[ https://issues.apache.org/jira/browse/OWB-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-1169. Resolution: Fixed > Invalid OSGI version ranges > --- > > Key: OWB-1169 > URL: https://issues.apache.org/jira/browse/OWB-1169 > Project: OpenWebBeans > Issue Type: Bug >Affects Versions: 1.7.1 >Reporter: Moritz Bechler > > Unfortunately did not realize this earlier: the open ended version ranges now > included in the osgi manifests are invalid per spec (although some tools seem > to parse them). Manifests have version="[x.y.z,)" but it seems the only > correct format for an atleast constraint is version="x.y.z". > Will provide a PR in the next couple of days. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (OWB-1175) Duplicate registration of ServletContextBean
[
https://issues.apache.org/jira/browse/OWB-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-1175.
Resolution: Fixed
Fix Version/s: 1.7.3
> Duplicate registration of ServletContextBean
>
>
> Key: OWB-1175
> URL: https://issues.apache.org/jira/browse/OWB-1175
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Web
>Affects Versions: 1.7.2
>Reporter: Benjamin Mueller
>Assignee: Mark Struberg
> Fix For: 1.7.3
>
> Attachments: test.zip
>
>
> After updating to 1.7.2 (from 1.6.3) my application on Tomcat 8 stopped
> working.
> It configures both the WebBeansConfigurationListener and
> WebBeansConfigurationFilter in web.xml
> {code:xml}
>
>
> org.apache.webbeans.servlet.WebBeansConfigurationListener
>
>
> WebBeansConfigurationFilter
>
> org.apache.webbeans.servlet.WebBeansConfigurationFilter
>
>
> WebBeansConfigurationFilter
> /*
> FORWARD
>
> {code}
> I need this setup to handle requests being forwarded by a different webapp
> (with cross-context).
> When starting, Open-Webbeans fails now with:
> {noformat}
> SCHWERWIEGEND: Exception starting filter WebBeansConfigurationFilter
> org.apache.webbeans.exception.DuplicateDefinitionException:
> PassivationCapable bean id is not unique: SERVLET_CONTEXT#interface
> javax.servlet.ServletContext#@javax.enterprise.inject.Default(),@javax.enterprise.inject.Any(),
> bean:ServletContext, WebBeansType:SERVLET_CONTEXT, Name:null, API
> Types:[java.lang.Object,javax.servlet.ServletContext],
> Qualifiers:[javax.enterprise.inject.Default,javax.enterprise.inject.Any]
> at
> org.apache.webbeans.container.BeanManagerImpl.addPassivationInfo(BeanManagerImpl.java:411)
> at
> org.apache.webbeans.container.BeanManagerImpl.addInternalBean(BeanManagerImpl.java:365)
> at
> org.apache.webbeans.web.lifecycle.WebContainerLifecycle.startApplication(WebContainerLifecycle.java:90)
> at
> org.apache.webbeans.servlet.WebBeansConfigurationFilter.init(WebBeansConfigurationFilter.java:90)
> {noformat}
> This is probably due to WebContainerLifecycle#startApplication, which does
> not first check if it is already started before it adds the
> ServletContextBean (again) in contrast to AbstractLifecycle#startApplication
> (bootstrapApplication).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (OWB-1174) seeing WebBeansDeploymentException: java.lang.ArrayIndexOutOfBoundsException: 3379
[ https://issues.apache.org/jira/browse/OWB-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938485#comment-15938485 ] Mark Struberg commented on OWB-1174: I'll try to reproduce it but I fear this is some missing Annotation or a class referenced inside an annotation. So this might be depending on your classpath. Can you probably try so set an Exception breakpoint on java.lang.ArrayIndexOutOfBoundsException ? > seeing WebBeansDeploymentException: java.lang.ArrayIndexOutOfBoundsException: > 3379 > -- > > Key: OWB-1174 > URL: https://issues.apache.org/jira/browse/OWB-1174 > Project: OpenWebBeans > Issue Type: Bug > Components: Lifecycle >Affects Versions: 1.7.2 > Environment: Mac OS X Sierra -- JDK 1.8_u121 -- maven 3.3.9 -- > Deltaspike 1.7.2 -- JUnit test context >Reporter: Andy Glick >Assignee: Mark Struberg > Labels: asm, lifecycle > Attachments: CdiContainerInitTest.java, stack-trace-for-owb.log > > > In an environment configured to use deltaspike and owb attempting to execute > deltaspike's cdiContainer.boot(); method, which worked consistently in the > past and now consistently generates an error and specifies WebBeansDeployment > Exception. This seems to be happening when OWB is scanning jars on the class > path. > Attaching the full IDEA generated logs, the logs produced by a maven > execution on the command line fail with the same exception. > Also attaching the source code of the test class. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OWB-1173) InjectionPoint with no ownerBean fails on serialisation
Mark Struberg created OWB-1173: -- Summary: InjectionPoint with no ownerBean fails on serialisation Key: OWB-1173 URL: https://issues.apache.org/jira/browse/OWB-1173 Project: OpenWebBeans Issue Type: Bug Components: Core Affects Versions: 1.7.2 Reporter: Mark Struberg Assignee: Mark Struberg Fix For: 1.7.3 If an InjectionTarget gets created manually then the InjectionPoints will have no ownerBean (the owner is a simple class but not a CDI Bean). If one tries to serialise such a class then we currently blow up with a NullPointerException. Detected and reported by Alexander Falb via chat. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OWB-1078) create Dockerfiles for installing OpenWebBeans as Docker Image based on Tomcat8
[ https://issues.apache.org/jira/browse/OWB-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OWB-1078: --- Fix Version/s: (was: 1.7.2) 1.7.3 > create Dockerfiles for installing OpenWebBeans as Docker Image based on > Tomcat8 > --- > > Key: OWB-1078 > URL: https://issues.apache.org/jira/browse/OWB-1078 > Project: OpenWebBeans > Issue Type: New Feature > Components: Samples & Documentation >Affects Versions: 1.5.0 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.7.3 > > > create Dockerfiles for installing OpenWebBeans as Docker Image based on > Tomcat8 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OWB-935) wrong result of javax.enterprise.inject.Instance in combination with alternatives
[
https://issues.apache.org/jira/browse/OWB-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg updated OWB-935:
--
Fix Version/s: (was: 1.7.2)
1.7.3
> wrong result of javax.enterprise.inject.Instance in combination with
> alternatives
> -
>
> Key: OWB-935
> URL: https://issues.apache.org/jira/browse/OWB-935
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Injection and Lookup
>Affects Versions: 1.2.2
>Reporter: Gerhard Petracek
>Assignee: Mark Struberg
> Fix For: 1.7.3
>
> Attachments: OWB-935.zip
>
>
> if the result of InjectionResolver#findByAlternatives is > 1 (for
> InstanceImpl#iterator) and there is one alternative-bean in the result, beans
> without alternative implementations aren't part of the result, because
> alternativeSet only contains alternative beans - see:
> {code}
> if (containsAlternative)
> {
> return alternativeSet;
> }
> return enableSet;
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[
https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg updated OWB-1074:
---
Fix Version/s: (was: 1.7.2)
1.7.3
> implement automatic supportsConversation() detection
>
>
> Key: OWB-1074
> URL: https://issues.apache.org/jira/browse/OWB-1074
> Project: OpenWebBeans
> Issue Type: Improvement
> Components: Context and Scopes
>Affects Versions: 1.5.0
>Reporter: Mark Struberg
> Fix For: 1.7.3
>
>
> Currently we rely on the user to define the configuration option in
> OpenWebBeansConfiguration
> {code}
> APPLICATION_SUPPORTS_CONVERSATION =
> "org.apache.webbeans.application.supportsConversation";
> {code}
> This is by default disabled in owb-impl (core) and gets enabled by adding the
> web or jsf plugins.
> We could improve this by not only allowing {{true}} or {{false}} but also
> with an {{auto}} mode.
> In this mode the BeanManager can walk through all registered beans and check
> whether there is a single @ConversationScoped bean. In that case we will
> automagically enable CDI conversations, otherwise OWB will dynamically
> disable conversation support and don't need to do all kinds of work in
> WebContextsService for example.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (OWB-1172) getResources doesn't work in OWB Arquillian container for WebArchives
[ https://issues.apache.org/jira/browse/OWB-1172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-1172. Resolution: Fixed > getResources doesn't work in OWB Arquillian container for WebArchives > - > > Key: OWB-1172 > URL: https://issues.apache.org/jira/browse/OWB-1172 > Project: OpenWebBeans > Issue Type: Bug > Components: Arquillian >Affects Versions: 1.7.2 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.7.3 > > > The OWB Arquillian container doesn't find resources in WEB-INF/lib/*.jar > within a WAR archive. > getResources currently only returns resources in WEB-INF/classes/ but not > from any of the jars in WEB-INF/-lib. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OWB-1172) getResources doesn't work in OWB Arquillian container for WebArchives
Mark Struberg created OWB-1172: -- Summary: getResources doesn't work in OWB Arquillian container for WebArchives Key: OWB-1172 URL: https://issues.apache.org/jira/browse/OWB-1172 Project: OpenWebBeans Issue Type: Bug Components: Arquillian Affects Versions: 1.7.2 Reporter: Mark Struberg Assignee: Mark Struberg Fix For: 1.7.3 The OWB Arquillian container doesn't find resources in WEB-INF/lib/*.jar within a WAR archive. getResources currently only returns resources in WEB-INF/classes/ but not from any of the jars in WEB-INF/-lib. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OWB-1090) remove jsf12 module for owb-2.0
[ https://issues.apache.org/jira/browse/OWB-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OWB-1090: --- Fix Version/s: (was: 2.0.0-alpha-1) 1.7.1 > remove jsf12 module for owb-2.0 > --- > > Key: OWB-1090 > URL: https://issues.apache.org/jira/browse/OWB-1090 > Project: OpenWebBeans > Issue Type: Task >Affects Versions: 2.0.0-alpha-1 >Reporter: Reinhard Sandtner > Fix For: 1.7.1 > > > jsf-1.x is from 2005. JSF2 got introduced in 2009 and doesn't support java8 > anyway. So we can remove this module. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OWB-1090) remove jsf12 module for owb-2.0
[ https://issues.apache.org/jira/browse/OWB-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-1090. Resolution: Fixed > remove jsf12 module for owb-2.0 > --- > > Key: OWB-1090 > URL: https://issues.apache.org/jira/browse/OWB-1090 > Project: OpenWebBeans > Issue Type: Task >Affects Versions: 2.0.0-alpha-1 >Reporter: Reinhard Sandtner > Fix For: 1.7.1 > > > jsf-1.x is from 2005. JSF2 got introduced in 2009 and doesn't support java8 > anyway. So we can remove this module. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OWB-1153) improve tomcat-plugin performance
[ https://issues.apache.org/jira/browse/OWB-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-1153. Resolution: Fixed > improve tomcat-plugin performance > - > > Key: OWB-1153 > URL: https://issues.apache.org/jira/browse/OWB-1153 > Project: OpenWebBeans > Issue Type: Improvement >Affects Versions: 1.7.0 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.7.1 > > > We could optimise the isManagedBean etc methods by first checking for > instanceof EventListener -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OWB-1156) implement support for feature of CDI-2.0
[
https://issues.apache.org/jira/browse/OWB-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-1156.
Resolution: Fixed
> implement support for feature of CDI-2.0
>
>
> Key: OWB-1156
> URL: https://issues.apache.org/jira/browse/OWB-1156
> Project: OpenWebBeans
> Issue Type: Improvement
> Components: Core
>Affects Versions: 1.7.0
>Reporter: Mark Struberg
>Assignee: Mark Struberg
> Fix For: 1.7.1
>
>
> The bean-discovery-mode="scoped" feature got tweaked. It will be activated
> via the following way:
> {code}
>
>
>
> {code}
> See https://issues.jboss.org/browse/CDI-420
> We should add this and switch to 'scoped' internally if we find this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OWB-1164) Third Party Beans do not include Any qualifier if not included in bean impl
[ https://issues.apache.org/jira/browse/OWB-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15785938#comment-15785938 ] Mark Struberg commented on OWB-1164: Indeed, if we end up having 2 'Any' annotations then there is a bug with equals/hashCode with one of the 2. Nonetheless checking for existence and only adding the annotation if missing is a good thing in terms of performance. Will do another perf tweak. > Third Party Beans do not include Any qualifier if not included in bean impl > --- > > Key: OWB-1164 > URL: https://issues.apache.org/jira/browse/OWB-1164 > Project: OpenWebBeans > Issue Type: Bug >Affects Versions: 1.7.0 >Reporter: John D. Ament > Fix For: 1.7.1 > > Attachments: > 0001-OWB-1164-Introduce-ThirdpartyBeanAttributes-to-calcu.patch > > > Section 2.3.1 of CDI 1.2 spec indicates that custom beans should include the > any qualifier even if not specified by the bean impl. OWB does not honor > this, instead only the original qualifiers are included in the bean. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OWB-1160) DefaultArchiveService migh mix up BDA urls if the containing folder is also a cp entry
[ https://issues.apache.org/jira/browse/OWB-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-1160. Resolution: Fixed > DefaultArchiveService migh mix up BDA urls if the containing folder is also a > cp entry > -- > > Key: OWB-1160 > URL: https://issues.apache.org/jira/browse/OWB-1160 > Project: OpenWebBeans > Issue Type: Bug > Components: Core >Affects Versions: 1.7.0 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.7.1 > > > If you have 2 classpath entries > * my/folder/ > * my/folder/some.jar > then we might mix up the classes from the BDAs, possibly even overwriting > classes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OWB-1160) DefaultArchiveService migh mix up BDA urls if the containing folder is also a cp entry
Mark Struberg created OWB-1160: -- Summary: DefaultArchiveService migh mix up BDA urls if the containing folder is also a cp entry Key: OWB-1160 URL: https://issues.apache.org/jira/browse/OWB-1160 Project: OpenWebBeans Issue Type: Bug Components: Core Affects Versions: 1.7.0 Reporter: Mark Struberg Assignee: Mark Struberg Fix For: 1.7.1 If you have 2 classpath entries * my/folder/ * my/folder/some.jar then we might mix up the classes from the BDAs, possibly even overwriting classes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OWB-1150) OSGI bundle version ranges too restrictive
[ https://issues.apache.org/jira/browse/OWB-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-1150. Resolution: Fixed Fix Version/s: 1.7.1 Patch applied. Thanks for the fix, Moritz! > OSGI bundle version ranges too restrictive > -- > > Key: OWB-1150 > URL: https://issues.apache.org/jira/browse/OWB-1150 > Project: OpenWebBeans > Issue Type: Bug >Affects Versions: 1.7.0 >Reporter: Moritz Bechler >Assignee: Mark Struberg > Fix For: 1.7.1 > > Attachments: OWB-1150-1.patch > > > openwebbeans-web imports javax.servlet* [2.6,3) and javax.el [2.2,3). > openwebbeans-el22 imports javax.el [2.2,3). > This is way too restrictive, they used to have no upper restrictions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OWB-1150) OSGI bundle version ranges too restrictive
[ https://issues.apache.org/jira/browse/OWB-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15516144#comment-15516144 ] Mark Struberg commented on OWB-1150: A perfect opportunity to ship a patch maybe? :D > OSGI bundle version ranges too restrictive > -- > > Key: OWB-1150 > URL: https://issues.apache.org/jira/browse/OWB-1150 > Project: OpenWebBeans > Issue Type: Bug >Affects Versions: 1.7.0 >Reporter: Moritz Bechler > > openwebbeans-web imports javax.servlet* [2.6,3) and javax.el [2.2,3). > openwebbeans-el22 imports javax.el [2.2,3). > This is way too restrictive, they used to have no upper restrictions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OWB-1150) OSGI bundle version ranges too restrictive
[ https://issues.apache.org/jira/browse/OWB-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15515841#comment-15515841 ] Mark Struberg commented on OWB-1150: Moritz, can you plz check out the latest build and verify the manifests whether they work for you? txs! > OSGI bundle version ranges too restrictive > -- > > Key: OWB-1150 > URL: https://issues.apache.org/jira/browse/OWB-1150 > Project: OpenWebBeans > Issue Type: Bug >Affects Versions: 1.7.0 >Reporter: Moritz Bechler > > openwebbeans-web imports javax.servlet* [2.6,3) and javax.el [2.2,3). > openwebbeans-el22 imports javax.el [2.2,3). > This is way too restrictive, they used to have no upper restrictions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OWB-1150) OSGI bundle version ranges too restrictive
[ https://issues.apache.org/jira/browse/OWB-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15513510#comment-15513510 ] Mark Struberg commented on OWB-1150: 1.1 and 1.2 are the same API. 1.2 was only a MR with polished wording. We don't even have a CDI-1.2 api in geronimo ;) > OSGI bundle version ranges too restrictive > -- > > Key: OWB-1150 > URL: https://issues.apache.org/jira/browse/OWB-1150 > Project: OpenWebBeans > Issue Type: Bug >Affects Versions: 1.7.0 >Reporter: Moritz Bechler > > openwebbeans-web imports javax.servlet* [2.6,3) and javax.el [2.2,3). > openwebbeans-el22 imports javax.el [2.2,3). > This is way too restrictive, they used to have no upper restrictions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OWB-1150) OSGI bundle version ranges too restrictive
[ https://issues.apache.org/jira/browse/OWB-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15513012#comment-15513012 ] Mark Struberg commented on OWB-1150: we also need to update the bundle import for cdi to 1.1 > OSGI bundle version ranges too restrictive > -- > > Key: OWB-1150 > URL: https://issues.apache.org/jira/browse/OWB-1150 > Project: OpenWebBeans > Issue Type: Bug >Affects Versions: 1.7.0 >Reporter: Moritz Bechler > > openwebbeans-web imports javax.servlet* [2.6,3) and javax.el [2.2,3). > openwebbeans-el22 imports javax.el [2.2,3). > This is way too restrictive, they used to have no upper restrictions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OWB-1150) OSGI bundle version ranges too restrictive
[ https://issues.apache.org/jira/browse/OWB-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15475000#comment-15475000 ] Mark Struberg commented on OWB-1150: What would you suggest to use? > OSGI bundle version ranges too restrictive > -- > > Key: OWB-1150 > URL: https://issues.apache.org/jira/browse/OWB-1150 > Project: OpenWebBeans > Issue Type: Bug >Affects Versions: 1.7.0 >Reporter: Moritz Bechler > > openwebbeans-web imports javax.servlet* [2.6,3) and javax.el [2.2,3). > openwebbeans-el22 imports javax.el [2.2,3). > This is way too restrictive, they used to have no upper restrictions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OWB-1153) improve tomcat-plugin performance
Mark Struberg created OWB-1153: -- Summary: improve tomcat-plugin performance Key: OWB-1153 URL: https://issues.apache.org/jira/browse/OWB-1153 Project: OpenWebBeans Issue Type: Improvement Affects Versions: 1.7.0 Reporter: Mark Struberg Assignee: Mark Struberg Fix For: 1.7.1 We could optimise the isManagedBean etc methods by first checking for instanceof EventListener -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OWB-1151) extend our default scan-excludes
[ https://issues.apache.org/jira/browse/OWB-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-1151. Resolution: Fixed > extend our default scan-excludes > > > Key: OWB-1151 > URL: https://issues.apache.org/jira/browse/OWB-1151 > Project: OpenWebBeans > Issue Type: Improvement > Components: Core >Affects Versions: 1.7.0 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.7.1 > > > e.g. we currently scan all surefire-* jars. which are provided by maven. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OWB-1152) Improve compatibility and handling with Java9
[ https://issues.apache.org/jira/browse/OWB-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-1152. Resolution: Fixed > Improve compatibility and handling with Java9 > - > > Key: OWB-1152 > URL: https://issues.apache.org/jira/browse/OWB-1152 > Project: OpenWebBeans > Issue Type: Improvement > Components: Core >Affects Versions: 1.7.0 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.7.1 > > > We should be able to build and run OWB on Java9. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OWB-1152) Improve compatibility and handling with Java9
Mark Struberg created OWB-1152: -- Summary: Improve compatibility and handling with Java9 Key: OWB-1152 URL: https://issues.apache.org/jira/browse/OWB-1152 Project: OpenWebBeans Issue Type: Improvement Components: Core Affects Versions: 1.7.0 Reporter: Mark Struberg Assignee: Mark Struberg Fix For: 1.7.1 We should be able to build and run OWB on Java9. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OWB-1151) extend our default scan-excludes
Mark Struberg created OWB-1151: -- Summary: extend our default scan-excludes Key: OWB-1151 URL: https://issues.apache.org/jira/browse/OWB-1151 Project: OpenWebBeans Issue Type: Improvement Components: Core Affects Versions: 1.7.0 Reporter: Mark Struberg Assignee: Mark Struberg Fix For: 1.7.1 e.g. we currently scan all surefire-* jars. which are provided by maven. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OWB-1140) Caused by: javax.enterprise.inject.UnsatisfiedResolutionException: Api type [xxx] is not found with the qualifiers
[
https://issues.apache.org/jira/browse/OWB-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15448240#comment-15448240
]
Mark Struberg commented on OWB-1140:
Hi Felipe!
When you need injection into Servlets then you always needed the context.xml.
Also in older OWB versions afair.
You btw can easily work around that by using CDI.current() or
CDI.getBeanManager() and resolve the Bean manually.
Note that it isn't guaranteed to be available in the SerletListener#init()
methods (it simply depends on the ordering).
@Inject on the business objects must work, no need to remove it. @Default is
usually not needed. This is the default anyway if no other qualifier is given.
I really would need to see the code to give more detailed information. It
sounds like you just miss a small bit (e.g. having the beans.xml in the wrong
folder etc)
> Caused by: javax.enterprise.inject.UnsatisfiedResolutionException: Api type
> [xxx] is not found with the qualifiers
> ---
>
> Key: OWB-1140
> URL: https://issues.apache.org/jira/browse/OWB-1140
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Injection and Lookup
>Affects Versions: 1.6.2
> Environment: Tomcat 7.0.70
>Reporter: Felipe
> Fix For: 1.7.0
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I was using Tomcat 7.0.54 with owb 1.2.7 and it was working fine.
> So i discovered a bug in tomcat version and then i updated to version 7.0.70,
> so the cdi stop working, and then i upgrade the owb to 1.6.2 too.
> This is my dependencies:
> cdi-api-1.2.jar
> geronimo-annotation_1.2_spec-1.0.jar
> geronimo-atinject_1.0_spec-1.0.jar
> geronimo-interceptor_1.2_spec-1.0.jar
> geronimo-jcdi_1.0_spec-1.0.jar
> openwebbeans-el22-1.6.2.jar
> openwebbeans-impl-1.6.2.jar
> openwebbeans-spi-1.6.2.jar
> openwebbeans-tomcat7-1.6.2.jar
> openwebbeans-web-1.6.2.jar
> And i am gettin this following error:
> I have 2 classes:
> @javax.enterprise.inject.Default
> public class FbirdDAOFactory extends DAOFactory
> @javax.enterprise.inject.Alternative
> public class SqlSrvDAOFactory extends DAOFactory
> and
> public abstract class ConsultaBase implements Consulta,
> SessaoUsuario {
> @javax.inject.Inject
> protected abstract void setDaoFactory(@DefaulDAO DAOFactory
> daofactory);
> }
> This stop working because the error below:
> Caused by: javax.enterprise.inject.UnsatisfiedResolutionException: Api type
> [br.com.growupge.factory.DAOFactory] is not found with the qualifiers
> So i put create a qualifier in FbirdDAOFactory e referenced the Qualifier in
> ConsultaBase and all children classes too. So i kept going to receive the
> same error
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OWB-1140) Caused by: javax.enterprise.inject.UnsatisfiedResolutionException: Api type [xxx] is not found with the qualifiers
[
https://issues.apache.org/jira/browse/OWB-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447090#comment-15447090
]
Mark Struberg commented on OWB-1140:
Hi Felipe!
Please remove cdi-api.jar This is redundant to geronimo-jcdi_1.1_spec.jar. I
don't assume it creates serious issues, but you will have an easier time to
analyze the issue.
* How does your setup look like? Are those classes all directly in
WEB-INF/classes of your WAR? Or are they packaged in a jar?
* Your beans 'extends DAOFactory'. How does DAOFactory look like? Does it
contain an interface? Or is it 'implements' (would be correct)?
> Caused by: javax.enterprise.inject.UnsatisfiedResolutionException: Api type
> [xxx] is not found with the qualifiers
> ---
>
> Key: OWB-1140
> URL: https://issues.apache.org/jira/browse/OWB-1140
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Injection and Lookup
>Affects Versions: 1.6.2
> Environment: Tomcat 7.0.70
>Reporter: Felipe
> Fix For: 1.7.0
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I was using Tomcat 7.0.54 with owb 1.2.7 and it was working fine.
> So i discovered a bug in tomcat version and then i updated to version 7.0.70,
> so the cdi stop working, and then i upgrade the owb to 1.6.2 too.
> This is my dependencies:
> cdi-api-1.2.jar
> geronimo-annotation_1.2_spec-1.0.jar
> geronimo-atinject_1.0_spec-1.0.jar
> geronimo-interceptor_1.2_spec-1.0.jar
> geronimo-jcdi_1.0_spec-1.0.jar
> openwebbeans-el22-1.6.2.jar
> openwebbeans-impl-1.6.2.jar
> openwebbeans-spi-1.6.2.jar
> openwebbeans-tomcat7-1.6.2.jar
> openwebbeans-web-1.6.2.jar
> And i am gettin this following error:
> I have 2 classes:
> @javax.enterprise.inject.Default
> public class FbirdDAOFactory extends DAOFactory
> @javax.enterprise.inject.Alternative
> public class SqlSrvDAOFactory extends DAOFactory
> and
> public abstract class ConsultaBase implements Consulta,
> SessaoUsuario {
> @javax.inject.Inject
> protected abstract void setDaoFactory(@DefaulDAO DAOFactory
> daofactory);
> }
> This stop working because the error below:
> Caused by: javax.enterprise.inject.UnsatisfiedResolutionException: Api type
> [br.com.growupge.factory.DAOFactory] is not found with the qualifiers
> So i put create a qualifier in FbirdDAOFactory e referenced the Qualifier in
> ConsultaBase and all children classes too. So i kept going to receive the
> same error
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OWB-1140) Caused by: javax.enterprise.inject.UnsatisfiedResolutionException: Api type [xxx] is not found with the qualifiers
[
https://issues.apache.org/jira/browse/OWB-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg updated OWB-1140:
---
Fix Version/s: 1.7.0
> Caused by: javax.enterprise.inject.UnsatisfiedResolutionException: Api type
> [xxx] is not found with the qualifiers
> ---
>
> Key: OWB-1140
> URL: https://issues.apache.org/jira/browse/OWB-1140
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Injection and Lookup
>Affects Versions: 1.6.2
> Environment: Tomcat 7.0.70
>Reporter: Felipe
> Fix For: 1.7.0
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I was using Tomcat 7.0.54 with owb 1.2.7 and it was working fine.
> So i discovered a bug in tomcat version and then i updated to version 7.0.70,
> so the cdi stop working, and then i upgrade the owb to 1.6.2 too.
> This is my dependencies:
> cdi-api-1.2.jar
> geronimo-annotation_1.2_spec-1.0.jar
> geronimo-atinject_1.0_spec-1.0.jar
> geronimo-interceptor_1.2_spec-1.0.jar
> geronimo-jcdi_1.0_spec-1.0.jar
> openwebbeans-el22-1.6.2.jar
> openwebbeans-impl-1.6.2.jar
> openwebbeans-spi-1.6.2.jar
> openwebbeans-tomcat7-1.6.2.jar
> openwebbeans-web-1.6.2.jar
> And i am gettin this following error:
> I have 2 classes:
> @javax.enterprise.inject.Default
> public class FbirdDAOFactory extends DAOFactory
> @javax.enterprise.inject.Alternative
> public class SqlSrvDAOFactory extends DAOFactory
> and
> public abstract class ConsultaBase implements Consulta,
> SessaoUsuario {
> @javax.inject.Inject
> protected abstract void setDaoFactory(@DefaulDAO DAOFactory
> daofactory);
> }
> This stop working because the error below:
> Caused by: javax.enterprise.inject.UnsatisfiedResolutionException: Api type
> [br.com.growupge.factory.DAOFactory] is not found with the qualifiers
> So i put create a qualifier in FbirdDAOFactory e referenced the Qualifier in
> ConsultaBase and all children classes too. So i kept going to receive the
> same error
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (OWB-1125) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/OWB-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-1125. Resolution: Fixed Txs Sebb, found it now. Removed 1.2.1. > Please delete old releases from mirroring system > > > Key: OWB-1125 > URL: https://issues.apache.org/jira/browse/OWB-1125 > Project: OpenWebBeans > Issue Type: Bug >Affects Versions: 1.2.1 >Reporter: Sebb >Assignee: Mark Struberg > Fix For: 1.7.0 > > > To reduce the load on the ASF mirrors, projects are required to delete old > releases [1] > Please can you remove all non-current releases? > i.e. the ones listed as affected. > Thanks! > Also, if you have a release guide, perhaps you could add a cleanup stage to > it? > [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OWB-1138) PassivationCapable bean id is not unique: PRODUCERMETHOD#class
[ https://issues.apache.org/jira/browse/OWB-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446990#comment-15446990 ] Mark Struberg commented on OWB-1138: You are welcome, Robert! And great to hear you enjoy our ASF projects and community. Feel free to ping us on the dev list if you need further assistance. > PassivationCapable bean id is not unique: PRODUCERMETHOD#class > -- > > Key: OWB-1138 > URL: https://issues.apache.org/jira/browse/OWB-1138 > Project: OpenWebBeans > Issue Type: Bug > Components: Injection and Lookup >Affects Versions: 1.6.2, 1.6.3 > Environment: Java 8, CDI 1.2, Deltaspike 1.7.0 servlet 3.1.0, jsf-api > 2.2.13, Hibernate 5.1.0.Final running on embedded Tomcat 8, Netbeans 8.1 IDE > on Windows 10. >Reporter: Robert F. Peake >Assignee: Mark Struberg > Labels: newbie > Fix For: 1.7.0 > > > OWB 1.6.3 throws exception in thread "main" > org.apache.webbeans.exception.DuplicateDefinitionException: > PassivationCapable bean id is not unique: PRODUCERMETHOD#class at > org.apache.webbeans.container.BeanManagerImpl.addPassivationInfo(BeanManagerImpl.java:406). > Downgrading to OWB 1.6.2 throws error reported in OWB-1101: > AmbiguousResolutionException: There are more than one WebBeans > with name : csfFLOWDISCOVERYCDIHELPER > In both instances, error is thrown following WARNING: Ignoring class > [org.apache.deltaspike.cdise.tck.control.VersionControlRule] because it could > not be loaded with NoClassDefFoundErrors for > org/junit/runners/model/Statement and org/junit/rules/TestRule. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OWB-1089) OpenWebBeansJsfPlugin is pretty much empty
[ https://issues.apache.org/jira/browse/OWB-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OWB-1089: --- Fix Version/s: 1.7.0 > OpenWebBeansJsfPlugin is pretty much empty > -- > > Key: OWB-1089 > URL: https://issues.apache.org/jira/browse/OWB-1089 > Project: OpenWebBeans > Issue Type: Task >Affects Versions: 1.6.3, 2.0.0-alpha-1 >Reporter: Reinhard Sandtner >Assignee: Mark Struberg > Fix For: 1.7.0 > > > and thus we can remove it? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OWB-1089) OpenWebBeansJsfPlugin is pretty much empty
[ https://issues.apache.org/jira/browse/OWB-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-1089. Resolution: Fixed removed it. > OpenWebBeansJsfPlugin is pretty much empty > -- > > Key: OWB-1089 > URL: https://issues.apache.org/jira/browse/OWB-1089 > Project: OpenWebBeans > Issue Type: Task >Affects Versions: 1.6.3, 2.0.0-alpha-1 >Reporter: Reinhard Sandtner >Assignee: Mark Struberg > Fix For: 1.7.0 > > > and thus we can remove it? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OWB-1089) OpenWebBeansJsfPlugin is pretty much empty
[ https://issues.apache.org/jira/browse/OWB-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OWB-1089: --- Affects Version/s: 1.6.3 > OpenWebBeansJsfPlugin is pretty much empty > -- > > Key: OWB-1089 > URL: https://issues.apache.org/jira/browse/OWB-1089 > Project: OpenWebBeans > Issue Type: Task >Affects Versions: 1.6.3, 2.0.0-alpha-1 >Reporter: Reinhard Sandtner >Assignee: Mark Struberg > Fix For: 1.7.0 > > > and thus we can remove it? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OWB-1089) OpenWebBeansJsfPlugin is pretty much empty
[ https://issues.apache.org/jira/browse/OWB-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned OWB-1089: -- Assignee: Mark Struberg > OpenWebBeansJsfPlugin is pretty much empty > -- > > Key: OWB-1089 > URL: https://issues.apache.org/jira/browse/OWB-1089 > Project: OpenWebBeans > Issue Type: Task >Affects Versions: 2.0.0-alpha-1 >Reporter: Reinhard Sandtner >Assignee: Mark Struberg > > and thus we can remove it? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OWB-1138) PassivationCapable bean id is not unique: PRODUCERMETHOD#class
[ https://issues.apache.org/jira/browse/OWB-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-1138. Resolution: Fixed I consider this problem as fixed. Please reopen if not! > PassivationCapable bean id is not unique: PRODUCERMETHOD#class > -- > > Key: OWB-1138 > URL: https://issues.apache.org/jira/browse/OWB-1138 > Project: OpenWebBeans > Issue Type: Bug > Components: Injection and Lookup >Affects Versions: 1.6.2, 1.6.3 > Environment: Java 8, CDI 1.2, Deltaspike 1.7.0 servlet 3.1.0, jsf-api > 2.2.13, Hibernate 5.1.0.Final running on embedded Tomcat 8, Netbeans 8.1 IDE > on Windows 10. >Reporter: Robert F. Peake >Assignee: Mark Struberg > Labels: newbie > Fix For: 1.7.0 > > > OWB 1.6.3 throws exception in thread "main" > org.apache.webbeans.exception.DuplicateDefinitionException: > PassivationCapable bean id is not unique: PRODUCERMETHOD#class at > org.apache.webbeans.container.BeanManagerImpl.addPassivationInfo(BeanManagerImpl.java:406). > Downgrading to OWB 1.6.2 throws error reported in OWB-1101: > AmbiguousResolutionException: There are more than one WebBeans > with name : csfFLOWDISCOVERYCDIHELPER > In both instances, error is thrown following WARNING: Ignoring class > [org.apache.deltaspike.cdise.tck.control.VersionControlRule] because it could > not be loaded with NoClassDefFoundErrors for > org/junit/runners/model/Statement and org/junit/rules/TestRule. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OWB-1121) IllegalStateException in case of duplicated classes
[ https://issues.apache.org/jira/browse/OWB-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-1121. Resolution: Fixed Fix Version/s: 1.7.0 In any case it works in DeltaSpike now - all green. > IllegalStateException in case of duplicated classes > --- > > Key: OWB-1121 > URL: https://issues.apache.org/jira/browse/OWB-1121 > Project: OpenWebBeans > Issue Type: Bug >Reporter: Gerhard Petracek >Assignee: Mark Struberg > Fix For: 1.7.0 > > > duplicated classes should lead to a warning (with the exact locations of the > redundant classes) and not to: > java.lang.IllegalStateException: It's not allowed to call getBeans(Type, > Annotation...) before AfterBeanDiscovery > at > org.apache.webbeans.container.InjectableBeanManager.checkAfterBeanDiscoveryProcessed(InjectableBeanManager.java:402) > at > org.apache.webbeans.container.InjectableBeanManager.getBeans(InjectableBeanManager.java:121) > ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OWB-1148) remove the webbeans-doc module
[ https://issues.apache.org/jira/browse/OWB-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OWB-1148. Resolution: Fixed > remove the webbeans-doc module > -- > > Key: OWB-1148 > URL: https://issues.apache.org/jira/browse/OWB-1148 > Project: OpenWebBeans > Issue Type: Task > Components: Samples & Documentation >Affects Versions: 1.6.3 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.7.0 > > > webbeans-doc stillcontains information for OWB-1.x and is oudated since a > long time. > All the information in this module is now available in our CMS site anyway. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
