[JBoss JIRA] (JBIDE-16292) Need to restore ability to select specific archetype version per runtime in Central
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16292?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-16292:
-------------------------------------
Yes, my understanding is WFK 2.5 archetypes will be bound to EAP 6.2. I believe WFK 2.4 archetypes will be available for EAP 6.1. [~rafabene] : am I correct?
> Need to restore ability to select specific archetype version per runtime in Central
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-16292
> URL: https://issues.jboss.org/browse/JBIDE-16292
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, project-examples
> Affects Versions: 4.1.1.Final
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 4.1.2.CR1
>
>
> The changes done in JBIDE-15645 introduced a regression in the way archetypes are selected.
> Basically, we can get different archetype versions depending on the EE version of the runtime (web/full-ee6 vs web/full-ee7) but we lost the ability to pick a different archetype version between 2 different runtimes of the same product and same EE level (eg. EAP 6.1 vs EAP 6.2)
> As a consequence, archetype versions designed to run on EAP 6.2 will be selected when EAP 6.1 is selected in the project wizard.
> Hopefully EAP 6.2 archetypes will still be able to run on EAP 6.1 so that shouldn't be a problem, but we should fix that for the next minor release.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (JBIDE-15881) Annotated field with QueryParam missing in URL Endpoint template
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15881?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-15881:
----------------------------------
Description:
Take the following classes:
{code}
@Path("/products")
public class ProductResourceLocator {
@QueryParam("foo1")
private String foo2;
@Path("/{productType}")
public Object getProductResourceLocator() {
return new BookResource();
}
}
{code}
and
{code}
@Produces({ MediaType.APPLICATION_XML, "application/json" })
public class BookResource {
@GET
@Path("/{id}")
@Produces({ "application/xml", "application/json" })
public Book getProduct(@PathParam("id") Integer id) {
return null;
}
}
{code}
ASSERT: the URL Template for the Endpoint should be something like
{code}
/products/{productType}/{id}?foo1={String}
{code}
was:
Take the following classes:
{code}
@Path("/products")
public class ProductResourceLocator {
@QueryParam("foo1")
private String foo2;
@Path("/{productType}")
public Object getProductResourceLocator() {
return new BookResource();
}
}
{code}
and
{code}
@Produces({ MediaType.APPLICATION_XML, "application/json" })
public class BookResource {
@GET
@Path("/{id}")
@Produces({ "application/xml", "application/json" })
public Book getProduct(@PathParam("id") Integer id) {
return null;
}
}
{code}
ASSERT: the URL Template for the Endpoint should be something like
/products/{productType}/{id}?foo1={String}
> Annotated field with QueryParam missing in URL Endpoint template
> ----------------------------------------------------------------
>
> Key: JBIDE-15881
> URL: https://issues.jboss.org/browse/JBIDE-15881
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.0.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.x
>
>
> Take the following classes:
> {code}
> @Path("/products")
> public class ProductResourceLocator {
> @QueryParam("foo1")
> private String foo2;
> @Path("/{productType}")
> public Object getProductResourceLocator() {
> return new BookResource();
> }
> }
> {code}
> and
> {code}
> @Produces({ MediaType.APPLICATION_XML, "application/json" })
> public class BookResource {
> @GET
> @Path("/{id}")
> @Produces({ "application/xml", "application/json" })
> public Book getProduct(@PathParam("id") Integer id) {
> return null;
> }
> }
> {code}
> ASSERT: the URL Template for the Endpoint should be something like
> {code}
> /products/{productType}/{id}?foo1={String}
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (JBDS-2370) Bad/non-helping error message when central has no connection
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBDS-2370?page=com.atlassian.jira.plugin.... ]
Radim Hopp closed JBDS-2370.
----------------------------
Verified in JBDS 7.1.1.CR1.
All error messages I was able to invoke were descriptive and were making sense.
> Bad/non-helping error message when central has no connection
> ------------------------------------------------------------
>
> Key: JBDS-2370
> URL: https://issues.jboss.org/browse/JBDS-2370
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 5.0.0.GA
> Environment: JDK 1.7 32-bit, Windows
> Reporter: David Chia
> Assignee: Radim Hopp
> Priority: Critical
> Labels: jbds711
> Fix For: 7.1.1.CR1
>
>
> After a successful install, I tried to create a "Java EE Web Project" and run into an error dialog "Failed to load Wizard - Wizard metadata could not be loaded". I've also tried all other projects and result in the same error. The only project I could create is the "Dynamic Web Project". Looking at the error log, there are a lot of these "Connection errors" like below.
> !SESSION 2012-10-23 15:28:07.909 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.7.0_07
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
> Framework arguments: -product com.jboss.jbds.product.product
> Command-line arguments: -os win32 -ws win32 -arch x86 -product com.jboss.jbds.product.product
> !ENTRY org.jboss.tools.central 4 0 2012-10-23 15:28:27.086
> !MESSAGE Permission denied: connect
> !STACK 0
> java.net.SocketException: Permission denied: connect
> at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
> at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:75)
> at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
> at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:157)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)
> at java.net.Socket.connect(Socket.java:579)
> at org.eclipse.ecf.provider.filetransfer.events.socket.SocketEventCreateUtil.createSocket(SocketEventCreateUtil.java:43)
> at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:81)
> at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:73)
> at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:65)
> at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
> at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361)
> at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
> at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
> at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
> at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
> at org.eclipse.ecf.provider.filetransfer.httpclient.HttpClientRetrieveFileTransfer.performConnect(HttpClientRetrieveFileTransfer.java:1142)
> at org.eclipse.ecf.provider.filetransfer.httpclient.HttpClientRetrieveFileTransfer.openStreams(HttpClientRetrieveFileTransfer.java:710)
> at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:889)
> at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:576)
> at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:106)
> at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.transfer(ECFExamplesTransport.java:319)
> at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.performDownload(ECFExamplesTransport.java:246)
> at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.download(ECFExamplesTransport.java:206)
> at org.jboss.tools.central.jobs.AbstractRefreshJob.run(AbstractRefreshJob.java:186)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.jboss.tools.central 4 0 2012-10-23 15:28:27.132
> !MESSAGE Permission denied: connect
> !STACK 0
> java.net.SocketException: Permission denied: connect
> at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
> at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:75)
> at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
> at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:157)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)
> at java.net.Socket.connect(Socket.java:579)
> at org.eclipse.ecf.provider.filetransfer.events.socket.SocketEventCreateUtil.createSocket(SocketEventCreateUtil.java:43)
> at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:81)
> at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:73)
> at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:65)
> at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
> at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361)
> at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
> at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
> at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
> at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
> at org.eclipse.ecf.provider.filetransfer.httpclient.HttpClientRetrieveFileTransfer.performConnect(HttpClientRetrieveFileTransfer.java:1142)
> at org.eclipse.ecf.provider.filetransfer.httpclient.HttpClientRetrieveFileTransfer.openStreams(HttpClientRetrieveFileTransfer.java:710)
> at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:889)
> at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:576)
> at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:106)
> at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.transfer(ECFExamplesTransport.java:319)
> at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.performDownload(ECFExamplesTransport.java:246)
> at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.download(ECFExamplesTransport.java:206)
> at org.jboss.tools.central.jobs.AbstractRefreshJob.run(AbstractRefreshJob.java:186)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (JBIDE-16292) Need to restore ability to select specific archetype version per runtime in Central
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16292?page=com.atlassian.jira.plugi... ]
Radim Hopp commented on JBIDE-16292:
------------------------------------
{quote}
In practice, the current stacks.yaml file doesn't currently provide ways to test the fix (unit tests do), We'll have to wait for WFK 2.5 archetypes to be added to EAP 6.2 to see it work
{quote}
[~fbricon] So basically we have to wait for WFK 2.5 to release GA to verify it?
> Need to restore ability to select specific archetype version per runtime in Central
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-16292
> URL: https://issues.jboss.org/browse/JBIDE-16292
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, project-examples
> Affects Versions: 4.1.1.Final
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 4.1.2.CR1
>
>
> The changes done in JBIDE-15645 introduced a regression in the way archetypes are selected.
> Basically, we can get different archetype versions depending on the EE version of the runtime (web/full-ee6 vs web/full-ee7) but we lost the ability to pick a different archetype version between 2 different runtimes of the same product and same EE level (eg. EAP 6.1 vs EAP 6.2)
> As a consequence, archetype versions designed to run on EAP 6.2 will be selected when EAP 6.1 is selected in the project wizard.
> Hopefully EAP 6.2 archetypes will still be able to run on EAP 6.1 so that shouldn't be a problem, but we should fix that for the next minor release.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (JBIDE-16286) CDI builder (not import, workspace rebuild) is very slow in wildfly
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-16286:
--------------------------------
Fix Version/s: (was: 4.1.2.CR1)
> CDI builder (not import, workspace rebuild) is very slow in wildfly
> -------------------------------------------------------------------
>
> Key: JBIDE-16286
> URL: https://issues.jboss.org/browse/JBIDE-16286
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi, maven
> Affects Versions: 4.1.1.Final
> Reporter: Andre Dietisheim
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: performance
> Fix For: 4.2.0.Beta1
>
> Attachments: cdi-builder.ogv, cleanBuild.png, full-bundle-listing.txt, maven-preferences-hide-children.png, thread-dump-7_05.txt, thread-dump-7_19.txt, updatingPom.png, VisualVM 1.3.2 _083.png
>
>
> When working in a wildfly workspace with all wildfly projects imported and CDI builder enabled, workspace rebuilds (that you trigger by changing poms and then do maven update project) are a lot slower than without it. Re-building the whole workspace can easily take up to 20 minutes for me.
> Hard to give more general purpose details, I did a quick screencast to give an impression how slow things are for me.
> [^cdi-builder.ogv]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (JBDS-2577) JBDS70_0813: [Partial] (Dev) (P1) Support non-minified/minified JS libs
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBDS-2577?page=com.atlassian.jira.plugin.... ]
Radim Hopp commented on JBDS-2577:
----------------------------------
m2e-wro4j is installable and is working. Closing.
> JBDS70_0813: [Partial] (Dev) (P1) Support non-minified/minified JS libs
> -----------------------------------------------------------------------
>
> Key: JBDS-2577
> URL: https://issues.jboss.org/browse/JBDS-2577
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: central, requirements
> Reporter: Jiri Pallich
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: new_and_noteworthy
> Fix For: 7.1.0.CR1
>
> Attachments: JBDS2577_installed_JBDS7beta1.png, JBDS2577_installed_JBT_CR1.png, m2e-wro4j-central.png
>
>
> Support non-minified JS libs for Dev, swap in minified JS libs for production (wro4j - maven integration?).
> Examples of JS libs: jQuery, jQuery Mobile
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (JBIDE-15827) Failed to remove JAX-RS Metamodel when closing a project
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15827?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-15827:
----------------------------------
Fix Version/s: 4.2.0.Beta1
(was: 4.2.x)
> Failed to remove JAX-RS Metamodel when closing a project
> --------------------------------------------------------
>
> Key: JBIDE-15827
> URL: https://issues.jboss.org/browse/JBIDE-15827
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.1.Beta1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Beta1
>
>
> When closing a JAX-RS project, the following error is reported in the log:
> {code}
> org.eclipse.core.internal.resources.ResourceException: The resource tree is locked for modifications.
> at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:116)
> at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:2283)
> at org.eclipse.core.internal.resources.Resource.deleteMarkers(Resource.java:844)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.remove(JaxrsMetamodel.java:332)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedListener.resourceChanged(ResourceChangedListener.java:62)
> at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285)
> at org.eclipse.core.internal.events.NotificationManager.handleEvent(NotificationManager.java:249)
> at org.eclipse.core.internal.resources.Workspace.broadcastEvent(Workspace.java:391)
> at org.eclipse.core.internal.resources.Project.close(Project.java:199)
> at org.eclipse.ui.actions.CloseResourceAction.invokeOperation(CloseResourceAction.java:129)
> at org.eclipse.ui.actions.WorkspaceAction.execute(WorkspaceAction.java:164)
> at org.eclipse.ui.actions.WorkspaceAction$2.runInWorkspace(WorkspaceAction.java:485)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month