December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-650) Sequential Phreak is broken

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-650?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated DROOLS-650: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1168746, https://bugzilla.redhat.com/show_bug.cgi?id=1168747, https://bugzilla.redhat.com/show_bug.cgi?id=1175886 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1168746, https://bugzilla.redhat.com/show_bug.cgi?id=1168747) > Sequential Phreak is broken > ---------------------------- > > Key: DROOLS-650 > URL: https://issues.jboss.org/browse/DROOLS-650 > Project: Drools > Issue Type: Feature Request > Affects Versions: 6.0.1.Final, 6.1.0.Final, 6.2.0.CR2 > Reporter: Mark Proctor > Assignee: Mario Fusco > Fix For: 6.2.0.CR3 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3640) EJB injection does not work in components added via Servlet Context

by Eduardo Silva (JIRA)

[ https://issues.jboss.org/browse/WFLY-3640?page=com.atlassian.jira.plugin.... ] Eduardo Silva commented on WFLY-3640: ------------------------------------- Is this still happening? I've just tested with the 9.0.0.Alpha2-SNAPSHOT and I was not able to get the NullPointerException. 17:41:38,896 INFO [stdout] (default task-1) before 17:41:38,905 INFO [stdout] (default task-1) after > EJB injection does not work in components added via Servlet Context > ------------------------------------------------------------------- > > Key: WFLY-3640 > URL: https://issues.jboss.org/browse/WFLY-3640 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.1.0.Final > Reporter: James Livingston > Fix For: Awaiting Volunteers > > Attachments: reproducer.zip > > > You can add web components at runtime ServletContext.addListener() and similar methods. @EJB injection inside those components does not work and the field remains null. I have not yet tested whether other forms of injection work or not. > I'm attaching a reproducer which adds a listener via a ServletContainerInitializer. Deploying the WAR and going to the root of the web app context (/scilistener-0.0.1-SNAPSHOT) will cause a NullPointerException -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4171) Provide an html5 archetype for wildfly

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/WFLY-4171?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on WFLY-4171: ----------------------------------- I added some comments on that commit. Other remarks : - JBoss AS 7 Banner is wrong, we need to get something widfly specific - There should be a cheatsheet.xml or else [~burrsutter] will likely bitch about the lack of it :-) I haven't tried the archetype itself yet > Provide an html5 archetype for wildfly > -------------------------------------- > > Key: WFLY-4171 > URL: https://issues.jboss.org/browse/WFLY-4171 > Project: WildFly > Issue Type: Feature Request > Reporter: Fred Bricon > Assignee: Rafael Benevides > > We'd like to provide a Wildfly-ified version of the html5 archetype in JBoss Central, for JBoss Tools and Developer Studio, The current versions we serve right now are : > * org.jboss.aerogear.archetypes:jboss-html5-mobile-archetype:7.1.3.Final > * org.jboss.archetype.wfk:jboss-html5-mobile-archetype:2.6.0.Final -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4171) Provide an html5 archetype for wildfly

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/WFLY-4171?page=com.atlassian.jira.plugin.... ] Rafael Benevides commented on WFLY-4171: ---------------------------------------- Initial commit: https://github.com/wildfly/wildfly-archetypes/commit/d3afafcde78638506c4b... Waiting for WFLY-4031 before doing a 9.0.0.CR1 released > Provide an html5 archetype for wildfly > -------------------------------------- > > Key: WFLY-4171 > URL: https://issues.jboss.org/browse/WFLY-4171 > Project: WildFly > Issue Type: Feature Request > Reporter: Fred Bricon > Assignee: Rafael Benevides > > We'd like to provide a Wildfly-ified version of the html5 archetype in JBoss Central, for JBoss Tools and Developer Studio, The current versions we serve right now are : > * org.jboss.aerogear.archetypes:jboss-html5-mobile-archetype:7.1.3.Final > * org.jboss.archetype.wfk:jboss-html5-mobile-archetype:2.6.0.Final -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3266) Exception are hidden by retry and end in a EJBCLIENT000032 Exception - the underlying client or server side cause is swallowed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3266?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3266: ----------------------------------------------- Panagiotis Sotiropoulos <psotirop(a)redhat.com> changed the Status of [bug 1088463|https://bugzilla.redhat.com/show_bug.cgi?id=1088463] from ASSIGNED to POST > Exception are hidden by retry and end in a EJBCLIENT000032 Exception - the underlying client or server side cause is swallowed > ------------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-3266 > URL: https://issues.jboss.org/browse/WFLY-3266 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.0.0.Final > Reporter: Wolf-Dieter Fink > Assignee: David Lloyd > Priority: Critical > > In case of large parameter input for EJB invocations the ejb-client throw the Exception below. > The underlying OutOfMemory is complete hidden, neither in the server.log nor in the ejb-client with TRACE a hint will be found. > java.lang.IllegalStateException: EJBCLIENT000032: Cannot retry a request which hasn't previously been completed > at org.jboss.ejb.client.EJBClientInvocationContext.retryRequest(EJBClientInvocationContext.java:200) > at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:256) > at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:265) > at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:198) > at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:181) > at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:144) > at com.sun.proxy.$Proxy6.uploadData(Unknown Source) > at de.info.biene.konsens.TestServiceWithAPITest.testUploadData(TestServiceWithAPITest.java:81) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4189) Wildfly Quickstarts using Java EE 6 references instead of Java EE 7

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/WFLY-4189?page=com.atlassian.jira.plugin.... ] Rafael Benevides resolved WFLY-4189. ------------------------------------ Resolution: Done Commit: https://github.com/wildfly/quickstart/commit/11cfe8951b81325a982416136418... > Wildfly Quickstarts using Java EE 6 references instead of Java EE 7 > ------------------------------------------------------------------- > > Key: WFLY-4189 > URL: https://issues.jboss.org/browse/WFLY-4189 > Project: WildFly > Issue Type: Enhancement > Reporter: Rafael Benevides > Assignee: Rafael Benevides > Labels: quickstarts > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4189) Wildfly Quickstarts using Java EE 6 references instead of Java EE 7

by Rafael Benevides (JIRA)

Rafael Benevides created WFLY-4189: -------------------------------------- Summary: Wildfly Quickstarts using Java EE 6 references instead of Java EE 7 Key: WFLY-4189 URL: https://issues.jboss.org/browse/WFLY-4189 Project: WildFly Issue Type: Enhancement Reporter: Rafael Benevides Assignee: Rafael Benevides -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4031) Wildfly Quickstarts using old namespaces for beans.xml and faces-config.xml

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/WFLY-4031?page=com.atlassian.jira.plugin.... ] Rafael Benevides reopened WFLY-4031: ------------------------------------ The current beans.xml has the following warning under JBDS / JBoss Tools: "cvc-complex-type.4: Attribute 'bean-discovery-mode' must appear on element 'beans'." > Wildfly Quickstarts using old namespaces for beans.xml and faces-config.xml > --------------------------------------------------------------------------- > > Key: WFLY-4031 > URL: https://issues.jboss.org/browse/WFLY-4031 > Project: WildFly > Issue Type: Bug > Reporter: Rafael Benevides > Assignee: Sebastian Łaskawiec > Priority: Minor > Labels: quickstarts, > > All Wildfly quickstarts have the wrong XML namespaces for the following files. > ./src/main/webapp/WEB-INF/beans.xml > ./src/main/webapp/WEB-INF/faces-config.xml > beans.xml and faces-config.xml are using java.sun.com-style namespaces instead of xmlns.jcp.org-style namespaces. > This affects the wildfly archetypes as well -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4171) Provide an html5 archetype for wildfly

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/WFLY-4171?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on WFLY-4171: ----------------------------------- It's fine, ideally, we need the archetype ready for early january. Sooner is great, but doesn't need you to work during a week end for that :-) > Provide an html5 archetype for wildfly > -------------------------------------- > > Key: WFLY-4171 > URL: https://issues.jboss.org/browse/WFLY-4171 > Project: WildFly > Issue Type: Feature Request > Reporter: Fred Bricon > Assignee: Rafael Benevides > > We'd like to provide a Wildfly-ified version of the html5 archetype in JBoss Central, for JBoss Tools and Developer Studio, The current versions we serve right now are : > * org.jboss.aerogear.archetypes:jboss-html5-mobile-archetype:7.1.3.Final > * org.jboss.archetype.wfk:jboss-html5-mobile-archetype:2.6.0.Final -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-671) KnowledgeBaseAdapter in legacy 5.x API is not serializable

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-671?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-671. -------------------------------- Fix Version/s: 6.2.0.Final Resolution: Done Fixed by https://github.com/droolsjbpm/drools/commit/59bc9905e > KnowledgeBaseAdapter in legacy 5.x API is not serializable > ---------------------------------------------------------- > > Key: DROOLS-671 > URL: https://issues.jboss.org/browse/DROOLS-671 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.2.0.Final > > > Trying to serialize a KnowledgeBase created with the legacy 5.x API causes the following exception. > java.io.NotSerializableException: org.drools.impl.adapters.KnowledgeBaseAdapter > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184) > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2014