November 2009 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-4955) Option to exclude files from deploying

by Adrian Mitev (JIRA)

Option to exclude files from deploying -------------------------------------- Key: JBIDE-4955 URL: https://jira.jboss.org/jira/browse/JBIDE-4955 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Affects Versions: 3.1.0.M3 Reporter: Adrian Mitev Assignee: Rob Stryker Hi! I would like to exclude .jsfdia files from being deployed. I know that i can exclude the files from the java builder, but this doesn't work for WebContent directory. -- 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

16 years, 4 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-5249) Drop support Smooks v1.0

by Xue Peng (JIRA)

Drop support Smooks v1.0 ------------------------ Key: JBIDE-5249 URL: https://jira.jboss.org/jira/browse/JBIDE-5249 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Xue Peng Assignee: Xue Peng Fix For: 3.1.0.CR1 The new Smooks editor will not support Smooks v1.0 -- 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

16 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5258) Remove the need for the <graphic> configs in the Smooks config

by Tom Fennelly (JIRA)

Remove the need for the <graphic> configs in the Smooks config -------------------------------------------------------------- Key: JBIDE-5258 URL: https://jira.jboss.org/jira/browse/JBIDE-5258 Project: Tools (JBoss Tools) Issue Type: Task Components: smooks Reporter: Tom Fennelly Assignee: Xue Peng Fix For: 3.1.0.CR1 All of this info can be stored in the global <params> section of the Smooks config, removing the need for the extra config namespace. This JIRA depends on another JIRA that Dart is working on (but I can't find) wrt to using the Smooks config namespaces to work out what nodes are on the process graph. After resolving that JIRA, we're only left with input config and node layout info in the <graphics> section, which can all be stored in one or more <param> elements in the <params> section. -- 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

16 years, 4 months

4
12
0 / 0

[JBoss JIRA] Created: (JBIDE-5271) Apply Template bindings not saved in Smooks Config XML

by Brian Fitzpatrick (JIRA)

Apply Template bindings not saved in Smooks Config XML ------------------------------------------------------ Key: JBIDE-5271 URL: https://jira.jboss.org/jira/browse/JBIDE-5271 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Reporter: Brian Fitzpatrick Assignee: Tom Fennelly Fix For: 3.1.0.GA With the latest fixes delivered to add CSV template mapping, I noticed that the XML for the configuration doesn't get updated when you drag/drop from the Java Classes to the CSV Template model. And because it's not updating the XML, it's not saving the changes and the mappings are not persisted when you reopen the configuration. This appears to be caused by a NPE in the "addMappings" method of the CSVFreeMarkerTemplateBuilder class. Tom, any ideas how to fix this? Here's the exception: java.lang.NullPointerException at java.io.StringReader.<init>(StringReader.java:33) at org.jboss.template.csv.CSVFreeMarkerTemplateBuilder.addMappings(CSVFreeMarkerTemplateBuilder.java:81) at org.jboss.template.csv.CSVFreeMarkerTemplateBuilder.<init>(CSVFreeMarkerTemplateBuilder.java:74) at org.jboss.tools.smooks.graphical.editors.SmooksFreemarkerTemplateGraphicalEditor$FreemarkerTemplateConnectionModelFactory.fillMapping(SmooksFreemarkerTemplateGraphicalEditor.java:385) at org.jboss.tools.smooks.graphical.editors.SmooksFreemarkerTemplateGraphicalEditor$FreemarkerTemplateConnectionModelFactory.createConnection(SmooksFreemarkerTemplateGraphicalEditor.java:260) at org.jboss.tools.smooks.graphical.editors.SmooksGraphicalEditorPart.createConnection(SmooksGraphicalEditorPart.java:820) at org.jboss.tools.smooks.graphical.editors.SmooksGraphicalEditorPart.createConnection(SmooksGraphicalEditorPart.java:917) at org.jboss.tools.smooks.graphical.editors.SmooksGraphicalEditorPart.createConnection(SmooksGraphicalEditorPart.java:923) at org.jboss.tools.smooks.graphical.editors.SmooksGraphicalEditorPart.createConnection(SmooksGraphicalEditorPart.java:923) at org.jboss.tools.smooks.graphical.editors.SmooksGraphicalEditorPart.createConnectionModel(SmooksGraphicalEditorPart.java:782) at org.jboss.tools.smooks.graphical.editors.SmooksGraphicalEditorPart.initGraphicalModel(SmooksGraphicalEditorPart.java:755) at org.jboss.tools.smooks.graphical.editors.SmooksGraphicalEditorPart.initializeGraphicalViewer(SmooksGraphicalEditorPart.java:1012) at org.eclipse.gef.ui.parts.GraphicalEditor.createGraphicalViewer(GraphicalEditor.java:153) at org.eclipse.gef.ui.parts.GraphicalEditor.createPartControl(GraphicalEditor.java:163) at org.jboss.tools.smooks.graphical.editors.SmooksGraphicalEditorPart.createPartControl(SmooksGraphicalEditorPart.java:210) at org.jboss.tools.smooks.graphical.editors.SmooksProcessGraphicalEditor.createTaskPage(SmooksProcessGraphicalEditor.java:981) at org.jboss.tools.smooks.graphical.editors.SmooksProcessGraphicalEditor.showTaskControl(SmooksProcessGraphicalEditor.java:941) at org.jboss.tools.smooks.graphical.editors.SmooksProcessGraphicalEditor$2.selectionChanged(SmooksProcessGraphicalEditor.java:340) at org.eclipse.zest.core.viewers.GraphViewer$1.widgetSelected(GraphViewer.java:96) at org.eclipse.zest.core.widgets.Graph.fireWidgetSelectedEvent(Graph.java:723) at org.eclipse.zest.core.widgets.Graph.access$4(Graph.java:715) at org.eclipse.zest.core.widgets.Graph$DragSupport.mousePressed(Graph.java:682) at org.eclipse.draw2d.Figure.handleMousePressed(Figure.java:873) at org.eclipse.draw2d.SWTEventDispatcher.dispatchMousePressed(SWTEventDispatcher.java:214) at org.eclipse.draw2d.LightweightSystem$EventHandler.mouseDown(LightweightSystem.java:513) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:179) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287) -- 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

16 years, 4 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-5191) ESB Editor - linking in other editors where appropriate

by Brian Fitzpatrick (JIRA)

ESB Editor - linking in other editors where appropriate ------------------------------------------------------- Key: JBIDE-5191 URL: https://jira.jboss.org/jira/browse/JBIDE-5191 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: esb Affects Versions: 3.1.0.M4 Reporter: Brian Fitzpatrick Assignee: Viacheslav Kabanovich Fix For: 3.1.0.CR1 New JIRA to deal with requirement "Developer Tools: Linking Editors" in the SOA-P PRD. >From the ESB editor, depending on the action used, the user has to currently open any associated editor manually to edit particular files, such as jboss-smooks.xml from the SmooksAction. This is a usability hit. It would be nice if, like in the Eclipse Plug-in/Manifest editor, the text beside the field for the file would show up as a hyperlink that the user could click to open the file in the associated editor. So in the SmooksAction case, the "Smooks Config:" label would become a hyperlink that would open the Smooks editor for the file referenced in the field. Product management is looking to link: Smooks editor Drools editor jPDL editor XSLT editor (once it gets added) Groovy editor (if added by the end-user) Would this be possible for JBDS 3? -- 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

16 years, 4 months

3
23
0 / 0

[JBoss JIRA] Created: (JBIDE-5248) can't find the port from bpel-deploy.xml editor

by Feng Qian (JIRA)

can't find the port from bpel-deploy.xml editor ----------------------------------------------- Key: JBIDE-5248 URL: https://jira.jboss.org/jira/browse/JBIDE-5248 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpm Affects Versions: 3.1.0.M4 Reporter: Feng Qian Assignee: Feng Qian Fix For: 3.1.0.M4 open a bpel-deploy.xml using the ode deploy file editor, click the port combo box of a service. can't get the ports list. -- 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

16 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-4922) Create portletbridge archetypes to work with JBoss Tools and m2eclipse

by Snjezana Peco (JIRA)

Create portletbridge archetypes to work with JBoss Tools and m2eclipse ---------------------------------------------------------------------- Key: JBIDE-4922 URL: https://jira.jboss.org/jira/browse/JBIDE-4922 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Portal, UpStream Affects Versions: 3.1.0.M3 Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 3.1.0.M4 -- 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

16 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-4345) HtmlAllTests/testJBIDE3280 failing and not possible to run standalone

by Max Rydahl Andersen (JIRA)

HtmlAllTests/testJBIDE3280 failing and not possible to run standalone --------------------------------------------------------------------- Key: JBIDE-4345 URL: https://jira.jboss.org/jira/browse/JBIDE-4345 Project: Tools (JBoss Tools) Issue Type: Task Components: Visual Page Editor core Reporter: Max Rydahl Andersen Assignee: Yahor Radtsevich Priority: Blocker Fix For: 3.1.0.M1 http://hudson.jboss.org/hudson/view/JBossTools/job/jbosstools-nightly-3.1... HtmlAllTests.testJBIDE3280 Failing for the past 9 builds (Since #173 ) Took 11 sec. Error Message Stacktrace java.lang.NullPointerException at org.jboss.tools.vpe.html.test.jbide.JBIDE3280Test.testJBIDE3280(JBIDE3280Test.java:66) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) I tried to run it but i'm getting a IllegalArgument in setup: java.lang.IllegalArgumentException at org.eclipse.ui.part.FileEditorInput.<init>(FileEditorInput.java:92) at org.jboss.tools.vpe.html.test.jbide.JBIDE3280Test.testJBIDE3280(JBIDE3280Test.java:49) How do you run this test standalone ? -- 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

16 years, 4 months

4
26
0 / 0

[JBoss JIRA] Created: (JBDS-890) JBDS 2.1 GA, Seam 2.2, and Drools Integration

by Gary Lamperillo (JIRA)

JBDS 2.1 GA, Seam 2.2, and Drools Integration --------------------------------------------- Key: JBDS-890 URL: https://jira.jboss.org/jira/browse/JBDS-890 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 2.1.0 Environment: EAP 5 , Seam 2.2, Drools 5, BRMS Reporter: Gary Lamperillo When integrating drools into Seam there are 2 compliation errors: >Description Resource Path Location Type The project was not built since its build path is incomplete. Cannot find the class file for org.drools.runtime.rule.WorkingMemoryEntryPoint. Fix the build path then try building this project SeamwithRules-ejb Unknown Java Problem >Description Resource Path Location Type The type org.drools.runtime.rule.WorkingMemoryEntryPoint cannot be resolved. It is indirectly referenced from required .class files CreditRunBean.java SeamwithRules-ejb/ejbModule/org/domain/seamwithrules/session line 33 Java Problem I will attach the components.xml and the source file. It appears that the WorkingMemoryEntryPoint can not be found. I tried bringing in enternal drools jars, but it did not help -- 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

16 years, 4 months

4
14
0 / 0

[JBoss JIRA] Created: (JBIDE-4872) Multiple issues with New hbm.xml wizard

by Max Rydahl Andersen (JIRA)

Multiple issues with New hbm.xml wizard --------------------------------------- Key: JBIDE-4872 URL: https://jira.jboss.org/jira/browse/JBIDE-4872 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.1.0.M3 Reporter: Max Rydahl Andersen Assignee: Dmitry Geraskov Priority: Critical Fix For: 3.1.0.M4 Attachments: hbmxmlwizardsuggestion.png Now that I can actual run the new hbm.xml wizard to completion here are a couple of issues/annoyances: 1) There are *zero* instructions in the wizard making it rather hard for the user to actual know what is going on. - first page shows a tree with no instructions of what you expect the user to do - second page shows a list that can be bigger than what were selected on the first page, with no explanation on what this extra page means and there does not seem to be any way of editing anything on this page ? - second page also shows a table with a (!) column that is for what ? 2) The first page does not take the current selection into account - i.e. if I select class Test, press New hbm.xml wizard I still have to go through *alot* of folders to locate it again to have it selected 3) I still think this tree is a bad first thing to show since it is not scalable beyond example projects. How about having a table showing the list of classes to add and then have an Add/Remove button for the items ? (see attached file) 2) The generated files got various bad defaults: - the proxy attribute is set which indicates the model behind is build wrong. seems like you use the base name instead of the FQN. i.e. my.package.Product should be used instead of just Product - associations have fetch="select" set; that doesn't seem like the default we want to encourage! 3) (feature request) be able to specify the default identity strategy for int, long, etc. i.e. to avoid seeing "assigned" everywhere. -- 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

16 years, 4 months

3
14
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 2009