May 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-8639) CDI support on MAC doesn't work with non-system encodings

by Ilya Dyoshin (JIRA)

CDI support on MAC doesn't work with non-system encodings ---------------------------------------------------------- Key: JBIDE-8639 URL: https://issues.jboss.org/browse/JBIDE-8639 Project: Tools (JBoss Tools) Issue Type: Bug Environment: MAC (with russian locale and default encoding set with MacCyrillic ) Jboss Tools and Eclipse with workspace configured for use UTF-8 Maven CDI-JSF application Reporter: Ilya Dyoshin When my workspace uses the same encoding as the system (in my case MacCyrillic) - everything works fine (except that my application uses lots of russian symbols, which became non-usable, 'cause my maven application is using utf-8 ) When I switch either the workspace or project encoding to UTF-8 I'm receiving following error: !ENTRY org.eclipse.core.resources 4 75 2011-03-28 22:57:25.354 !MESSAGE Errors occurred during the build. !SUBENTRY 1 org.jboss.tools.cdi.core 4 75 2011-03-28 22:57:25.354 !MESSAGE Errors running builder 'CDI (Context and Dependency Injection) Builder' on project 'lex-maven'. !STACK 0 java.lang.StringIndexOutOfBoundsException: String index out of range: -72 at java.lang.String.substring(String.java:1937) at org.jboss.tools.cdi.internal.core.impl.definition.MethodDefinition.loadParamDefinitions(MethodDefinition.java:88) at org.jboss.tools.cdi.internal.core.impl.definition.MethodDefinition.init(MethodDefinition.java:64) at org.jboss.tools.cdi.internal.core.impl.definition.AbstractMemberDefinition.setAnnotatable(AbstractMemberDefinition.java:50) at org.jboss.tools.cdi.internal.core.impl.definition.MethodDefinition.setMethod(MethodDefinition.java:49) at org.jboss.tools.cdi.internal.core.impl.definition.TypeDefinition.init(TypeDefinition.java:62) at org.jboss.tools.cdi.internal.core.impl.definition.AbstractMemberDefinition.setAnnotatable(AbstractMemberDefinition.java:50) at org.jboss.tools.cdi.internal.core.impl.definition.AbstractTypeDefinition.setType(AbstractTypeDefinition.java:54) at org.jboss.tools.cdi.internal.core.scanner.CDIBuilderDelegate.build(CDIBuilderDelegate.java:56) at org.jboss.tools.cdi.core.CDICoreBuilder.incrementalBuild(CDICoreBuilder.java:202) at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:161) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:629) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:172) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:203) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:255) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:258) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:311) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:343) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:242) 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

14 years, 10 months

5
18
0 / 0

[JBoss JIRA] Created: (JBIDE-8590) Widget is disposed error in deltacloud tools

by Rob Stryker (JIRA)

Widget is disposed error in deltacloud tools -------------------------------------------- Key: JBIDE-8590 URL: https://issues.jboss.org/browse/JBIDE-8590 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.Final Reporter: Rob Stryker Assignee: Andre Dietisheim Fix For: 3.2.1 Use case is as follows: 1) Define one (or two) connections in Cloud Viewer 2) Open Images view 3) Rename cloud connection, verify changes in Image view 4) Close Image View 5) Open Image View 6) Rename cloud connection EXPECTED: Cloud renames properly RESULT: Widget is disposed error Stack trace is as follows: org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(SWT.java:4083) at org.eclipse.swt.SWT.error(SWT.java:3998) at org.eclipse.swt.SWT.error(SWT.java:3969) at org.eclipse.swt.widgets.Widget.error(Widget.java:466) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:403) at org.eclipse.swt.widgets.Combo.getSelectionIndex(Combo.java:1025) at org.jboss.tools.deltacloud.ui.views.cloudelements.AbstractCloudElementTableView$4.run(AbstractCloudElementTableView.java:371) at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:179) at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150) at org.eclipse.swt.widgets.Display.syncExec(Display.java:4282) at org.jboss.tools.deltacloud.ui.views.cloudelements.AbstractCloudElementTableView.updateCloudSelector(AbstractCloudElementTableView.java:366) at org.jboss.tools.deltacloud.ui.views.cloudelements.AbstractCloudElementTableView.propertyChange(AbstractCloudElementTableView.java:359) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:339) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:347) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:276) at org.jboss.tools.internal.deltacloud.core.observable.ObservablePojo.firePropertyChange(ObservablePojo.java:29) at org.jboss.tools.deltacloud.core.DeltaCloud.setName(DeltaCloud.java:208) at org.jboss.tools.deltacloud.core.DeltaCloud.updateName(DeltaCloud.java:122) at org.jboss.tools.deltacloud.core.DeltaCloud.update(DeltaCloud.java:102) at org.jboss.tools.internal.deltacloud.ui.wizards.EditCloudConnectionWizard.performFinish(EditCloudConnectionWizard.java:46) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-8979) jpdl3 node selection properties view not updated

by erik van altena (JIRA)

jpdl3 node selection properties view not updated ------------------------------------------------ Key: JBIDE-8979 URL: https://issues.jboss.org/browse/JBIDE-8979 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.2.0.Final Environment: eclipse helios SR2, WindowsXP 32 bits Reporter: erik van altena Assignee: Koen Aers Since JBoss Tools 3.2 / Eclipse Helios, selecting a node in the JBPM 3 jPdl editor does not update the Eclipse properties view, which means you cannot edit the properties of the selected node. Neither does anything change when you select the background of the editor (which would normally allow you to change the properties of the process). Making node selections in the Eclipse outline view does work however. A clean installation of Eclipse did not change anything. The behavior is seen in already existing definitions (created with older JBoss Tools versions) as well as in newly created definitions. This behavior is not observed when using JBoss Tools 3.1 / Eclipse Ganymede. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

5
15
0 / 0

[JBoss JIRA] Created: (JBIDE-8798) org.jboss.tools.cdi.ui.test.CDIUIAllTests.testDeleteAllInjectedConstructorsResolution failure

by Alexey Kazakov (JIRA)

org.jboss.tools.cdi.ui.test.CDIUIAllTests.testDeleteAllInjectedConstructorsResolution failure --------------------------------------------------------------------------------------------- Key: JBIDE-8798 URL: https://issues.jboss.org/browse/JBIDE-8798 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.1.M1 Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.2.1.M1 Error Message Marker resolution did not decrease number of problems. was: 5 now: 5 Stacktrace junit.framework.AssertionFailedError: Marker resolution did not decrease number of problems. was: 5 now: 5 at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.jboss.tools.cdi.ui.test.marker.CDIMarkerResolutionTest.checkResolution(CDIMarkerResolutionTest.java:108) at org.jboss.tools.cdi.ui.test.marker.CDIMarkerResolutionTest.checkResolution(CDIMarkerResolutionTest.java:50) at org.jboss.tools.cdi.ui.test.marker.CDIMarkerResolutionTest.testDeleteAllInjectedConstructorsResolution(CDIMarkerResolutionTest.java:357) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-8191) 2010 in the copyright headers should be replaced by 2011

by Lukas Jungmann (JIRA)

2010 in the copyright headers should be replaced by 2011 -------------------------------------------------------- Key: JBIDE-8191 URL: https://issues.jboss.org/browse/JBIDE-8191 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.2.0.CR1 Reporter: Lukas Jungmann applies to all JBT features (JMX, Hibernate Tools, ESB Tools...) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (JBDS-1602) Web Service Tester generates SOAP bodies that cause marshaling issues

by Bill Meyer (JIRA)

Web Service Tester generates SOAP bodies that cause marshaling issues --------------------------------------------------------------------- Key: JBDS-1602 URL: https://issues.jboss.org/browse/JBDS-1602 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Affects Versions: 4.0.0.GA Environment: JBoss Developer Studio 4.0.0 on Mac OS X 10.6.6 Reporter: Bill Meyer Open JBDS 4, go to Window -> Show View -> Other -> Web Service Tester. If I enter my WSDL and select the appropriate Service, Port, and Operation (there's only 1), the SOAP Body gets filled in as: <?xml version="1.0" encoding="utf-8" standalone="yes" ?> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" > <soap:Body> <getStockQuoteBySymbol xmlns = "http://www.jboss.com/webservices/StockQuoteService"> <arg0>?</arg0> </getStockQuoteBySymbol> </soap:Body> </soap:Envelope> which seems to cause the operation invocation to choke with a NullPointerException. It appears to be a problem with unmarshalling on the Web Service side. Interesting note is that soapUI causes the same behavior when I copy the above SOAP envelope into soapUI and execute the call. If I change the SOAP envelope by moving the operation namespace to the top of the XML body: <?xml version="1.0" encoding="utf-8" standalone="yes" ?> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:stoc = "http://www.jboss.com/webservices/StockQuoteService" > <soap:Body> <stoc:getStockQuoteBySymbol> <arg0>?</arg0> </stoc:getStockQuoteBySymbol> </soap:Body> </soap:Envelope> Everything executes perfectly. So, I am assuming that the Web Service Tester is generating a SOAP Body that results in a failed web service invocation. I've tried this with a few different web services (String and float args) and they all fail the same. I am trying to invoke a JAX-WS based web service. I have tried an ASMX-based web service up on webservicex.net (http://www.webservicex.net/stockquote.asmx?WSDL) and not had the same issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
32
0 / 0

[JBoss JIRA] Created: (JBIDE-8804) [tester] NPE in the log while working with the tester

by Lukas Jungmann (JIRA)

[tester] NPE in the log while working with the tester ------------------------------------------------------ Key: JBIDE-8804 URL: https://issues.jboss.org/browse/JBIDE-8804 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.1.M1 Environment: jbdevstudio-product-eap-linux-gtk-4.1.0.v201104171649R-H346-M1.jar Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick Not sure about exact steps to reproduce this yet but in the log there can be found: Exception in thread "Timer-5" java.lang.NullPointerException at org.jboss.tools.ws.ui.views.WSDLBrowseDialog.validateLocation(WSDLBrowseDialog.java:176) at org.jboss.tools.ws.ui.views.WSDLBrowseDialog.access$6(WSDLBrowseDialog.java:175) at org.jboss.tools.ws.ui.views.WSDLBrowseDialog$2$1.run(WSDLBrowseDialog.java:223) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (JBIDE-8608) ESB Tooling Needs Drools' Object Mapping Property

by Brad Davis (JIRA)

ESB Tooling Needs Drools' Object Mapping Property ------------------------------------------------- Key: JBIDE-8608 URL: https://issues.jboss.org/browse/JBIDE-8608 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: esb Affects Versions: 3.2.0.CR1 Reporter: Brad Davis Assignee: Brian Fitzpatrick Property "object-paths" needs to be provided in the Drools' content based router. Example: <action class="org.jboss.soa.esb.actions.ContentBasedRouter" name="cbr-router"> <property name="cbrAlias" value="Drools"/> <property name="ruleSet" value="/META-INF/drools/airport-code.drl"/> <property name="ruleLanguage"/> <property name="destinations"> <route-to destination-name="ERROR" service-category="com.example.soa" service-name="error-service"/> <route-to destination-name="SUCCESS" service-category="com.example.soa" service-name="successful-record"/> </property> <property name="object-paths"> <object-path esb="body.'org.jboss.soa.esb.message.defaultEntry'" /> </property> </action> This currently requires that you jump into XML view to add the required property object-paths. Otherwise, only the Message object is mapped into the rule context. This should be provided in the ContentBasedRouter UI in JBoss Tools if possible. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-8956) Make Conditional Transitions Illegal if they are Leaving a Node that is not a Decision Node

by Koen Aers (JIRA)

Make Conditional Transitions Illegal if they are Leaving a Node that is not a Decision Node ------------------------------------------------------------------------------------------- Key: JBIDE-8956 URL: https://issues.jboss.org/browse/JBIDE-8956 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jbpm Affects Versions: 3.2.1.M1, 3.3.0.M1 Reporter: Koen Aers Assignee: Koen Aers Fix For: 3.2.1.CR1, 3.3.0.M2 This request is related to SOA-2010. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
14
0 / 0

[JBoss JIRA] Created: (JBIDE-8330) JBPM 3 process definiton wizard creates files with new (JBPM 4?) naming convention

by joe freeman (JIRA)

JBPM 3 process definiton wizard creates files with new (JBPM 4?) naming convention ----------------------------------------------------------------------------------- Key: JBIDE-8330 URL: https://issues.jboss.org/browse/JBIDE-8330 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.2.0.CR1 Reporter: joe freeman Assignee: Koen Aers We just upgraded to the 3.2.0 JBoss JBPM editing tools and the behavior has changed for the definition creation wizard. It looks like the JBPM 3 wizard now creates files with the JBPM 4 naming convention.It used to create files with the name gpd.xml, processdefinition.xml and processimage.jpg. Now it creates files with <def_name>.jpdl.xml, process.jpg and .<def_name>.gpd.xml. This broke our file system loader code and we can't find any release notes or Jira tickets that describe why or when this change was made. Was this change on purpose -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

5
10
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 May 2011