July 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-9443) Wizard for creating Service implementations (ServiceLoader / Service file)

by Lincoln Baxter III (JIRA)

Wizard for creating Service implementations (ServiceLoader / Service file) -------------------------------------------------------------------------- Key: JBIDE-9443 URL: https://issues.jboss.org/browse/JBIDE-9443 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.3.0.M2 Reporter: Lincoln Baxter III It would be very nice if we had a wizard or hotkey to create a new service implementation: CTRL-N --> New Service Implementation Class 1. Wizard asks you to specify the service Interface you wish to implement, and then lets you give the typical new-class information (with Interface already populated and greyed out.) 2. When submitted, the wizard creates the implementing class, and also creates a service file in the java-resources 'META-INF/services' directory, containing the name of your service implementation class. If the Service file already exists, your class should be added to it on a new line: META-INF/services/org.example.service.spi.Interface -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

8
30
0 / 0

[JBoss JIRA] (JBIDE-12347) Unable to invoke SOAP web service

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-12347: ----------------------------------------- Summary: Unable to invoke SOAP web service Key: JBIDE-12347 URL: https://issues.jboss.org/browse/JBIDE-12347 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.3.1 Reporter: Jaroslav Jankovič Assignee: Brian Fitzpatrick Fix For: 3.3.2 I am unable to invoke SOAP web service in WS Tester from http://www.webservicex.net/BibleWebservice.asmx?WSDL. In Response Body of WS Tester I got the message: {code} javax.xml.ws.soap.SOAPFaultException: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: . at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest() at System.Web.Services.Protocols.SoapServerProtocol.RouteRequest(SoapServerMessage message) at System.Web.Services.Protocols.SoapServerProtocol.Initialize() at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing) {code} In error log I got the error: {code} java.lang.Exception: javax.xml.ws.soap.SOAPFaultException: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: . at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest() at System.Web.Services.Protocols.SoapServerProtocol.RouteRequest(SoapServerMessage message) at System.Web.Services.Protocols.SoapServerProtocol.Initialize() at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing) at org.jboss.tools.ws.ui.utils.JAXWSTester2.doTest(JAXWSTester2.java:205) at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.handleWSTest(JAXRSWSTestView2.java:1803) at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.access$34(JAXRSWSTestView2.java:1789) at org.jboss.tools.ws.ui.views.JAXRSWSTestView2$21.run(JAXRSWSTestView2.java:1706) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: javax.xml.ws.soap.SOAPFaultException: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: . at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest() at System.Web.Services.Protocols.SoapServerProtocol.RouteRequest(SoapServerMessage message) at System.Web.Services.Protocols.SoapServerProtocol.Initialize() at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing) 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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
12
0 / 0

[JBoss JIRA] (JBIDE-12331) Integration tests modules separation from components

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-12331: ------------------------------------ Summary: Integration tests modules separation from components Key: JBIDE-12331 URL: https://issues.jboss.org/browse/JBIDE-12331 Project: Tools (JBoss Tools) Issue Type: Task Components: Build/Releng Affects Versions: 3.3.0.Final Reporter: Jiri Peterka Assignee: Nick Boldt Fix For: 3.1.2 Integration tests should be separated for these major reasons: * QE need to update them during JBT code freeze * Integration tests should not trigger components builds * Integration test mvn execution can be optimized * Common JBT build can be free from Integration tests specifics -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

4
6
0 / 0

[JBoss JIRA] (JBIDE-12310) generate sources for m2e-apt; add to update site for consumption & inclusion downstream by JBDS

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-12310: ---------------------------------- Summary: generate sources for m2e-apt; add to update site for consumption & inclusion downstream by JBDS Key: JBIDE-12310 URL: https://issues.jboss.org/browse/JBIDE-12310 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.4.0.M1 Reporter: Nick Boldt Assignee: Fred Bricon Fix For: 3.4.0.M1 http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/m2e-a... contains no source features/plugins. Please generate them according to the rules here: http://wiki.eclipse.org/Minerva#Source -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-8654) New Instance wizard: add capability to create server adapter from instance

by Andre Dietisheim (JIRA)

New Instance wizard: add capability to create server adapter from instance -------------------------------------------------------------------------- Key: JBIDE-8654 URL: https://issues.jboss.org/browse/JBIDE-8654 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: deltacloud Affects Versions: 3.2.0.Final, 3.3.0.M1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.x Currently you may create a new server adapter in 2 ways: 1) fully automatically when launching the instance: check "Create Server Adapter" 2) manually: * launch an instance * show in remote system explorer (creates the RSE connection) * create server adapter, switch it to remote mode and use the RSE connection as host Option 1) is pretty error prone. If 1 of the 3 tasks fail no server adapter is created and it's hard to find out why it went wrong. IMHO the process is too automatic, too long, too intrasparent. Option 2) is pretty transparent, but not obvious. We would improve the situation if we would offer an action "Create Server Adapter" in the context menu of the instances. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
4
0 / 0

[JBoss JIRA] (JBIDE-12143) Create core plugin

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-12143: ---------------------------------------- Summary: Create core plugin Key: JBIDE-12143 URL: https://issues.jboss.org/browse/JBIDE-12143 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 3.3.0.CR1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.x, 3.4.x We currently only have a *org.jboss.tools.openshift.express.ui* plugin which holds core and ui components. We should factor the core components out and put them into their own plugin *org.jboss.tools.openshift.express.core* -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-11689) Target Platforms Should Optionally Include Source Code

by Dan Florian (JIRA)

Dan Florian created JBIDE-11689: ----------------------------------- Summary: Target Platforms Should Optionally Include Source Code Key: JBIDE-11689 URL: https://issues.jboss.org/browse/JBIDE-11689 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: target-platform Affects Versions: 3.3.0.Beta3 Reporter: Dan Florian Assignee: Mickael Istria Fix For: 3.4.x When developers are researching issues they typically end up debugging in classes found in the target platform. It would be nice if the JBT target platforms optionally could contain source or if new target platforms with source could be created. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBDS-1377) Eclipse Makretplace in JBDS

by Libor Zoubek (JIRA)

Eclipse Makretplace in JBDS --------------------------- Key: JBDS-1377 URL: https://jira.jboss.org/browse/JBDS-1377 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: Build Affects Versions: 4.0.0.Beta1 Reporter: Libor Zoubek It would be nice to have Eclipse market place available in JBDS. It is present in JBT (when I install it on top of helios-jee bundle), but it is missing in JBDS (probably because we build JBDS against SDK). -- 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

13 years, 5 months

4
8
0 / 0

[JBoss JIRA] (JBIDE-11269) remote console should not assume jbossas7 log file names

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11269: ------------------------------------------- Summary: remote console should not assume jbossas7 log file names Key: JBIDE-11269 URL: https://issues.jboss.org/browse/JBIDE-11269 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Max Rydahl Andersen Assignee: Andre Dietisheim currently it seems remote console just shows jboss log files. should be defaulting to *.log and be configurable - possibly based on the apptype ? have a preference that says which pattern to use for application types. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

4
12
0 / 0

[JBoss JIRA] (JBIDE-11806) Offline Suppert for central - fine tuning

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-11806: ---------------------------------- Summary: Offline Suppert for central - fine tuning Key: JBIDE-11806 URL: https://issues.jboss.org/browse/JBIDE-11806 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: central Affects Versions: 3.3.0.Beta3 Reporter: Radim Hopp Assignee: Snjezana Peco Priority: Minor Fix For: 3.3.0.CR1 Offline support [JBIDE-11192|https://issues.jboss.org/browse/JBIDE-11192] works fine except for two things I noticed: * When trying to create example/quickstart which is not cached (so it won't create), there is still offered readme.md to be opened (which of course doesn't exist) -> errors in Error Log * Would it be possible to put some better text than "java.net.UnknownHostException <hostname>" in tooltip (see screenshot)? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

4
15
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2012