August 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6592) Bad UI in Sample Web Wizard

by Max Rydahl Andersen (JIRA)

Bad UI in Sample Web Wizard --------------------------- Key: JBIDE-6592 URL: https://jira.jboss.org/browse/JBIDE-6592 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Reporter: Max Rydahl Andersen Assignee: Brian Fitzpatrick Fix For: 3.2.0.M2 The sample web wizard is nice and simple but got a few weird usage of eclipse ui. 1) There is a "Use default value" checkbox that greys out the text field which means users who want to change the default has to check the checkbox and then click the textfield and then type into the textbox. The text field should just be filled up with an initial default value to avoid user having to press too many buttons and typing. 2) Even though there is only 4 input fields to fill out (or just get the default from) it is spread out over two pages. Move it onto one page. The above will make it much more consistent with rest of eclipse ui AND easier for the user since everything is on one page instead of two. -- 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, 7 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-6643) Improve error message "Stereotype declares any qualifier annotation other than @Named"

by Pete Muir (JIRA)

Improve error message "Stereotype declares any qualifier annotation other than @Named" -------------------------------------------------------------------------------------- Key: JBIDE-6643 URL: https://jira.jboss.org/browse/JBIDE-6643 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Reporter: Pete Muir Assignee: Max Rydahl Andersen Should be "Stereotypes cannot declare qualifier annotations (except @Named)" -- 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, 7 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6683) NPE error when useing the web project that has web module 2.4 facet to create web service

by Feng Qian (JIRA)

NPE error when useing the web project that has web module 2.4 facet to create web service ----------------------------------------------------------------------------------------- Key: JBIDE-6683 URL: https://jira.jboss.org/browse/JBIDE-6683 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.1.x Environment: windows vista Reporter: Feng Qian Assignee: Feng Qian Fix For: 3.2.0.M2 Create a dynamic web project using web module 2.4 facet, then use it to generate web service, you will get the NPE error. -- 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, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6808) IllegalArgumentException during Weld example building.

by Alexey Kazakov (JIRA)

IllegalArgumentException during Weld example building. ------------------------------------------------------ Key: JBIDE-6808 URL: https://jira.jboss.org/browse/JBIDE-6808 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.0.M2 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.2.0.M2 The exception is thrown if I build an example created using weld-jsf-jee maven archetype. See http://seamframework.org/Documentation/WeldQuickstartForMavenUsers#H-Crea... java.lang.IllegalArgumentException at org.eclipse.jdt.core.Signature.appendTypeSignature(Signature.java:2377) at org.eclipse.jdt.core.Signature.appendTypeSignature(Signature.java:2284) at org.eclipse.jdt.core.Signature.toCharArray(Signature.java:2263) at org.jboss.tools.common.model.util.EclipseJavaUtil.resolveTypeAsString(EclipseJavaUtil.java:67) at org.jboss.tools.cdi.internal.core.impl.definition.ParametedTypeFactory.getParametedType(ParametedTypeFactory.java:108) at org.jboss.tools.cdi.internal.core.impl.definition.ParametedTypeFactory.getParametedTypeForParameter(ParametedTypeFactory.java:195) at org.jboss.tools.cdi.internal.core.impl.definition.ParametedTypeFactory.newParametedType(ParametedTypeFactory.java:68) at org.jboss.tools.cdi.internal.core.impl.definition.AbstractTypeDefinition.init(AbstractTypeDefinition.java:62) at org.jboss.tools.cdi.internal.core.impl.definition.TypeDefinition.init(TypeDefinition.java:42) at org.jboss.tools.cdi.internal.core.impl.definition.AbstractMemberDefinition.setAnnotatable(AbstractMemberDefinition.java:50) at org.jboss.tools.cdi.internal.core.impl.definition.AbstractTypeDefinition.setType(AbstractTypeDefinition.java:54) at org.jboss.tools.cdi.internal.core.scanner.CDIBuilderDelegate.build(CDIBuilderDelegate.java:56) at org.jboss.tools.cdi.core.CDICoreBuilder.buildJars(CDICoreBuilder.java:229) at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:145) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:629) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:172) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:203) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:255) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:258) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:311) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:343) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:242) 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, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6612) Helios does not recognize JBoss 6.0 Runtime as JEE6 environment

by Thorsten Kunz (JIRA)

Helios does not recognize JBoss 6.0 Runtime as JEE6 environment --------------------------------------------------------------- Key: JBIDE-6612 URL: https://jira.jboss.org/browse/JBIDE-6612 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.M1 Environment: Helios 3.6.0 Linux x64 All JBoss Tools - 3.2.0.v201007020601N-H408-M1 Reporter: Thorsten Kunz Assignee: Rob Stryker I installed JBoss Tools 3.2.0.v201007020601N-H408-M1 nightly build for Helios. Now when I try to create e.g. an EJB Project and set the "Target Runtime" to "JBoss 6.0 Runtime" based on a JBAS 6.0-M3 I loose the option to set the "EJB Module Version" to 3.1. Only 3.0 is available. Same is true for "Enterprise Application Projects". I can only set the the "EAR Version" to 5.0. No 6.0 is available. Now when I set the "Target Runtime" to my Glassfish 3 Runtime I have all the JEE6 options available. This is very unfortunate since it disabled lots of built in JEE6 functionality provided by the native Helios JEE distribution. -- 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, 7 months

5
8
0 / 0

[JBoss JIRA] Created: (JBIDE-6841) The method getProcess() is undefined for the type JBossServerBehavior in org/jboss/tools/ws/creation/core/test/command/AbstractJBossWSCommandTest.java

by Nick Boldt (JIRA)

The method getProcess() is undefined for the type JBossServerBehavior in org/jboss/tools/ws/creation/core/test/command/AbstractJBossWSCommandTest.java ------------------------------------------------------------------------------------------------------------------------------------------------------ Key: JBIDE-6841 URL: https://jira.jboss.org/browse/JBIDE-6841 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.M2 Reporter: Nick Boldt Assignee: Brian Fitzpatrick Priority: Blocker [ERROR] Failed to execute goal org.sonatype.tycho:maven-osgi-compiler-plugin:0.9.0:compile (default-compile) on project org.jboss.tools.ws.creation.core.test: Compilation failure: Compilation failure: /mnt/hudson_workspace/workspace/jbosstools-3.2.0.M2.continuous/sources/ws/tests/org.jboss.tools.ws.creation.core.test/src/org/jboss/tools/ws/creation/core/test/command/AbstractJBossWSCommandTest.java (at line 415):[-1,-1] if (behavior.getProcess() != null) { ^^^^^^^^^^ The method getProcess() is undefined for the type JBossServerBehavior /mnt/hudson_workspace/workspace/jbosstools-3.2.0.M2.continuous/sources/ws/tests/org.jboss.tools.ws.creation.core.test/src/org/jboss/tools/ws/creation/core/test/command/AbstractJBossWSCommandTest.java (at line 416):[-1,-1] return behavior.getProcess().getStreamsProxy() ^^^^^^^^^^ The method getProcess() is undefined for the type JBossServerBehavior -- 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, 7 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6865) WS Tester fails to parse some WSDL operations

by Robert (Bob) Brodt (JIRA)

WS Tester fails to parse some WSDL operations --------------------------------------------- Key: JBIDE-6865 URL: https://jira.jboss.org/browse/JBIDE-6865 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Environment: All Reporter: Robert (Bob) Brodt Assignee: Brian Fitzpatrick Fix For: 3.2.x The WSDL at http://flightaware.com/commercial/flightxml/data/wsdl1.xml appears to parsed correctly by WS Tester, but when I select the "AiportInfo" operation, the message template is not generated. -- 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, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6850) [tester] provide ability to test services running over HTTPS

by Lukas Jungmann (JIRA)

[tester] provide ability to test services running over HTTPS ------------------------------------------------------------ Key: JBIDE-6850 URL: https://jira.jboss.org/browse/JBIDE-6850 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Affects Versions: 3.2.0.M2 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick -let's have a service running over HTTPS, sample for JBoss6- https://community.jboss.org/servlet/JiveServlet/download/38-15328/secured... Note: in this case only web service invocation is secured (POST) -load WSDL in the tester - http://localhost:8080/demo/HelloWorld?WSDL -test the service => response body 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 -- 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, 7 months

2
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6763) Console configuration lists shold be sorted in alphabetic ignore case order

by Vitali Yemialyanchyk (JIRA)

Console configuration lists shold be sorted in alphabetic ignore case order --------------------------------------------------------------------------- Key: JBIDE-6763 URL: https://jira.jboss.org/browse/JBIDE-6763 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.2.0.M2 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Priority: Minor Fix For: 3.2.0.M2 -- 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, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6795) incorrect warning is shown by ws from wsdl wizard

by Lukas Jungmann (JIRA)

incorrect warning is shown by ws from wsdl wizard ------------------------------------------------- Key: JBIDE-6795 URL: https://jira.jboss.org/browse/JBIDE-6795 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.M2 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick Attachments: screenshot.png -create some web service service from WSDL in "org.jboss.wsimpl" package -invoke the ws from wsdl wizard again but now set package name to be "org.jboss.ws" => Warning in the wizard says "package already exists" which is not true, see attached screenshot -- 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, 7 months

3
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 August 2010