September 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-6448) Injection points with a raw type should resolve to corresponding bean.

by Alexey Kazakov (JIRA)

Injection points with a raw type should resolve to corresponding bean. ---------------------------------------------------------------------- Key: JBIDE-6448 URL: https://jira.jboss.org/browse/JBIDE-6448 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.next Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.2.next For example: @Produces public Dao<Object, Object> getDao() {...} @Produces Dao getRawDao() {...} @Produces public Dao<String, String> getDao() {...} and @Inject Dao dao; should resove to all the producers but @Inject Dao<String, String> should resolve to the last one. org.jboss.tools.cdi.core.test.tck.AssignabilityOfRawAndParameterizedTypesTest.testAssignabilityToRawType() should pass. -- 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-6447) Injection points should not resolve to non-selected alternatives.

by Alexey Kazakov (JIRA)

Injection points should not resolve to non-selected alternatives. ----------------------------------------------------------------- Key: JBIDE-6447 URL: https://jira.jboss.org/browse/JBIDE-6447 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.next Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.2.next See the spec.: 5.1.4. Inter-module injection A bean is available for injection in a certain module if: ... • the bean is either not an alternative, or the module is a bean archive and the bean is a selected alternative of the bean archive org.jboss.tools.cdi.core.test.tck.ResolutionByTypeTest.testPolicyNotAvailableInNonDeploymentArchive() should pass. IBean.isSelectedAlternative() should be implemented. -- 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

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6441) Typesafe resolution doesn't work for parameted CDI class beans.

by Alexey Kazakov (JIRA)

Typesafe resolution doesn't work for parameted CDI class beans. --------------------------------------------------------------- Key: JBIDE-6441 URL: https://jira.jboss.org/browse/JBIDE-6441 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.next Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.2.next For example there is the following class bean: @Typed(FlightlessBird.class) public class Emu extends FlightlessBird<Australian> { } Then this bean has FlightlessBird<Australian> bean type. Not just FlightlessBird. org.jboss.tools.cdi.core.test.tck.ResolutionByTypeTest.testGenericBeanTypesOnManagedBean() should pass. -- 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

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6498) cannot create bottom-up ws with JBossWS-metro-3.3.1GA

by Lukas Jungmann (JIRA)

cannot create bottom-up ws with JBossWS-metro-3.3.1GA ----------------------------------------------------- Key: JBIDE-6498 URL: https://jira.jboss.org/browse/JBIDE-6498 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.M1 Environment: Version: Helios Release, Build id: 20100616-2317 + JBT from svn r. 22872 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick -have JBossAS6-M3 with ws stack changed to JBossWS-metro-3.3.1GA -create a bottom-up ws in dynamic web project => after finishing a wizard error dialog says: error: Could not find class file for s.S1 error Error: Could not generate. (use --show-traces to see full traces) Error: Wsgen invocation failed. Try the '-verbose' switch for more information after adding "--show-traces" to the command in Java2WSCommand the error message is less cryptic: error: Could not find class file for s.S 1 error Error: Could not generate. (use --show-traces to see full traces) java.lang.RuntimeException: Wsgen invocation failed. Try the '-verbose' switch for more information at org.jboss.wsf.stack.metro.tools.MetroProviderImpl.provide(MetroProviderImpl.java:195) at org.jboss.wsf.stack.metro.tools.MetroProviderImpl.provide(MetroProviderImpl.java:98) at org.jboss.wsf.spi.tools.cmd.WSProvide.generate(WSProvide.java:191) at org.jboss.wsf.spi.tools.cmd.WSProvide.main(WSProvide.java:79) -- 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
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6544) [Tester] Minor tweaks found while prepping for demo

by Brian Fitzpatrick (JIRA)

[Tester] Minor tweaks found while prepping for demo --------------------------------------------------- Key: JBIDE-6544 URL: https://jira.jboss.org/browse/JBIDE-6544 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.M1 Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Priority: Minor Fix For: 3.2.0.M1 While creating a demo script for the WS Tester for next week, I ran across a couple of minor issues. 1) JAX-RS body text was not being stripped of CRLF when submitted to a POST or PUT, causing issues. 2) Though the user could see the response headers, there wasn't a way for them to use them in another context (i.e. copy one to use elsewhere). -- 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-2704) Code completion of annotations in webbeans.xml

by Max Rydahl Andersen (JIRA)

Code completion of annotations in webbeans.xml ---------------------------------------------- Key: JBIDE-2704 URL: https://jira.jboss.org/jira/browse/JBIDE-2704 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: webbeans Reporter: Max Rydahl Andersen Fix For: LATER web-beans.xml should provide code completion for the relevant annotations in webbeans.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6785) "Partner Link Type" Chooser will not open after deleting a resource WSDL from bpelContent folder.

by Marek Baluch (JIRA)

"Partner Link Type" Chooser will not open after deleting a resource WSDL from bpelContent folder. ------------------------------------------------------------------------------------------------- Key: JBIDE-6785 URL: https://jira.jboss.org/browse/JBIDE-6785 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.1.1 Environment: JBDS 3.0.1.GA JBoss BPEL Editor v 1.0.0.v201003031622-27l-F9JgLWLLrLrXMgg Reporter: Marek Baluch Attachments: npe.txt How to reproduce ... 1) Open a BPEL project. 2) Delete a WSDL of some partner web service 3) open the .bpel file 4) click add partner link in "PartnerLinks" perspective ... 5) in properties window under Details tab click the Browse button. The error log shows: 1) Unhandled event loop exception: see attachment file npe.txt for the stack-trace 2) Resource platform:/resource/bpel_cxf_invoke/bpelContent/HelloWorld.wsdl is empty. (no stack-trace here) -- 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

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6523) beans.xml validation.

by Alexey Kazakov (JIRA)

beans.xml validation. --------------------- Key: JBIDE-6523 URL: https://jira.jboss.org/browse/JBIDE-6523 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.2.x For example we could validate if a decorator/interceptor/alternative declared in beans.xml exists. -- 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-6756) Run On Server on annotated servlet (3.0 spec) opens invalid url

by Snjezana Peco (JIRA)

Run On Server on annotated servlet (3.0 spec) opens invalid url --------------------------------------------------------------- Key: JBIDE-6756 URL: https://jira.jboss.org/browse/JBIDE-6756 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS, UpStream Affects Versions: 3.2.0.M1 Reporter: Snjezana Peco Assignee: Rob Stryker Steps to reproduce : - create JBoss AS 6.0 M4 runtime and server - create a Dynamic Web project with Web Module version 3.0 - add a servlet - right-click the servlet and call Run As>Run On Server Eclipse will open a url like : http://localhost:8080/<your_project_name>/servlet/<servletPackage>/<servelClassName> The correct URL is : http://localhost:8080/<your_project_name>/<yourServletMapping> <yourServletMapping> is defined when creating a servlet. It is defined as an annotation for Web Module 3.0 (@WebServlet) The problem can't be reproduced if servlet mappings is defined in web.xml. I think this is a webtools problem. Will create a bug against webtools and add a patch. I will also make a workaround that will work on JBoss Tools servers. -- 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

5
13
0 / 0

[JBoss JIRA] Created: (JBDS-1279) Wrong dialog opens when installing JBDS 4.0.0.M1

by Koen Aers (JIRA)

Wrong dialog opens when installing JBDS 4.0.0.M1 ------------------------------------------------ Key: JBDS-1279 URL: https://jira.jboss.org/browse/JBDS-1279 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 4.0.0.M1 Environment: OSX 10.5.8 Reporter: Koen Aers Fix For: 4.0.0.M1 Attachments: jbds-installer-step3.png When installing JBDS 4.0.0.M1 I noticed that during step 3 clicking the 'Browse...' button results in opening a selection dialog for the Java VM instead of a dialog to select the installation location. -- 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

6
12
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