[JBoss JIRA] Created: (JBIDE-8196) Support @Veto annotation.
by Alexey Kazakov (JIRA)
Support @Veto annotation.
-------------------------
Key: JBIDE-8196
URL: https://issues.jboss.org/browse/JBIDE-8196
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: cdi (jsr-299)
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 3.3.x
Seam-solder reference guide:
2.1.1. @Veto.
Annotating a class @Veto will cause the type to be ignored, such that any definitions on the type will not be processed, including:
• the managed bean, decorator, interceptor or session bean defined by the type
• any producer methods or producer fields defined on the type
• any observer methods defined on the type
For example:
@Veto
class Utilities {
...
}
--
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-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
[JBoss JIRA] Created: (JBIDE-7923) Allow user to re-create the Top-down web service
by Lukas Jungmann (JIRA)
Allow user to re-create the Top-down web service
------------------------------------------------
Key: JBIDE-7923
URL: https://issues.jboss.org/browse/JBIDE-7923
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Webservices
Reporter: Lukas Jungmann
Assignee: Brian Fitzpatrick
Priority: Minor
use case:
-have a dynamic web project with some messed up implementation of a web service from wsdl
-goal is to recreate the service - regenerate artifacts from wsdl, replace current ws implementation class with new, empty one and readd entries into web.xml if needed
current approach:
-user has to clean everything manually - delete entries from DD, delete generated classes, delete service implementation class and rerun the new web service wizard
suggested approach:
-allow user to rerun the web service wizard for service existing in the project asking him if he wants to re-create it and if so then rerun the wsconsume, recreate service impl class and update DD. All these steps should be presented to the user (by default all would be on) and user should be allowed to choose which of them he wants the IDE to do
and/or
-provide some context sensitive action for this somewhere in the IDE, perhaps service node in project explorer view looks like a good candidate for this
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months