December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-666) In KIE workbench found a major problem, the Project Explorer disappears randomly I am using kie-drools-wb-distribution-6.1.0.Final

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-666?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-666: ---------------------------------- Assignee: Michael Anstis (was: Mark Proctor) > In KIE workbench found a major problem, the Project Explorer disappears randomly I am using kie-drools-wb-distribution-6.1.0.Final > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-666 > URL: https://issues.jboss.org/browse/DROOLS-666 > Project: Drools > Issue Type: Bug > Affects Versions: 6.1.0.Final > Reporter: Yajavendra Patel > Assignee: Michael Anstis > > In KIE workbench found a major problem, the Project Explorer disappears randomly I am using kie-drools-wb-distribution-6.1.0.Final > the "Project Explorer" view on the left side suddenly disappears. It is user dependent - if I log in with an affected user from another machine, PE is also missing - and browser and OS and everything else independent. > There is no way to restore the PE permanently. > This issue has been discussed for different versions of Guvnor already: > http://drools-moved.46999.n3.nabble.com/Project-Explorer-has-dissappeared... > https://bugzilla.redhat.com/show_bug.cgi?id=1041021 > https://developer.jboss.org/thread/237501 > The workarounds - changing the URL - are not permanent and seem not to work with 6.2. Also, this is no option to tell our users. > Currently, this bug is a huge blocker for us since it renders the Workbench / Guvnor useless for our users. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-666) In KIE workbench found a major problem, the Project Explorer disappears randomly I am using kie-drools-wb-distribution-6.1.0.Final

by Yajavendra Patel (JIRA)

Yajavendra Patel created DROOLS-666: --------------------------------------- Summary: In KIE workbench found a major problem, the Project Explorer disappears randomly I am using kie-drools-wb-distribution-6.1.0.Final Key: DROOLS-666 URL: https://issues.jboss.org/browse/DROOLS-666 Project: Drools Issue Type: Bug Affects Versions: 6.1.0.Final Reporter: Yajavendra Patel Assignee: Mark Proctor In KIE workbench found a major problem, the Project Explorer disappears randomly I am using kie-drools-wb-distribution-6.1.0.Final the "Project Explorer" view on the left side suddenly disappears. It is user dependent - if I log in with an affected user from another machine, PE is also missing - and browser and OS and everything else independent. There is no way to restore the PE permanently. This issue has been discussed for different versions of Guvnor already: http://drools-moved.46999.n3.nabble.com/Project-Explorer-has-dissappeared... https://bugzilla.redhat.com/show_bug.cgi?id=1041021 https://developer.jboss.org/thread/237501 The workarounds - changing the URL - are not permanent and seem not to work with 6.2. Also, this is no option to tell our users. Currently, this bug is a huge blocker for us since it renders the Workbench / Guvnor useless for our users. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4153) Incorrect interface definition in ejb-jar.xml for entity beans shows just NullPointer exception

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4153?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4153: ----------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 900798|https://bugzilla.redhat.com/show_bug.cgi?id=900798] from ON_QA to VERIFIED > Incorrect interface definition in ejb-jar.xml for entity beans shows just NullPointer exception > ----------------------------------------------------------------------------------------------- > > Key: WFLY-4153 > URL: https://issues.jboss.org/browse/WFLY-4153 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Minor > > {noformat} > In case that you specify interface type for entity bean in ejb-jar.xml that does not correspond with definition in the class of the bean then just Null Pointer exception is shown without any other info what's happening. > I mean when you define bean through interface as remote and the ejb-jar.xml describes bean interfaces as local > {code} > public interface SomeBean extends EJBObject { > ... > } > public interface SomeBeanHome extends EJBHome { > ... > } > {code} > and the ejb-jar.xml looks like > {code} > <ejb-jar xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd" version="3.1"> > <enterprise-beans> > <entity> > <ejb-name>SomeBean</ejb-name> > <local-home>package.SomeBeanHome</local-home> > <local>package.SomeBean</local> > <ejb-class>package.SomeBeanBean</ejb-class> > <persistence-type>Bean</persistence-type> > <prim-key-class>java.lang.Integer</prim-key-class> > <reentrant>true</reentrant> > </entity> > </enterprise-beans> > </ejb-jar> > {code} > then NullPointerException is thrown > {code} > ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.deployment.unit."entitybeanbmp.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."entitybeanbmp.jar".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "entitybeanbmp.jar" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_23] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_23] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_23] > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011058: Failed to install component SimpleBMPBean > at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deploy(ComponentInstallProcessor.java:102) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > ... 5 more > Caused by: java.lang.NullPointerException > at org.jboss.as.ejb3.component.entity.EntityBeanObjectViewConfigurator$2.configureDependency(EntityBeanObjectViewConfigurator.java:108) > at org.jboss.as.ejb3.component.entity.EntityBeanObjectViewConfigurator$2.configureDependency(EntityBeanObjectViewConfigurator.java:105) > at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deployComponent(ComponentInstallProcessor.java:139) > at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deploy(ComponentInstallProcessor.java:95) > ... 6 more > {code} > instead of some informative one. > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4156) WildFly is not able to parse ejb-jar.xml of version 2.0

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4156?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4156: ----------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 1057835|https://bugzilla.redhat.com/show_bug.cgi?id=1057835] from ON_QA to VERIFIED > WildFly is not able to parse ejb-jar.xml of version 2.0 > ------------------------------------------------------- > > Key: WFLY-4156 > URL: https://issues.jboss.org/browse/WFLY-4156 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 9.0.0.Beta1 > > > - While using "ejb-jar.xml" of version 2.0 as following EAP/WildFly throws the parsing error: > {code} > <?xml version="1.0"?> > <!DOCTYPE ejb-jar > PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" > "http://java.sun.com/dtd/ejb-jar_2_0.dtd"> > <ejb-jar> > <enterprise-beans> > <message-driven> > <ejb-name>ExampleMDB</ejb-name> > <ejb-class>test.mdb.ExampleMDB</ejb-class> > <transaction-type>Container</transaction-type> > <message-driven-destination> > <destination-type>javax.jms.Queue</destination-type> > </message-driven-destination> > <resource-ref> > <res-ref-name>jms/QueueConnectionFactory</res-ref-name> > <res-type>javax.jms.QueueConnectionFactory</res-type> > <res-auth>Container</res-auth> > </resource-ref> > </message-driven> > </enterprise-beans> > </ejb-jar> > {code} > - The following error is encountered at the time of deployment: > {code} > 17:40:04,405 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."TestEJB.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."TestEJB.jar".PARSE: JBAS018733: Failed to process phase PARSE of deployment "TestEJB.jar" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_45] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_45] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45] > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS014185: Exception while parsing ejb-jar.xml: /content/TestEJB.jar/META-INF/ejb-jar.xml > at org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.parseEjbJarXml(EjbJarParsingDeploymentUnitProcessor.java:250) > at org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.deploy(EjbJarParsingDeploymentUnitProcessor.java:121) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] > ... 5 more > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[14,10] > Message: Unexpected element 'message-driven-destination' encountered > at org.jboss.metadata.parser.util.MetaDataElementParser.unexpectedElement(MetaDataElementParser.java:109) > at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElement(AbstractMetaDataParser.java:56) > at org.jboss.metadata.ejb.parser.spec.AbstractNamedMetaDataWithDescriptionGroupParser.processElement(AbstractNamedMetaDataWithDescriptionGroupParser.java:67) > at org.jboss.metadata.ejb.parser.spec.AbstractEnterpriseBeanMetaDataParser.processElement(AbstractEnterpriseBeanMetaDataParser.java:85) > at org.jboss.metadata.ejb.parser.spec.AbstractMessageDrivenBeanParser.processElement(AbstractMessageDrivenBeanParser.java:94) > at org.jboss.metadata.ejb.parser.spec.MessageDrivenBean31Parser.processElement(MessageDrivenBean31Parser.java:77) > at org.jboss.metadata.ejb.parser.spec.MessageDrivenBean31Parser.processElement(MessageDrivenBean31Parser.java:37) > at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElements(AbstractMetaDataParser.java:69) > at org.jboss.metadata.ejb.parser.spec.MessageDrivenBean31Parser.parse(MessageDrivenBean31Parser.java:44) > at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.processElement(EnterpriseBeansMetaDataParser.java:99) > at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.processElement(EnterpriseBeansMetaDataParser.java:40) > at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElements(AbstractMetaDataParser.java:69) > at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.parse(EnterpriseBeansMetaDataParser.java:75) > at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.parse(EnterpriseBeansMetaDataParser.java:68) > at org.jboss.metadata.ejb.parser.spec.AbstractEjbJarMetaDataParser.processElement(AbstractEjbJarMetaDataParser.java:112) > at org.jboss.metadata.ejb.parser.spec.AbstractEjbJarMetaDataParser.processElement(AbstractEjbJarMetaDataParser.java:39) > at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElements(AbstractMetaDataParser.java:69) > at org.jboss.metadata.ejb.parser.spec.EjbJarMetaDataParser.parseDocument(EjbJarMetaDataParser.java:110) > at org.jboss.metadata.ejb.parser.spec.EjbJarMetaDataParser.parse(EjbJarMetaDataParser.java:54) > at org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.parseEjbJarXml(EjbJarParsingDeploymentUnitProcessor.java:247) > ... 7 more > 17:40:04,422 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "TestEJB.jar" was rolled back with the following failure message: > {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"TestEJB.jar\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"TestEJB.jar\".PARSE: JBAS018733: Failed to process phase PARSE of deployment \"TestEJB.jar\" > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS014185: Exception while parsing ejb-jar.xml: /content/TestEJB.jar/META-INF/ejb-jar.xml > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[14,10] > Message: Unexpected element 'message-driven-destination' encountered"}} > {code} > **NOTE:** According to the link [1] EJB2.0 is supported with EAP6 so ideally JBoss should be able to parse the "ejb-jar.xml" of version 2.0 DTDs. > **NOTE:** there is a feature request seen for JBossAS7 for requesting support for ejb-jar.xml 2.0 DTDs [2] > [1] https://access.redhat.com/site/articles/113373 > [2] https://issues.jboss.org/browse/JBMETA-354 > Version-Release number of selected component (if applicable): > How reproducible: > Steps to Reproduce: > 1. Deploy an MDB based EJB jar in EAP6/WildFly and use the ejb-jar.xml as mentioned in the issue description. > Actual results: > - EAP6/WildFly should be able to parse the ejb-jar.xml properly and should deploy the MDB properly. > Expected results: > - Deployment should be successful. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBMETA-354) Support EJB 2.0 dtd descriptors

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBMETA-354?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBMETA-354: ------------------------------------------------ Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 1057835|https://bugzilla.redhat.com/show_bug.cgi?id=1057835] from ON_QA to VERIFIED > Support EJB 2.0 dtd descriptors > ------------------------------- > > Key: JBMETA-354 > URL: https://issues.jboss.org/browse/JBMETA-354 > Project: JBoss Metadata > Issue Type: Bug > Components: ejb > Affects Versions: 7.0.0.Final > Reporter: Carlo de Wolf > Assignee: Ivo Studensky > Fix For: 8.1.2.Final, 7.2.1.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SECURITY-868) Multithread issue when validate with cached hased password + nonce credential info from JBossCachedAuthenticationManager

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-868?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-868: -------------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1173492|https://bugzilla.redhat.com/show_bug.cgi?id=1173492] from NEW to ASSIGNED > Multithread issue when validate with cached hased password + nonce credential info from JBossCachedAuthenticationManager > -------------------------------------------------------------------------------------------------------------------------- > > Key: SECURITY-868 > URL: https://issues.jboss.org/browse/SECURITY-868 > Project: PicketBox > Issue Type: Task > Components: PicketBox > Reporter: Jim Ma > Assignee: Stefan Guilhen > Fix For: PicketBox_4_9_0.Beta3 > > > When the new security domain is configured with catch-type=default in standalone.xml, the validated credential will be put in the JBossCachedAuthenticationManager with principal and domaininfo value pair. In multithread environment, a new validated credential can overwrite the previous thread cached domain info. This will cause even in the same thread , the cached authentication info could not work. For example if one user login with username , password and nonce in two threads : thread A and thread B ;thread A caches the validated credential(hased password +nonce) in JBossCachedAuthenticationMessager, thread B does the authentication, then caches the validated credential (hashed password + nonce) , even it's the same user and passoword, the credential is different because the nonce is diffrent. So the new credential created in thread B will overwrite the previous value created by thread A . So in thread A, the cached validation info won't work and following validation with cached credential will all fail. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SECURITY-866) Add jboss module option to ServerLoginModule

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-866?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-866: -------------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1173493|https://bugzilla.redhat.com/show_bug.cgi?id=1173493] from NEW to ASSIGNED > Add jboss module option to ServerLoginModule > -------------------------------------------- > > Key: SECURITY-866 > URL: https://issues.jboss.org/browse/SECURITY-866 > Project: PicketBox > Issue Type: Task > Components: PicketBox > Reporter: Jim Ma > Assignee: Jim Ma > > If the callback class isn't in the picketbox module or the deployment module, there is module option can be provided to define the module path for the callback class or validator class. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SECURITY-866) Add jboss module option to ServerLoginModule

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-866?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated SECURITY-866: --------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1173493 > Add jboss module option to ServerLoginModule > -------------------------------------------- > > Key: SECURITY-866 > URL: https://issues.jboss.org/browse/SECURITY-866 > Project: PicketBox > Issue Type: Task > Components: PicketBox > Reporter: Jim Ma > Assignee: Jim Ma > > If the callback class isn't in the picketbox module or the deployment module, there is module option can be provided to define the module path for the callback class or validator class. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SECURITY-868) Multithread issue when validate with cached hased password + nonce credential info from JBossCachedAuthenticationManager

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-868?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated SECURITY-868: --------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1173492 > Multithread issue when validate with cached hased password + nonce credential info from JBossCachedAuthenticationManager > -------------------------------------------------------------------------------------------------------------------------- > > Key: SECURITY-868 > URL: https://issues.jboss.org/browse/SECURITY-868 > Project: PicketBox > Issue Type: Task > Components: PicketBox > Reporter: Jim Ma > Assignee: Stefan Guilhen > Fix For: PicketBox_4_9_0.Beta3 > > > When the new security domain is configured with catch-type=default in standalone.xml, the validated credential will be put in the JBossCachedAuthenticationManager with principal and domaininfo value pair. In multithread environment, a new validated credential can overwrite the previous thread cached domain info. This will cause even in the same thread , the cached authentication info could not work. For example if one user login with username , password and nonce in two threads : thread A and thread B ;thread A caches the validated credential(hased password +nonce) in JBossCachedAuthenticationMessager, thread B does the authentication, then caches the validated credential (hashed password + nonce) , even it's the same user and passoword, the credential is different because the nonce is diffrent. So the new credential created in thread B will overwrite the previous value created by thread A . So in thread A, the cached validation info won't work and following validation with cached credential will all fail. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBMETA-354) Support EJB 2.0 dtd descriptors

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBMETA-354?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBMETA-354: ------------------------------------------------ Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1171105|https://bugzilla.redhat.com/show_bug.cgi?id=1171105] from ON_QA to VERIFIED > Support EJB 2.0 dtd descriptors > ------------------------------- > > Key: JBMETA-354 > URL: https://issues.jboss.org/browse/JBMETA-354 > Project: JBoss Metadata > Issue Type: Bug > Components: ejb > Affects Versions: 7.0.0.Final > Reporter: Carlo de Wolf > Assignee: Ivo Studensky > Fix For: 8.1.2.Final, 7.2.1.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2014