[JBoss JIRA] Created: (JBIDE-7776) CDI tools core doesn't take into account disabled beans while resolving beans.
by Alexey Kazakov (JIRA)
CDI tools core doesn't take into account disabled beans while resolving beans.
------------------------------------------------------------------------------
Key: JBIDE-7776
URL: https://jira.jboss.org/browse/JBIDE-7776
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.2.0.Beta2
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 3.2.0.CR1
5.1.2. Enabled and disabled beans
A bean is said to be enabled if:
• it is deployed in a bean archive, and
• it is not a producer method or field of a disabled bean, and
• it is not specialized by any other enabled bean, as defined in Section 4.3, "Specialization", and either
• it is not an alternative, or it is a selected alternative of at least one bean archive.
org.jboss.tools.cdi.core.test.tck.ResolutionByNameTest.testAmbiguousELNamesResolved() should pass.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBIDE-7932) New Seam EAR project fails to deploy to JBoss AS 6 CR1
by Jozef Hartinger (JIRA)
New Seam EAR project fails to deploy to JBoss AS 6 CR1
------------------------------------------------------
Key: JBIDE-7932
URL: https://issues.jboss.org/browse/JBIDE-7932
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.2.0.Beta2
Environment: Linux 64bit
JDK 1.6.0_23
JBoss Tools 3.2.0 Beta 2 (20101206)
Seam 2.2.1.CR2
Reporter: Jozef Hartinger
Assignee: Alexey Kazakov
Priority: Critical
Steps to reproduce:
1) Unzip JBoss AS 6 CR1
2) Add the server to JBoss Tools
3) Create new Seam 2.2 project (select EAR project and either HSQLDB or MySQL)
4) Start the application server
5) An exception is thrown during deployment of the project (see the attached file for the stacktrace)
Note that an WAR project deploys without problems. Also, and EAR or WAR project generated via seam-gen works as expected.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBIDE-8019) Injection point is not resolved to producer from jar.
by Alexey Kazakov (JIRA)
Injection point is not resolved to producer from jar.
-----------------------------------------------------
Key: JBIDE-8019
URL: https://issues.jboss.org/browse/JBIDE-8019
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.2.0.CR1
1. Project A has weld-se-core-1.1.0.Beta1-sources.jar in its class path.
2. weld-se-core-1.1.0.Beta1-sources.jar has ParametersFactory.class:
@Produces
@Parameters
public List<String> getArgs()
{
return argsList;
}
and Parameters.class:
@Qualifier
@Retention(RUNTIME)
@Target({ PARAMETER, METHOD, FIELD, TYPE })
public @interface Parameters {}
3. Project A also has the following class:
public class ShellImpl {
@Inject
@Parameters
private List<String> parameters;
}
4. But private List<String> parameters; is not resolved to getArgs() producer.
This example is from froge-shell (seam-forge) project.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBIDE-7681) Cannot create two or more web services in a web project
by Lukas Jungmann (JIRA)
Cannot create two or more web services in a web project
-------------------------------------------------------
Key: JBIDE-7681
URL: https://jira.jboss.org/browse/JBIDE-7681
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.2.0.Beta2
Reporter: Lukas Jungmann
Assignee: Brian Fitzpatrick
Priority: Critical
-create a new ear project ("Ear")
-create a new dynamic web project ("WsWar")
-create a top down ws from some wsdl using wtp wizard in WsWar project
- ws project WsWar, ear project Ear, server runtime JBossAS6.0, ws runtime JBossWS
-create another top down ws from different wsdl there
- ws project WsWar, ear project Ear, server runtime JBossAS6.0, ws runtime JBossWS
=> wizard ends with "The Web Service Name has been used in the web.xml of the web project." error message and doesn't allow user to finish it but all I'm trying to do is to create two completely different services in one project
message is comming from line 190 in org.jboss.tools.ws.creation.core.commands.MergeWebXMLCommand
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBIDE-7913) Top-Down ws wizard is overwriting existing unrelated ws impl classes
by Lukas Jungmann (JIRA)
Top-Down ws wizard is overwriting existing unrelated ws impl classes
--------------------------------------------------------------------
Key: JBIDE-7913
URL: https://issues.jboss.org/browse/JBIDE-7913
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.2.0.Beta2
Reporter: Lukas Jungmann
Assignee: Brian Fitzpatrick
this came up as a result of JBIDE-7681 (see comment from 12/15/10)
-create a new Dynamic web project
-create following interface there:
package x;
import javax.jws.WebService;
@WebService()
public interface Zws {
String test();
}
-create following class there:
package x;
import javax.jws.WebService;
@WebService()
public class ZwsImpl {
public String test() {
return "Hello Dolly!";
}
}
-create some Top-Down ws there using default settings package (use default package)
-open ZwsImpl.java in the editor
=>
Current: ZwsImpl class is rewritten
Expected: the class remains untouched
Note for myself: Check this also for Bottom up case
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months