[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Maria Beltrán (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Maria Beltrán commented on JBIDE-2720:
--------------------------------------
Hi Konstantin I have W8.1 ,
Eclipse Indigo and JBoss tools I have JBoss 4.2.3.GA,
I donw loaded it from
http://sourceforge.net/projects/jboss/files/JBoss/JBoss-4.2.3.GA/
place.
> Need 64-bit windows support
> ---------------------------
>
> Key: JBIDE-2720
> URL: https://issues.jboss.org/browse/JBIDE-2720
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha
> Reporter: Samuel Mendenhall
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.x
>
> Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, vpe-win-jdk64.png
>
>
> If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load.
> We should look into providing a xulrunner for Windows 64-bit.
> *Update:*
> In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is provided via experimental update site: http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr...
> {color:red}*Known problems:*{color}
> * XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK
> *If you get [R6034 error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277169...] you may:*
> * Try to uninstall Intel OpenCL SDK
> * *OR* Disable XULRunner by adding the option {{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or {{jbdevstudio.ini}} if you use JBoss Developer Studio)
> If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will very appreciate if you run Process Explorer as described in [this comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772...] and help us to find conflicting library.
--
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, 4 months
[JBoss JIRA] (JBIDE-15307) Testing deployed SwitchYard service with SOAP gateway fails with SOAPException
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15307?page=com.atlassian.jira.plugi... ]
Andrej Podhradsky closed JBIDE-15307.
-------------------------------------
Verified with JBDS 7.1.0.CR1 (v20131124-0717-B560)
> Testing deployed SwitchYard service with SOAP gateway fails with SOAPException
> ------------------------------------------------------------------------------
>
> Key: JBIDE-15307
> URL: https://issues.jboss.org/browse/JBIDE-15307
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.0.Final
> Reporter: Brian Fitzpatrick
> Assignee: Brian Fitzpatrick
> Fix For: 4.1.1.Alpha1
>
>
> While testing the SwitchYard tooling, discovered an issue where a deployed SwitchYard service with a SOAP gateway could not be tested. The exception is being caught and the message "InputStream does not represent a valid SOAP 1.1 Message" is being returned to the user.
> The exception is logged:
> {code}
> java.lang.Exception: javax.xml.ws.WebServiceException: javax.xml.soap.SOAPException: InputStream does not represent a valid SOAP 1.1 Message
> at org.jboss.tools.ws.ui.utils.JAXWSTester2.doTest(JAXWSTester2.java:205)
> at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.handleWSTest(JAXRSWSTestView2.java:1823)
> at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.access$34(JAXRSWSTestView2.java:1809)
> at org.jboss.tools.ws.ui.views.JAXRSWSTestView2$21.run(JAXRSWSTestView2.java:1726)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: javax.xml.ws.WebServiceException: javax.xml.soap.SOAPException: InputStream does not represent a valid SOAP 1.1 Message
> at com.sun.xml.internal.ws.message.saaj.SAAJMessage.access(Unknown Source)
> at com.sun.xml.internal.ws.message.saaj.SAAJMessage.getPayloadNamespaceURI(Unknown Source)
> at com.sun.xml.internal.ws.api.message.Message.getOperation(Unknown Source)
> at com.sun.xml.internal.ws.api.message.Message.getOperation(Unknown Source)
> at com.sun.xml.internal.ws.api.message.Message.isOneWay(Unknown Source)
> at com.sun.xml.internal.ws.handler.HandlerTube.checkOneWay(Unknown Source)
> at com.sun.xml.internal.ws.handler.HandlerTube.processRequest(Unknown Source)
> at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Unknown Source)
> at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Unknown Source)
> at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Unknown Source)
> at com.sun.xml.internal.ws.api.pipe.Fiber.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> Caused by: javax.xml.soap.SOAPException: InputStream does not represent a valid SOAP 1.1 Message
> at com.sun.xml.internal.messaging.saaj.soap.ver1_1.SOAPPart1_1Impl.createEnvelopeFromSource(Unknown Source)
> at com.sun.xml.internal.messaging.saaj.soap.SOAPPartImpl.getEnvelope(Unknown Source)
> ... 14 more
> {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, 4 months
[JBoss JIRA] (JBIDE-16124) "Add Arquillian Profiles" does nothing, changes the selected resource in Project Explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16124?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16124:
-------------------------------------
Steps to Reproduce:
# ASSERT have the wildfly codebase checked out
# EXEC create a launch config for wildfly-ts-integ-basic/org.jboss.as.test.integration.ejb.pool.override.PoolOverrideTestCase
# EXEC Switch to "Arquillian" tab and hit "Add Arquillian Profiles"
Result:
Nothing happens, no profile is added. At the same time the selection in the Project explorer switches, wildfly-ts-integ-basic get selected.
Expected result:
"Add Arquillian Profiles" should inform me what's wrong, why nothing happens.
was:
# ASSERT have the wildfly codebase checked out
# EXEC create a launch config for wildfly-ts-integ-basic/org.jboss.as.test.integration.ejb.pool.override.PoolOverrideTestCase
# EXEC: close your launch profile but dont launch it.
# EXEC. select some file in a different project
# EXEC open your launch profile again, switch to "Arquillian" tab and hit "Add Arquillian Profiles"
Result:
Nothing happens, no profile is added. At the same time the selection in the Project explorer switches, wildfly-ts-integ-basic get selected.
> "Add Arquillian Profiles" does nothing, changes the selected resource in Project Explorer
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-16124
> URL: https://issues.jboss.org/browse/JBIDE-16124
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.1.CR1
> Reporter: Andre Dietisheim
>
--
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, 4 months
[JBoss JIRA] (JBIDE-15788) Download runtime wizard shouldn't complain if install folder doesn't exist
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15788?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-15788:
---------------------------------------
OK. One more comment: I'm not particularly happy with the approach here. The usual workflow is that you enter a path and when you proceed (press next or finish or whatever) and the path does not exist, you are asked if you want to create it. For example the JBDS installer works this way and many other applications. I think it's better than to show this warning that we have now, especially when the information that the directory will be created for you is somewhat hidden. But this is just my opinion :) WDYT?
> Download runtime wizard shouldn't complain if install folder doesn't exist
> --------------------------------------------------------------------------
>
> Key: JBIDE-15788
> URL: https://issues.jboss.org/browse/JBIDE-15788
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: runtime-detection, server
> Affects Versions: 4.1.1.Alpha2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Fix For: 4.1.2
>
> Attachments: cr1-nonexistent-folder.png, install_folder_must_exist.png
>
>
> If the install folder is missing, the download runtime wizard should cope with it, instead of displaying an error (i.e. create the missing folders when necessary)
> - assert no EAP/AS7 are installed
> - create a new html5 project from central
> - click download and install for the server requirement
> - enter a non-existing location for the install folder
> !install_folder_must_exist.png!
--
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, 4 months
[JBoss JIRA] (JBIDE-15978) Properties view: URL for embedded cartridges is empty
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15978?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-15978:
------------------------------------------
according to comments in OpenShift bugzilla bug 1030984, the "url" property is only provided by downloadable cartrdiges and not defined for all other cartridges.
The code in the openshift-java-client suggests that "url" was used to provide the connection url for ex. mysql etc. Unfortunately I could not prove this via old captured responses.
> Properties view: URL for embedded cartridges is empty
> -----------------------------------------------------
>
> Key: JBIDE-15978
> URL: https://issues.jboss.org/browse/JBIDE-15978
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.2.x
>
> Attachments: empty-url-property.png
>
>
--
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, 4 months
[JBoss JIRA] (JBIDE-15978) Properties view: URL for embedded cartridges is empty
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15978?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-15978 at 11/26/13 4:10 AM:
--------------------------------------------------------------------
according to comments in OpenShift bugzilla (https://bugzilla.redhat.com/show_bug.cgi?id=1030984), the "url" property is only provided by downloadable cartrdiges and not defined for all other cartridges.
The code in the openshift-java-client suggests that "url" was used to provide the connection url for ex. mysql etc. Unfortunately I could not prove this via old captured responses.
was (Author: adietish):
according to comments in OpenShift bugzilla bug 1030984, the "url" property is only provided by downloadable cartrdiges and not defined for all other cartridges.
The code in the openshift-java-client suggests that "url" was used to provide the connection url for ex. mysql etc. Unfortunately I could not prove this via old captured responses.
> Properties view: URL for embedded cartridges is empty
> -----------------------------------------------------
>
> Key: JBIDE-15978
> URL: https://issues.jboss.org/browse/JBIDE-15978
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.2.x
>
> Attachments: empty-url-property.png
>
>
--
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, 4 months