December 2009 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-5369) Warning: attribute type type is declared more than once in element hotKey. is occured any time when call CA on xhtml pages.

by Anton Klimkovich (JIRA)

Warning: attribute type type is declared more than once in element hotKey. is occured any time when call CA on xhtml pages. --------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-5369 URL: https://jira.jboss.org/jira/browse/JBIDE-5369 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.0.3.GA Environment: jbdevstudio-eap-win32-2.1.1.v200911051555R-H173-GA Reporter: Anton Klimkovich Assignee: Alexey Kazakov Priority: Minor EXECUTE: Create Seam 2.2AP web project EXECUTE: Open any xhtml page EXECUTE: Call CA FAILURE: 1. Warning: attribute type onbeforedomupdate is declared more than once in element ajaxValidator. 2. Warning: attribute type type is declared more than once in element hotKey. -- 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, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5362) Allow bean wiring to be performed using drag and drop

by Tom Fennelly (JIRA)

Allow bean wiring to be performed using drag and drop ----------------------------------------------------- Key: JBIDE-5362 URL: https://jira.jboss.org/jira/browse/JBIDE-5362 Project: Tools (JBoss Tools) Issue Type: Task Components: smooks Reporter: Tom Fennelly Assignee: Xue Peng Fix For: 3.1.0.CR1, 3.1.0.GA Allow beans to be wired together using drag and drop from source class onto target bean property (including onto collections). Dart... I need your help with this one :) -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5311) Changes for the Java Bean Creation Wizard

by Brian Fitzpatrick (JIRA)

Changes for the Java Bean Creation Wizard ----------------------------------------- Key: JBIDE-5311 URL: https://jira.jboss.org/jira/browse/JBIDE-5311 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Affects Versions: 3.1.0.CR1 Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Fix For: 3.1.0.GA The Java Bean Creation wizard needs to be changed... See Tom's comments on http://www.jboss.org/community/wiki/GuidetotheRevisedSmooksConfigurationE... The comments say: "I think the Bean Creation Wizard should be simplified down to just "Java Class" and "Bean/Unique ID". If users want to manually create a top level collection of objects, they can create the collection object same as any other (selecting the collection type and giving it a beanId) and then wire the Object into the collection using drag & drop." So... 1) Change the wizard to be the "Java Class Creation" wizard 2) Change "Bean Class" to "Java Class" 3) Remove all other fields beyond "Bean Class" (change to "Java Class") and "Bean ID" -- 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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5359) v1.1 java bindings being added to configs.

by Tom Fennelly (JIRA)

v1.1 java bindings being added to configs. ------------------------------------------ Key: JBIDE-5359 URL: https://jira.jboss.org/jira/browse/JBIDE-5359 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Reporter: Tom Fennelly Fix For: 3.1.0.CR1, 3.1.0.GA Should be adding v1.2 version of binding configs. -- 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, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBDS-966) Getting Started Guide contains incorrect information on setting up included EAP 5.0 server

by Matt Davis (JIRA)

Getting Started Guide contains incorrect information on setting up included EAP 5.0 server ------------------------------------------------------------------------------------------ Key: JBDS-966 URL: https://jira.jboss.org/jira/browse/JBDS-966 Project: JBoss Developer Studio Issue Type: Bug Components: Doc - JBossAS Affects Versions: 2.1.0 Reporter: Matt Davis The JBDS 2.1 'Getting Started wtih JBoss Developer Studio' document includes instructions on installing EAP 5.0 during the JBDS installation. JBDS 2.1 did not ship with an EAP release because the EAP 5.0 GA release was not ready at the time. Section 1.4 still has a slide of step 5 of the installation which includes the option to install JBoss EAP. This slide needs to be updated to show the actual step 5 of the JBDS 2.1 installation , which does not include the option to instll JBDS. -- 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, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5329) New JBoss icons scaled badly

by Max Rydahl Andersen (JIRA)

New JBoss icons scaled badly ---------------------------- Key: JBIDE-5329 URL: https://jira.jboss.org/jira/browse/JBIDE-5329 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Reporter: Max Rydahl Andersen Assignee: Rob Stryker Fix For: 3.1.0.CR1 See attached screenshot - the icon is pixelated more than it should. If we don't have one that is scaled properly we should get one made/requested. Let me know :) -- 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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-4369) Issues with BIRT classloader

by Snjezana Peco (JIRA)

Issues with BIRT classloader ---------------------------- Key: JBIDE-4369 URL: https://jira.jboss.org/jira/browse/JBIDE-4369 Project: Tools (JBoss Tools) Issue Type: Bug Components: birt, UpStream Affects Versions: 3.0.0.GA Reporter: Snjezana Peco Assignee: Snjezana Peco Steps to reproduce: 1) create a new Seam Web Project with the "BIRT Reporting Runtime Component" facet 2) call "Generates Seam Entities" and create some entities 3) create a BIRT report 4) restart Eclipse 5) add JBoss Hibernate Data Source and click Test Connection You will get the "Could not create JPA based Configuration" error (Problem 1). Attached is log1.txt If you build a session factory using the Hibernate Configuration view in the Hibernate perspective, you will be able to create a data source (5) and data set(6) 6) create Hibernate Data Set 7) call the Previews Result tab in the Edit Data Set dialog 8) call "Generate Seam Entities" and click "Refresh" on the second page of the wizard You will get the "<Couldn't connect to Database>" error (Problem 2). 9) try to open *.xhtml file using the VPE editor You will get an error (attached log2.txt). Sometimes Eclipse freezes (Problem 3). There are two issues related to the BIRT engine: - https://bugs.eclipse.org/bugs/show_bug.cgi?id=258574 I have created a patch for this issue. - an issue in DataSetEditor.ItemModelHandler. BIRT sets a context classloader in this class, but doesn't revert the old context classloader. The issue exists in BIRT 2.3.1 and BIRT 2.5.0M7. It is fixed in the current CVS. BIRT creates a classloader using libraries from all the projects in the workspace including thirdparty-all.jar from the *-test project that contains an incompatible xerces version (which causes problems 2 and 3). The BIRT classloader returns the META-INF/persistence.xml file multiple times because multiple instances of the EJB's source folder are in the classpath (which causes problem 1). -- 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, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5314) Smooks Config - Add menu on Java Mapping canvas not appearing consistently

by Brian Fitzpatrick (JIRA)

Smooks Config - Add menu on Java Mapping canvas not appearing consistently -------------------------------------------------------------------------- Key: JBIDE-5314 URL: https://jira.jboss.org/jira/browse/JBIDE-5314 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.1.0.CR1 Reporter: Brian Fitzpatrick Assignee: Xue Peng Fix For: 3.1.0.GA When the Java Mapping canvas is first painted, if you right-click on the canvas to add a class you can't do so until you right click repeatedly. Then the "Add" menu is added to the popup. Is there something going on to prevent the "Add" menu to be added initially? -- 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, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (JBIDE-3939) 'Ignored reentrant call while viewer is busy. This is only logged once per viewer instance, but similar calls will still be ignored' in form editor tree

by Denis Golovin (JIRA)

'Ignored reentrant call while viewer is busy. This is only logged once per viewer instance, but similar calls will still be ignored' in form editor tree -------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-3939 URL: https://jira.jboss.org/jira/browse/JBIDE-3939 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.0.0.GA Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 3.1.0 I've seen this on trunks version built in local development environment. ColumnViewer.update(ColumnViewer.java:552) at org.eclipse.ui.model.WorkbenchContentProvider$4.run(WorkbenchContentProvider.java:304) at org.eclipse.ui.model.WorkbenchContentProvider.runUpdates(WorkbenchContentProvider.java:129) at org.eclipse.ui.model.WorkbenchContentProvider.processDelta(WorkbenchContentProvider.java:102) at org.eclipse.ui.model.WorkbenchContentProvider.resourceChanged(WorkbenchContentProvider.java:76) at org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:288) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:282) at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:148) at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:313) at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1022) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1809) at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:782) at org.eclipse.jdt.core.JavaCore.setClasspathContainer(JavaCore.java:4616) at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.install(J2EEComponentClasspathContainer.java:385) at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathInitializer.initialize(J2EEComponentClasspathInitializer.java:29) at org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2483) at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1702) at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:2553) at org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2611) at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:1872) at org.eclipse.jdt.internal.core.JavaProject.buildStructure(JavaProject.java:440) at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:257) at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:514) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:251) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:237) at org.eclipse.jdt.internal.core.JavaElement.getChildren(JavaElement.java:192) at org.eclipse.jdt.internal.core.JavaProject.getPackageFragmentRoots(JavaProject.java:1743) at org.eclipse.jst.j2ee.internal.project.J2EEProjectUtilities.getSourceContainers(J2EEProjectUtilities.java:858) at org.eclipse.jst.j2ee.internal.project.J2EEProjectUtilities.getOutputContainers(J2EEProjectUtilities.java:895) at org.eclipse.jst.j2ee.internal.project.J2EEProjectUtilities.getAllOutputContainers(J2EEProjectUtilities.java:931) at org.eclipse.jst.j2ee.internal.classpathdep.ClasspathDependencyValidator$ClasspathDependencyValidatorData.<init>(ClasspathDependencyValidator.java:219) at org.eclipse.jst.j2ee.classpathdep.ClasspathDependencyUtil.getComponentClasspathDependencies(ClasspathDependencyUtil.java:252) at org.eclipse.jst.j2ee.classpathdep.ClasspathDependencyUtil.getComponentClasspathDependencies(ClasspathDependencyUtil.java:236) at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getJavaClasspathReferences(J2EEModuleVirtualComponent.java:195) at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getNonManifestReferences(J2EEModuleVirtualComponent.java:132) at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:99) at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:95) at org.eclipse.wst.common.componentcore.internal.builder.DependencyGraphImpl$GraphUpdateJob$1.run(DependencyGraphImpl.java:303) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.wst.common.componentcore.internal.builder.DependencyGraphImpl$GraphUpdateJob.run(DependencyGraphImpl.java:282) at org.eclipse.wst.common.componentcore.internal.builder.DependencyGraphImpl.waitForAllUpdates(DependencyGraphImpl.java:440) at org.eclipse.wst.common.componentcore.internal.builder.DependencyGraphImpl.getReferencingComponents(DependencyGraphImpl.java:72) at org.eclipse.wst.common.componentcore.internal.builder.DependencyGraph.getReferencingComponents(DependencyGraph.java:30) at org.eclipse.wst.common.componentcore.internal.resources.VirtualComponent.getReferencingComponents(VirtualComponent.java:437) at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.update(J2EEComponentClasspathContainer.java:202) at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.install(J2EEComponentClasspathContainer.java:382) at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathInitializer.initialize(J2EEComponentClasspathInitializer.java:29) at org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2483) at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1702) at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:2553) at org.eclipse.jst.common.jdt.internal.classpath.ClasspathUtil.getResolvedClasspath(ClasspathUtil.java:83) at org.eclipse.jst.common.jdt.internal.classpath.ClasspathUtil.getResolvedClasspath(ClasspathUtil.java:37) at org.eclipse.jst.common.jdt.internal.classpath.FlexibleProjectContainer.computeClasspathEntries(FlexibleProjectContainer.java:182) at org.eclipse.jst.common.jdt.internal.classpath.FlexibleProjectContainer.<init>(FlexibleProjectContainer.java:122) at org.eclipse.jst.j2ee.internal.web.classpath.WebAppLibrariesContainer.<init>(WebAppLibrariesContainer.java:48) at org.eclipse.jst.j2ee.internal.web.classpath.WebAppLibrariesContainerInitializer.initialize(WebAppLibrariesContainerInitializer.java:34) at org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2483) at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1702) at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:2553) at org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2611) at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:1905) at org.jboss.tools.common.model.util.EclipseResourceUtil.getClassPath(EclipseResourceUtil.java:482) at org.jboss.tools.common.model.filesystems.impl.FileSystemsLoader.updateLibs(FileSystemsLoader.java:168) at org.jboss.tools.common.model.filesystems.impl.FileSystemsLoader.load(FileSystemsLoader.java:81) at org.jboss.tools.common.model.loaders.impl.RootLoaderImpl.load(RootLoaderImpl.java:33) at org.jboss.tools.common.model.impl.XModelImpl.load(XModelImpl.java:404) at org.jboss.tools.common.model.XModelFactory.createInstance(XModelFactory.java:35) at org.jboss.tools.common.model.XModelFactory.getModel(XModelFactory.java:28) at org.jboss.tools.common.model.project.ModelNature.createProject(ModelNature.java:120) at org.jboss.tools.common.model.project.ModelNature.setProject(ModelNature.java:49) at org.eclipse.core.internal.resources.NatureManager.createNature(NatureManager.java:232) at org.eclipse.core.internal.resources.Project.getNature(Project.java:377) at org.jboss.tools.common.model.util.EclipseResourceUtil.getModelNature(EclipseResourceUtil.java:220) at org.jboss.tools.common.model.util.EclipseResourceUtil.getObjectByResource(EclipseResourceUtil.java:93) at org.jboss.tools.common.model.markers.XMarkerManager.reload(XMarkerManager.java:74) at org.jboss.tools.common.model.markers.XMarkerManager.reload(XMarkerManager.java:65) at org.jboss.tools.common.model.markers.XMarkerManager.<init>(XMarkerManager.java:39) at org.jboss.tools.common.model.markers.XMarkerManager.getInstance(XMarkerManager.java:30) at org.jboss.tools.common.model.ui.navigator.LabelDecoratorImpl.getErrorState(LabelDecoratorImpl.java:71) at org.jboss.tools.common.model.ui.navigator.LabelDecoratorImpl.decorateImage(LabelDecoratorImpl.java:40) at org.eclipse.jface.viewers.DecoratingLabelProvider.getImage(DecoratingLabelProvider.java:94) at org.eclipse.jface.viewers.DecoratingLabelProvider.updateLabel(DecoratingLabelProvider.java:356) at org.eclipse.jface.viewers.WrappedViewerLabelProvider.update(WrappedViewerLabelProvider.java:183) at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:145) at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:932) at org.eclipse.jface.viewers.AbstractTreeViewer$UpdateItemSafeRunnable.run(AbstractTreeViewer.java:102) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:880) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:1012) at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:466) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:880) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2041) at org.eclipse.jface.viewers.AbstractTreeViewer.createTreeItem(AbstractTreeViewer.java:827) at org.eclipse.jface.viewers.AbstractTreeViewer$1.run(AbstractTreeViewer.java:802) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:776) at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:634) at org.eclipse.jface.viewers.AbstractTreeViewer.internalInitializeTree(AbstractTreeViewer.java:1490) at org.eclipse.jface.viewers.TreeViewer.internalInitializeTree(TreeViewer.java:823) at org.eclipse.jface.viewers.AbstractTreeViewer$5.run(AbstractTreeViewer.java:1474) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1365) at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:397) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1328) at org.eclipse.jface.viewers.AbstractTreeViewer.inputChanged(AbstractTreeViewer.java:1467) at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:274) at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1603) at org.jboss.tools.common.editor.XModelObjectTreeViewComponent.createControl(XModelObjectTreeViewComponent.java:81) at org.jboss.tools.common.editor.form.SampleTreeForm.createClientArea(SampleTreeForm.java:71) at org.jboss.tools.common.model.ui.forms.ExpandableForm.createControl(ExpandableForm.java:108) at org.jboss.tools.common.model.ui.forms.SplitFormContainer.createFirstForm(SplitFormContainer.java:79) at org.jboss.tools.common.model.ui.forms.SplitFormContainer.createControl(SplitFormContainer.java:103) at org.jboss.tools.common.model.ui.forms.DefaultFormContainer.createControl(DefaultFormContainer.java:47) at org.jboss.tools.common.model.ui.forms.DefaultFormPage.createFormControl(DefaultFormPage.java:94) at org.jboss.tools.common.editor.TreeFormPage.createFormControl(TreeFormPage.java:150) at org.jboss.tools.common.model.ui.forms.DefaultFormPage.createControl(DefaultFormPage.java:108) at org.jboss.tools.common.editor.TreeFormPage.createPartControl(TreeFormPage.java:393) at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:217) at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:187) at org.jboss.tools.common.editor.ObjectMultiPageEditor.addFormPage(ObjectMultiPageEditor.java:886) at org.jboss.tools.jst.web.ui.editors.WebCompoundEditor.doCreatePages(WebCompoundEditor.java:33) at org.jboss.tools.common.editor.ObjectMultiPageEditor.createPages(ObjectMultiPageEditor.java:234) at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:310) at org.jboss.tools.common.model.ui.editor.EditorPartWrapper.createPartControl(EditorPartWrapper.java:176) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:428) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:594) at org.eclipse.ui.internal.EditorAreaHelper.setVisibleEditor(EditorAreaHelper.java:263) at org.eclipse.ui.internal.EditorManager.setVisibleEditor(EditorManager.java:1410) at org.eclipse.ui.internal.EditorManager$5.runWithException(EditorManager.java:944) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3378) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3036) at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803) at org.eclipse.ui.internal.Workbench$27.runWithException(Workbench.java:1363) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3378) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3036) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2295) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2200) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:495) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:490) 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:193) 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:386) 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:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) at org.eclipse.equinox.launcher.Main.main(Main.java:1212) -- 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, 5 months

1
6
0 / 0

[JBoss JIRA] Created: (JBIDE-5312) Smooks Run Configuration - needs unique name to avoid collisions

by Brian Fitzpatrick (JIRA)

Smooks Run Configuration - needs unique name to avoid collisions ---------------------------------------------------------------- Key: JBIDE-5312 URL: https://jira.jboss.org/jira/browse/JBIDE-5312 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.1.0.CR1 Reporter: Brian Fitzpatrick Assignee: Tom Fennelly Priority: Minor Fix For: 3.1.0.GA While testing the Run As... Smooks Configuration functionality, I discovered that each Runtime Configuration was named the same as the smooks configuration file. This is great until you have two smooks configs with the same name. When that happens, the new Runtime Config overrides the old Runtime Config and you lose whatever was set for the first one with the same name. I recommend that you use a "<project name> + <smooks config name>" approach to create more unique Runtime Configuration names. This will avoid the issue. The workaround for now is to rename the existing configuration before creating another. -- 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, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-5129) JBoss SSH Server Plugin has no provider name

by Anton Klimkovich (JIRA)

JBoss SSH Server Plugin has no provider name -------------------------------------------- Key: JBIDE-5129 URL: https://jira.jboss.org/jira/browse/JBIDE-5129 Project: Tools (JBoss Tools) Issue Type: Bug Components: common Affects Versions: 3.1.0.CR1 Reporter: Anton Klimkovich Assignee: Denis Golovin Priority: Optional Attachments: SSH provider Name.PNG EXECUTE: Help -> About Eclipse SDK -> Installation Detailes FAILURE: JBoss SSH Server Plugin has no provider name Look at screenshot. -- 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, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (JBDS-960) Scaling possibility is added to VPE

by Svetlana mukhina (JIRA)

Scaling possibility is added to VPE ----------------------------------- Key: JBDS-960 URL: https://jira.jboss.org/jira/browse/JBDS-960 Project: JBoss Developer Studio Issue Type: Task Components: Doc - VisualWebTools Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 2.1.0-doc update VPE screens -- 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, 5 months

1
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5321) Input task not picking up XML input when opening existing Smooks config

by Brian Fitzpatrick (JIRA)

Input task not picking up XML input when opening existing Smooks config ----------------------------------------------------------------------- Key: JBIDE-5321 URL: https://jira.jboss.org/jira/browse/JBIDE-5321 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Affects Versions: 3.1.0.CR1 Reporter: Brian Fitzpatrick Assignee: Xue Peng Fix For: 3.1.0.GA When I try to open the Smooks configuration for the xml-to-java sample, it's not picking up the Input configuration - just like for the java-to-java sample. Once I selected "XML" as the reader type and selected the input message sample however, it looks fine. We need to interpret the XML input configuration for the Input task when opening existing configurations. -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5326) Change the current "Error Page" for unsupported config namespaces to be an info/warning on the Smooks Editor

by Tom Fennelly (JIRA)

Change the current "Error Page" for unsupported config namespaces to be an info/warning on the Smooks Editor ------------------------------------------------------------------------------------------------------------ Key: JBIDE-5326 URL: https://jira.jboss.org/jira/browse/JBIDE-5326 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 3.1.0.GA Attachments: Screen shot 2009-12-01 at 11.53.03.png At the moment, opening an unsupported config will result in an "Error" page being displayed to the user, informing her of the issue as well as directing to use the XML Editor (see screenshot). Need to change this to be more consistent with other Eclipse Editors (see Hibernate screencast). -- 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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5322) Input task not picking up Java input when opening existing Smooks config

by Brian Fitzpatrick (JIRA)

Input task not picking up Java input when opening existing Smooks config ------------------------------------------------------------------------ Key: JBIDE-5322 URL: https://jira.jboss.org/jira/browse/JBIDE-5322 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.1.0.CR1 Reporter: Brian Fitzpatrick Assignee: Xue Peng Fix For: 3.1.0.GA When I try to open the Smooks configuration for the java-to-java sample, it's not picking up the Input configuration. Once I selected "Java" as the reader type and selected the input message sample however, it looks fine. We need to interpret the Java input configuration for the Input task when opening existing configurations. -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5343) Template 'Value' mappings should not be allowed inside a Collection target before the collection mappings is made

by Tom Fennelly (JIRA)

Template 'Value' mappings should not be allowed inside a Collection target before the collection mappings is made ----------------------------------------------------------------------------------------------------------------- Key: JBIDE-5343 URL: https://jira.jboss.org/jira/browse/JBIDE-5343 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Reporter: Tom Fennelly Fix For: 3.1.0.CR1, 3.1.0.GA At the moment, the editor allows the user to map bean model values into target templating model collection nodes (maxOccurs > 1 or maxOccurs == -1) before the collection mapping has been made. Should block the user from making these mappings (and tell them why they are being blocked!!!) until after the collection mapping has been made. -- 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, 5 months

2
1
0 / 0

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

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5351) Remove unnecessary setSmooksConfig method on the RuntimeMetadata class

by Tom Fennelly (JIRA)

Remove unnecessary setSmooksConfig method on the RuntimeMetadata class ---------------------------------------------------------------------- Key: JBIDE-5351 URL: https://jira.jboss.org/jira/browse/JBIDE-5351 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 3.1.0.CR1 The additional code in this method (cut & paste of existing version) is just opening a FileInputStream on the smooks configFile (and not closing) if the new InputStream param is null. Not really sure why that was added?? Of course the potential file handle leak is the big issue here!! -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5346) Java Mapping form should show an error on beans that don't have the createOnElement configured

by Tom Fennelly (JIRA)

Java Mapping form should show an error on beans that don't have the createOnElement configured ---------------------------------------------------------------------------------------------- Key: JBIDE-5346 URL: https://jira.jboss.org/jira/browse/JBIDE-5346 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Reporter: Tom Fennelly Fix For: 3.1.0.CR1, 3.1.0.GA i.e. where the user hasn't selected the source model event to trigger creation. -- 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, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5344) Bean wizard allowing non concrete classes to be selected

by Tom Fennelly (JIRA)

Bean wizard allowing non concrete classes to be selected -------------------------------------------------------- Key: JBIDE-5344 URL: https://jira.jboss.org/jira/browse/JBIDE-5344 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Reporter: Tom Fennelly Fix For: 3.1.0.CR1, 3.1.0.GA E.g..... it allows the user to select java.util.Collection as the bean 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

16 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5337) Change FreeMarker config namespace prefix from "flt" to "ftl"

by Tom Fennelly (JIRA)

Change FreeMarker config namespace prefix from "flt" to "ftl" ------------------------------------------------------------- Key: JBIDE-5337 URL: https://jira.jboss.org/jira/browse/JBIDE-5337 Project: Tools (JBoss Tools) Issue Type: Task Components: smooks Reporter: Tom Fennelly Priority: Minor Fix For: 3.1.0.GA -- 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, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5348) Problem with importing remote WSIL/WSDL still exists.

by Feng Qian (JIRA)

Problem with importing remote WSIL/WSDL still exists. -------------------------------------------------------- Key: JBIDE-5348 URL: https://jira.jboss.org/jira/browse/JBIDE-5348 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpm Reporter: Feng Qian Assignee: Feng Qian this issue is linked to the bug : https://bugs.eclipse.org/bugs/show_bug.cgi?id=278205 -- 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, 5 months

1
1
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, 5 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, 5 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-5342) ProjectClassLoader not resolving internal project jar files

by Tom Fennelly (JIRA)

ProjectClassLoader not resolving internal project jar files ----------------------------------------------------------- Key: JBIDE-5342 URL: https://jira.jboss.org/jira/browse/JBIDE-5342 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 3.1.0.CR1, 3.1.0.GA -- 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, 5 months

1
1
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, 5 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, 5 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, 5 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, 5 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, 5 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, 5 months

3
14
0 / 0

[JBoss JIRA] Created: (JBIDE-5335) Add "Fix" info (where possible) for unsupported config namespaces

by Tom Fennelly (JIRA)

Add "Fix" info (where possible) for unsupported config namespaces ----------------------------------------------------------------- Key: JBIDE-5335 URL: https://jira.jboss.org/jira/browse/JBIDE-5335 Project: Tools (JBoss Tools) Issue Type: Task Components: smooks Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 3.1.0.CR1, 3.1.0.GA -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-4191) Requested ESB wizard enhancements

by Aaron Pestel (JIRA)

Requested ESB wizard enhancements --------------------------------- Key: JBIDE-4191 URL: https://jira.jboss.org/jira/browse/JBIDE-4191 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: esb Environment: Version: 2.0.0.CR1 Build id: R200812221144 Build date: 12/22/2008 11:54 Reporter: Aaron Pestel Priority: Minor Have some requested enhancements to the ESB wizard functionality and documented them with rough proposed screenshots attached to this Jira. -- 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, 5 months

4
15
0 / 0

[JBoss JIRA] Created: (JBIDE-5332) Problems with JBT update site - Smooks tools have 3.5.1 Eclipse dependensies.

by Aliaksey Nis (JIRA)

Problems with JBT update site - Smooks tools have 3.5.1 Eclipse dependensies. ----------------------------------------------------------------------------- Key: JBIDE-5332 URL: https://jira.jboss.org/jira/browse/JBIDE-5332 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, smooks Affects Versions: 3.1.0.CR1 Environment: WindowsXP SP2 JBoss Tools Version: 3.1.0.CR1 eclipse-SDK-3.5RC3-win32.zip Build id: JBossTools-Update-3.1.0.v200911251807N-H130-RC1 JRE 1.6 Reporter: Aliaksey Nis Priority: Critical EXECUTE: Update from JBT update site. FAILURE: Smooks tools requires 3.5.1 Eclipse and couldn't be installed on 3.5.0. Log(with updated Eclipse Releng tools - other parts is 3.5.0): Software currently installed: Eclipse SDK 3.5.0.I20090528-2000 (org.eclipse.sdk.ide 3.5.0.I20090528-2000) Only one of the following can be installed at once: Debug UI 3.5.0.v20090603 (org.eclipse.debug.ui 3.5.0.v20090603) Debug UI 3.5.1.v20090811_r351 (org.eclipse.debug.ui 3.5.1.v20090811_r351) Debug UI 3.5.0.v20090527 (org.eclipse.debug.ui 3.5.0.v20090527) Cannot satisfy dependency: From: Eclipse Platform 3.5.0.v20090526-9fEdG1HFtGcZmCVWq9ZOYoxFeqNQuz035sD (org.eclipse.platform.feature.group 3.5.0.v20090526-9fEdG1HFtGcZmCVWq9ZOYoxFeqNQuz035sD) To: org.eclipse.debug.ui [3.5.0.v20090527] Cannot satisfy dependency: From: Eclipse Project SDK 3.5.0.v20090423-7Q7bA7DPP1RM6K_fQ-ZRS58BB1jD8UanUR5ThkmDbpM-7 (org.eclipse.sdk.feature.group 3.5.0.v20090423-7Q7bA7DPP1RM6K_fQ-ZRS58BB1jD8UanUR5ThkmDbpM-7) To: org.eclipse.platform.feature.group [3.5.0.v20090526-9fEdG1HFtGcZmCVWq9ZOYoxFeqNQuz035sD] Cannot satisfy dependency: From: Eclipse SDK 3.5.0.I20090528-2000 (org.eclipse.sdk.ide 3.5.0.I20090528-2000) To: org.eclipse.sdk.feature.group [3.5.0.v20090423-7Q7bA7DPP1RM6K_fQ-ZRS58BB1jD8UanUR5ThkmDbpM-7] Cannot satisfy dependency: From: Smooks Tools 1.1.0.v200912010124N-H1-RC1 (org.jboss.tools.smooks.feature.feature.group 1.1.0.v200912010124N-H1-RC1) To: org.jboss.tools.smooks.ui [1.1.0.v200912010124N-H1-RC1] Cannot satisfy dependency: From: Smooks Tools UI Plug-in 1.1.0.v200912010124N-H1-RC1 (org.jboss.tools.smooks.ui 1.1.0.v200912010124N-H1-RC1) To: bundle org.eclipse.debug.ui 3.5.1 -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5158) Test New Smooks Configuration Editor with as many Smooks quickstarts as possible

by Brian Fitzpatrick (JIRA)

Test New Smooks Configuration Editor with as many Smooks quickstarts as possible -------------------------------------------------------------------------------- Key: JBIDE-5158 URL: https://jira.jboss.org/jira/browse/JBIDE-5158 Project: Tools (JBoss Tools) Issue Type: Task Components: smooks Affects Versions: 3.1.0.M4 Reporter: Brian Fitzpatrick Assignee: Xue Peng Fix For: 3.1.0.CR1 We absolutely MUST test with as many of the Smooks Quickstarts as we can to see what we support and what we don't. If we don't support something, we should handle that gracefully and not simply bomb out. At the very least create all the Smooks example projects and try the editor with the generated sample projects to see what shakes out. -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBIDE-1787) Support for Seam Mail tags in VPE

by Pete Muir (JIRA)

Support for Seam Mail tags in VPE --------------------------------- Key: JBIDE-1787 URL: http://jira.jboss.com/jira/browse/JBIDE-1787 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Seam Reporter: Pete Muir A bit different from what the VPE normally does as it would need a fixed layout for the header (e.g. Thunderbird compose), and then a standard editor for the body (if html was selected). -- 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

16 years, 5 months

8
19
0 / 0

[JBoss JIRA] Created: (JBIDE-5072) RichFaces 3.3 capabilities contains libraries from 3.3.0.GA and 3.3.2.SR1

by Denis Golovin (JIRA)

RichFaces 3.3 capabilities contains libraries from 3.3.0.GA and 3.3.2.SR1 ------------------------------------------------------------------------- Key: JBIDE-5072 URL: https://jira.jboss.org/jira/browse/JBIDE-5072 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.M4 Environment: Ubuntu Linux 9.04 Java 1.6.0 update 16 JBossTools 3.1.0.v200910210603N-H225-M4 installed through nightly update site workspace from previous release JBossTools 3.1.0.M3 Reporter: Denis Golovin Assignee: Viacheslav Kabanovich Priority: Critical Fix For: 3.1.0.M4 Try this scenarion to reproduce: 1. EXECUTE: Install Last JBT Development Release 3.1.0.M3 from http://download.jboss.org/jbosstools/updates/development 2. EXECUTE: Start eclipse and create any JSF project to make sure org.jboss.tools.common.projecttemplates plugin is activated 3. EXECUTE: Install Last Nightly build for JBT Development Release 3.1.0.M4 from http://download.jboss.org/jbosstools/updates/nightly/3.1.0.M4 4. EXECUTE: Restart eclipse 5. EXECUTE: Add RichFaces capabilities to project created on step 2 6. ASSERT: There are three richfaces*3.3.2.SR1.jar libraries in Web App Libraries ClassPath container of JSF project Now it fails on step 6 and you'll see 6 libraries three from 3.3.0.GA release and three from 3.3.2.SR1. -- 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, 5 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-5260) Create Test page in the Smooks Config editor

by Brian Fitzpatrick (JIRA)

Create Test page in the Smooks Config editor -------------------------------------------- Key: JBIDE-5260 URL: https://jira.jboss.org/jira/browse/JBIDE-5260 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Fix For: 3.1.0.CR1 Create a Test page in the Smooks Configuration Editor that utilizes the Test functionality as presented by... http://www.milyn.org/docs/smooks-report/report.html# By simply hosting this generated page in a web browser control on the Test page, we provide at least some basic testing capability. I have gone ahead and tried creating such a page. I still hit bigtime issues with classloaders in the SAX parser not being able to find one or more schemas referenced in the namespace declaration of the Smooks XML file. However, this is a start. If we could resolve the namespace issues with the graph element in the editor, I think we could get this in for this release. -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBDS-348) Demos on JBDS and Tools

by Svetlana mukhina (JIRA)

Demos on JBDS and Tools ----------------------- Key: JBDS-348 URL: http://jira.jboss.com/jira/browse/JBDS-348 Project: Developer Studio Issue Type: Task Affects Versions: 1.1.0.CR1 Reporter: Svetlana mukhina Assigned To: OLga Chikvina Fix For: 2.0.0.alpha Prepare a lits of topics for demos -- 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

16 years, 5 months

3
21
0 / 0

[JBoss JIRA] Created: (JBIDE-5240) apply button is not become enable in same cases

by Sergey Dzmitrovich (JIRA)

apply button is not become enable in same cases ------------------------------------------------- Key: JBIDE-5240 URL: https://jira.jboss.org/jira/browse/JBIDE-5240 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.M4 Reporter: Sergey Dzmitrovich Assignee: Sergey Dzmitrovich -- 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, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-5236) Struts diagram update fails when diagram contains action comment

by Viacheslav Kabanovich (JIRA)

Struts diagram update fails when diagram contains action comment ---------------------------------------------------------------- Key: JBIDE-5236 URL: https://jira.jboss.org/jira/browse/JBIDE-5236 Project: Tools (JBoss Tools) Issue Type: Bug Components: struts/shale Affects Versions: 3.0.1.GA Environment: Eclipse: 3.4.2 Struts Tools: 3.0.1 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.1.0.CR1 when "Action" has "Comment", drawing "Forward Link" causes some "Forward Link" line vanished. how to reproduce bug: 1. you have "Action1" and "Action2" 2. add Comment to "Action1" 3. draw "Forward Link" line from "Action1" to "Action2". 4. draw "Forward Link" line from "Action2" to "Action1". then line from Action2 to Aciton1 disappear from the screen. I found data file .strutsdia is not valid comparing to real struts-config.xml -- 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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5230) itext.jar isn't added to Seam Web Project libs

by Yura Zhishko (JIRA)

itext.jar isn't added to Seam Web Project libs ---------------------------------------------- Key: JBIDE-5230 URL: https://jira.jboss.org/jira/browse/JBIDE-5230 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.M4 Reporter: Yura Zhishko Assignee: Alexey Kazakov Attachments: patch.patch 1) Create Seam Web Project with Seam 2.0 fp or Seam 2.1.1 GA 2) Open Web App Libraries project directory or Web-Inf/lib of this project RESULT: jboss-seam-pdf.jar library needs itext.jar as a dependence, but itext.jar isn't included into libs (screenshot-1). I've attached a patch that should fix that. Libs will be added to the project. But maybe some changes should be added to tests. -- 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, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5278) "Add/Remove Struts support..." action

by Alexey Kazakov (JIRA)

"Add/Remove Struts support..." action ------------------------------------- Key: JBIDE-5278 URL: https://jira.jboss.org/jira/browse/JBIDE-5278 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: struts/shale Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.1.0.CR1 If there is JSF nature then we should show "Configure"->"Add..." action and "Configure"->"Remove..." otherwise. -- 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, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5277) "Add/Remove JSF support..." action

by Alexey Kazakov (JIRA)

"Add/Remove JSF support..." action ---------------------------------- Key: JBIDE-5277 URL: https://jira.jboss.org/jira/browse/JBIDE-5277 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: JSF Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.1.0.CR1 If there is JSF nature then we should show "Configure"->"Add..." action and "Configure"->"Remove..." otherwise. -- 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, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5257) Seam project doesn't include jfreechart lib

by Yura Zhishko (JIRA)

Seam project doesn't include jfreechart lib ------------------------------------------- Key: JBIDE-5257 URL: https://jira.jboss.org/jira/browse/JBIDE-5257 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.M4 Reporter: Yura Zhishko Assignee: Alexey Kazakov Priority: Minor Fix For: 3.1.0.CR1 Some components from seam-pdf library need jfreechart lib as a dependence, but this lib isn't included into Seam project. Here is a little patch to fix it :) -- 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, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5324) Invalid thread access when refreshing or adding validation markers

by Feng Qian (JIRA)

Invalid thread access when refreshing or adding validation markers ------------------------------------------------------------------ Key: JBIDE-5324 URL: https://jira.jboss.org/jira/browse/JBIDE-5324 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpm Reporter: Feng Qian Assignee: Feng Qian This issue is linked to the eclipse bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=294501 -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5301) Will we release the EDI Message Mapping Editor?

by Xue Peng (JIRA)

Will we release the EDI Message Mapping Editor? ----------------------------------------------- Key: JBIDE-5301 URL: https://jira.jboss.org/jira/browse/JBIDE-5301 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.1.0.M4 Reporter: Xue Peng Assignee: Xue Peng Fix For: 3.1.0.CR1 This editor is for editing the EDI Mapping configuration file , there is a flash demo to show it: http://screencast.com/t/ODUyY2Vh Will we release it in CR1? If we won't , I will remove the editor from smooks tools. -- 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, 5 months

2
3
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 December 2009