October 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-11534) Wrong error on <jar-file/> option in multi-module EAR

by Marius Bogoevici (JIRA)

Marius Bogoevici created JBIDE-11534: ---------------------------------------- Summary: Wrong error on <jar-file/> option in multi-module EAR Key: JBIDE-11534 URL: https://issues.jboss.org/browse/JBIDE-11534 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 3.3.0.Beta2 Reporter: Marius Bogoevici Assignee: Dmitry Geraskov In a multi-module ear, one of the modules has a persistence.xml file which uses the following option to reference another module. {code} <jar-file>snowdrop-domain.jar</jar-file> {code} This results in a validation error in JBDS/JBoss Tools, the jar is deemed not to be found. -- 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, 4 months

5
20
0 / 0

[JBoss JIRA] (JBIDE-12971) Add mockito to the TP

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-12971: ---------------------------------------- Summary: Add mockito to the TP Key: JBIDE-12971 URL: https://issues.jboss.org/browse/JBIDE-12971 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Build/Releng Affects Versions: 4.0.0.Beta1 Reporter: Andre Dietisheim Assignee: Nick Boldt Fix For: 4.0.x It would be great if we could use mockito (http://code.google.com/p/mockito/) in our tests. We would have to add it to our target platform (TP) for our plugins to use it. -- 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

13 years, 4 months

3
5
0 / 0

[JBoss JIRA] (JBDS-2279) Investigate use of JRebel 5.0.1 in JBoss Central

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2279: -------------------------------- Summary: Investigate use of JRebel 5.0.1 in JBoss Central Key: JBDS-2279 URL: https://issues.jboss.org/browse/JBDS-2279 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Security Level: Public (Everyone can see) Components: 3rdPartyCertification, 3rdPartyDependencies, central Affects Versions: 6.0.0.Alpha1 Reporter: Nick Boldt Assignee: Len DiMaggio Fix For: 6.0.0.Beta1 Latest on update site (http://www.zeroturnaround.com/update-site/) is this: JRebel 5.0.1.RELEASE-201207191833 We're not allowed to redistribute this, so when you're testing if this works with Eclipse 4.2 / JBT 4.0 / JBDS 6.0, please ensure that you record the version you're using to verify it's the same (or newer) than the version stated above. Should the major version change, please update the description of this JIRA. -- 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

13 years, 4 months

5
14
0 / 0

[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, 4 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, 4 months

2
12
0 / 0

[JBoss JIRA] (JBIDE-12881) CLONE - OpenShift description in N&N

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-12881: ------------------------------------- Summary: CLONE - OpenShift description in N&N Key: JBIDE-12881 URL: https://issues.jboss.org/browse/JBIDE-12881 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: openshift Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.0.0.Alpha2 -- 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

13 years, 4 months

3
4
0 / 0

[JBoss JIRA] (JBIDE-12973) publish reddeer update site to download.jboss.org

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-12973: ---------------------------------- Summary: publish reddeer update site to download.jboss.org Key: JBIDE-12973 URL: https://issues.jboss.org/browse/JBIDE-12973 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, testing, updatesite Affects Versions: 4.0.0.CR1 Reporter: Nick Boldt Assignee: Martin Malina Fix For: 4.1.x Red deer should publish nightly/development/stable update sites like other components of JBT onto download.jboss.org. Simplest way to get a nightly build into download.jboss.org/jbosstools/builds/staging/ is to use my publish.sh [1] script as a step during your build job. Then, if you want to copy that to a more stable URL (for a dev milestone or stable release) use this job [2]: [1] https://svn.jboss.org/repos/jbosstools/trunk/build/publish/publish.sh [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-promote/ -- 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

13 years, 4 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-12944) migrate installer tests to use new directory structure (git) and new published sites

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-12944: ---------------------------------- Summary: migrate installer tests to use new directory structure (git) and new published sites Key: JBIDE-12944 URL: https://issues.jboss.org/browse/JBIDE-12944 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Build/Releng, testing Affects Versions: 4.0.0.CR1 Reporter: Nick Boldt Assignee: Mickael Istria Fix For: 4.0.0.CR1 These jobs are broken w/ the migration to git: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... I've done what I can to point them at the correct sources, but the first one [1] is trying to install code from an old repo [2] that no longer exists. It should be pointing at the new one [3]. [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... [2] http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.0_trunk.... [3] http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.0_trunk.... -- 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

13 years, 4 months

2
6
0 / 0

[JBoss JIRA] (JBIDE-12950) publish JBoss Tools SOA 3.3.1 release site to www.jboss.org

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-12950: ---------------------------------- Summary: publish JBoss Tools SOA 3.3.1 release site to www.jboss.org Key: JBIDE-12950 URL: https://issues.jboss.org/browse/JBIDE-12950 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, updatesite Affects Versions: 3.3.1.Final-SOA Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.1.Final-SOA Update the following pages: http://www.jboss.org/tools/download/ http://www.jboss.org/tools/download/stable http://www.jboss.org/tools/download/stable/3_3_Final http://www.jboss.org/tools/download/dev/3_3_SOA (copy to http://www.jboss.org/tools/download/stable/3_3_SOA_Final, then delete original - DO NOT MOVE PAGE) -- 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

13 years, 4 months

1
4
0 / 0

[JBoss JIRA] (JBIDE-12834) Could not resolve target platform

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBIDE-12834: ----------------------------------------- Summary: Could not resolve target platform Key: JBIDE-12834 URL: https://issues.jboss.org/browse/JBIDE-12834 Project: Tools (JBoss Tools) Issue Type: Bug Components: target-platform Affects Versions: 4.0.0.Beta1 Reporter: Andrej Podhradsky Assignee: Nick Boldt Attachments: debug.log After running $ cd jbosstools/tests $ mvn clean verify I get the following error java.lang.RuntimeException: Could not resolve target platform specification artifact org.jboss.tools.target-platforms.jbosstools-JunoSR0c:unified:target:unified:4.0.0.Beta1-SNAPSHOT -> [Help 1] org.apache.maven.InternalErrorException: Internal error: -- 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

13 years, 4 months

5
21
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 October 2012