[JBoss JIRA] (JBIDE-17735) JAX-RS Application wizard: double comments in generated class
by Radoslav Rábara (JIRA)
Radoslav Rábara created JBIDE-17735:
---------------------------------------
Summary: JAX-RS Application wizard: double comments in generated class
Key: JBIDE-17735
URL: https://issues.jboss.org/browse/JBIDE-17735
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Affects Versions: 4.2.0.Beta2
Reporter: Radoslav Rábara
Fix For: 4.2.0.Beta3
JAX-RS Application class looks quite unusual, when is generated using JAX-RS Application wizard with option generate comments into default package.
{code}
@ApplicationPath("/rest")
/**
*
*/
/**
* @author rrabara
*
*/
public class App extends Application {
}
{code}
When it is generated into user defined package, then there is just one java doc comment:
{code}
@ApplicationPath("/rest")
/**
* @author rrabara
*
*/
public class App extends Application {
}
{code}
However, shouldn't the comment be above the annotation? It seems that it's the preferred way (e.g. see examples http://docs.oracle.com/javase/tutorial/java/annotations/predefined.html)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17624) (un)checking Early Access while refreshing the connector logs an org.eclipse.swt.SWTException
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17624?page=com.atlassian.jira.plugi... ]
Rastislav Wagner commented on JBIDE-17624:
------------------------------------------
I was able to reproduce on OSX, but unable on ubuntu. Using nightly build.
> (un)checking Early Access while refreshing the connector logs an org.eclipse.swt.SWTException
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-17624
> URL: https://issues.jboss.org/browse/JBIDE-17624
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.Beta2
> Reporter: Fred Bricon
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.2.0.Beta3
>
>
> In Central > Software/Update page, (un)checking Early Access while refreshing the connector logs the following exception :
> {noformat}
> org.eclipse.swt.SWTException: Graphic is disposed
> 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.graphics.Image.getBounds(Image.java:1164)
> at org.eclipse.swt.widgets.Label.computeSize(Label.java:149)
> at org.eclipse.swt.layout.GridData.computeSize(GridData.java:491)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:221)
> at org.eclipse.swt.layout.GridLayout.computeSize(GridLayout.java:164)
> at org.eclipse.swt.widgets.Composite.computeSize(Composite.java:234)
> at org.eclipse.swt.layout.GridData.computeSize(GridData.java:491)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:221)
> at org.eclipse.swt.layout.GridLayout.computeSize(GridLayout.java:164)
> at org.eclipse.swt.widgets.Composite.computeSize(Composite.java:234)
> at org.eclipse.swt.layout.GridData.computeSize(GridData.java:491)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:221)
> at org.eclipse.swt.layout.GridLayout.computeSize(GridLayout.java:164)
> at org.eclipse.swt.widgets.Composite.computeSize(Composite.java:234)
> at org.eclipse.swt.layout.GridData.computeSize(GridData.java:491)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:221)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:197)
> at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1290)
> at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1276)
> at org.eclipse.swt.widgets.Composite.layout(Composite.java:665)
> at org.jboss.tools.central.editors.xpl.DiscoveryViewer.updateFilters(DiscoveryViewer.java:628)
> at org.jboss.tools.central.editors.SoftwarePage.handleEarlyAccessChanged(SoftwarePage.java:536)
> at org.jboss.tools.central.editors.SoftwarePage.access$8(SoftwarePage.java:486)
> at org.jboss.tools.central.editors.SoftwarePage$5.widgetSelected(SoftwarePage.java:229)
> {noformat}
> scrolledContents is checked for disposed state, but the error occurs within layout()
> {code}
> if (this.scrolledContents != null && !this.scrolledContents.isDisposed()) {
> this.scrolledContents.layout(true, true); //crashes here
> ...
> }
> {code}
> I don't know how we can prevent that
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17696) Enabling Maven Dependency Management job waits forever
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17696?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-17696:
--------------------------------
Fix Version/s: 4.2.x
> Enabling Maven Dependency Management job waits forever
> ------------------------------------------------------
>
> Key: JBIDE-17696
> URL: https://issues.jboss.org/browse/JBIDE-17696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.Beta2
> Environment: OpenJDK 1.7, 64b
> Ubuntu 12.04, 64b
> Reporter: Rastislav Wagner
> Fix For: 4.2.x
>
> Attachments: jstack1.out, jstack2.out, jstack_mvn.out, mvn.png, wait1.png, wait2.png
>
>
> I dont have exact steps to reproduce because this usually occurs after longer work. I'm testing various configurators (CDI/Seam/JAXRS..) using this scenario:
> 1. Create Dynamic Web Project
> 2. Convert to maven project (using Configure -> Convert to maven..)
> 3. Add some dependency
> 4. check if proper facet was enabled
> 5. delete project and repeat
> After trying this 10-15 times (sometimes more, sometimes less), during step 2 "Enabling Maven Dependency Management" job is waiting and never ends - see screenshot - there's always "Setting classpath containers".
> JVM thread dump attached.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17715) JAX-RS metamodel failed to build/refresh due to StringIndexOutOfBoundsException
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17715?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-17715:
---------------------------------------
cool ! thanks, [~rrabara] ;-)
> 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
> Assignee: Xavier Coulon
> 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
[JBoss JIRA] (JBDS-2844) Management API Server Adapter
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2844?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2844:
--------------------------------------
Fix Version/s: 8.0.0.Beta3
> Management API Server Adapter
> -----------------------------
>
> Key: JBDS-2844
> URL: https://issues.jboss.org/browse/JBDS-2844
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements, server
> Reporter: Burr Sutter
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Fix For: 8.0.0.Beta3
>
>
> Related to JBIDE-14073 and EAP6-1
> The current EAP/JBossAS/Wildfly Server Adapter often interacts with the underlying file-system of the app server. Users have asked that the following scenarios be supported:
> - Remote Server Start/Stop
> - Remote Server Deployment/Undeployment
> - Remote Server single file update (e.g. html, js, jsp, xhtml, etc) with hot-deployment (to be worked out with the Wildfly team)
> - Remote Server Log Viewing
> and while the focus here in on remote servers, it should work just as well with localhost-based servers.
> Also related, not having the actual server code locally installed, being able to work wholly with a remote server (comes up in the Data Virt/Teiid world).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months