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