August 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6380) Specializing bean should inherit the qualifiers and name of specialized bean.

by Alexey Kazakov (JIRA)

Specializing bean should inherit the qualifiers and name of specialized bean. ----------------------------------------------------------------------------- Key: JBIDE-6380 URL: https://jira.jboss.org/browse/JBIDE-6380 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: @Mock @Specializes public class MockAsynchronousService extends AsynchronousService { ... } @Default @Asynchronous @Named("asyncService") public class AsynchronousService implements Service{ ... } then MockAsynchronousService inherits the qualifiers and name of AsynchronousService. See 4.3 section of the spec. All the tests of org.jboss.tools.cdi.core.test.tck.BeanSpecializationTest JUnit 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-6436) Managed bean class must have a constructor with no parameters, or the class must declare a constructor annotated @Inject.

by Alexey Kazakov (JIRA)

Managed bean class must have a constructor with no parameters, or the class must declare a constructor annotated @Inject. ------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-6436 URL: https://jira.jboss.org/browse/JBIDE-6436 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 Following class is not a managed bean and should not to be included in CDI model: public class Parrot implements Bird { public Parrot(String name) {} } org.jboss.tools.cdi.core.test.tck.ResolutionByTypeTest.testBeanTypesOnManagedBean() 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
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6703) QueryExporter should be added into Exporters in Hibernate Code Generation Configurations

by Vitali Yemialyanchyk (JIRA)

QueryExporter should be added into Exporters in Hibernate Code Generation Configurations ---------------------------------------------------------------------------------------- Key: JBIDE-6703 URL: https://jira.jboss.org/browse/JBIDE-6703 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.2.0.M1 Reporter: Vitali Yemialyanchyk Assignee: Max Rydahl Andersen 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, 6 months

3
21
0 / 0

[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

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