November 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-7093) [Web Service wizard] Error creating web service top down

by Brian Fitzpatrick (JIRA)

[Web Service wizard] Error creating web service top down -------------------------------------------------------- Key: JBIDE-7093 URL: https://jira.jboss.org/browse/JBIDE-7093 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.0.1.GA Reporter: Brian Fitzpatrick Assignee: Feng Qian Attachments: BuscarExpedientePorPkWS.wsdl, jbosstools-diagnostics-20100917171023.zip The steps the customer describes are: - Hi, I need to create a web service implementation from a given WSDL (attached). So, I created a dynamic web project and when using the create web service wizard using JBossWS, in the second step (after pressing 'next' twice) I got the following error: Failed to generate implementation class org.eclipse.core.runtime.CoreException: Failed to Generate Web Service code, please check the log for more details at org.jboss.tools.ws.creation.core.commands.ImplementationClassCreationCommand.getCompilationUnitForInterface(ImplementationClassCreationCommand.java:447) at org.jboss.tools.ws.creation.core.commands.ImplementationClassCreationCommand.generateImplClass(ImplementationClassCreationCommand.java:133) Darran tried both JBoss Enterprise AS 4.3.0CP06 & 5.0.1. -- 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

13 years, 12 months

4
17
0 / 0

[JBoss JIRA] Created: (JBIDE-9777) Seam config creates a duplicate bean

by Alexey Kazakov (JIRA)

Seam config creates a duplicate bean ------------------------------------ Key: JBIDE-9777 URL: https://issues.jboss.org/browse/JBIDE-9777 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI extensions Affects Versions: 3.3.0.M3 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M4 EXECUTE: Download/clone and install http://seamframework.org/Seam3/SecurityModule as an existing maven project. Make sure CDI support is enabled for the projects. EXECUTE: Open /seam-security-example-openid-rp/src/main/resources/META-INF/seam-beans.xml EXECUTE: Remove org.jboss.seam.security.external.openid.OpenIdRpInApplicationScopeProducer (line 25) to fix this XML. Save the file. FAILURE: There is a warning "A few beans (IdentityImpl) have the same EL name and the name is not resolvable [JSR-299 §5.3.1]" on /seam-security/src/main/java/org/jboss/seam/security/IdentityImpl.java IdentityImpl.java and seam-beans.xml are placed in different but dependent projects. In this case seam-security-example-openid-rp has two beans with the same name identity. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-9855) Infinite cycle in parsing seam-beans.xml

by Viacheslav Kabanovich (Created) (JIRA)

Infinite cycle in parsing seam-beans.xml ---------------------------------------- Key: JBIDE-9855 URL: https://issues.jboss.org/browse/JBIDE-9855 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI extensions Affects Versions: 3.3.0.M3 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M4 EXECUTE: Create Seam Config project. EXECUTE: Replace content of beans.xml (or seam-beans.xml) with text {code} <?xml version="1.0" encoding="UTF-8"?> </ {code} EXECUTE: Save file. FAILURE: Progress shows job building CDI model that sticks forever. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-9053) seam-registration examle from wolf test repo is incorrectly deployed

by Libor Zoubek (JIRA)

seam-registration examle from wolf test repo is incorrectly deployed --------------------------------------------------------------------- Key: JBIDE-9053 URL: https://issues.jboss.org/browse/JBIDE-9053 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.3.0.M1 Environment: JBossTools 3.3.0 M1 on top of indigo 3.7 M6a, org.eclipse.m2e.core (0.13.0.201103291237), org.maven.ide.eclipse.wtp (0.13.0.201103231111) Reporter: Libor Zoubek Assignee: Fred Bricon Fix For: 3.3.0.M2 I am testing wolf repository (maven repo of EAP 5.1). There are several example projects. These examples depend on maven artifacts shipped by wolf repo. There is a problem with example called webapp-seam-registration. This example can be built and deployed using maven CLI (mvn install jboss:deploy). But .. when I import it into JBoss Tools using 'Import existing maven project' and then deploy it on EAP 5.1 I get deployment errors. I was comparing the deoplyed EARs and found out, that the problem is, that component.xml (contained in registration-web project) is not deployed/added to archive. When deploying using mvn jboss:deploy components.xml gets into registration-ear.ear/jboss-seam-registration.war/WEB-INF but when deploying by JBossTools components.xml is missing there. I am not sure if it is a bug in tooling or bad configuraion in pom. I'll attach example project together with settings.xml for easy configuration. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

8
17
0 / 0

[JBoss JIRA] (JBIDE-10119) Filter project examples per compatible target runtime

by Fred Bricon (Created) (JIRA)

Filter project examples per compatible target runtime ----------------------------------------------------- Key: JBIDE-10119 URL: https://issues.jboss.org/browse/JBIDE-10119 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: project-examples Affects Versions: 3.3.0.M3 Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 3.3.0.Beta1 With the upcoming (40+) new Quickstarts , we'll need a way to filter project examples so as to not overwhelm the user with too much choice. We'd need : - a combobox with the list of all wtp runtimes found in all examples - selecting a runtime would filter compatible examples/quickstarts out - installed runtimes would be listed first -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-9685) Seam JMS: CDI validator should be aware of JMS resource injections

by Alexey Kazakov (JIRA)

Seam JMS: CDI validator should be aware of JMS resource injections ------------------------------------------------------------------ Key: JBIDE-9685 URL: https://issues.jboss.org/browse/JBIDE-9685 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: CDI extensions Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.0.M4 See http://docs.jboss.org/seam/3/jms/latest/reference/en-US/html/resource-inj... {code} The following JMS resources are now available for injection: javax.jms.Connection javax.jms.Session Destination-based resources: javax.jms.Topic javax.jms.Queue javax.jms.TopicPublisher javax.jms.QueueSender javax.jms.TopicSubscriber javax.jms.QueueReceiver {code} If an injection has any type from the list above and also it has a qualifier JmsDestination then it should be ignored by CDI validator. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-8942) Show Java Doc for relevant proposal in Seam Config code completion

by Alexey Kazakov (JIRA)

Show Java Doc for relevant proposal in Seam Config code completion ------------------------------------------------------------------ Key: JBIDE-8942 URL: https://issues.jboss.org/browse/JBIDE-8942 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: cdi (jsr-299) Affects Versions: 3.3.0.M1 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.x -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-9606) Null pointer exception when creating Top down Web Service

by Jaroslav Jankovič (JIRA)

Null pointer exception when creating Top down Web Service --------------------------------------------------------- Key: JBIDE-9606 URL: https://issues.jboss.org/browse/JBIDE-9606 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.3.0.M3 Reporter: Jaroslav Jankovič Assignee: Brian Fitzpatrick Fix For: 3.3.0.M3 Attachments: nullpointer.png There is a problem when creating top down web service from wsdl file. After selection wsdl file and click on Finish button, null pointer exception is thrown. If Next button and after that Finish Button is clicked, Web service is created properly. However Web Service should be created properly from main dialog too. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

5
31
0 / 0

[JBoss JIRA] Created: (JBIDE-9693) There is no way to delete remote hosts in System Deployment UI.

by Jaroslav Jankovič (JIRA)

There is no way to delete remote hosts in System Deployment UI. --------------------------------------------------------------- Key: JBIDE-9693 URL: https://issues.jboss.org/browse/JBIDE-9693 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Affects Versions: 3.3.0.M3 Reporter: Jaroslav Jankovič Assignee: Rob Stryker Fix For: 3.3.0.M4 1. double click on server in Servers view 2. in Server Behaviour, choose "Remote System Deployment" in combobox Adding new host can be done by click "New Host..." but removing added hosts cannot be done through this UI. In my opinion we should provide an easy way for removing hosts for remote deployment too. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

7
9
0 / 0

[JBoss JIRA] Created: (JBIDE-9496) [regression] - Exported files don't honor the module assembly settings

by Fred Bricon (JIRA)

[regression] - Exported files don't honor the module assembly settings ---------------------------------------------------------------------- Key: JBIDE-9496 URL: https://issues.jboss.org/browse/JBIDE-9496 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Environment: Vista, eclipse 3.5.1, JBT 3.1.CR1 Reporter: Fred Bricon Assignee: Rob Stryker I'm investigating ways to implement SAR support in m2eclipse (for selfish motivations I agree). See https://issues.sonatype.org/browse/MNGECLIPSE-1984. A SAR project would need to export dependencies in a lib folder, inside the archive. During my investigation, I tried to use the JBT 3.1.CR1 module assembly page, which would, from my understanding, allow me to reach the desired effect. So I've created sample maven-less projects : -sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The resulting org.eclipse.wst.common.component contains : {noformat} <project-modules id="moduleCoreId" project-version="1.5.0"> <wb-module deploy-name="sarproject"> <wb-resource deploy-path="/" source-path="/src"/> <dependent-module archiveName="junit.jar" deploy-path="/" handle="module:/classpath/var/JUNIT_HOME/junit.jar"> <dependency-type>uses</dependency-type> </dependent-module> </wb-module> </project-modules> {noformat} -earproject : needed so sarproject can be a Module project (which totally sucks). I've manually tweaked org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed. Here is the end result : {noformat} <project-modules id="moduleCoreId" project-version="1.5.0"> <wb-module deploy-name="earproject"> <wb-resource deploy-path="/" source-path="/EarContent"/> <dependent-module archiveName="sarproject.sar" deploy-path="/" handle="module:/resource/sarproject/sarproject"> <dependency-type>uses</dependency-type> </dependent-module> </wb-module> </project-modules> {noformat} Now, when exporting earproject.ear, there's no junit.jar to be found in sarproject.sar (not expected) nor in the ear (expected). When using export module on sarproject, the resulting file doesn't contain junit.jar either. This looks like a bug I've opened at eclipse's bugzilla for Connector projects : https://bugs.eclipse.org/bugs/show_bug.cgi?id=298735 The module assembly page looks very promising in theory, as it would allow support for any kind of archives (sar, har ...) but from what I understand it's only usable for ear and war projects. This bug should probably be opened at eclipse.org or is totally a duplicate of #298735 (you tell me), but I think the module assembly page should not be visible on unsupported projects. regards, Fred Bricon -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

6
19
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 November 2011