[JBoss JIRA] (JBIDE-18710) Invalid generated code in JAX-RS Endpoint
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-18710:
-------------------------------------
Summary: Invalid generated code in JAX-RS Endpoint
Key: JBIDE-18710
URL: https://issues.jboss.org/browse/JBIDE-18710
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Affects Versions: 4.2.0.Final
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 4.2.1.Final, 4.3.0.Alpha1
The generated code in the 'create' method contains something like this:
{code}
return Response.created(
UriBuilder.fromResource(Session.class)
.path(String.valueOf(session.getId())).build()).build();
{code}
but the {{Session.class}} should be {{SessionEndpoint.class}} since it must be the resource class annotated with {{@Path}}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18706) NPE wrt JPA when creating a new Java EE7/Maven project
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18706?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-18706:
-------------------------------------
Randomly occurring error. Must be a race condition :-/
> NPE wrt JPA when creating a new Java EE7/Maven project
> ------------------------------------------------------
>
> Key: JBIDE-18706
> URL: https://issues.jboss.org/browse/JBIDE-18706
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate, maven
> Affects Versions: 4.2.0.Final
> Reporter: Xavier Coulon
>
> I got the following error when creating a new Maven project using the 'wildfly-javaee7-blank-archetype' archetype:
> {code}
> java.lang.NullPointerException
> at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.defaultResourceLocation(JpaFacetInstallDelegate.java:123)
> at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.createPersistenceXml(JpaFacetInstallDelegate.java:107)
> at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.createProjectXml(JpaFacetInstallDelegate.java:100)
> at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.execute_(JpaFacetInstallDelegate.java:61)
> at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetActionDelegate.execute(JpaFacetActionDelegate.java:35)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1477)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:441)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1181)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1117)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:324)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configureFacets(JpaProjectConfigurator.java:154)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configure(JpaProjectConfigurator.java:109)
> at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:120)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:477)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:470)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:250)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:163)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:109)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1348)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:133)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProjects0(ProjectConfigurationManager.java:789)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$5.call(ProjectConfigurationManager.java:719)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$5.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1348)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProjects(ProjectConfigurationManager.java:717)
> at org.eclipse.m2e.core.ui.internal.wizards.MavenProjectWizard$5.doCreateMavenProjects(MavenProjectWizard.java:244)
> at org.eclipse.m2e.core.ui.internal.wizards.AbstactCreateMavenProjectJob$1.doCreateMavenProjects(AbstactCreateMavenProjectJob.java:46)
> at org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectsOperation.run(AbstractCreateMavenProjectsOperation.java:62)
> at org.eclipse.m2e.core.ui.internal.wizards.AbstactCreateMavenProjectJob.runInWorkspace(AbstactCreateMavenProjectJob.java:50)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-16593) JBDS6 sets lower default memory settings for SOA server start than are defined in SOA run.conf
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16593?page=com.atlassian.jira.plugi... ]
Andrej Podhradsky commented on JBIDE-16593:
-------------------------------------------
JBDS 8 still supports SOA-P 5.x (the last one is SOA-P 5.3.1.GA) where the recommended memory settings (and also specified in run.conf) are
-Xms1303m -Xmx1303m -XX:MaxPermSize=256m
but JBDS 8 sets by default lower memory settings which means that customer needs to set the settings manually.
Note that this is not a problem of SOA-P 6 (now called FSW).
> JBDS6 sets lower default memory settings for SOA server start than are defined in SOA run.conf
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-16593
> URL: https://issues.jboss.org/browse/JBIDE-16593
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Environment: Version: 5.0.2.GA
> Build id: v20130119-0035-H249-GA
> Build date: 20130119-0035
> http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.3.GA.soa-to...
> Reporter: Len DiMaggio
> Assignee: Rob Stryker
> Fix For: 4.2.x
>
>
> JBDS6:
> "-Dprogram.name=JBossTools: JBoss SOA 531_ER4 Runtime"
> -server -Xms256m -Xmx768m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true
> -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 "-Djava.endorsed.dirs=/jboss/local/SOA_servers/531_ER4/jboss-soa-p-5/jboss-as/lib/endorsed"
> SOA 5.3.1 run.conf:
> if [ "x$JAVA_OPTS" = "x" ]; then
> JAVA_OPTS="-Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.awt.headless=true -Dorg.apache.xml.dtm.DTMManager=org.apache.xml.dtm.ref.DTMManagerDefault -Dorg.jboss.net.protocol.file.useURI=false -Dorg.jboss.resolver.warning
> =true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsun.lang.ClassLoader.allowArraySyntax=true"
> fi
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18523) [JBDS 7.1.1] org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18523?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-18523:
--------------------------------
Affects Version/s: 4.1.2.Final
(was: 4.2.0.CR1)
> [JBDS 7.1.1] org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-18523
> URL: https://issues.jboss.org/browse/JBIDE-18523
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.2.Final
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.1.3.Final
>
>
> When working through JBIDE-16066 for the web services wizard, I discovered that EAP_61 is not included in the array provided by the ALL_JBOSS_RUNTIMES list in org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants. I can work around this on the WS side, but I would imagine that this has a broader impact to other tooling projects using the runtime framework
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18523) [JBDS 7.1.1] org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18523?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-18523:
--------------------------------
Fix Version/s: 4.1.3.Final
> [JBDS 7.1.1] org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-18523
> URL: https://issues.jboss.org/browse/JBIDE-18523
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.1.3.Final
>
>
> When working through JBIDE-16066 for the web services wizard, I discovered that EAP_61 is not included in the array provided by the ALL_JBOSS_RUNTIMES list in org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants. I can work around this on the WS side, but I would imagine that this has a broader impact to other tooling projects using the runtime framework
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18709) EAP alpha releases not require credentials; verify downloadRuntimes works
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-18709:
-----------------------------------
Summary: EAP alpha releases not require credentials; verify downloadRuntimes works
Key: JBIDE-18709
URL: https://issues.jboss.org/browse/JBIDE-18709
Project: Tools (JBoss Tools)
Issue Type: Task
Components: runtime-detection, server
Affects Versions: 4.2.0.Final, 4.2.1.Final, 4.3.0.Alpha1
Reporter: Rob Stryker
A new requirement by the EAP team is asking for anonymous downloads of alpha releases. If such url's made it into stacks.yaml it *could* break our recent release.
We'll need to verify that if such a new url made it into stacks, it wouldn't break our download runtimes at all.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18699) Angular.js is present in both supported and Early Access
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18699?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-18699:
-----------------------------------
Assignee: Max Rydahl Andersen
I tend to agree this is confusing.
The AngularJS connector in central only contains Ionic tooling, not the whole AngularJS IDE. That one is part of Early Access.
I'd prefer if we could disambiguate these, but my understanding is we needed to keep the same connector ids, in order to be able to upgrade from regular central to early access without seeing duplicates. [~maxandersen] knows more about this.
> Angular.js is present in both supported and Early Access
> --------------------------------------------------------
>
> Key: JBIDE-18699
> URL: https://issues.jboss.org/browse/JBIDE-18699
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.Final
> Environment: JBDS 8.0.0.GA
> Reporter: Karel Piwko
> Assignee: Max Rydahl Andersen
> Attachments: early-access.png, no-early-access.png
>
>
> If I click on enable early access in JBoss Central page Software/Update tab, Angular JS is in Early access.
> However, it is in supported as well. I guess only Arquillian should pop up in early access.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18707) FrameworkEvent ERROR
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18707?page=com.atlassian.jira.plugi... ]
Fred Bricon closed JBIDE-18707.
-------------------------------
Resolution: Duplicate Issue
Closing as duplicate of JBIDE-18681
> FrameworkEvent ERROR
> --------------------
>
> Key: JBIDE-18707
> URL: https://issues.jboss.org/browse/JBIDE-18707
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.Final
> Reporter: Xavier Coulon
>
> This error appeared in my Error Log after I exited JBDS 8.0.0.Final:
> {code}
> org.osgi.framework.BundleException: Exception in org.jboss.tools.central.JBossCentralActivator.stop() of bundle org.jboss.tools.central.
> at org.eclipse.osgi.internal.framework.BundleContextImpl.stop(BundleContextImpl.java:847)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.stopWorker0(EquinoxBundle.java:950)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.stopWorker(EquinoxBundle.java:324)
> at org.eclipse.osgi.container.Module.doStop(Module.java:626)
> at org.eclipse.osgi.container.Module.stop(Module.java:488)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.decStartLevel(ModuleContainer.java:1623)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1542)
> at org.eclipse.osgi.container.SystemModule.stopWorker(SystemModule.java:248)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule.stopWorker(EquinoxBundle.java:145)
> at org.eclipse.osgi.container.Module.doStop(Module.java:626)
> at org.eclipse.osgi.container.Module.stop(Module.java:488)
> at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:186)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:160)
> at java.lang.Thread.run(Thread.java:744)
> Caused by: org.eclipse.swt.SWTException: Invalid thread access
> at org.eclipse.swt.SWT.error(SWT.java:4441)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.SWT.error(SWT.java:4327)
> at org.eclipse.swt.widgets.Display.error(Display.java:1083)
> at org.eclipse.swt.widgets.Display.createDisplay(Display.java:840)
> at org.eclipse.swt.widgets.Display.create(Display.java:823)
> at org.eclipse.swt.graphics.Device.<init>(Device.java:130)
> at org.eclipse.swt.widgets.Display.<init>(Display.java:714)
> at org.eclipse.swt.widgets.Display.<init>(Display.java:705)
> at org.eclipse.swt.widgets.Display.getDefault(Display.java:1403)
> at org.jboss.tools.central.JBossCentralActivator.stop(JBossCentralActivator.java:215)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:827)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:1)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.stop(BundleContextImpl.java:820)
> ... 13 more
> Root exception:
> org.eclipse.swt.SWTException: Invalid thread access
> at org.eclipse.swt.SWT.error(SWT.java:4441)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.SWT.error(SWT.java:4327)
> at org.eclipse.swt.widgets.Display.error(Display.java:1083)
> at org.eclipse.swt.widgets.Display.createDisplay(Display.java:840)
> at org.eclipse.swt.widgets.Display.create(Display.java:823)
> at org.eclipse.swt.graphics.Device.<init>(Device.java:130)
> at org.eclipse.swt.widgets.Display.<init>(Display.java:714)
> at org.eclipse.swt.widgets.Display.<init>(Display.java:705)
> at org.eclipse.swt.widgets.Display.getDefault(Display.java:1403)
> at org.jboss.tools.central.JBossCentralActivator.stop(JBossCentralActivator.java:215)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:827)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:1)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.stop(BundleContextImpl.java:820)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.stopWorker0(EquinoxBundle.java:950)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.stopWorker(EquinoxBundle.java:324)
> at org.eclipse.osgi.container.Module.doStop(Module.java:626)
> at org.eclipse.osgi.container.Module.stop(Module.java:488)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.decStartLevel(ModuleContainer.java:1623)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1542)
> at org.eclipse.osgi.container.SystemModule.stopWorker(SystemModule.java:248)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule.stopWorker(EquinoxBundle.java:145)
> at org.eclipse.osgi.container.Module.doStop(Module.java:626)
> at org.eclipse.osgi.container.Module.stop(Module.java:488)
> at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:186)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:160)
> at java.lang.Thread.run(Thread.java:744)
> {code}
> Note: I exited JBDS after my laptop came back from a long week-end of hibernation, because I wanted to start using the IDE with a fresh JVM. Not sure if this can be related to the problem reported here, though.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months