[JBoss JIRA] (HIBERNATE-18) Problem when path containing the project is too long
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/HIBERNATE-18?page=com.atlassian.jira.plug... ]
Max Rydahl Andersen closed HIBERNATE-18.
----------------------------------------
Resolution: Out of Date
this issue is 10 years old and refer to long dead code/examples.
closing as out of date
> Problem when path containing the project is too long
> ----------------------------------------------------
>
> Key: HIBERNATE-18
> URL: https://issues.jboss.org/browse/HIBERNATE-18
> Project: Hibernate Integration
> Issue Type: Bug
> Environment: Eclipse 3.1
> Embeddable EJB 3.0
> Example: microcontainer-deployment
> Reporter: Doink06 Doink06
> Assignee: Gavin King
>
> Hello,
> I have the following configuration:
> - an eclipse workspace, which contains all the examples extrated from "Embeddable EJB 3.0"
> - Each example is transformed into a java project
> - a special project named Jboss is containing Embeddable EJB 3.0 with subdirectories lib/ and conf/
> Case #1
> The workspace is located on my disk at the following place : "D:/EJB3Examples"
> The example microcontainer-deployment is working perfectly
> Case #2
> I moved the workspace to the following place : "D:/Projects/Java/Eclipse3/EJB3Examples"
> The example microcontainer-deployment is crashing.
> WARN 30-08 01:02:38,906 (JBossEntityResolver.java:getLocalEntityName:201) -Entity is not registered, publicId=null systemId=file:/D:/Projects/Java/Eclipse3/EJB3Examples/jboss/conf/bean-deployer_1_0.xsd
> WARN 30-08 01:02:38,953 (SaxJBossXBParser.java:warning:226) -schema_reference.4: Failed to read schema document 'bean-deployer_1_0.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. @ file:/D:/Projects/Java/Eclipse3/EJB3Examples/jboss/conf/embedded-jboss-beans.xml[5,45]
> WARN 30-08 01:02:41,062 (JBossEntityResolver.java:getLocalEntityName:201) -Entity is not registered, publicId=null systemId=file:/D:/Projects/Java/Eclipse3/EJB3Examples/microcontainer-deployment/conf/bean-deployer_1_0.xsd
> WARN 30-08 01:02:41,062 (SaxJBossXBParser.java:warning:226) -schema_reference.4: Failed to read schema document 'bean-deployer_1_0.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. @ file:/D:/Projects/Java/Eclipse3/EJB3Examples/microcontainer-deployment/conf/ejb3-deployment.xml[5,45]
> ERROR 30-08 01:02:45,609 (EjbTimerUtil.java:getTimerService:43) -Unable to initialize timer service
> ----------------------------------------------------------
> Exception in thread "main" javax.ejb.EJBException: null; CausedByException is:
> Unknown entity: org.jboss.tutorial.mcdeploy.Customer
> at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:46)
> at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:70)
> at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:134)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:61)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:39)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:63)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:91)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:152)
> at org.jboss.ejb3.stateless.StatelessLocalProxy.invoke(StatelessLocalProxy.java:60)
> at $Proxy11.createCustomer(Unknown Source)
> at org.jboss.tutorial.mcdeploy.Main.main(Main.java:32)
> java.lang.IllegalArgumentException: Unknown entity: org.jboss.tutorial.mcdeploy.Customer
> at org.hibernate.ejb.AbstractEntityManagerImpl.persist(AbstractEntityManagerImpl.java:133)
> at org.jboss.ejb3.entity.InjectedEntityManager.persist(InjectedEntityManager.java:97)
> at org.jboss.tutorial.mcdeploy.CustomerDAOBean.createCustomer(CustomerDAOBean.java:28)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
> at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:32)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:66)
> at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:134)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:61)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:39)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:63)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:91)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:152)
> at org.jboss.ejb3.stateless.StatelessLocalProxy.invoke(StatelessLocalProxy.java:60)
> at $Proxy11.createCustomer(Unknown Source)
> at org.jboss.tutorial.mcdeploy.Main.main(Main.java:32)
> Case #3
> I have copied the workspace to the following directory "D:\Projects\EJB3Examples"
> It works fine
> Case #4
> I have copied the workspace to the following directory "D:\Projects\Java\EJB3Examples"
> It works fine
> Case #5
> I have copied the workspace to the following directory "D:\Projects\Java\Eclips3\EJB3Examples"
> Without the "e" for eclips3. It works fine
> Case #5
> As soon as I rename the directory Eclips3 into Eclipse3, it crashes ... ?!?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (HIBERNATE-18) Problem when path containing the project is too long
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/HIBERNATE-18?page=com.atlassian.jira.plug... ]
Max Rydahl Andersen commented on HIBERNATE-18:
----------------------------------------------
The Hibernate Tools part of JBoss Tools / Red Hat JBoss Developer Studio has its issue tracker here (project = JBIDE, component = hibernate):
https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20compon...
> Problem when path containing the project is too long
> ----------------------------------------------------
>
> Key: HIBERNATE-18
> URL: https://issues.jboss.org/browse/HIBERNATE-18
> Project: Hibernate Integration
> Issue Type: Bug
> Environment: Eclipse 3.1
> Embeddable EJB 3.0
> Example: microcontainer-deployment
> Reporter: Doink06 Doink06
> Assignee: Gavin King
>
> Hello,
> I have the following configuration:
> - an eclipse workspace, which contains all the examples extrated from "Embeddable EJB 3.0"
> - Each example is transformed into a java project
> - a special project named Jboss is containing Embeddable EJB 3.0 with subdirectories lib/ and conf/
> Case #1
> The workspace is located on my disk at the following place : "D:/EJB3Examples"
> The example microcontainer-deployment is working perfectly
> Case #2
> I moved the workspace to the following place : "D:/Projects/Java/Eclipse3/EJB3Examples"
> The example microcontainer-deployment is crashing.
> WARN 30-08 01:02:38,906 (JBossEntityResolver.java:getLocalEntityName:201) -Entity is not registered, publicId=null systemId=file:/D:/Projects/Java/Eclipse3/EJB3Examples/jboss/conf/bean-deployer_1_0.xsd
> WARN 30-08 01:02:38,953 (SaxJBossXBParser.java:warning:226) -schema_reference.4: Failed to read schema document 'bean-deployer_1_0.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. @ file:/D:/Projects/Java/Eclipse3/EJB3Examples/jboss/conf/embedded-jboss-beans.xml[5,45]
> WARN 30-08 01:02:41,062 (JBossEntityResolver.java:getLocalEntityName:201) -Entity is not registered, publicId=null systemId=file:/D:/Projects/Java/Eclipse3/EJB3Examples/microcontainer-deployment/conf/bean-deployer_1_0.xsd
> WARN 30-08 01:02:41,062 (SaxJBossXBParser.java:warning:226) -schema_reference.4: Failed to read schema document 'bean-deployer_1_0.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. @ file:/D:/Projects/Java/Eclipse3/EJB3Examples/microcontainer-deployment/conf/ejb3-deployment.xml[5,45]
> ERROR 30-08 01:02:45,609 (EjbTimerUtil.java:getTimerService:43) -Unable to initialize timer service
> ----------------------------------------------------------
> Exception in thread "main" javax.ejb.EJBException: null; CausedByException is:
> Unknown entity: org.jboss.tutorial.mcdeploy.Customer
> at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:46)
> at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:70)
> at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:134)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:61)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:39)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:63)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:91)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:152)
> at org.jboss.ejb3.stateless.StatelessLocalProxy.invoke(StatelessLocalProxy.java:60)
> at $Proxy11.createCustomer(Unknown Source)
> at org.jboss.tutorial.mcdeploy.Main.main(Main.java:32)
> java.lang.IllegalArgumentException: Unknown entity: org.jboss.tutorial.mcdeploy.Customer
> at org.hibernate.ejb.AbstractEntityManagerImpl.persist(AbstractEntityManagerImpl.java:133)
> at org.jboss.ejb3.entity.InjectedEntityManager.persist(InjectedEntityManager.java:97)
> at org.jboss.tutorial.mcdeploy.CustomerDAOBean.createCustomer(CustomerDAOBean.java:28)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
> at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:32)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:66)
> at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:134)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:61)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:39)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:63)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:91)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:152)
> at org.jboss.ejb3.stateless.StatelessLocalProxy.invoke(StatelessLocalProxy.java:60)
> at $Proxy11.createCustomer(Unknown Source)
> at org.jboss.tutorial.mcdeploy.Main.main(Main.java:32)
> Case #3
> I have copied the workspace to the following directory "D:\Projects\EJB3Examples"
> It works fine
> Case #4
> I have copied the workspace to the following directory "D:\Projects\Java\EJB3Examples"
> It works fine
> Case #5
> I have copied the workspace to the following directory "D:\Projects\Java\Eclips3\EJB3Examples"
> Without the "e" for eclips3. It works fine
> Case #5
> As soon as I rename the directory Eclips3 into Eclipse3, it crashes ... ?!?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (HIBERNATE-123) Cannot install hibernate tool in eclipse Helios because of conflicting dependency.
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/HIBERNATE-123?page=com.atlassian.jira.plu... ]
Max Rydahl Andersen closed HIBERNATE-123.
-----------------------------------------
Resolution: Rejected
the error indicates user have cross updatestreams somehow. i.e. mixed helios with juno or similar.
closing and suggest to open bugs in JBIDE if issue persists on newer versions.
> Cannot install hibernate tool in eclipse Helios because of conflicting dependency.
> ----------------------------------------------------------------------------------
>
> Key: HIBERNATE-123
> URL: https://issues.jboss.org/browse/HIBERNATE-123
> Project: Hibernate Integration
> Issue Type: Bug
> Environment: Eclipse Java EE IDE for Web Developers (Helios Release, Build id: 20100617-1415)
> Jboss Update site : http://download.jboss.org/jbosstools/updates/JBossTools-3.1.1.GA
> Reporter: Alexis Morillo
> Assignee: Steve Ebersole
>
> Get the error message :
> Cannot complete the install because of a conflicting dependency.
> Software being installed: Hibernate Tools 3.3.1.v201006011046R-H111-GA (org.hibernate.eclipse.feature.feature.group 3.3.1.v201006011046R-H111-GA)
> Software currently installed: Eclipse IDE for Java EE Developers 1.3.0.20100617-0521 (epp.package.jee 1.3.0.20100617-0521)
> Only one of the following can be installed at once:
> JavaServer Faces Tools - Common UI 1.2.0.v20100329 (org.eclipse.jst.jsf.common.ui 1.2.0.v20100329)
> JavaServer Faces Tools - Common UI 1.1.1.v20081209 (org.eclipse.jst.jsf.common.ui 1.1.1.v20081209)
> Only one of the following can be installed at once:
> Common Frameworks 1.2.0.v201003040800 (org.eclipse.wst.common.frameworks 1.2.0.v201003040800)
> Common Frameworks 1.1.300.v200904160730 (org.eclipse.wst.common.frameworks 1.1.300.v200904160730)
> Cannot satisfy dependency:
> From: Eclipse IDE for Java EE Developers 1.3.0.20100617-0521 (epp.package.jee 1.3.0.20100617-0521)
> To: org.eclipse.epp.package.jee.feature.feature.group [1.3.0.20100617-0521]
> Cannot satisfy dependency:
> From: Java EE IDE Feature 1.3.0.20100617-0521 (org.eclipse.epp.package.jee.feature.feature.group 1.3.0.20100617-0521)
> To: org.eclipse.jsf.feature.feature.group 0.0.0
> Cannot satisfy dependency:
> From: Java EE IDE Feature 1.3.0.20100617-0521 (org.eclipse.epp.package.jee.feature.feature.group 1.3.0.20100617-0521)
> To: org.eclipse.jst.web_ui.feature.feature.group 0.0.0
> Cannot satisfy dependency:
> From: Dali Java Persistence Tools - Core 2.2.1.v200908270220 (org.eclipse.jpt.core 2.2.1.v200908270220)
> To: bundle org.eclipse.wst.common.frameworks [1.1.200,1.2.0)
> Cannot satisfy dependency:
> From: JavaServer Faces Tools (JSF) Project 3.2.0.v20100526-7E7I-F9JgLWLMBYy3114 (org.eclipse.jsf.feature.feature.group 3.2.0.v20100526-7E7I-F9JgLWLMBYy3114)
> To: org.eclipse.jst.jsf.common.ui [1.2.0.v20100329]
> Cannot satisfy dependency:
> From: Common JST UI Plug-in 1.0.0.v201005270700 (org.eclipse.jst.common.ui 1.0.0.v201005270700)
> To: bundle org.eclipse.wst.common.frameworks 1.2.0
> Cannot satisfy dependency:
> From: JST Web UI 3.1.1.v200908121609-7E77FBfDlwYa_9sdy2q77doi14gl (org.eclipse.jst.web_ui.feature.feature.group 3.1.1.v200908121609-7E77FBfDlwYa_9sdy2q77doi14gl)
> To: org.eclipse.jst.jsf.common.ui [1.1.1.v20081209]
> Cannot satisfy dependency:
> From: JST Web UI 3.1.1.v200908121609-7E77FBiDlwYcICNdz-5z-9PGqZCy (org.eclipse.jst.web_ui.feature.feature.group 3.1.1.v200908121609-7E77FBiDlwYcICNdz-5z-9PGqZCy)
> To: org.eclipse.jst.jsf.common.ui [1.1.1.v20081209]
> Cannot satisfy dependency:
> From: JST Web UI 3.2.0.v201005250611-7F77FJJC25Skdw1pheuO_q6p-Idh (org.eclipse.jst.web_ui.feature.feature.group 3.2.0.v201005250611-7F77FJJC25Skdw1pheuO_q6p-Idh)
> To: org.eclipse.jst.common.ui [1.0.0.v201005270700]
> Cannot satisfy dependency:
> From: Hibernate Tools 3.3.1.v201006011046R-H111-GA (org.hibernate.eclipse.feature.feature.group 3.3.1.v201006011046R-H111-GA)
> To: org.jboss.tools.hibernate.jpt.core [3.3.1.v201006011046R-H111-GA]
> Cannot satisfy dependency:
> From: Hibernate Jdt Core 3.3.1.v201006011046R-H111-GA (org.jboss.tools.hibernate.jpt.core 3.3.1.v201006011046R-H111-GA)
> To: bundle org.eclipse.jpt.core [2.2.0,2.2.2)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (HIBERNATE-123) Cannot install hibernate tool in eclipse Helios because of conflicting dependency.
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/HIBERNATE-123?page=com.atlassian.jira.plu... ]
Max Rydahl Andersen commented on HIBERNATE-123:
-----------------------------------------------
The Hibernate Tools part of JBoss Tools / Red Hat JBoss Developer Studio has its issue tracker here (project = JBIDE, component = hibernate):
https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20compon...
> Cannot install hibernate tool in eclipse Helios because of conflicting dependency.
> ----------------------------------------------------------------------------------
>
> Key: HIBERNATE-123
> URL: https://issues.jboss.org/browse/HIBERNATE-123
> Project: Hibernate Integration
> Issue Type: Bug
> Environment: Eclipse Java EE IDE for Web Developers (Helios Release, Build id: 20100617-1415)
> Jboss Update site : http://download.jboss.org/jbosstools/updates/JBossTools-3.1.1.GA
> Reporter: Alexis Morillo
> Assignee: Steve Ebersole
>
> Get the error message :
> Cannot complete the install because of a conflicting dependency.
> Software being installed: Hibernate Tools 3.3.1.v201006011046R-H111-GA (org.hibernate.eclipse.feature.feature.group 3.3.1.v201006011046R-H111-GA)
> Software currently installed: Eclipse IDE for Java EE Developers 1.3.0.20100617-0521 (epp.package.jee 1.3.0.20100617-0521)
> Only one of the following can be installed at once:
> JavaServer Faces Tools - Common UI 1.2.0.v20100329 (org.eclipse.jst.jsf.common.ui 1.2.0.v20100329)
> JavaServer Faces Tools - Common UI 1.1.1.v20081209 (org.eclipse.jst.jsf.common.ui 1.1.1.v20081209)
> Only one of the following can be installed at once:
> Common Frameworks 1.2.0.v201003040800 (org.eclipse.wst.common.frameworks 1.2.0.v201003040800)
> Common Frameworks 1.1.300.v200904160730 (org.eclipse.wst.common.frameworks 1.1.300.v200904160730)
> Cannot satisfy dependency:
> From: Eclipse IDE for Java EE Developers 1.3.0.20100617-0521 (epp.package.jee 1.3.0.20100617-0521)
> To: org.eclipse.epp.package.jee.feature.feature.group [1.3.0.20100617-0521]
> Cannot satisfy dependency:
> From: Java EE IDE Feature 1.3.0.20100617-0521 (org.eclipse.epp.package.jee.feature.feature.group 1.3.0.20100617-0521)
> To: org.eclipse.jsf.feature.feature.group 0.0.0
> Cannot satisfy dependency:
> From: Java EE IDE Feature 1.3.0.20100617-0521 (org.eclipse.epp.package.jee.feature.feature.group 1.3.0.20100617-0521)
> To: org.eclipse.jst.web_ui.feature.feature.group 0.0.0
> Cannot satisfy dependency:
> From: Dali Java Persistence Tools - Core 2.2.1.v200908270220 (org.eclipse.jpt.core 2.2.1.v200908270220)
> To: bundle org.eclipse.wst.common.frameworks [1.1.200,1.2.0)
> Cannot satisfy dependency:
> From: JavaServer Faces Tools (JSF) Project 3.2.0.v20100526-7E7I-F9JgLWLMBYy3114 (org.eclipse.jsf.feature.feature.group 3.2.0.v20100526-7E7I-F9JgLWLMBYy3114)
> To: org.eclipse.jst.jsf.common.ui [1.2.0.v20100329]
> Cannot satisfy dependency:
> From: Common JST UI Plug-in 1.0.0.v201005270700 (org.eclipse.jst.common.ui 1.0.0.v201005270700)
> To: bundle org.eclipse.wst.common.frameworks 1.2.0
> Cannot satisfy dependency:
> From: JST Web UI 3.1.1.v200908121609-7E77FBfDlwYa_9sdy2q77doi14gl (org.eclipse.jst.web_ui.feature.feature.group 3.1.1.v200908121609-7E77FBfDlwYa_9sdy2q77doi14gl)
> To: org.eclipse.jst.jsf.common.ui [1.1.1.v20081209]
> Cannot satisfy dependency:
> From: JST Web UI 3.1.1.v200908121609-7E77FBiDlwYcICNdz-5z-9PGqZCy (org.eclipse.jst.web_ui.feature.feature.group 3.1.1.v200908121609-7E77FBiDlwYcICNdz-5z-9PGqZCy)
> To: org.eclipse.jst.jsf.common.ui [1.1.1.v20081209]
> Cannot satisfy dependency:
> From: JST Web UI 3.2.0.v201005250611-7F77FJJC25Skdw1pheuO_q6p-Idh (org.eclipse.jst.web_ui.feature.feature.group 3.2.0.v201005250611-7F77FJJC25Skdw1pheuO_q6p-Idh)
> To: org.eclipse.jst.common.ui [1.0.0.v201005270700]
> Cannot satisfy dependency:
> From: Hibernate Tools 3.3.1.v201006011046R-H111-GA (org.hibernate.eclipse.feature.feature.group 3.3.1.v201006011046R-H111-GA)
> To: org.jboss.tools.hibernate.jpt.core [3.3.1.v201006011046R-H111-GA]
> Cannot satisfy dependency:
> From: Hibernate Jdt Core 3.3.1.v201006011046R-H111-GA (org.jboss.tools.hibernate.jpt.core 3.3.1.v201006011046R-H111-GA)
> To: bundle org.eclipse.jpt.core [2.2.0,2.2.2)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (HIBERNATE-130) Exporting schema using HibernateTool task
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/HIBERNATE-130?page=com.atlassian.jira.plu... ]
Max Rydahl Andersen commented on HIBERNATE-130:
-----------------------------------------------
The Hibernate Tools part of JBoss Tools / Red Hat JBoss Developer Studio has its issue tracker here (project = JBIDE, component = hibernate):
https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20compon...
> Exporting schema using HibernateTool task
> -----------------------------------------
>
> Key: HIBERNATE-130
> URL: https://issues.jboss.org/browse/HIBERNATE-130
> Project: Hibernate Integration
> Issue Type: Feature Request
> Reporter: Dhana kumar
> Assignee: Steve Ebersole
>
> Hi,
> I have a question on exporting schema using HibernateTool task, the below annotations are not read and exported schema doesnt have the expected changes.. look at the below.. the size goes default to 255 instead of 30, how to achieve this, I dont want to specify the @Column size there, instead i am using, javax validation api..
> pls help.
> @NotNull
> @Size(min = 1, max = 30)
> @Column(name = "C_LAST_NAME")
> private String lastName;
> create table JpaHibernate.PUBLIC.T_CUSTOMER (
> C_ID bigint not null,
> C_FIRST_NAME varchar(255),
> C_LAST_NAME varchar(255),
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (WFLY-5710) AS doesn't compile with oracle java 1.8.0_25
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-5710?page=com.atlassian.jira.plugin.... ]
Stuart Douglas resolved WFLY-5710.
----------------------------------
Resolution: Rejected
This looks like a bug in the compiler, not a problem with Wildfly
> AS doesn't compile with oracle java 1.8.0_25
> --------------------------------------------
>
> Key: WFLY-5710
> URL: https://issues.jboss.org/browse/WFLY-5710
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.0.0.CR4
> Reporter: Martin Choma
> Priority: Minor
>
> Adding this issue mainly for reference as on latest java 1.8.0_66 works fine again.
> Whole affected java version is
> {code}
> java version "1.8.0_25"
> Java(TM) SE Runtime Environment (build 1.8.0_25-b17)
> Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)
> {code}
> Whole compilation error is
> {code}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project wildfly-clustering-common: Compilation failure
> [ERROR] /home/mchoma/workspace/git-repositories/wildfly/clustering/common/src/main/java/org/jboss/as/clustering/controller/ExecutionHandler.java:[54,48] no suitable method found for collect(java.util.stream.Collector<E,capture#1 of ?,java.util.Map<java.lang.String,java.lang.Object>>)
> [ERROR] method java.util.stream.Stream.<R>collect(java.util.function.Supplier<R>,java.util.function.BiConsumer<R,? super capture#2 of ? extends E>,java.util.function.BiConsumer<R,R>) is not applicable
> [ERROR] (cannot infer type-variable(s) R
> [ERROR] (actual and formal argument lists differ in length))
> [ERROR] method java.util.stream.Stream.<R,A>collect(java.util.stream.Collector<? super capture#2 of ? extends E,A,R>) is not applicable
> [ERROR] (cannot infer type-variable(s) capture#3 of ?,T,K,U,T
> [ERROR] (argument mismatch; java.util.function.Function<capture#2 of ? extends E,capture#2 of ? extends E> cannot be converted to java.util.function.Function<? super capture#2 of ? extends E,? extends capture#2 of ? extends E>))
> {code}
> Works ok on
> {code}
> java version "1.8.0_05"
> Java(TM) SE Runtime Environment (build 1.8.0_05-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.5-b02, mixed mode)
> {code}
> {code}
> java version "1.8.0_66"
> Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
> Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (DROOLS-985) Loaded wrong version's jar file after restarting kie-server.
by hoon lee (JIRA)
[ https://issues.jboss.org/browse/DROOLS-985?page=com.atlassian.jira.plugin... ]
hoon lee commented on DROOLS-985:
---------------------------------
MP4 for reproduce. : https://youtu.be/0aG5orOJN28
> Loaded wrong version's jar file after restarting kie-server.
> ------------------------------------------------------------
>
> Key: DROOLS-985
> URL: https://issues.jboss.org/browse/DROOLS-985
> Project: Drools
> Issue Type: Bug
> Components: kie server
> Affects Versions: 6.3.0.Final
> Environment: CentOS
> WAS : wildfly-8.2.1.Final
> Drools : 6.3.0.Final
> Reporter: hoon lee
> Assignee: Edson Tirelli
> Fix For: 6.3.0.Final
>
> Attachments: drools-simple-1.0.0.jar, drools-simple-1.0.1.jar
>
>
> 1. Start unmanaged kie-server
> 2. Create a container
> name : test
> kjar : test:test-rule:1.0.0
> 3. update & release (kjar)
> name : test
> kjar : test:test-rule:1.0.1
> 4. Restart unmanaged kie-server
> * Issue
> => Container 'test' is automatically started and load a 'test-rule:1.0.0' (not 1.0.1)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (DROOLS-985) Loaded wrong version's jar file after restarting kie-server.
by hoon lee (JIRA)
[ https://issues.jboss.org/browse/DROOLS-985?page=com.atlassian.jira.plugin... ]
hoon lee updated DROOLS-985:
----------------------------
Attachment: drools-simple-1.0.0.jar
drools-simple-1.0.1.jar
> Loaded wrong version's jar file after restarting kie-server.
> ------------------------------------------------------------
>
> Key: DROOLS-985
> URL: https://issues.jboss.org/browse/DROOLS-985
> Project: Drools
> Issue Type: Bug
> Components: kie server
> Affects Versions: 6.3.0.Final
> Environment: CentOS
> WAS : wildfly-8.2.1.Final
> Drools : 6.3.0.Final
> Reporter: hoon lee
> Assignee: Edson Tirelli
> Fix For: 6.3.0.Final
>
> Attachments: drools-simple-1.0.0.jar, drools-simple-1.0.1.jar
>
>
> 1. Start unmanaged kie-server
> 2. Create a container
> name : test
> kjar : test:test-rule:1.0.0
> 3. update & release (kjar)
> name : test
> kjar : test:test-rule:1.0.1
> 4. Restart unmanaged kie-server
> * Issue
> => Container 'test' is automatically started and load a 'test-rule:1.0.0' (not 1.0.1)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (DROOLS-985) Loaded wrong version's jar file after restarting kie-server.
by hoon lee (JIRA)
[ https://issues.jboss.org/browse/DROOLS-985?page=com.atlassian.jira.plugin... ]
hoon lee reopened DROOLS-985:
-----------------------------
I attached jar file and mp4 for reproduce. Please check this file.
> Loaded wrong version's jar file after restarting kie-server.
> ------------------------------------------------------------
>
> Key: DROOLS-985
> URL: https://issues.jboss.org/browse/DROOLS-985
> Project: Drools
> Issue Type: Bug
> Components: kie server
> Affects Versions: 6.3.0.Final
> Environment: CentOS
> WAS : wildfly-8.2.1.Final
> Drools : 6.3.0.Final
> Reporter: hoon lee
> Assignee: Edson Tirelli
> Fix For: 6.3.0.Final
>
>
> 1. Start unmanaged kie-server
> 2. Create a container
> name : test
> kjar : test:test-rule:1.0.0
> 3. update & release (kjar)
> name : test
> kjar : test:test-rule:1.0.1
> 4. Restart unmanaged kie-server
> * Issue
> => Container 'test' is automatically started and load a 'test-rule:1.0.0' (not 1.0.1)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (WFLY-5720) CDI deployment problems on web application runtime name not ending in .war
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-5720?page=com.atlassian.jira.plugin.... ]
Stuart Douglas resolved WFLY-5720.
----------------------------------
Resolution: Rejected
Runtime name is used to determine the type. If it is a web application it must end in .war
> CDI deployment problems on web application runtime name not ending in .war
> --------------------------------------------------------------------------
>
> Key: WFLY-5720
> URL: https://issues.jboss.org/browse/WFLY-5720
> Project: WildFly
> Issue Type: Bug
> Environment: Wildfly 10CR4
> Reporter: Guillermo González de Agüero
> Assignee: Jason Greene
> Attachments: cdi-test.war
>
>
> CDI complains when deploying a war setting the runtime name without extension.
> The following is logged with the attached application:
> {code:java}
> 2015-11-22 21:55:59,830 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "cdi-test-1.0-SNAPSHOT.war" (runtime-name: "cdi-test")
> 2015-11-22 21:55:59,861 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Processing weld deployment cdi-test
> 2015-11-22 21:55:59,882 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0006: Starting Services for CDI deployment: cdi-test
> 2015-11-22 21:55:59,888 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0009: Starting weld service for deployment cdi-test
> 2015-11-22 21:55:59,955 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 1) WELD-000119: Not generating any bean definitions from com.example.BeanTest because of underlying class loading error: Type com.example.BeanTest from [Module "deployment.cdi-test:main" from Service Module Loader] not found. If this is unexpected, enable DEBUG logging to see the full error.
> 2015-11-22 21:56:00,243 INFO [org.jboss.as.server] (XNIO-1 task-2) WFLYSRV0010: Deployed "cdi-test-1.0-SNAPSHOT.war" (runtime-name : "cdi-test")
> {code}
> Application is apparently deployed, but doesn't work. I'm not sure this is a bug in Wildfly or in Weld subsystem or even expected behaviour, since every type of file is allowed to be deployed. Is the extension used to determine the type of deployment?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months