July 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6257) Remove Wizards wich dublicate WTP wizards

by Maxim Areshkau (JIRA)

Remove Wizards wich dublicate WTP wizards ----------------------------------------- Key: JBIDE-6257 URL: https://jira.jboss.org/jira/browse/JBIDE-6257 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml source editing Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: 3.2.next Remove Wizards wich dublicate WTP wizards. For example WTP provide dublicate wizard and we provide such wizard too. So it's duplicated. -- 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, 7 months

6
19
0 / 0

[JBoss JIRA] Created: (JBIDE-6353) Changing SoapAction in Process service WSDL causes BPEL Validator to report an error

by Jeff DeLong (JIRA)

Changing SoapAction in Process service WSDL causes BPEL Validator to report an error ------------------------------------------------------------------------------------ Key: JBIDE-6353 URL: https://jira.jboss.org/browse/JBIDE-6353 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: bpm Environment: latest JB Tools Nightly Build on Mac Reporter: Jeff DeLong Changing SoapAction value in Process service WSDL causes BPEL Validator to report an error. Description Resource Path Location Type <bpel:receive> activity "ReceivePolicyQuoteRequest" specifies a portType "orchws:PolicyQuoteProcessServicePortType", yet this portType does not match the portType derived from "myRole" of partnerLink "PolicyQuoteProcessService" defined in WSDL "platform:/resource/PolicyQuoteProcessService/bpelContent/PolicyQuoteProcessService.wsdl" PolicyQuoteProcess.bpel /PolicyQuoteProcessService/bpelContent line 61 BPEL Validation Marker Description Resource Path Location Type variable "PolicyQuoteRequest" of type "<wsdl:message "PolicyQuoteProcessServiceReq">" is not compatible with WSDL message "<wsdl:message "PolicyQuoteProcessServiceReq">". PolicyQuoteProcess.bpel /PolicyQuoteProcessService/bpelContent line 61 BPEL Validation Marker Rebuilding the project does not make the error go away. The BPEL Validator appears to be too sensitive to changes in the WSDL. The SoapAction is not relevant to the BPEL process definition, changing it should not cause errors. In particular, the PortType did not change (the binding changed). -- 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
7
0 / 0

[JBoss JIRA] Created: (JBIDE-3875) Provide content assist for faset@name attribute based on parent JSF tag metadata

by Denis Golovin (JIRA)

Provide content assist for faset@name attribute based on parent JSF tag metadata -------------------------------------------------------------------------------- Key: JBIDE-3875 URL: https://jira.jboss.org/jira/browse/JBIDE-3875 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF Affects Versions: 3.0.0.GA Reporter: Denis Golovin Assignee: Alexey Kazakov Fix For: 3.1.0 -- 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, 7 months

4
19
0 / 0

[JBoss JIRA] Created: (JBIDE-4064) Quick Fix for Seam validation problems.

by Alexey Kazakov (JIRA)

Quick Fix for Seam validation problems. --------------------------------------- Key: JBIDE-4064 URL: https://jira.jboss.org/jira/browse/JBIDE-4064 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Seam Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.1.0 -- 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, 7 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-6031) Implement CDIProject.getBeans(boolean attemptToResolveAmbiguousDependency, IType beanType, IType... qualifiers)

by Alexey Kazakov (JIRA)

Implement CDIProject.getBeans(boolean attemptToResolveAmbiguousDependency, IType beanType, IType... qualifiers) --------------------------------------------------------------------------------------------------------------- Key: JBIDE-6031 URL: https://jira.jboss.org/jira/browse/JBIDE-6031 Project: Tools (JBoss Tools) Issue Type: Task Components: cdi (jsr-299) Affects Versions: 3.1.0.CR2 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.2.next See CDIProject.getBeans(boolean attemptToResolveAmbiguousDependency, IType beanType, IType... qualifiers) and CDIProject.getBeans(boolean attemptToResolveAmbiguousDependency, String fullQualifiedBeanType, String... fullQualifiedQualifiersTypes) Following tests should pass: org.jboss.tools.cdi.core.test.tck.BeanDefinitionTest.testBeanTypesNonEmpty() org.jboss.tools.cdi.core.test.tck.BeanDefinitionTest.testQualifiersNonEmpty() org.jboss.tools.cdi.core.test.tck.BeanDefinitionTest.testHasScopeType() org.jboss.tools.cdi.core.test.tck.BeanDefinitionTest.testPrivitiveTypes() -- 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, 7 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6073) Bean class should inherit qualifiers annotated as @Inherited

by Alexey Kazakov (JIRA)

Bean class should inherit qualifiers annotated as @Inherited ------------------------------------------------------------ Key: JBIDE-6073 URL: https://jira.jboss.org/jira/browse/JBIDE-6073 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.1.0.GA Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.2.next See JSR-299 spec. Section 4.1 Tests: QualifierDefinitionTest.testQualifierDeclaredInheritedIsInherited() QualifierDefinitionTest.testQualifierNotDeclaredInheritedIsNotInherited QualifierDefinitionTest.testQualifierDeclaredInheritedIsBlockedByIntermediateClass() QualifierDefinitionTest.testQualifierDeclaredInheritedIsIndirectlyInherited() -- 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, 7 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6147) Scope type for directly extended managed bean annotated @Inherited should be inherited.

by Alexey Kazakov (JIRA)

Scope type for directly extended managed bean annotated @Inherited should be inherited. --------------------------------------------------------------------------------------- Key: JBIDE-6147 URL: https://jira.jboss.org/jira/browse/JBIDE-6147 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 Suppose a class X is extended directly or indirectly by the bean class of a managed bean or session bean Y. If X is annotated with a scope type Z then Y inherits the annotation if and only if Z declares the @Inherited meta-annotation and neither Y nor any intermediate class that is a subclass of X and a superclass of Y declares a scope type See JSR-299 Spec. 4.1. Inheritance of type-level metadata org.jboss.tools.cdi.core.test.tck.ScopeDefinitionTest.testScopeTypeDeclaredInheritedIsInherited() must pass. -- 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, 7 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6146) Wrong default scope for CDI bean.

by Alexey Kazakov (JIRA)

Wrong default scope for CDI bean. --------------------------------- Key: JBIDE-6146 URL: https://jira.jboss.org/jira/browse/JBIDE-6146 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 bean must have javax.enterprise.context.Dependent default scope: package org.jboss.jsr299.tck.tests.definition.scope; class Order{} org.jboss.tools.cdi.core.test.tck.ScopeDefinitionTest.testDefaultScope() must pass. See JSR-299 Spec: 2.4.4. Default scope When no scope is explicitly declared by annotating the bean class or producer method or field the scope of a bean is defaulted. The default scope for a bean which does not explicitly declare a scope depends upon its declared stereotypes: • If the bean does not declare any stereotype with a declared default scope, the default scope for the bean is @Dependent. • If all stereotypes declared by the bean that have some declared default scope have the same default scope, then that scope is the default scope for the bean. • If there are two different stereotypes declared by the bean that declare different default scopes, then there is no default scope and the bean must explicitly declare a scope. If it does not explicitly declare a scope, the container automatically detects the problem and treats it as a definition error. If a bean explicitly declares a scope, any default scopes declared by stereotypes are ignored. -- 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, 7 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6151) Scope Type declared @Inherited should be blocked by intermediate scope type which is not marked @Inherited

by Alexey Kazakov (JIRA)

Scope Type declared @Inherited should be blocked by intermediate scope type which is not marked @Inherited ---------------------------------------------------------------------------------------------------------- Key: JBIDE-6151 URL: https://jira.jboss.org/jira/browse/JBIDE-6151 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: class GoldenLabrador extends Labrador {} @NotInheritedScope class Labrador extends Dog {} @RequestScoped class Dog {} @RequestScoped is marked @Inherited but @NotInheritedScope is not. Then GoldenLabrador should have javax.enterprise.context.Dependent scope type. org.jboss.tools.cdi.core.test.tck.ScopeDefinitionTest.testScopeTypeDeclaredInheritedIsBlockedByIntermediateScopeTypeNotMarkedInherited() must pass. -- 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, 7 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6196) CDI model doesn't load observer methods.

by Alexey Kazakov (JIRA)

CDI model doesn't load observer methods. ---------------------------------------- Key: JBIDE-6196 URL: https://jira.jboss.org/jira/browse/JBIDE-6196 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: class Spider { public void observe(@Observes Event foo) { } } destorySpider is a observer method since it has a parameter is anootated @Observers. org.jboss.tools.cdi.core.test.tck.ValidationTest.testProducerMethodWithParameterAnnotatedObserves() must pass. -- 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, 7 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 July 2010