[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, 7 months
[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, 7 months
[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, 7 months