April 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6079) Creating Sample Web service fails on Java Project

by Libor Zoubek (JIRA)

Creating Sample Web service fails on Java Project ------------------------------------------------- Key: JBIDE-6079 URL: https://jira.jboss.org/jira/browse/JBIDE-6079 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.GA Reporter: Libor Zoubek Attachments: .log When I create Jboss Tools->Sample Web Service and the only project in my workspace is classic java project, errors in log appear 1. Use clean workspace 2. Create 'Java Project' 3. Try to create 'Jboss Tools->Sample Web Service' by selecting it in tree. 4. Errors in log appear and you can't even click "Next >' Truth is, that maybe it does not make real sense, to create web service in Java Project, but this should not happen. I'll attach log -- 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, 4 months

5
23
0 / 0

[JBoss JIRA] Created: (JBIDE-6175) Cannot create JbossWS on EAP 4.2

by Libor Zoubek (JIRA)

Cannot create JbossWS on EAP 4.2 -------------------------------- Key: JBIDE-6175 URL: https://jira.jboss.org/jira/browse/JBIDE-6175 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.1.0.GA Reporter: Libor Zoubek Assignee: Brian Fitzpatrick Attachments: .log I am not able to generate web service client stubs on eap 4.2. btw there is no direct support for eap 4.2 runtime. One can add only eap 4.3 runtime or jboss-as 4.2. I am getting error with stacktrace: IWAB0014E Unexpected exception occurred. java.lang.NullPointerException at org.jboss.tools.ws.creation.core.commands.ClientSampleCreationCommand.findJavaUnitsByAnnotation(ClientSampleCreationCommand.java:310) at org.jboss.tools.ws.creation.core.commands.ClientSampleCreationCommand.execute(ClientSampleCreationCommand.java:80) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419) Steps to reporoduce: 1. Get eap-4.2 (e.g. from pokchop) 2. Add eap-4.2 as eap 4.3 runtime or jboss-as 4.2 runtime 3. Create dynamic web project 4. Create web service client (to enter valid wsdl url you might need to create some webservice) Reproducible : always -- 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, 4 months

5
21
0 / 0

[JBoss JIRA] Created: (JBIDE-5715) Dynamic Web Service Project Wizard

by Burr Sutter (JIRA)

Dynamic Web Service Project Wizard ---------------------------------- Key: JBIDE-5715 URL: https://jira.jboss.org/jira/browse/JBIDE-5715 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Reporter: Burr Sutter Attachments: New_WS_Project.pdf See attached document -- 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, 4 months

5
25
0 / 0

[JBoss JIRA] Created: (JBIDE-5538) Contract First Web Service Fails to deploy

by Burr Sutter (JIRA)

Contract First Web Service Fails to deploy ------------------------------------------ Key: JBIDE-5538 URL: https://jira.jboss.org/jira/browse/JBIDE-5538 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Environment: jbdevstudio-win32-3.0.0.v200912111227M-H41-RC1 Windows Vista 64-bit Java 1.6 Reporter: Burr Sutter I tried to use the New Web Service Wizard (I think it comes from WTP) to create a new WS endpoint starting from WSDL. The attached PDF shows the "workflow" that I choose. When you get to the end, it builds an EAR (Why? an EAR is not necessary), deploys it but it throws up an error and the WS endpoint is not properly deployed. -- 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, 4 months

4
15
0 / 0

[JBoss JIRA] Created: (JBIDE-5035) Add support for the option "--extension" in wsconsume command

by Denny Xu (JIRA)

Add support for the option "--extension" in wsconsume command -------------------------------------------------------------- Key: JBIDE-5035 URL: https://jira.jboss.org/jira/browse/JBIDE-5035 Project: Tools (JBoss Tools) Issue Type: Task Components: Webservices Affects Versions: 3.1.0.M3 Reporter: Denny Xu Assignee: Denny Xu Fix For: 3.1.0.M4 since JBossAS 5.0, the JBossWS JAX-WS tools command has a new option "--extension", it used to enable SOAP 1.2 binding extension, JBoss tools should provide a UI to support the option when generating web service code from wsdl. -- 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, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-4257) cannot create top down java bean web service

by Gina Kim (JIRA)

cannot create top down java bean web service -------------------------------------------- Key: JBIDE-4257 URL: https://jira.jboss.org/jira/browse/JBIDE-4257 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS, Webservices Environment: Windows XP, Eclipse 3.4.1, JBoss 4.2.3, JBossWS 3.1.0, JDK 1.5 Reporter: Gina Kim I get this error when I try to create a top down web service using a valid wsdl: Error: Could not import. (use --verbose to see full traces) Error: WsImport invocation failed. Try the verbose switch for more information To reproduce the error, I navigated to File > New > Other > Web Service. I selected JBossWS for Web service runtime. -- 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, 4 months

9
26
0 / 0

[JBoss JIRA] Created: (JBIDE-5703) Hibernate Reverse Engineering Editor should show multiple catalogs/schemas from a MySQL database

by Pieter Hartog (JIRA)

Hibernate Reverse Engineering Editor should show multiple catalogs/schemas from a MySQL database ------------------------------------------------------------------------------------------------ Key: JBIDE-5703 URL: https://jira.jboss.org/jira/browse/JBIDE-5703 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.1.0.CR1 Reporter: Pieter Hartog Priority: Minor MySQL is funny with catalogs and schemas. It doesn't support schemas like most other databases do. It's just called 'databases'. When you try to create a reveng.xml file using the Hibernate Reverse Engineering Editor, you can't get multiple databases / schemas to show up. It looks like the wizard looks at the hibernate.connection.url property in the hibernate-console.properties file. However, when I leave out the name of the database (e.g. jdbc:mysql://localhost:3306) without the database, the wizard does not return any tables. When you leave out the default database (i.e. schema) name in the connection.url, you should see all databases/ schemas for that one connection. When a user selects multiple schemas, the resulting reveng.xml file should have one <schema-selection ...> element for each schema the user wants to map tables from. -- 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, 4 months

5
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5826) Incorrect work of EL and CDI validator for action Validate

by Viacheslav Kabanovich (JIRA)

Incorrect work of EL and CDI validator for action Validate ---------------------------------------------------------- Key: JBIDE-5826 URL: https://jira.jboss.org/jira/browse/JBIDE-5826 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.CR1 Reporter: Viacheslav Kabanovich Assignee: Alexey Kazakov Fix For: 3.1.0.CR2 1. Switch off automatic build. 2. Create 2 seam projects. 3. Build them manually. 4. Open an xhtml of the first project. 5. Add some correct EL in it, and run Validate on that file. 6. Repeat that several times corrupting and fixing EL and running Validate to make sure that it is ok. 7. Open an xhtml of the second project. 8. Try to do the same as with the first xhtml. Make sure that action Validate does not work. 9. Return to the first xhtml. Make sure that action Validate works. It looks like action Validate works only for the project on which it was run first. -- 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, 4 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5799) CDI Validator fails with BadLocationException

by Alexey Kazakov (JIRA)

CDI Validator fails with BadLocationException --------------------------------------------- Key: JBIDE-5799 URL: https://jira.jboss.org/jira/browse/JBIDE-5799 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.CR2 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.1.0.CR2 Add such producer field to any CDI bean: @Produces @Typed(String.class) private Integer i = new Integer(0); Force CDI validation (build the project). See eclipse log: org.eclipse.jface.text.BadLocationException at org.eclipse.jface.text.TreeLineTracker.fail(TreeLineTracker.java:1061) at org.eclipse.jface.text.TreeLineTracker.lineByOffset(TreeLineTracker.java:271) at org.eclipse.jface.text.TreeLineTracker.getLineNumberOfOffset(TreeLineTracker.java:1143) at org.eclipse.jface.text.AbstractLineTracker.getLineNumberOfOffset(AbstractLineTracker.java:161) at org.eclipse.jface.text.AbstractDocument.getLineOfOffset(AbstractDocument.java:881) at org.eclipse.core.internal.filebuffers.SynchronizableDocument.getLineOfOffset(SynchronizableDocument.java:398) at org.jboss.tools.jst.web.kb.internal.validation.ValidationErrorManager.addError(ValidationErrorManager.java:182) at org.jboss.tools.jst.web.kb.internal.validation.ValidationErrorManager.addError(ValidationErrorManager.java:119) at org.jboss.tools.jst.web.kb.internal.validation.ValidationErrorManager.addError(ValidationErrorManager.java:133) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateBean(CDICoreValidator.java:263) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateResource(CDICoreValidator.java:223) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validate(CDICoreValidator.java:179) at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validate(ValidatorManager.java:92) at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateInJob(ValidatorManager.java:75) at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) The resoun of this execption is that ITypedDeclaration returns start position == -1 for String.class -- 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, 4 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5747) IllegalArgumentException is thrown during CDI validation.

by Alexey Kazakov (JIRA)

IllegalArgumentException is thrown during CDI validation. --------------------------------------------------------- Key: JBIDE-5747 URL: https://jira.jboss.org/jira/browse/JBIDE-5747 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.1.0.CR2 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.1.0.CR2 java.lang.IllegalArgumentException at org.eclipse.jdt.core.Signature.appendTypeSignature(Signature.java:2371) at org.eclipse.jdt.core.Signature.appendTypeSignature(Signature.java:2278) at org.eclipse.jdt.core.Signature.toCharArray(Signature.java:2257) at org.jboss.tools.common.model.util.EclipseJavaUtil.resolveTypeAsString(EclipseJavaUtil.java:50) at org.jboss.tools.cdi.internal.core.impl.definition.ParametedTypeFactory.getParametedType(ParametedTypeFactory.java:18) at org.jboss.tools.cdi.internal.core.impl.AbstractBeanElement.getRestrictedTypeDeclaratios(AbstractBeanElement.java:133) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateBean(CDICoreValidator.java:246) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateAll(CDICoreValidator.java:197) at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateAll(ValidatorManager.java:99) at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateInJob(ValidatorManager.java:78) at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) org.eclipse.jdt.core.Signature.toCharArray() is supposed to get a singnature but CDI model gives a type name instead of signature. -- 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, 4 months

3
2
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 April 2010