[JBoss JIRA] Created: (JBIDE-7281) Wizards should not allow user to select unsupported JAX-WS spec version
by Lukas Jungmann (JIRA)
Wizards should not allow user to select unsupported JAX-WS spec version
-----------------------------------------------------------------------
Key: JBIDE-7281
URL: https://jira.jboss.org/browse/JBIDE-7281
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.2.0.Beta1
Reporter: Lukas Jungmann
Assignee: Brian Fitzpatrick
-create a dynamic web project with target runtime set to JBossAS6-M5
-create a ws client there with JAX-WS spec set to 2.1 and finish the wizard
=> generated code is of JAX-WS version 2.2
default ws stack in JBossAS6-M5 does not seem to allow user to set JAX-WS spec version. Even though the wsconsume's output says it is generating JAX-WS 2.1 code, it in fact the generated code is of version 2.2
jlukas@lukas-laptop:~/latest/jboss-6.0.0.20100911-M5/bin$ ./wsconsume.sh --target=2.2 -o /tmp/fff -k http://footballpool.dataaccess.eu/data/info.wso?WSDL
Could not find log4j.xml configuration, logging to console.
WSConsume (CXF) does not allow to setup the JAX-WS specification target, using JAX-WS 2.1.
log4j:WARN No appenders could be found for logger (org.apache.cxf.common.logging.LogUtils).
log4j:WARN Please initialize the log4j system properly.
Loading FrontEnd jaxws ...
Loading DataBinding jaxb ...
wsdl2java -compile -exsh false -d /tmp/fff -verbose -classdir /tmp/fff -allowElementReferences http://footballpool.dataaccess.eu/data/info.wso?WSDL
wsdl2java - Apache CXF 2.2.10
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBIDE-6942) Prompt for Basic Auth when accessing secured WSDL
by Juergen Zimmermann (JIRA)
Prompt for Basic Auth when accessing secured WSDL
-------------------------------------------------
Key: JBIDE-6942
URL: https://jira.jboss.org/browse/JBIDE-6942
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Webservices
Affects Versions: 3.2.0.M1
Reporter: Juergen Zimmermann
Assignee: Brian Fitzpatrick
A SOAP based Web Service can be defined as follows:
@WebService(name = "MyService")
@WebContext(contextRoot = "/myRoot", authMethod = "BASIC", secureWSDLAccess = true)
@EndpointConfig(configName = "Standard WSSecurity Endpoint")
Now the WSDL cannot be accessed without BASIC authentication.
Therefore, it would be fine, if you could provide a checkbox within the dialog "Select WSDL", so that username and password could be prompted. Just as the checkbox below "Request details" in the main window.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-8003) DeltaCloud: move #deleteKey to Key
by Andre Dietisheim (JIRA)
DeltaCloud: move #deleteKey to Key
----------------------------------
Key: JBIDE-8003
URL: https://issues.jboss.org/browse/JBIDE-8003
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: deltacloud
Affects Versions: 3.2.0.CR1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.2.x
The DeltaCloud class currently has a method #deleteKey. The Deltacloud server reports available actions on objects and does so with Keys. This approach is perfect REST style as it offers links to available actions.
Keys currently have a destroy action and deltacloud tools do unmarshall this correctly. The tools implementation should therefore remove #deleteKey from the DeltaCloud class and offer such a method on the key that then delegates to the appropriate (destroy-) action.
The current tools implementation already offers this approach for instances but took a shortcut with Keys to have higher prio items for CR1 implemented.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-5535) New Web Service
by Burr Sutter (JIRA)
New Web Service
---------------
Key: JBIDE-5535
URL: https://jira.jboss.org/jira/browse/JBIDE-5535
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Burr Sutter
Attachments: New_WebService_Wizard.jpg, New_Wizard.jpg
There should be a New Web Service Project wizard (the same as New Dynamic Web Project) and a New Web Service component wizard.
The New Web Service Project wizard creates the exact same thing as New Dynamic Web Project but with HelloWorldWS.java containing the following:
package com.jboss.lab;
import javax.jws.WebMethod;
import javax.jws.WebService;
@WebService
public class MyWebService {
@WebMethod
public String sayHello(String name) {
return "Hello2 " + name + "!";
}
}
And the appropriate entries in the web.xml.
<servlet>
<servlet-name>MyWebServiceServlet</servlet-name>
<servlet-class>com.jboss.lab.MyWebService</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>MyWebServiceServlet</servlet-name>
<url-pattern>/MyWebService</url-pattern>
</servlet-mapping>
See screenshots for current functionality.
This suggestion is based on how Visual Studio handles this scenario. For a New Web Service or New Web Service project, it drops in the annotated mywebservice.asmx automatically. You can deploy the project/component immediately without further editing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months