May 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-8325) Injection point should be re-validated automatically if any bean with the same bean type created.

by Alexey Kazakov (JIRA)

Injection point should be re-validated automatically if any bean with the same bean type created. ------------------------------------------------------------------------------------------------- Key: JBIDE-8325 URL: https://issues.jboss.org/browse/JBIDE-8325 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.0.CR1 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M1 1. Create ITestBean interface. 2. Create public class TestBeanImpl implements ITestBean {...} 3. Add @Inject ITestBean foo; field to any bean but TestBeanImpl. 4. Validate the project. @Inject ITestBean foo; is valid since there is the only bean TestBeanImpl to be injected. 5. Create public class TestBeanImpl2 implements ITestBean {...}. Save the file, build the project (using the incremental builder). 6. @Inject ITestBean foo; is not valid anymore because there are two beans TestBeanImpl and TestBeanImpl2 to be injected. But CDI validator doesn't re-validate @Inject ITestBean foo; We have to change/validate the file with the injection to re-validate it and have a marker on this invalid injection. Slava, let's add IInjectionPoint getInjections(String fullyQuilifeidTypeName); method to IBeanManager interface and its implementation. Then assign the issue to me and I will fix this bug in CDI validator. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-8265) Let

by Denis Golovin (JIRA)

Let --- Key: JBIDE-8265 URL: https://issues.jboss.org/browse/JBIDE-8265 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Denis Golovin -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6768) Migrate CDI/Seam/EL validators (KB Validation framwork) to WST validation V2.

by Alexey Kazakov (JIRA)

Migrate CDI/Seam/EL validators (KB Validation framwork) to WST validation V2. ----------------------------------------------------------------------------- Key: JBIDE-6768 URL: https://jira.jboss.org/browse/JBIDE-6768 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.2.x Now we use V1. V2 has some improvements. For instance we can use Validation->Settings page for include/exclude rules. This framework is being developed yet but seems to be stable enough. -- 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

14 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBIDE-8933) Check if there are any problems with VPE on Eclipse 3.7.M7

by Yahor Radtsevich (JIRA)

Check if there are any problems with VPE on Eclipse 3.7.M7 ---------------------------------------------------------- Key: JBIDE-8933 URL: https://issues.jboss.org/browse/JBIDE-8933 Project: Tools (JBoss Tools) Issue Type: Task Components: Visual Page Editor core, Visual Page Editor Templates Affects Versions: 3.3.0.M1 Reporter: Yahor Radtsevich Assignee: Denis Maliarevich Fix For: 3.3.0.M1 Please, test VPE on Eclipse 3.7.M7 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-6619) VPE Resizer is not shown on XULRunner 1.9.2

by Yahor Radtsevich (JIRA)

VPE Resizer is not shown on XULRunner 1.9.2 ------------------------------------------- Key: JBIDE-6619 URL: https://jira.jboss.org/browse/JBIDE-6619 Project: Tools (JBoss Tools) Issue Type: Bug Components: aop Affects Versions: 3.2.0.M2 Environment: XULRunner 1.9.2 Reporter: Yahor Radtsevich Assignee: Yahor Radtsevich Fix For: 3.2.0.M2 Compare screenshots on both versions of XULRunner: 1.9.1 and 1.9.2 (screenshots.png). -- 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

14 years, 9 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-8794) Smooks editor does't work with Abstract classes

by Ganesh Puri (JIRA)

Smooks editor does't work with Abstract classes ----------------------------------------------- Key: JBIDE-8794 URL: https://issues.jboss.org/browse/JBIDE-8794 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: smooks Affects Versions: 3.2.0.Final, 3.1.1, 3.1.0.GA, 3.0.3.GA, 3.0.2.GA, 3.0.1.GA, 3.0.0.GA, 2.1.2, 2.1.1, 2.1.0.GA, 2.0.1, 2.0.0.GA Reporter: Ganesh Puri Assignee: Brian Fitzpatrick When you have an abstract class and couple of extended classes e.g. one abstract Address class and couple of extended classes say AddressStructured and AddressFreeForm, the smooks editor doesn't parse it. The error shown on the Smooks Processing screen is "Check Input Task configuration.Error creating Input Model from Sample Input Data. Error: "Error build project classpath." -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-8885) Cannot add a new Task Node if a Processing Task node is not properly selected

by Tom Fennelly (JIRA)

Cannot add a new Task Node if a Processing Task node is not properly selected ----------------------------------------------------------------------------- Key: JBIDE-8885 URL: https://issues.jboss.org/browse/JBIDE-8885 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.2.1.M1 Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 3.2.1.CR1 AddNextTaskNodeAction.addFreemarkerTemplateTask just returns if a node is not properly selected on the Processing Tasks canvas -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
6
0 / 0

[JBoss JIRA] Created: (JBIDE-9026) Separate specific runtime detection plugins from base core

by Max Rydahl Andersen (JIRA)

Separate specific runtime detection plugins from base core ----------------------------------------------------------- Key: JBIDE-9026 URL: https://issues.jboss.org/browse/JBIDE-9026 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: runtimes Affects Versions: 3.3.0.M2 Reporter: Max Rydahl Andersen Assignee: Snjezana Peco Priority: Blocker JBoss Runtime detection should not assume all plugins are available especially with drools and jbpm plugins being separated out for SOA pack. Copied from JBIDE-8456: 2. org.jboss.tools.runtime It contains a plugin that implements the JBoss AS, Drools, Seam and jBPM detectors and depends on AS, Drools, jBPM, Seam and JBoss Runtime Detection Core. The problem was because JBDS installer detection wasn't separating AS runtime within EAP, EPP, SOA-P ... from Seam, Drools, jBPM runtimes. I have inherited that code. Because of that, all these detectors are included in the org.jboss.tools.runtime plugin. If we want to separate those dependencies, we need to do the following: separate the Drools, Seam, jBPM detectors from the AS/EAP/EPP/SOA-P detector move runtime detectors to separated features (the AS, Drools, jBPM, Seam, ESB feature or some new features) change the JBDS installer detection code according to these changes As to optional dependencies, P2 treats them as hard dependencies. If IU exists, P2 will install it no matter if it is optional or not. Currently only the drools dependency is optional. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-8188) Runtimes preferences page has wrong layout

by Denis Golovin (JIRA)

Runtimes preferences page has wrong layout ------------------------------------------ Key: JBIDE-8188 URL: https://issues.jboss.org/browse/JBIDE-8188 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.2.0.CR1 Reporter: Denis Golovin Fix For: 3.3.x All groups should have name and should be stretched by width -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6942) Prompt for Basic Auth when accessing secured WSDL

by Juergen Zimmermann (JIRA)

Prompt for Basic Auth when accessing secured WSDL ------------------------------------------------- Key: JBIDE-6942 URL: https://jira.jboss.org/browse/JBIDE-6942 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Affects Versions: 3.2.0.M1 Reporter: Juergen Zimmermann Assignee: Brian Fitzpatrick A SOAP based Web Service can be defined as follows: @WebService(name = "MyService") @WebContext(contextRoot = "/myRoot", authMethod = "BASIC", secureWSDLAccess = true) @EndpointConfig(configName = "Standard WSSecurity Endpoint") Now the WSDL cannot be accessed without BASIC authentication. Therefore, it would be fine, if you could provide a checkbox within the dialog "Select WSDL", so that username and password could be prompted. Just as the checkbox below "Request details" in the main window. -- 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

14 years, 9 months

3
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 May 2011