September 2012 - jbosstools-issues

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

5
20
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, 3 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] (JBDS-2339) create Marketplace entry for JBDS 6 so we can publish the "Core Features" feature

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2339: -------------------------------- Summary: create Marketplace entry for JBDS 6 so we can publish the "Core Features" feature Key: JBDS-2339 URL: https://issues.jboss.org/browse/JBDS-2339 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Build, updatesite Affects Versions: 6.0.0.Alpha2 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 6.0.0.Beta1 As per decisions in JBDS-2253, I need to create an Eclipse Marketplace entry for JBDS 6 so we can publish the "Core Features" feature and get people trying it out that way instead of via Early Access update site or installer. -- 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
5
0 / 0

[JBoss JIRA] (JBIDE-12479) Investigate CDI Tools performance issues

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-12479: -------------------------------------- Summary: Investigate CDI Tools performance issues Key: JBIDE-12479 URL: https://issues.jboss.org/browse/JBIDE-12479 Project: Tools (JBoss Tools) Issue Type: Task Components: CDI Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 4.0.x -- 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

1
2
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, 4 months

4
6
0 / 0

[JBoss JIRA] (JBIDE-12466) Find a new home for org.jboss.tools.runtime.as.ui.bot.test

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-12466: ----------------------------------- Summary: Find a new home for org.jboss.tools.runtime.as.ui.bot.test Key: JBIDE-12466 URL: https://issues.jboss.org/browse/JBIDE-12466 Project: Tools (JBoss Tools) Issue Type: Task Components: runtime detection Affects Versions: 4.0.0.M1 Reporter: Rob Stryker Assignee: Len DiMaggio Fix For: 4.0.0.M1 JIRA JBIDE-12465 will soon disable the org.jboss.tools.runtime.as.ui.bot.test plugin test. It is not the intention that this test plugin disappear; just that it get moved. The test plugin will be disabled shortly. Once it is removed from the build, it will be safe for QE to find a new home for it. The given test plugin is more of an integration test plugin and belongs with other integration tests and integration swtbot tests. -- 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

4
5
0 / 0

[JBoss JIRA] (JBIDE-12505) ensure all JBT SOA components have published exploded update sites on http://download.jboss.org/jbosstools/updates/

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-12505: ---------------------------------- Summary: ensure all JBT SOA components have published exploded update sites on http://download.jboss.org/jbosstools/updates/ Key: JBIDE-12505 URL: https://issues.jboss.org/browse/JBIDE-12505 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, SOA Tooling, updatesite Affects Versions: 3.3.0.Final-SOA, 4.0.0.M1-SOA Reporter: Nick Boldt Assignee: Nick Boldt For each of the JBT SOA components, we should ensure that they're all publishing into standard locations on http://download.jboss.org/jbosstools/updates/. This issue should be a container for child issues assigned to each project's releng person. Done: * SwitchYard - JBIDE-10672 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/sw... Publishes elsewhere, manually symlinked: * Drools/jbpm5 - JBRULES-3470 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/dr... Publishes elsewhere: * Modeshape Tools - JBBUILD-720, MODE-1506 - http://download.jboss.org/modeshape/builds/staging/modeshape-tools-contin... ? * Savara - http://download.jboss.org/savara/releases/updates/2.0.x/ * pi4soa - http://pi4soa.sourceforge.net/updates/ Publishes as zip only: * Teiid Designer - https://www.jboss.org/teiiddesigner/downloads/ -> http://sourceforge.net/projects/teiid/files/teiid-designer/7.7/teiid_desi... No publishing strategy (staging only): * ESB - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... * jbpm3 - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... * JBoss BPEL - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... -- 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

1
10
0 / 0

[JBoss JIRA] (JBIDE-12615) allow as7 classpath containers have access restrictions

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-12615: ----------------------------------- Summary: allow as7 classpath containers have access restrictions Key: JBIDE-12615 URL: https://issues.jboss.org/browse/JBIDE-12615 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: JBossAS/Servers Affects Versions: 4.0.0.Alpha1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 4.0.0.Alpha2 We will eventually have access restrictions on the as7 jars provided. This will require the classpath container in charge of making the entries to provide the classpath acces rules. ClientAllRuntimeClasspathProvider: protected IClasspathEntry getEntry(Entry entry) { IPath p = entry.getPath(); IAccessRule[] rules = null; if( p.toString().contains("picketbox")) { IPath filePattern= new Path("**/ssl/**"); rules = new IAccessRule[]{JavaCore.newAccessRule(filePattern, IAccessRule.K_NON_ACCESSIBLE)}; System.out.println("break here"); } IClasspathEntry e = JavaCore.newLibraryEntry(entry.getPath(), null, null, rules == null ? ClasspathEntry.NO_ACCESS_RULES : rules, ClasspathEntry.NO_EXTRA_ATTRIBUTES, false/*not exported*/); Above is example code. -- 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
7
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 September 2012