September 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-7065) RSE Deployment does not work for complex deployments on running servers

by Dominik Pospisil (JIRA)

RSE Deployment does not work for complex deployments on running servers ----------------------------------------------------------------------- Key: JBIDE-7065 URL: https://jira.jboss.org/browse/JBIDE-7065 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.M2 Reporter: Dominik Pospisil Assignee: Rob Stryker RSE Deployment does not work for complex deployments on running servers. The problem is that the deployment structure is copied file by file to remote system, which could be potentially slow operation. There is a high chance that the deployer scanner on target server pickup new deployment before copy operation is completed and the deployment fails. I have never managed to deploy a Seam project successfully. -- 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

15 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-7027) InjectionPointQueryParticipant throws NullPointerException if user searches references for class from jar file

by Daniel Azarov (JIRA)

InjectionPointQueryParticipant throws NullPointerException if user searches references for class from jar file -------------------------------------------------------------------------------------------------------------- Key: JBIDE-7027 URL: https://jira.jboss.org/browse/JBIDE-7027 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.0.M2 Reporter: Daniel Azarov Assignee: Daniel Azarov Fix For: 3.2.0.Beta Test case: 1. Start studio 2. Create Java project, make it CDI project 3. Expand in Package Explorer any folder with jars 4. Expand any jar file 5. Expand any class file 6. Right click on any method 7. Select "References->Workspace" menu item 8. Check Error log FAIL: Exception: java.lang.NullPointerException at org.jboss.tools.cdi.ui.search.InjectionPointQueryParticipant.search(InjectionPointQueryParticipant.java:65) at org.eclipse.jdt.internal.ui.search.JavaSearchQuery$2.run(JavaSearchQuery.java:164) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.jdt.internal.ui.search.JavaSearchQuery.run(JavaSearchQuery.java:170) at org.eclipse.search2.internal.ui.InternalSearchUI$InternalSearchJob.run(InternalSearchUI.java:91) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- 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

15 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7044) CDI model does not load data from beans.xml

by Daniel Azarov (JIRA)

CDI model does not load data from beans.xml ------------------------------------------- Key: JBIDE-7044 URL: https://jira.jboss.org/browse/JBIDE-7044 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.0.M2 Reporter: Daniel Azarov Assignee: Viacheslav Kabanovich Fix For: 3.2.0.Beta For example, CDI model does not recognize selected alternative Bean classes which must be registered in beans.xml file -- 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

15 years, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7091) cdi test failures

by Alexey Kazakov (JIRA)

cdi test failures ----------------- Key: JBIDE-7091 URL: https://jira.jboss.org/browse/JBIDE-7091 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.0.Beta Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.2.0.Beta Failed tests: testBeansXML(org.jboss.tools.cdi.core.test.BeansXMLTest) testWeldBeansXML(org.jboss.tools.cdi.core.test.BeansXMLTest) testSelectedAlternativeManagedBean(org.jboss.tools.cdi.core.test.tck.SelectedAlternativeTest) testSelectedAlternativeStereotype(org.jboss.tools.cdi.core.test.tck.SelectedAlternativeTest) testSelectedAlternativeProducer(org.jboss.tools.cdi.core.test.tck.SelectedAlternativeTest) -- 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

15 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7119) java lib path not set correctly for remote servers

by Rob Stryker (JIRA)

java lib path not set correctly for remote servers -------------------------------------------------- Key: JBIDE-7119 URL: https://jira.jboss.org/browse/JBIDE-7119 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.M2 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.2.0.Beta java lib path still uses the local runtime location rather than the rseHome. -- 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

15 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7137) WS Component N&N

by Max Andersen (JIRA)

WS Component N&N ---------------- Key: JBIDE-7137 URL: https://jira.jboss.org/browse/JBIDE-7137 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Webservices Affects Versions: 3.2.0.M2 Reporter: Denis Golovin Assignee: Brian Fitzpatrick Fix For: 3.2.0.M2 https://jira.jboss.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=pro... -- 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

15 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6999) [Tester] Can't test a valid WSDL with no services, but user gets no feedback in WSDL browse dialog

by Brian Fitzpatrick (JIRA)

[Tester] Can't test a valid WSDL with no services, but user gets no feedback in WSDL browse dialog -------------------------------------------------------------------------------------------------- Key: JBIDE-6999 URL: https://jira.jboss.org/browse/JBIDE-6999 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.M2 Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Fix For: 3.2.0.Beta Attachments: HelloWorld.wsdl While working on the web services tooling documentation, Ben Clare hit upon an interesting case. He has a WSDL that's perfectly valid but has no services defined. So the WSDL Browse dialog was parsing it and saying "hey that's valid but I have no services, I'll just blindly go on like nothing's wrong..." We obviously need to handle this case and provide some meaningful message back to the user as to why they can't test the WSDL selected. -- 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

15 years, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6925) [Tester] Body text for PUT operation not being cleared of CRLF prior to invocation

by Brian Fitzpatrick (JIRA)

[Tester] Body text for PUT operation not being cleared of CRLF prior to invocation ---------------------------------------------------------------------------------- Key: JBIDE-6925 URL: https://jira.jboss.org/browse/JBIDE-6925 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.M2 Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Fix For: 3.2.0.Beta While working on a wiki page documenting the WS Tester (http://community.jboss.org/wiki/UsingtheWebServiceTester) I discovered that when doing a PUT operation for JAX-RS, the body text is not being cleaned of CRLF characters prior to invocation as happens during a POST. Should also check the DELETE operation as well to make sure it's covered. -- 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

15 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7215) In creating a Seam Web project can not change the domain to a client name. Example: default is com.domain.{projectname].entity. The project name will be filled in with the selected project name; but the domain will not change to HP or IBM for example

by Robb Greathouse (JIRA)

In creating a Seam Web project can not change the domain to a client name. Example: default is com.domain.{projectname].entity. The project name will be filled in with the selected project name; but the domain will not change to HP or IBM for example --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-7215 URL: https://jira.jboss.org/browse/JBIDE-7215 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Environment: MacOS and Windows. Also effects JBoss Developer Studio 4.0 Reporter: Robb Greathouse Assignee: Alexey Kazakov Priority: Minor Developers would like to change the domain name to their company or department name. The wizard does not allow this. To change it you have to change package name after creation and alter the settings manually. -- 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

15 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6851) [tester] provide ability to read WSDL exxposed over HTTPS

by Lukas Jungmann (JIRA)

[tester] provide ability to read WSDL exxposed over HTTPS --------------------------------------------------------- Key: JBIDE-6851 URL: https://jira.jboss.org/browse/JBIDE-6851 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Affects Versions: 3.2.0.M2 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick similar to JBIDE-6850 -let's have a service running over HTTPS, sample for JBoss6- https://community.jboss.org/servlet/JiveServlet/download/38-15328/secured... -open web.xml of service project -add '<http-method>GET</http-method>' before the '<http-method>POST</http-method>' element -save web.xml and republish the project on the server Note: in this case both web service invocation and service description are secured (GET, POST) -open tester and click on the 'Get from WSDL' button -click on 'URL...' button, fill in http://localhost:8080/demo/HelloWorld?WSDL (or https://localhost:8443/demo/HelloWorld?WSDL) and press OK => no service, no port, nor operation are shown in the dialog IDE log says: com.sun.xml.internal.ws.wsdl.parser.InaccessibleWSDLException: 2 counts of InaccessibleWSDLException. javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(RuntimeWSDLParser.java:161) at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:133) at com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(WSServiceDelegate.java:254) at com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:217) at com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:165) at com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:93) at javax.xml.ws.Service.<init>(Service.java:56) at javax.xml.ws.Service.create(Service.java:680) at org.jboss.tools.ws.ui.utils.JAXWSTester2.doTest(JAXWSTester2.java:98) at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.handleWSTest(JAXRSWSTestView2.java:1265) at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.access$25(JAXRSWSTestView2.java:1251) at org.jboss.tools.ws.ui.views.JAXRSWSTestView2$18.run(JAXRSWSTestView2.java:1195) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- 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

15 years, 6 months

2
14
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 2010