[JBoss JIRA] (JBIDE-14739) Generated JBoss WS SOAP message is invalid
by Jaroslav Jankovič (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14739?page=com.atlassian.jira.plugi... ]
Jaroslav Jankovič updated JBIDE-14739:
--------------------------------------
Summary: Generated JBoss WS SOAP message is invalid (was: JBoss WS SOAP message is not generated well)
> Generated JBoss WS SOAP message is invalid
> ------------------------------------------
>
> Key: JBIDE-14739
> URL: https://issues.jboss.org/browse/JBIDE-14739
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Affects Versions: 4.1.0.Beta1
> Reporter: Jaroslav Jankovič
> Fix For: 4.1.0.Beta2
>
>
> STEP: create dynamic web project and register web.xml (to be able to create simple soap web service)
> STEP: create simple web service (File -> New -> Other -> JBoss Tools -> Simple Web Service with default settings
> STEP: run a server, deploy a project
> STEP: open Web Service Tester, enter url of web service and try to invoke its default method (sayHello)
> STEP: open the generated web service class (HelloWorld.java)
> STEP: add a new web method like this:
> {code}
> @WebMethod()
> public String echo() {
> return "Hello World";
> }
> {code} redeploy the project
> STEP: open web service tester again, url should be still set on text box, so click on the "Get from WSDL"
> STEP: in opened dialog, choose the new method "echo", and press OK
> ASSERT: generated request message has valid format
> {code}
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
> <soap:Header/>
> <soap:Body>
> <ns2:echo xmlns:ns2="http://webservices.samples.jboss.org/"/>
> </soap:Body>
> </soap:Envelope>
> {code}
> ASSERT: invoking the generated message tends to valid response
> FAIL: generated request message has invalid format
> {code}
> <?xml version="1.0" encoding="utf-8" standalone="yes" ?>
> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" >
> <soap:Header>
> </soap:Header>
> <soap:Body>
> </soap:Body>
> </soap:Envelope>
> {code}
> FAIL: invoking the message throws a SOAPFaultException:
> {code}
> java.lang.Exception: javax.xml.ws.soap.SOAPFaultException: Fault occurred while processing.
> 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.soap.SOAPFaultException: Fault occurred while processing.
> at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178)
> at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:111)
> at com.sun.xml.internal.ws.client.dispatch.DispatchImpl$DispatchAsyncInvoker$1.onCompletion(DispatchImpl.java:450)
> at com.sun.xml.internal.ws.client.Stub$1.onCompletion(Stub.java:381)
> at com.sun.xml.internal.ws.api.pipe.Fiber.completionCheck(Fiber.java:502)
> at com.sun.xml.internal.ws.api.pipe.Fiber.run(Fiber.java:420)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> {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, 10 months
[JBoss JIRA] (JBIDE-14739) JBoss WS SOAP message is not generated well
by Jaroslav Jankovič (JIRA)
Jaroslav Jankovič created JBIDE-14739:
-----------------------------------------
Summary: JBoss WS SOAP message is not generated well
Key: JBIDE-14739
URL: https://issues.jboss.org/browse/JBIDE-14739
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 4.1.0.Beta1
Reporter: Jaroslav Jankovič
Fix For: 4.1.0.Beta2
STEP: create dynamic web project and register web.xml (to be able to create simple soap web service)
STEP: create simple web service (File -> New -> Other -> JBoss Tools -> Simple Web Service with default settings
STEP: run a server, deploy a project
STEP: open Web Service Tester, enter url of web service and try to invoke its default method (sayHello)
STEP: open the generated web service class (HelloWorld.java)
STEP: add a new web method like this:
{code}
@WebMethod()
public String echo() {
return "Hello World";
}
{code} redeploy the project
STEP: open web service tester again, url should be still set on text box, so click on the "Get from WSDL"
STEP: in opened dialog, choose the new method "echo", and press OK
ASSERT: generated request message has valid format
{code}
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header/>
<soap:Body>
<ns2:echo xmlns:ns2="http://webservices.samples.jboss.org/"/>
</soap:Body>
</soap:Envelope>
{code}
ASSERT: invoking the generated message tends to valid response
FAIL: generated request message has invalid format
{code}
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" >
<soap:Header>
</soap:Header>
<soap:Body>
</soap:Body>
</soap:Envelope>
{code}
FAIL: invoking the message throws a SOAPFaultException:
{code}
java.lang.Exception: javax.xml.ws.soap.SOAPFaultException: Fault occurred while processing.
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.soap.SOAPFaultException: Fault occurred while processing.
at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178)
at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:111)
at com.sun.xml.internal.ws.client.dispatch.DispatchImpl$DispatchAsyncInvoker$1.onCompletion(DispatchImpl.java:450)
at com.sun.xml.internal.ws.client.Stub$1.onCompletion(Stub.java:381)
at com.sun.xml.internal.ws.api.pipe.Fiber.completionCheck(Fiber.java:502)
at com.sun.xml.internal.ws.api.pipe.Fiber.run(Fiber.java:420)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
{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, 10 months
[JBoss JIRA] (JBIDE-14720) No Project Facets are set when creating a "Java EE Web Project" for JBossAS 7.1
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14720?page=com.atlassian.jira.plugi... ]
Rastislav Wagner commented on JBIDE-14720:
------------------------------------------
I cant reproduce the issue.
My config: Beta1b, Kepler RC2 for JEE, EAP 6.1, AS 7.1.
I've tried Java EE Project, HTML5 and Richfaces from central.
> No Project Facets are set when creating a "Java EE Web Project" for JBossAS 7.1
> -------------------------------------------------------------------------------
>
> Key: JBIDE-14720
> URL: https://issues.jboss.org/browse/JBIDE-14720
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.1.0.Alpha2, 4.1.0.Beta1
> Reporter: Juergen Zimmermann
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 4.1.0.Beta2
>
> Attachments: jbosstools-diagnostics-20130601182344.zip, screenshot-after-wizard-has-completed.jpg
>
>
> 1) I'm using JBoss Tools version 2013-05-29_02-05-21-B272 which I got from http://download.jboss.org/jbosstools/builds/development/4.1.0.Beta1b.core... and also the Java EE package for Kepler RC2.
> 2) I created a server config for JBossAS 7.1.0 (btw, same happens for EAP 6.1).
> 3) I created a new "Java EE Web Project".
> I'll attach a screenshot after the project wizard has completed, and also a "Help > Report Problem".
--
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, 10 months
[JBoss JIRA] (JBIDE-14400) create p2 remediation UI icons
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14400?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-14400:
---------------------------------------------
sorry should have closed it. this is at eclipse.
> create p2 remediation UI icons
> ------------------------------
>
> Key: JBIDE-14400
> URL: https://issues.jboss.org/browse/JBIDE-14400
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: upstream
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.0.Beta1
>
> Attachments: down1.png, down2.png, down3.png, screen1.jpg, screen2.jpg, screen3.jpg, Screen_Shot_2013-05-06_at_9.59.35_AM.png, up1.png, up2.png, up3.png
>
>
> Pascal from p2 on eclipse side is working on p2 remediation UI and have asked if we got two icons for < and > (bigger than and less than).
> See the screenshot for where they would be used (basically in the tree to indicate which are being down or upgraded.
> Daniel could you make such that can be shown nicely in a treeviewer ?
> I think having a v and ^ to show up and down might be better.
--
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, 10 months
[JBoss JIRA] (JBIDE-13527) [tester] freeze parsing wsdl
by Jaroslav Jankovič (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13527?page=com.atlassian.jira.plugi... ]
Jaroslav Jankovič commented on JBIDE-13527:
-------------------------------------------
Brian I was talking about response to invoking the message. Not a request message body - I am getting a correct SOAP message too.
The error I am talking about is:
{code}
javax.xml.ws.WebServiceException: {http://types.complex.jaxws.ws.test.jboss.org/}RegistrationServiceImplService is not a valid service. Valid services are: {http://complex.jaxws.ws.test.jboss.org}RegistrationServiceImplService
at com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:226)
at com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:171)
at com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:96)
at javax.xml.ws.Service.<init>(Service.java:77)
at javax.xml.ws.Service.create(Service.java:707)
at org.jboss.tools.ws.ui.utils.JAXWSTester2.doTest(JAXWSTester2.java:139)
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)
{code}
> [tester] freeze parsing wsdl
> ----------------------------
>
> Key: JBIDE-13527
> URL: https://issues.jboss.org/browse/JBIDE-13527
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Affects Versions: 3.3.2.Final
> Reporter: Alessio Soldano
> Assignee: Brian Fitzpatrick
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Beta1
>
> Attachments: jaxws-complex.war, threaddump.txt
>
>
> JBT freezes when the ws tester is used to consume the wsdl contract for the jaxws-complex.war test deployment of JBossWS testsuite.
--
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, 10 months
[JBoss JIRA] (JBIDE-14544) Cannot run Cordova project on Android Emulator/Device
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14544?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-14544:
---------------------------------------------
[~vpakan] that is a separate issue - seems the launch is not considering differences between windows and linux based systems. Can you open seperate issue for it please ?
> Cannot run Cordova project on Android Emulator/Device
> -----------------------------------------------------
>
> Key: JBIDE-14544
> URL: https://issues.jboss.org/browse/JBIDE-14544
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.0.Beta1
> Environment: Fedora 17 32bit
> Android 4.1.2
> Reporter: Stefan Bunciak
> Assignee: Gorkem Ercan
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.1.0.Beta2
>
> Attachments: runasandroidemulatorwin7_32.png, Screen Shot 2013-06-03 at 10.50.52 AM.png
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> {code}
> java.io.IOException: No such file or directory
> at java.io.UnixFileSystem.createFileExclusively(Native Method)
> at java.io.File.createNewFile(File.java:883)
> at org.jboss.tools.aerogear.hybrid.core.util.FileUtils.fileCopy(FileUtils.java:105)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidProjectGenerator.generateNativeFiles(AndroidProjectGenerator.java:99)
> at org.jboss.tools.aerogear.hybrid.core.platform.AbstractPlatformProjectGenerator.generateNow(AbstractPlatformProjectGenerator.java:68)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:68)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:825)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:706)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222)
> 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, 10 months
[JBoss JIRA] (JBIDE-14544) Cannot run Cordova project on Android Emulator/Device
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14544?page=com.atlassian.jira.plugi... ]
Vlado Pakan edited comment on JBIDE-14544 at 6/4/13 3:44 AM:
-------------------------------------------------------------
On MS Widnows 7 32 bit this error dialog is displayed.
!runasandroidemulatorwin7_32.png!
Tested with latest Aerogear plugin version installed from staging site mentioned in Gorkem comment.
No error messages in error log appeared after project was run on Android emulator.
There is this error in error log after JBT with Mobile Hybrid project in workspace is started:
{noformat}
eclipse.buildId=4.3.0.I20130502-0800
java.version=1.6.0_26
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86 -debug
Error
Tue Jun 04 07:44:13 PDT 2013
Failed to load properties file for project 'cordova'
Plugin: com.android.ide.eclipse.adt
{noformat}
I renamed file android.bat to android and then I got another message saying android is not proper win32 application
was (Author: vpakan):
On MS Widnows 7 32 bit this error dialog is displayed.
!runasandroidemulatorwin7_32.png!
Tested with latest Aerogear plugin version installed from staging site mentioned in Gorkem comment.
No error messages in error log.
> Cannot run Cordova project on Android Emulator/Device
> -----------------------------------------------------
>
> Key: JBIDE-14544
> URL: https://issues.jboss.org/browse/JBIDE-14544
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.0.Beta1
> Environment: Fedora 17 32bit
> Android 4.1.2
> Reporter: Stefan Bunciak
> Assignee: Gorkem Ercan
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.1.0.Beta2
>
> Attachments: runasandroidemulatorwin7_32.png, Screen Shot 2013-06-03 at 10.50.52 AM.png
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> {code}
> java.io.IOException: No such file or directory
> at java.io.UnixFileSystem.createFileExclusively(Native Method)
> at java.io.File.createNewFile(File.java:883)
> at org.jboss.tools.aerogear.hybrid.core.util.FileUtils.fileCopy(FileUtils.java:105)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidProjectGenerator.generateNativeFiles(AndroidProjectGenerator.java:99)
> at org.jboss.tools.aerogear.hybrid.core.platform.AbstractPlatformProjectGenerator.generateNow(AbstractPlatformProjectGenerator.java:68)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:68)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:825)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:706)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222)
> 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, 10 months