June 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17717) Validation of @Path annotation with invalid argument cause error

by Radoslav Rábara (JIRA)

Radoslav Rábara created JBIDE-17717: --------------------------------------- Summary: Validation of @Path annotation with invalid argument cause error Key: JBIDE-17717 URL: https://issues.jboss.org/browse/JBIDE-17717 Project: Tools (JBoss Tools) Issue Type: Bug Components: webservices Affects Versions: 4.2.0.Beta3 Environment: JBoss WebServices Tools 1.7.0.Beta3-v20140628-0157-B555 Reporter: Radoslav Rábara Priority: Critical Fix For: 4.2.0.Beta3 An error occurs when the argument of the path annotation is invalid. It occurs not only when the file is saved but also during typing. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17668) JBoss 4.2.3 Hot Deployment does not work (worked with 4.1.x)

by Nero M (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17668?page=com.atlassian.jira.plugi... ] Nero M commented on JBIDE-17668: -------------------------------- Just FYI : Ive also tryed to use the context menu "incremental deploy" method to redeploy, but this also results in JBoss 4.2.3 trying to redeploy the ear - which of course a.) Is very slow and b.) sometimes simply doesnt work especially if there are EAR-dependency The desired behaviour should be that only the changed file is being redeployed without touching the EAR/WAR folders or doing any communication to JBoss. Ive found a workaround for now which is to set the following in jboss-service.xml <attribute name="ScanEnabled">false</attribute> However this is not very desired, because each time i change a small file , the workers redeploy very slowly, the change sometimes is visibly only 2minutes later. (Note: The EARs we have are very big) > JBoss 4.2.3 Hot Deployment does not work (worked with 4.1.x) > ------------------------------------------------------------ > > Key: JBIDE-17668 > URL: https://issues.jboss.org/browse/JBIDE-17668 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Environment: Win7 x64, Eclipse Luna 4.4 RC3, JBoss 4.2.3GA > Reporter: Nero M > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.2.0.Beta3 > > Attachments: duplicate-scanner.png > > > When i start JBoss 4.2.3GA i get this: > org.jboss.deployment.DeploymentException: Trying to install an already registered mbean: jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3 > at org.jboss.system.ServiceCreator.install(ServiceCreator.java:103) > Then when i change any file (just an xhtml for instance) The Server shuts down. Instead it should just hot-deploy that file like it did with Kepler + AS Tools 4.1. But here it seems a full deployment is being done (Not just the file) resulting in a Server reboot > 12:09:29,452 INFO [EARDeployer] Undeploying J2EE application, destroy step: file:/C:/server/jboss/............ear > 12:09:29,452 INFO [EARDeployer] Undeployed J2EE application: file:/C:/server/jboss/..........................ear > Thanks for any help :( If this is not fixed, we cannot move to Luna. unfortunately i cant move to a different application server -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17642) eap 6.2 defaults to java 6 even though java 7 is available

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17642?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17642. --------------------------------- Assignee: Rob Stryker Fix Version/s: 4.2.0.Beta3 Resolution: Duplicate Issue This is a duplicate of https://issues.jboss.org/browse/JBIDE-17646. Users can now customize their execution environment. > eap 6.2 defaults to java 6 even though java 7 is available > ---------------------------------------------------------- > > Key: JBIDE-17642 > URL: https://issues.jboss.org/browse/JBIDE-17642 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.2.0.Beta3 > > > creating EAP 6.2+ server results in it using Java 6 when I have this setup in JRE: > http://screencast.com/t/mvlXDAFv5 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17668) JBoss 4.2.3 Hot Deployment does not work (worked with 4.1.x)

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17668?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-17668: --------------------------------------- [~rob.stryker] what about the incremental deployment? That should work, right? > JBoss 4.2.3 Hot Deployment does not work (worked with 4.1.x) > ------------------------------------------------------------ > > Key: JBIDE-17668 > URL: https://issues.jboss.org/browse/JBIDE-17668 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Environment: Win7 x64, Eclipse Luna 4.4 RC3, JBoss 4.2.3GA > Reporter: Nero M > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.2.0.Beta3 > > Attachments: duplicate-scanner.png > > > When i start JBoss 4.2.3GA i get this: > org.jboss.deployment.DeploymentException: Trying to install an already registered mbean: jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3 > at org.jboss.system.ServiceCreator.install(ServiceCreator.java:103) > Then when i change any file (just an xhtml for instance) The Server shuts down. Instead it should just hot-deploy that file like it did with Kepler + AS Tools 4.1. But here it seems a full deployment is being done (Not just the file) resulting in a Server reboot > 12:09:29,452 INFO [EARDeployer] Undeploying J2EE application, destroy step: file:/C:/server/jboss/............ear > 12:09:29,452 INFO [EARDeployer] Undeployed J2EE application: file:/C:/server/jboss/..........................ear > Thanks for any help :( If this is not fixed, we cannot move to Luna. unfortunately i cant move to a different application server -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17668) JBoss 4.2.3 Hot Deployment does not work (worked with 4.1.x)

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17668?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17668: ------------------------------------- https://github.com/jbosstools/jbosstools-server/pull/236 It seems the wrong separators were in use because of a call to IPath.toString() in our local path handler. IPath.toString() uses the internal eclispe separator. This led to an equivilent path being added to deployment scanners rather than being recognized as a duplicate. > JBoss 4.2.3 Hot Deployment does not work (worked with 4.1.x) > ------------------------------------------------------------ > > Key: JBIDE-17668 > URL: https://issues.jboss.org/browse/JBIDE-17668 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Environment: Win7 x64, Eclipse Luna 4.4 RC3, JBoss 4.2.3GA > Reporter: Nero M > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.2.0.Beta3 > > Attachments: duplicate-scanner.png > > > When i start JBoss 4.2.3GA i get this: > org.jboss.deployment.DeploymentException: Trying to install an already registered mbean: jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3 > at org.jboss.system.ServiceCreator.install(ServiceCreator.java:103) > Then when i change any file (just an xhtml for instance) The Server shuts down. Instead it should just hot-deploy that file like it did with Kepler + AS Tools 4.1. But here it seems a full deployment is being done (Not just the file) resulting in a Server reboot > 12:09:29,452 INFO [EARDeployer] Undeploying J2EE application, destroy step: file:/C:/server/jboss/............ear > 12:09:29,452 INFO [EARDeployer] Undeployed J2EE application: file:/C:/server/jboss/..........................ear > Thanks for any help :( If this is not fixed, we cannot move to Luna. unfortunately i cant move to a different application server -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17716) An error "TypeParameter cannot be cast to IType" occurs when quick fix is used

by Radoslav Rábara (JIRA)

Radoslav Rábara created JBIDE-17716: --------------------------------------- Summary: An error "TypeParameter cannot be cast to IType" occurs when quick fix is used Key: JBIDE-17716 URL: https://issues.jboss.org/browse/JBIDE-17716 Project: Tools (JBoss Tools) Issue Type: Bug Components: webservices Affects Versions: 4.2.0.Beta3 Reporter: Radoslav Rábara Fix For: 4.2.0.Beta3 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17713) ProjectExample definition content mutates every time an example is created

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17713?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-17713: -------------------------------- Description: Each ProjectExample instance, loaded from project example descriptors is mutated several times when actual exampled are created, such as https://github.com/jbosstools/jbosstools-central/blob/94cccaa18c185657c5c.... This prevents us from mixing for instance maven projects with non maven projects, since we lose all expected project names The example definition and the actual example set per the user choices should be split, using the concept of a working copy (similar to what is done for launchconfigurations or runtimes) was: Each ProjectExample instance, loaded from project example descriptors is mutated several times when actual exampled are created, such as https://github.com/jbosstools/jbosstools-central/blob/94cccaa18c185657c5c.... This prevents us from mixing for instance maven projects with non maven projects The example definition and the actual example set per the user choices should be split, using the concept of a working copy (similar to what is done for launchconfigurations or runtimes) > ProjectExample definition content mutates every time an example is created > -------------------------------------------------------------------------- > > Key: JBIDE-17713 > URL: https://issues.jboss.org/browse/JBIDE-17713 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 3.2.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.2.0.Beta3 > > > Each ProjectExample instance, loaded from project example descriptors is mutated several times when actual exampled are created, such as https://github.com/jbosstools/jbosstools-central/blob/94cccaa18c185657c5c.... > This prevents us from mixing for instance maven projects with non maven projects, since we lose all expected project names > The example definition and the actual example set per the user choices should be split, using the concept of a working copy (similar to what is done for launchconfigurations or runtimes) > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17715) JAX-RS metamodel failed to build/refresh due to StringIndexOutOfBoundsException

by Radoslav Rábara (JIRA)

Radoslav Rábara created JBIDE-17715: --------------------------------------- Summary: JAX-RS metamodel failed to build/refresh due to StringIndexOutOfBoundsException Key: JBIDE-17715 URL: https://issues.jboss.org/browse/JBIDE-17715 Project: Tools (JBoss Tools) Issue Type: Bug Components: webservices Affects Versions: 4.2.0.Beta3 Environment: JBoss WebServices Tools 1.7.0.Beta3-v20140628-0157-B555 Reporter: Radoslav Rábara Fix For: 4.2.0.Beta3 While editing bean class, an error occurred: "Failed to build or refresh the JAX-RS metamodel". {code} java.lang.StringIndexOutOfBoundsException: String index out of range: -9 at java.lang.String.substring(String.java:1911) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsEndpoint.getDisplayablePathTemplate(JaxrsEndpoint.java:446) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsEndpoint.refreshUriPathTemplate(JaxrsEndpoint.java:327) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsEndpoint.update(JaxrsEndpoint.java:234) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsElementChangedProcessorDelegate.processChange(JaxrsElementChangedProcessorDelegate.java:394) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsElementChangedProcessorDelegate.processEvent(JaxrsElementChangedProcessorDelegate.java:100) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processElementChange(JaxrsMetamodel.java:712) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.update(JaxrsMetamodel.java:734) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsJavaElement.updateAnnotation(JaxrsJavaElement.java:223) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processJavaAnnotationChange(JaxrsMetamodel.java:492) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processJavaElementChange(JaxrsMetamodel.java:421) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.run(JavaElementChangedBuildJob.java:75) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.execute(JavaElementChangedBuildJob.java:44) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedListener.elementChanged(JavaElementChangedListener.java:69) at org.eclipse.jdt.internal.core.DeltaProcessor$4.run(DeltaProcessor.java:1695) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.jdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1685) at org.eclipse.jdt.internal.core.DeltaProcessor.fireReconcileDelta(DeltaProcessor.java:1537) at org.eclipse.jdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1496) at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:770) at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:789) at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1247) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:126) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.access$0(JavaReconcilingStrategy.java:108) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy$1.run(JavaReconcilingStrategy.java:89) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:87) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:151) at org.eclipse.jdt.internal.ui.text.CompositeReconcilingStrategy.reconcile(CompositeReconcilingStrategy.java:86) at org.eclipse.jdt.internal.ui.text.JavaCompositeReconcilingStrategy.reconcile(JavaCompositeReconcilingStrategy.java:104) at org.eclipse.jface.text.reconciler.MonoReconciler.process(MonoReconciler.java:77) at org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:206) {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17714) Cyclic dependency between Project Examples and Maven Project Examples

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17714?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-17714: -------------------------------- Fix Version/s: 4.2.0.Beta3 > Cyclic dependency between Project Examples and Maven Project Examples > --------------------------------------------------------------------- > > Key: JBIDE-17714 > URL: https://issues.jboss.org/browse/JBIDE-17714 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, project-examples > Affects Versions: 3.2.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.2.0.Beta3 > > > While working on JBIDE-17713, I noticed the Project Example tests failed because they require the Maven Project Examples to be built. But Maven Project Examples depends on Project Examples in the first place. This creates a Cyclic dependency between the Maven and Examples components. > Solution is to move the Maven Project Examples to the Project Examples component -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17714) Cyclic dependency between Project Examples and Maven Project Examples

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17714?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-17714: ----------------------------------- Assignee: Fred Bricon > Cyclic dependency between Project Examples and Maven Project Examples > --------------------------------------------------------------------- > > Key: JBIDE-17714 > URL: https://issues.jboss.org/browse/JBIDE-17714 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, project-examples > Affects Versions: 3.2.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > > While working on JBIDE-17713, I noticed the Project Example tests failed because they require the Maven Project Examples to be built. But Maven Project Examples depends on Project Examples in the first place. This creates a Cyclic dependency between the Maven and Examples components. > Solution is to move the Maven Project Examples to the Project Examples component -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2014