January 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-2070) SOA Modeler

by Mark Little (JIRA)

SOA Modeler ----------- Key: JBIDE-2070 URL: http://jira.jboss.com/jira/browse/JBIDE-2070 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: esb Reporter: Mark Little Thomas Erl donated IP to us around the SOA Modeler. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
9
0 / 0

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

4
17
0 / 0

[JBoss JIRA] Created: (JBIDE-7309) Testing a direct-to-source mapping errors out

by Brian Fitzpatrick (JIRA)

Testing a direct-to-source mapping errors out ---------------------------------------------- Key: JBIDE-7309 URL: https://jira.jboss.org/browse/JBIDE-7309 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.2.0.Beta2 Reporter: Brian Fitzpatrick Assignee: Tom Fennelly Fix For: 3.2.0.Beta2 While playing with some ideas, I tried using the Smooks Run Configuration for testing a XML-to-XML mapping. And I don't think I've done anything too wacky, but I'm getting some interesting results when I try to test the configuration. Any ideas? I'll attach the config, input, and output XML files... Oct 11, 2010 12:22:58 PM freemarker.log.JDK14LoggerFactory$JDK14Logger error SEVERE: Error on line 4, column 15 in free-marker-template Expecting a string, date or number here, Expression .vars["PERIODIC_TABLE"]["ATOM/NAME"] is instead a freemarker.ext.dom.NodeListModel The problematic instruction: ---------- ==> ${.vars["PERIODIC_TABLE"]["ATOM/NAME"]} [on line 4, column 13 in free-marker-template] ---------- Java backtrace for programmers: ---------- freemarker.core.NonStringException: Error on line 4, column 15 in free-marker-template Expecting a string, date or number here, Expression .vars["PERIODIC_TABLE"]["ATOM/NAME"] is instead a freemarker.ext.dom.NodeListModel at freemarker.core.Expression.getStringValue(Expression.java:126) at freemarker.core.Expression.getStringValue(Expression.java:93) at freemarker.core.DollarVariable.accept(DollarVariable.java:76) at freemarker.core.Environment.visit(Environment.java:208) at freemarker.core.MixedContent.accept(MixedContent.java:92) at freemarker.core.Environment.visit(Environment.java:208) at freemarker.core.Environment.process(Environment.java:188) at freemarker.template.Template.process(Template.java:232) at org.milyn.templating.freemarker.FreeMarkerTemplateProcessor.applyTemplate(FreeMarkerTemplateProcessor.java:356) at org.milyn.templating.freemarker.FreeMarkerTemplateProcessor.applyTemplate(FreeMarkerTemplateProcessor.java:349) at org.milyn.templating.freemarker.FreeMarkerTemplateProcessor.visitAfter(FreeMarkerTemplateProcessor.java:327) at org.milyn.delivery.sax.SAXHandler.visitAfter(SAXHandler.java:389) at org.milyn.delivery.sax.SAXHandler.endElement(SAXHandler.java:204) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.milyn.delivery.sax.SAXParser.parse(SAXParser.java:57) at org.milyn.delivery.sax.SmooksSAXFilter.doFilter(SmooksSAXFilter.java:75) at org.milyn.delivery.sax.SmooksSAXFilter.doFilter(SmooksSAXFilter.java:61) at org.milyn.Smooks._filter(Smooks.java:519) at org.milyn.Smooks.filterSource(Smooks.java:488) at org.milyn.Smooks.filterSource(Smooks.java:462) at org.jboss.tools.smooks.launch.SmooksLauncher.main(SmooksLauncher.java:81) Exception in thread "main" org.milyn.SmooksException: Failed to filter source. at org.milyn.delivery.sax.SmooksSAXFilter.doFilter(SmooksSAXFilter.java:86) at org.milyn.delivery.sax.SmooksSAXFilter.doFilter(SmooksSAXFilter.java:61) at org.milyn.Smooks._filter(Smooks.java:519) at org.milyn.Smooks.filterSource(Smooks.java:488) at org.milyn.Smooks.filterSource(Smooks.java:462) at org.jboss.tools.smooks.launch.SmooksLauncher.main(SmooksLauncher.java:81) Caused by: org.milyn.SmooksException: Failed to apply FreeMarker template to fragment 'PERIODIC_TABLE'. Resource: Target Profile: [[org.milyn.profile.profile#default_profile]], Selector: [#document], Selector Namespace URI: [null], Resource: [<?xml version="1.0" encoding="UTF-8"?> <html> <section> <h1>${.vars["PERIODIC_TABLE"]["ATOM/NAME"]}</h1> <p>${.vars["PERIODIC_TABLE"]["ATOM/SYMBOL"]}</p> <p>${.vars["PERIODIC_TABLE"]["ATOM/ATOMIC_NUMBER"]}</p> <p>${.vars["PERIODIC_TABLE"]["ATOM/ATOMIC_WEIGHT"]}</p> </section> </html>], Num Params: [4] at org.milyn.templating.freemarker.FreeMarkerTemplateProcessor.applyTemplate(FreeMarkerTemplateProcessor.java:359) at org.milyn.templating.freemarker.FreeMarkerTemplateProcessor.applyTemplate(FreeMarkerTemplateProcessor.java:349) at org.milyn.templating.freemarker.FreeMarkerTemplateProcessor.visitAfter(FreeMarkerTemplateProcessor.java:327) at org.milyn.delivery.sax.SAXHandler.visitAfter(SAXHandler.java:389) at org.milyn.delivery.sax.SAXHandler.endElement(SAXHandler.java:204) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.milyn.delivery.sax.SAXParser.parse(SAXParser.java:57) at org.milyn.delivery.sax.SmooksSAXFilter.doFilter(SmooksSAXFilter.java:75) ... 5 more Caused by: freemarker.core.NonStringException: Error on line 4, column 15 in free-marker-template Expecting a string, date or number here, Expression .vars["PERIODIC_TABLE"]["ATOM/NAME"] is instead a freemarker.ext.dom.NodeListModel at freemarker.core.Expression.getStringValue(Expression.java:126) at freemarker.core.Expression.getStringValue(Expression.java:93) at freemarker.core.DollarVariable.accept(DollarVariable.java:76) at freemarker.core.Environment.visit(Environment.java:208) at freemarker.core.MixedContent.accept(MixedContent.java:92) at freemarker.core.Environment.visit(Environment.java:208) at freemarker.core.Environment.process(Environment.java:188) at freemarker.template.Template.process(Template.java:232) at org.milyn.templating.freemarker.FreeMarkerTemplateProcessor.applyTemplate(FreeMarkerTemplateProcessor.java:356) ... 19 more -- 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, 11 months

6
33
0 / 0

[JBoss JIRA] Created: (JBIDE-6828) Provide actions to open AS/EAP/SOA-P specific management apps

by Lukas Jungmann (JIRA)

Provide actions to open AS/EAP/SOA-P specific management apps ------------------------------------------------------------- Key: JBIDE-6828 URL: https://jira.jboss.org/browse/JBIDE-6828 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Reporter: Lukas Jungmann Assignee: Rob Stryker It would be nice if a user would be able to open ie JBoss jmx console within embedded browser in the IDE through some specific action on the server node in the server view. List of apps worth to have some specific action: -jmx console -administration console -jbossws app there might be others I'm not aware of but first two from the list are IMO the most important ones See attached screenshot for how this looks like in Glassfish plugin -- 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, 11 months

10
13
0 / 0

[JBoss JIRA] Created: (JBIDE-7969) Empty error message from KB validator

by Max Andersen (JIRA)

Empty error message from KB validator ------------------------------------- Key: JBIDE-7969 URL: https://issues.jboss.org/browse/JBIDE-7969 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Reporter: Max Andersen Assignee: Alexey Kazakov Fix For: 3.2.0.CR1 Not sure what triggered it but got about 10 of these in my error log: The error message is empty in the error log view; only the stack trace reveals details. org.eclipse.jface.text.BadLocationException at org.eclipse.jface.text.ListLineTracker.getLineNumberOfOffset(ListLineTracker.java:140) at org.eclipse.jface.text.AbstractLineTracker.getLineNumberOfOffset(AbstractLineTracker.java:161) at org.eclipse.jface.text.AbstractDocument.getLineOfOffset(AbstractDocument.java:915) at org.eclipse.core.internal.filebuffers.SynchronizableDocument.getLineOfOffset(SynchronizableDocument.java:398) at org.jboss.tools.jst.web.kb.internal.validation.ValidationErrorManager.addError(ValidationErrorManager.java:223) at org.jboss.tools.jst.web.kb.internal.validation.ValidationErrorManager.addError(ValidationErrorManager.java:259) at org.jboss.tools.jst.web.kb.internal.validation.ValidationErrorManager.addError(ValidationErrorManager.java:175) at org.jboss.tools.jst.web.kb.internal.validation.ValidationErrorManager.addError(ValidationErrorManager.java:126) at org.jboss.tools.jst.web.kb.internal.validation.ValidationErrorManager.addError(ValidationErrorManager.java:140) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateInjectionPoint(CDICoreValidator.java:1213) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateBean(CDICoreValidator.java:440) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateAll(CDICoreValidator.java:268) at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateAll(ValidatorManager.java:116) at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateInJob(ValidatorManager.java:81) at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-8046) org.jboss.tools.ws.creation.core.test has 5 test failures/errors

by Nick Boldt (JIRA)

org.jboss.tools.ws.creation.core.test has 5 test failures/errors ---------------------------------------------------------------- Key: JBIDE-8046 URL: https://issues.jboss.org/browse/JBIDE-8046 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.CR1 Reporter: Nick Boldt Assignee: Brian Fitzpatrick Failed tests: testDeployResult(org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest) testDeployResult(org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest) Tests in error: testInitialClientCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) testClientCodeGenerationCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) testRemoveClientJarsCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Tests run: 7, Failures: 2, Errors: 3, Skipped: 0 http://hudson.qa.jboss.com/hudson/job/jbosstools-3.2_trunk.component--ws/... http://hudson.qa.jboss.com/hudson/job/jbosstools-3.2_trunk.component--ws/... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

6
14
0 / 0

[JBoss JIRA] Created: (JBIDE-7143) JBossWS project facet is not added to the project after creating sample web service

by Lukas Jungmann (JIRA)

JBossWS project facet is not added to the project after creating sample web service ----------------------------------------------------------------------------------- Key: JBIDE-7143 URL: https://jira.jboss.org/browse/JBIDE-7143 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.M2 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick -create a new dynamic web project without any special facet -create new sample web service there using JBT wizard -open project properties -> project facets => JBossWS project facet is not checked - should it be ckecked or not? -- 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, 11 months

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-8280) Content assist for JSF 2 should not add managed beans annotated with @ManagedBean when faces-config@metadata-complete="true" in WEB-INF/faces-config.xml

by Denis Golovin (JIRA)

Content assist for JSF 2 should not add managed beans annotated with @ManagedBean when faces-config@metadata-complete="true" in WEB-INF/faces-config.xml -------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8280 URL: https://issues.jboss.org/browse/JBIDE-8280 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF Affects Versions: 3.2.0.CR1, 3.3.0.M1 Reporter: Denis Golovin Assignee: Alexey Kazakov Fix For: 3.3.x According faces-config 2.0 scheme: "Attribute : metadata-complete The metadata-complete attribute defines whether this JavaServer Faces application is complete, or whether the class files available to this module and packaged with this application should be examined for annotations that specify configuration information. This attribute is only inspected on the application configuration resource file located at "WEB-INF/faces-config.xml". The presence of this attribute on any application configuration resource other than the one located at "WEB-INF/faces-config.xml", including any files named using the javax.faces.CONFIG_FILES attribute, must be ignored. If metadata-complete is set to "true", the JavaServer Faces runtime must ignore any annotations that specify configuration information, which might be present in the class files of the application. If metadata-complete is not specified or is set to "false", the JavaServer Faces runtime must examine the class files of the application for annotations, as specified by the specification. If "WEB-INF/faces-config.xml" is not present, the JavaServer Faces runtime will assume metadata-complete to be "false". The value of this attribute will have no impact on runtime annotations such as @ResourceDependency or @ListenerFor. Data Type : boolean Enumerated Values : - true - false" -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6138) create an import wizard for the jBPM3 examples

by Koen Aers (JIRA)

create an import wizard for the jBPM3 examples ---------------------------------------------- Key: JBIDE-6138 URL: https://jira.jboss.org/jira/browse/JBIDE-6138 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jbpm Reporter: Koen Aers Assignee: Koen Aers Fix For: 3.1.1, 3.1.x, 3.2.next -- 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

13 years, 11 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-8195) Support Seam Solder extensions.

by Alexey Kazakov (JIRA)

Support Seam Solder extensions. ------------------------------- Key: JBIDE-8195 URL: https://issues.jboss.org/browse/JBIDE-8195 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Alexey Kazakov 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, 11 months

3
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 January 2011