[JBoss JIRA] (JBIDE-15932) CordovaSim needs to display console logs especially during startup
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15932?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-15932:
-------------------------------------
[~burrsutter], now you can give ia a go :-) . PR for 4.1.1.x is sent
> CordovaSim needs to display console logs especially during startup
> ------------------------------------------------------------------
>
> Key: JBIDE-15932
> URL: https://issues.jboss.org/browse/JBIDE-15932
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Affects Versions: 4.1.1.Beta1
> Reporter: Gorkem Ercan
> Assignee: Ilya Buziuk
> Priority: Blocker
> Labels: jbds711
> Fix For: 4.1.2.CR1, 4.2.0.Alpha2
>
>
> When a cordova application is launched the console.log calls are not displayed on Eclipse console (or anywhere else). CordovaSim needs a place to display the logs either within eclipse or on the Ripple console so the user can be notified about errors happening early on.
> Just using firebug or similar would not solve this issue since it is not started early enough.
--
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
11 years, 11 months
[JBoss JIRA] (JBDS-2857) Add OS X 10.9 Mavericks to the support matrix
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2857?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2857 at 1/31/14 12:37 PM:
------------------------------------------------------------
Therefore we're saying:
* "JBDS 7.x *works with* OSX 10.9, but is unsupported there."
and
* "JBDS 7.1.1 is *supported* on OSX 10.9."
>From a GSS point of view, that means:
* "Any customer on JBDS 7.0 or 7.1 needs to upgrade/update to 7.1.1 in order to be *supported* on OSX 10.9, but older JBDS 7.x versions may work on OSX 10.9 too."
Clear as mud? :D
was (Author: nickboldt):
Therefore we're saying:
* "JBDS 7.x *works with* OSX 10.9, but is unsupported there."
and
* "JBDS 7.1.1 is *supported* on OSX 10.9."
>From a GSS point of view, that means:
* "Any customer on JBDS 7.0 or 7.1 needs to upgrade/update to 7.1.1 in order to be *supported* on OSX 10.9, but older versions may work too."
Clear as mud? :D
> Add OS X 10.9 Mavericks to the support matrix
> ---------------------------------------------
>
> Key: JBDS-2857
> URL: https://issues.jboss.org/browse/JBDS-2857
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Affects Versions: 7.1.0.CR1
> Reporter: Martin Malina
> Assignee: Len DiMaggio
> Fix For: 7.1.1.CR1, 8.0.0.Alpha2
>
>
> I know this comes very late, so you may want to just push this to 8.0.0 immediately.
> However, we've already been testing on Mavericks (I use it every day myself) since it was introduced on October 22, 2013 and have never seen any problem specific to it.
> I only realized we still don't have Mavericks in the matrix today when I checked Michelle's Supported Configurations document.
--
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
11 years, 11 months
[JBoss JIRA] (JBIDE-15394) Add arquillian.xml GUI editor to jbosstools-arquillian
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15394?page=com.atlassian.jira.plugi... ]
Denis Golovin edited comment on JBIDE-15394 at 1/31/14 12:35 PM:
-----------------------------------------------------------------
The editor shows a pom.xml fragment, but still unconditionally changes pom.xml.
I like the feature, but think it would be better to implement it as arquillian.xml/arquillian.properies validator.
The validator would create markers that could have quickfixes that would refactor pom.xml in the standard way, that is, using a refactoring dialog, a pom.xml preview ...
There are a few bugs (when editing pom.xml and arquillian.xml at the same time, for instance) that could be fixed. However, the editor has been implemented from scratch what would make maintenance more difficult. In my opinion, it would be better to implement the editor using the [Saphire framework|http://www.eclipse.org/sapphire/] or the JBoss XModel framework. I would like to try to implement it using the Saphire framework because it is better documented.
was (Author: snjeza):
The editor shows a pom.xml fragment, but still unconditionally changes pom.xml.
I like the feature, but think it would be better to implement it as arquillian.xml/arquillian.properies validator.
The validator would create markers that could have quickfixes that would refactor pom.xml in the standard way, that is, using a refactoring dialog, a pom.xml preview ...
There are a few bugs (when editing pom.xml and arquillian.xml at the same time, for instance) that could be fixed. However, the editor has been implemented from scratch what would make maintenance more difficult. In my opinion, it would be better to implement the editor using the Saphire framework or the JBoss XModel framework. I would like to try to implement it using the Saphire framework because it is better documented.
> Add arquillian.xml GUI editor to jbosstools-arquillian
> ------------------------------------------------------
>
> Key: JBIDE-15394
> URL: https://issues.jboss.org/browse/JBIDE-15394
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: testing-tools
> Reporter: Masao Kunii
> Assignee: Snjezana Peco
> Priority: Optional
> Fix For: 4.2.0.Beta1
>
>
> The arquillian.xml editor is an editor to edit arquillian.xml easily and visually. This is a feature for jbosstools-arquillian(https://github.com/jbosstools/jbosstools-arquillian) and enables to:
> - Edit containers, container groups, extensions, protocols and engines
> - Modify pom.xml automatically corresponding settings in arquillian.xml
> - Register favorite container/container groups from Eclipse preferences
--
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
11 years, 11 months
[JBoss JIRA] (JBDS-2857) Add OS X 10.9 Mavericks to the support matrix
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2857?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2857:
----------------------------------
Therefore we're saying:
* "JBDS 7.x *works with* OSX 10.9, but is unsupported there."
and
* "JBDS 7.1.1 is *supported* on OSX 10.9."
>From a GSS point of view, that means:
* "Any customer on JBDS 7.0 or 7.1 needs to upgrade/update to 7.1.1 in order to be *supported* on OSX 10.9, but older versions may work too."
Clear as mud? :D
> Add OS X 10.9 Mavericks to the support matrix
> ---------------------------------------------
>
> Key: JBDS-2857
> URL: https://issues.jboss.org/browse/JBDS-2857
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Affects Versions: 7.1.0.CR1
> Reporter: Martin Malina
> Assignee: Len DiMaggio
> Fix For: 7.1.1.CR1, 8.0.0.Alpha2
>
>
> I know this comes very late, so you may want to just push this to 8.0.0 immediately.
> However, we've already been testing on Mavericks (I use it every day myself) since it was introduced on October 22, 2013 and have never seen any problem specific to it.
> I only realized we still don't have Mavericks in the matrix today when I checked Michelle's Supported Configurations document.
--
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
11 years, 11 months
[JBoss JIRA] (JBDS-2370) Bad/non-helping error message when central has no connection
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBDS-2370?page=com.atlassian.jira.plugin.... ]
Snjezana Peco commented on JBDS-2370:
-------------------------------------
{quote}
You can't mention JBoss Central or a refresh button as the wizards can also be opened via the New Project... menu
{quote}
The same message will be shown on a wizard page if a wizard is opened via the File>New menu.
{quote}
I believe that, once the connection issue is solved, next attempt to open the wizard should succeed without having the need to refresh anything. Or am I wrong?
{quote}
You are right. The wizard refresh tutorials. Ja sam promenila poruku. Nova je:
{quote}
Please check your Internet connection, <a>Proxy Settings</a> and try again!
{quote}
> 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: upstream
> Affects Versions: 5.0.0.GA
> Environment: JDK 1.7 32-bit, Windows
> Reporter: David Chia
> Assignee: Snjezana Peco
> Priority: Critical
> Labels: jbds711
> Fix For: 7.1.1.CR1, 8.0.0.Alpha2
>
>
> 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
11 years, 11 months
[JBoss JIRA] (JBDS-2370) Bad/non-helping error message when central has no connection
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBDS-2370?page=com.atlassian.jira.plugin.... ]
Snjezana Peco reassigned JBDS-2370:
-----------------------------------
Assignee: Fred Bricon (was: Snjezana Peco)
> 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: upstream
> Affects Versions: 5.0.0.GA
> Environment: JDK 1.7 32-bit, Windows
> Reporter: David Chia
> Assignee: Fred Bricon
> Priority: Critical
> Labels: jbds711
> Fix For: 7.1.1.CR1, 8.0.0.Alpha2
>
>
> 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
11 years, 11 months
[JBoss JIRA] (JBIDE-16264) @PathParam with hyphen in value shows as JAX-RS error
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16264?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-16264:
--------------------------------
Fix Version/s: 4.1.2.CR1
> @PathParam with hyphen in value shows as JAX-RS error
> -----------------------------------------------------
>
> Key: JBIDE-16264
> URL: https://issues.jboss.org/browse/JBIDE-16264
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.1.CR1
> Reporter: Jim Boettcher
> Assignee: Fred Bricon
> Priority: Minor
> Fix For: 4.1.2.CR1, 4.2.0.Alpha2
>
>
> if I have a method like:
> @GET
> @Path("/rule/{rule-file-name}")
> public byte[] getRuleSet(@PathParam("rule-file-name") String ruleSetName)
> I get the error:
> @PathParam value 'rule-file-name' does not match any @Path annotation template parameters of the java method and the enclosing java type.
> If I remove the hyphens from "rule-file-name" the error goes away.
> However the hyphen should be allowed.
--
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
11 years, 11 months
[JBoss JIRA] (JBDS-2857) Add OS X 10.9 Mavericks to the support matrix
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBDS-2857?page=com.atlassian.jira.plugin.... ]
Burr Sutter commented on JBDS-2857:
-----------------------------------
7.1.1 it is.
> Add OS X 10.9 Mavericks to the support matrix
> ---------------------------------------------
>
> Key: JBDS-2857
> URL: https://issues.jboss.org/browse/JBDS-2857
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Affects Versions: 7.1.0.CR1
> Reporter: Martin Malina
> Assignee: Len DiMaggio
> Fix For: 7.1.1.CR1, 8.0.0.Alpha2
>
>
> I know this comes very late, so you may want to just push this to 8.0.0 immediately.
> However, we've already been testing on Mavericks (I use it every day myself) since it was introduced on October 22, 2013 and have never seen any problem specific to it.
> I only realized we still don't have Mavericks in the matrix today when I checked Michelle's Supported Configurations document.
--
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
11 years, 11 months