May 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1159) Project examples are created with lots of unresolved types

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1159?page=com.atlassian.jira.plugi... ] Andrej Podhradsky commented on DROOLS-1159: ------------------------------------------- Well... this is a bit confusing because it should be a maven project but it is created as a common java project in eclipse > Project examples are created with lots of unresolved types > ---------------------------------------------------------- > > Key: DROOLS-1159 > URL: https://issues.jboss.org/browse/DROOLS-1159 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Affects Versions: 6.4.0.Final > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > > After creating an example form online repository there are lots of errors such as unresolved types. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1159) Project examples are created with lots of unresolved types

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1159?page=com.atlassian.jira.plugi... ] Andrej Podhradsky reopened DROOLS-1159: --------------------------------------- Ok, so it seems that only libraries for JUnit and Arquillian are missing which makes sense since there are no such libs in jbpm/drools runtime. > Project examples are created with lots of unresolved types > ---------------------------------------------------------- > > Key: DROOLS-1159 > URL: https://issues.jboss.org/browse/DROOLS-1159 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Affects Versions: 6.4.0.Final > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > > After creating an example form online repository there are lots of errors such as unresolved types. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2058) Probe: add bundler type at runtime

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2058?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2058: --------------------------- Fix Version/s: 3.6.10 > Probe: add bundler type at runtime > ---------------------------------- > > Key: JGRP-2058 > URL: https://issues.jboss.org/browse/JGRP-2058 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.6.10, 4.0 > > > Add a method to shutdown the old Bundler implementation in TP and create and start a new one. Argument should either be {{bundler_type}} or the fully qualified classname of a {{Bundler}} impl, so that unknown bundlers can also be created as long as the code is on the classpath. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2058) Probe: add bundler type at runtime

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2058?page=com.atlassian.jira.plugin.... ] Bela Ban reopened JGRP-2058: ---------------------------- Need to selectively backport to 3.6 branch > Probe: add bundler type at runtime > ---------------------------------- > > Key: JGRP-2058 > URL: https://issues.jboss.org/browse/JGRP-2058 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.0 > > > Add a method to shutdown the old Bundler implementation in TP and create and start a new one. Argument should either be {{bundler_type}} or the fully qualified classname of a {{Bundler}} impl, so that unknown bundlers can also be created as long as the code is on the classpath. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-209) do not export api if excluded within jboss-deployment-structure.xml

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-209?page=com.atlassian.jira.plugin... ] Tomaz Cerar closed WFCORE-209. ------------------------------ Fix Version/s: 2.0.0.Final Resolution: Out of Date Fixed in WildFly 9. > do not export api if excluded within jboss-deployment-structure.xml > ------------------------------------------------------------------- > > Key: WFCORE-209 > URL: https://issues.jboss.org/browse/WFCORE-209 > Project: WildFly Core > Issue Type: Bug > Components: Server > Environment: JBoss EAP 6.3 + Spring 3.2.11.RELEASE > Reporter: Mathieu Lachance > Fix For: 2.0.0.Final > > > I'm currently trying to upgrade JPA 2.0 to JPA 2.1 in JBoss EAP 6.3 by leveraging the jboss-deployment-structure.xml: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <jboss-deployment-structure> > <deployment> > <exclude-subsystems> > <subsystem name="jpa" /> > <subsystem name="webservices" /> > <subsystem name="weld" /> > </exclude-subsystems> > <exclusions> > <module name="javax.persistence.api" /> > <module name="org.hibernate" /> > </exclusions> > </deployment> > </jboss-deployment-structure> > {code} > When trying to deploy my war (containing all hibernate 4.3.6 jars) I get the following error: > {quote} > Caused by: java.lang.NoSuchMethodError: javax.persistence.Table.indexes()[Ljavax/persistence/Index; > at org.hibernate.cfg.annotations.EntityBinder.processComplementaryTableDefinitions(EntityBinder.java:936) [hibernate-core-4.3.6.Final.jar:4.3.6.Final] > at org.hibernate.cfg.AnnotationBinder.bindClass(AnnotationBinder.java:824) [hibernate-core-4.3.6.Final.jar:4.3.6.Final] > at org.hibernate.cfg.Configuration$MetadataSourceQueue.processAnnotatedClassesQueue(Configuration.java:3788) [hibernate-core-4.3.6.Final.jar:4.3.6.Final] > at org.hibernate.cfg.Configuration$MetadataSourceQueue.processMetadata(Configuration.java:3742) [hibernate-core-4.3.6.Final.jar:4.3.6.Final] > at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1410) [hibernate-core-4.3.6.Final.jar:4.3.6.Final] > at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1844) [hibernate-core-4.3.6.Final.jar:4.3.6.Final] > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:850) [hibernate-entitymanager-4.3.6.Final.jar:4.3.6.Final] > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:843) [hibernate-entitymanager-4.3.6.Final.jar:4.3.6.Final] > at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:398) [hibernate-core-4.3.6.Final.jar:4.3.6.Final] > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:842) [hibernate-entitymanager-4.3.6.Final.jar:4.3.6.Final] > at org.hibernate.jpa.HibernatePersistenceProvider.createContainerEntityManagerFactory(HibernatePersistenceProvider.java:152) [hibernate-entitymanager-4.3.6.Final.jar:4.3.6.Final] > at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:290) [spring-orm-3.2.11.RELEASE.jar:3.2.11.RELEASE] > at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:310) [spring-orm-3.2.11.RELEASE.jar:3.2.11.RELEASE] > at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1573) [spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1511) [spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > ... 23 more > {quote} > {{Index}} was introduced with JPA 2.1 and even though: > 1. my application bundle the correct JPA jar > 2. my application excluded the javax.persistence.api > 3. my application excluded the jpa subsystem > I get a conflict. > The only way I made it possible to upgrade the JPA version was to explicitely state to not export the javax.persistence.api (see workaround). This way of doing thing though is not portable (as it impacts all other war deployed in the JBoss server) and is critical in our situation. > The issue might/is probably not be related to jboss-modules component but I was not able to find within the jboss sources the explicit line of code responsible of reading the jboss-deployment-structure.xml. > If you can point me out the correct component it will be a pleasure to help resolve the issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1160) It is possible to create duplicate drools runtime

by Tomas David (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1160?page=com.atlassian.jira.plugi... ] Tomas David updated DROOLS-1160: -------------------------------- Labels: reported-by-qe (was: ) > It is possible to create duplicate drools runtime > ------------------------------------------------- > > Key: DROOLS-1160 > URL: https://issues.jboss.org/browse/DROOLS-1160 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Environment: Drools plugin 6.4.1 > Reporter: Tomas David > Assignee: Robert (Bob) Brodt > Priority: Minor > Labels: reported-by-qe > > It is possible to create drools runtime with a name of runtime which already exists. If the location or version text input is changed, the OK button is enabled. Only case when it is not possible to create duplicate runtime is when the name input is changed as the last input to the duplicate name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1161) Installed Drools Runtimes Apply button unchecks default runtime

by Tomas David (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1161?page=com.atlassian.jira.plugi... ] Tomas David updated DROOLS-1161: -------------------------------- Labels: reported-by-qe (was: ) > Installed Drools Runtimes Apply button unchecks default runtime > --------------------------------------------------------------- > > Key: DROOLS-1161 > URL: https://issues.jboss.org/browse/DROOLS-1161 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Environment: Drools plugin 6.4.1 > Reporter: Tomas David > Assignee: Robert (Bob) Brodt > Priority: Minor > Labels: reported-by-qe > > When you add drools runtime and then you click on the Apply button, default runtime will be unchecked. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1161) Installed Drools Runtimes Apply button unchecks default runtime

by Tomas David (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1161?page=com.atlassian.jira.plugi... ] Tomas David updated DROOLS-1161: -------------------------------- Component/s: eclipse plugin > Installed Drools Runtimes Apply button unchecks default runtime > --------------------------------------------------------------- > > Key: DROOLS-1161 > URL: https://issues.jboss.org/browse/DROOLS-1161 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Environment: Drools plugin 6.4.1 > Reporter: Tomas David > Assignee: Robert (Bob) Brodt > Priority: Minor > Labels: reported-by-qe > > When you add drools runtime and then you click on the Apply button, default runtime will be unchecked. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1161) Installed Drools Runtimes Apply button unchecks default runtime

by Tomas David (JIRA)

Tomas David created DROOLS-1161: ----------------------------------- Summary: Installed Drools Runtimes Apply button unchecks default runtime Key: DROOLS-1161 URL: https://issues.jboss.org/browse/DROOLS-1161 Project: Drools Issue Type: Bug Environment: Drools plugin 6.4.1 Reporter: Tomas David Assignee: Robert (Bob) Brodt Priority: Minor When you add drools runtime and then you click on the Apply button, default runtime will be unchecked. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-209) do not export api if excluded within jboss-deployment-structure.xml

by Antoine Rey (JIRA)

[ https://issues.jboss.org/browse/WFCORE-209?page=com.atlassian.jira.plugin... ] Antoine Rey commented on WFCORE-209: ------------------------------------ I've got the same Issue with JBoss 6.4 EAP. The workarround 1 works fine but this is non-portable. The workarround 2 works with WAR but not EAR. Do you have any idea? > do not export api if excluded within jboss-deployment-structure.xml > ------------------------------------------------------------------- > > Key: WFCORE-209 > URL: https://issues.jboss.org/browse/WFCORE-209 > Project: WildFly Core > Issue Type: Bug > Components: Server > Environment: JBoss EAP 6.3 + Spring 3.2.11.RELEASE > Reporter: Mathieu Lachance > > I'm currently trying to upgrade JPA 2.0 to JPA 2.1 in JBoss EAP 6.3 by leveraging the jboss-deployment-structure.xml: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <jboss-deployment-structure> > <deployment> > <exclude-subsystems> > <subsystem name="jpa" /> > <subsystem name="webservices" /> > <subsystem name="weld" /> > </exclude-subsystems> > <exclusions> > <module name="javax.persistence.api" /> > <module name="org.hibernate" /> > </exclusions> > </deployment> > </jboss-deployment-structure> > {code} > When trying to deploy my war (containing all hibernate 4.3.6 jars) I get the following error: > {quote} > Caused by: java.lang.NoSuchMethodError: javax.persistence.Table.indexes()[Ljavax/persistence/Index; > at org.hibernate.cfg.annotations.EntityBinder.processComplementaryTableDefinitions(EntityBinder.java:936) [hibernate-core-4.3.6.Final.jar:4.3.6.Final] > at org.hibernate.cfg.AnnotationBinder.bindClass(AnnotationBinder.java:824) [hibernate-core-4.3.6.Final.jar:4.3.6.Final] > at org.hibernate.cfg.Configuration$MetadataSourceQueue.processAnnotatedClassesQueue(Configuration.java:3788) [hibernate-core-4.3.6.Final.jar:4.3.6.Final] > at org.hibernate.cfg.Configuration$MetadataSourceQueue.processMetadata(Configuration.java:3742) [hibernate-core-4.3.6.Final.jar:4.3.6.Final] > at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1410) [hibernate-core-4.3.6.Final.jar:4.3.6.Final] > at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1844) [hibernate-core-4.3.6.Final.jar:4.3.6.Final] > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:850) [hibernate-entitymanager-4.3.6.Final.jar:4.3.6.Final] > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:843) [hibernate-entitymanager-4.3.6.Final.jar:4.3.6.Final] > at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:398) [hibernate-core-4.3.6.Final.jar:4.3.6.Final] > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:842) [hibernate-entitymanager-4.3.6.Final.jar:4.3.6.Final] > at org.hibernate.jpa.HibernatePersistenceProvider.createContainerEntityManagerFactory(HibernatePersistenceProvider.java:152) [hibernate-entitymanager-4.3.6.Final.jar:4.3.6.Final] > at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:290) [spring-orm-3.2.11.RELEASE.jar:3.2.11.RELEASE] > at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:310) [spring-orm-3.2.11.RELEASE.jar:3.2.11.RELEASE] > at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1573) [spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1511) [spring-beans-3.2.11.RELEASE.jar:3.2.11.RELEASE] > ... 23 more > {quote} > {{Index}} was introduced with JPA 2.1 and even though: > 1. my application bundle the correct JPA jar > 2. my application excluded the javax.persistence.api > 3. my application excluded the jpa subsystem > I get a conflict. > The only way I made it possible to upgrade the JPA version was to explicitely state to not export the javax.persistence.api (see workaround). This way of doing thing though is not portable (as it impacts all other war deployed in the JBoss server) and is critical in our situation. > The issue might/is probably not be related to jboss-modules component but I was not able to find within the jboss sources the explicit line of code responsible of reading the jboss-deployment-structure.xml. > If you can point me out the correct component it will be a pleasure to help resolve the issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

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 May 2016