[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, 8 months
[JBoss JIRA] Created: (JBIDE-8455) NPE in HibernateProjectConfigurator when importing maven or mavenArchetype project example
by Snjezana Peco (JIRA)
NPE in HibernateProjectConfigurator when importing maven or mavenArchetype project example
------------------------------------------------------------------------------------------
Key: JBIDE-8455
URL: https://issues.jboss.org/browse/JBIDE-8455
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Affects Versions: 3.2.0.Final
Reporter: Snjezana Peco
Assignee: Snjezana Peco
Fix For: 3.3.0.M1
If you import the Weld Java EE 6 example, you will face the following exception:
!ENTRY org.hibernate.eclipse.console 4 4 2011-02-20 22:54:41.156
!MESSAGE Could not activate Hibernate nature on projectjboss-javaee6-webapp
!SUBENTRY 1 org.hibernate.eclipse.console 4 150 2011-02-20 22:54:41.156
!MESSAGE org.eclipse.core.runtime.CoreException: Problems encountered while setting project description.
!STACK 1
org.eclipse.core.runtime.CoreException: Problems encountered while setting project description.
at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1212)
at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1238)
at org.hibernate.eclipse.console.utils.ProjectUtils.addProjectNature(ProjectUtils.java:133)
at org.hibernate.eclipse.console.utils.ProjectUtils.toggleHibernateOnProject(ProjectUtils.java:104)
at org.jboss.tools.maven.hibernate.configurators.HibernateProjectConfigurator.configureInternal(HibernateProjectConfigurator.java:55)
at org.jboss.tools.maven.hibernate.configurators.HibernateProjectConfigurator.mavenProjectChanged(HibernateProjectConfigurator.java:67)
at org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.mavenProjectChanged(ProjectConfigurationManager.java:646)
at org.maven.ide.eclipse.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:636)
at org.maven.ide.eclipse.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:767)
at org.maven.ide.eclipse.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:346)
at org.maven.ide.eclipse.project.MavenProjectManager.refresh(MavenProjectManager.java:65)
at org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.configureNewMavenProject(ProjectConfigurationManager.java:209)
at org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:146)
at org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.createArchetypeProject(ProjectConfigurationManager.java:481)
at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizard$1.run(ArchetypeExamplesWizard.java:73)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975)
at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizard$2.run(ArchetypeExamplesWizard.java:85)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 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, 8 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, 8 months