December 2009 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-5187) SSH Runtime has no icon in JBoss Community group.

by Anton Klimkovich (JIRA)

SSH Runtime has no icon in JBoss Community group. ------------------------------------------------- Key: JBIDE-5187 URL: https://jira.jboss.org/jira/browse/JBIDE-5187 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.1.0.CR1 Reporter: Anton Klimkovich Assignee: Rob Stryker Priority: Minor EXECUTE: Preferences-> Server-> Runtime Environments EXECUTE: press Add button EXECUTE: Select JBoss Community group FAILURE: SSH Runtime has no icon -- 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

14 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-5328) org.eclipse.debug.core.DebugException: org.xml.sax.SAXParseException: The element type "stringAttribute" must be terminated by the matching end-tag "</stringAttribute>". occurred while reading launch configuration file.

by Anton Klimkovich (JIRA)

org.eclipse.debug.core.DebugException: org.xml.sax.SAXParseException: The element type "stringAttribute" must be terminated by the matching end-tag "</stringAttribute>". occurred while reading launch configuration file. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-5328 URL: https://jira.jboss.org/jira/browse/JBIDE-5328 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.CR1 Environment: Version: 3.1.0.v200911302353N-H140-RC1 Reporter: Anton Klimkovich Assignee: Alexey Kazakov EXECUTE: Create Seam web project FAILURE: org.eclipse.debug.core.DebugException: org.xml.sax.SAXParseException: The element type "stringAttribute" must be terminated by the matching end-tag "</stringAttribute>". occurred while reading launch configuration file: C:\jbdevstudio300M4Version96\ws\seam22-ejb\seam22-ejb.launch. at org.eclipse.debug.internal.core.LaunchManager.createDebugException(LaunchManager.java:887) at org.eclipse.debug.internal.core.LaunchManager.throwException(LaunchManager.java:2404) at org.eclipse.debug.internal.core.LaunchManager.getInfo(LaunchManager.java:1320) at org.eclipse.debug.internal.core.LaunchConfiguration.getInfo(LaunchConfiguration.java:453) at org.eclipse.debug.internal.core.LaunchConfiguration.getType(LaunchConfiguration.java:614) at org.eclipse.debug.internal.core.LaunchManager.isValid(LaunchManager.java:2038) at org.eclipse.debug.internal.core.LaunchManager.launchConfigurationAdded(LaunchManager.java:2061) at org.eclipse.debug.internal.core.LaunchManager.projectOpened(LaunchManager.java:2169) at org.eclipse.debug.internal.core.LaunchManager$LaunchManagerVisitor.visit(LaunchManager.java:358) at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:68) at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79) at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:48) at org.eclipse.debug.internal.core.LaunchManager.resourceChanged(LaunchManager.java:2238) at org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:291) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285) at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149) at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:313) at org.eclipse.core.internal.resources.Workspace.aboutToBuild(Workspace.java:244) at org.eclipse.core.internal.resources.Project$1.run(Project.java:513) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1782) at org.eclipse.core.internal.resources.Project.internalBuild(Project.java:502) at org.eclipse.core.internal.resources.Project.build(Project.java:94) at org.jboss.tools.seam.ui.wizard.SeamProjectWizard.buildProjects(SeamProjectWizard.java:416) at org.jboss.tools.seam.ui.wizard.SeamProjectWizard.performFinish(SeamProjectWizard.java:346) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$3.run(ModifyFacetedProjectWizard.java:331) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$4.run(ModifyFacetedProjectWizard.java:345) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Caused by: org.xml.sax.SAXParseException: The element type "stringAttribute" must be terminated by the matching end-tag "</stringAttribute>". at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source) at org.eclipse.debug.internal.core.LaunchManager.createInfoFromXML(LaunchManager.java:908) at org.eclipse.debug.internal.core.LaunchManager.getInfo(LaunchManager.java:1313) ... 27 more -- 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

14 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (JBDS-971) New icon is designed for ESB project creation wizard

by Svetlana mukhina (JIRA)

New icon is designed for ESB project creation wizard ---------------------------------------------------- Key: JBDS-971 URL: https://jira.jboss.org/jira/browse/JBDS-971 Project: JBoss Developer Studio Issue Type: Task Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: Svetlana mukhina Priority: Minor Fix For: 2.1.0-doc Update the screens, better together with some other task on ESB wizard functionality. -- 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

14 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5353) Project context menu contain incorrect name of JBoss Tools .

by Anton Klimkovich (JIRA)

Project context menu contain incorrect name of JBoss Tools . ------------------------------------------------------------ Key: JBIDE-5353 URL: https://jira.jboss.org/jira/browse/JBIDE-5353 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.CR1 Reporter: Anton Klimkovich Assignee: Alexey Kazakov EXECUTE: Create web project EXECUTE: Open context menu from Package Explorer FAILURE: context menu contain incorrect name of JBoss Tools menu. (example: JBoss Tools Developer Studio) -- 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

14 years, 6 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-4864) BPEL Process Versioning

by Brian Fitzpatrick (JIRA)

BPEL Process Versioning ----------------------- Key: JBIDE-4864 URL: https://jira.jboss.org/jira/browse/JBIDE-4864 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: bpm Affects Versions: 3.1.0.M4 Reporter: Brian Fitzpatrick Assignee: Denny Xu The process versioning requirement is to support an optional 'version' attribute on the top level 'deploy' element in the bpel-deploy.xml deployment descriptor, and provide: 1) Extension to ODE deployment descriptor editor to allow user to define the version. 2) When BPEL project is deployed to AS server, if a version has been specified, then it should be used as the suffix of the jar name. The version attribute should be defined in its own namespace - open to suggestions? -- 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

14 years, 6 months

5
25
0 / 0

[JBoss JIRA] Created: (JBIDE-5363) Change the BPEL version number to be format: yyyymmddHHMMSS

by Denny Xu (JIRA)

Change the BPEL version number to be format: yyyymmddHHMMSS ------------------------------------------------------------ Key: JBIDE-5363 URL: https://jira.jboss.org/jira/browse/JBIDE-5363 Project: Tools (JBoss Tools) Issue Type: Task Components: bpm Affects Versions: 3.1.0.M4 Reporter: Denny Xu Assignee: Denny Xu when deploying a bpel project, a version number will be appended to the archive name, now, we need to update the version format to be yyyymmddHHMMSS -- 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

14 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5392) BPEL validation errors in simple_invoke riftsaw quickstart sample

by Gary Brown (JIRA)

BPEL validation errors in simple_invoke riftsaw quickstart sample ----------------------------------------------------------------- Key: JBIDE-5392 URL: https://jira.jboss.org/jira/browse/JBIDE-5392 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpm Reporter: Gary Brown This error occurred when importing the $riftsaw/samples/quickstarts/simple_invoke project into Eclipse: The expression in <{http://docs.oasis-open.org/wsbpel/2.0/process/executable}to> is not a variable reference expression. SimpleInvoke.bpel /Quickstart_bpel_simple_invoke/bpelContent line 71 BPEL Validation Marker -- 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

14 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5391) BPEL validation errors in Quickstart_bpel_loan_approval riftsaw quickstart sample

by Gary Brown (JIRA)

BPEL validation errors in Quickstart_bpel_loan_approval riftsaw quickstart sample --------------------------------------------------------------------------------- Key: JBIDE-5391 URL: https://jira.jboss.org/jira/browse/JBIDE-5391 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpm Reporter: Gary Brown These errors occur when importing the RiftSaw/samples/quickstarts/loan_approval example. Description Resource Path Location Type <{http://docs.oasis-open.org/wsbpel/2.0/process/executable}transitionCondition> cannot be a child of <{http://docs.oasis-open.org/wsbpel/2.0/process/executable}source>; it can only be a child of "sources" loan_approval.bpel /Quickstart_bpel_loan_approval/bpelContent line 125 BPEL Validation Marker <{http://docs.oasis-open.org/wsbpel/2.0/process/executable}transitionCondition> cannot be a child of <{http://docs.oasis-open.org/wsbpel/2.0/process/executable}source>; it can only be a child of "sources" loan_approval.bpel /Quickstart_bpel_loan_approval/bpelContent line 135 BPEL Validation Marker <{http://docs.oasis-open.org/wsbpel/2.0/process/executable}transitionCondition> cannot be a child of <{http://docs.oasis-open.org/wsbpel/2.0/process/executable}source>; it can only be a child of "sources" loan_approval.bpel /Quickstart_bpel_loan_approval/bpelContent line 145 BPEL Validation Marker <{http://docs.oasis-open.org/wsbpel/2.0/process/executable}transitionCondition> cannot be a child of <{http://docs.oasis-open.org/wsbpel/2.0/process/executable}source>; it can only be a child of "sources" loan_approval.bpel /Quickstart_bpel_loan_approval/bpelContent line 191 BPEL Validation Marker <{http://docs.oasis-open.org/wsbpel/2.0/process/executable}transitionCondition> cannot be a child of <{http://docs.oasis-open.org/wsbpel/2.0/process/executable}source>; it can only be a child of "sources" loan_approval.bpel /Quickstart_bpel_loan_approval/bpelContent line 181 BPEL Validation Marker -- 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

14 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5376) Hide smooks version selection page in smooks new file wizard

by Xue Peng (JIRA)

Hide smooks version selection page in smooks new file wizard ------------------------------------------------------------ Key: JBIDE-5376 URL: https://jira.jboss.org/jira/browse/JBIDE-5376 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.1.0.CR1 Reporter: Xue Peng Assignee: Xue Peng Fix For: 3.1.0.CR1 There is only v1.2 can be choose , so the smooks version selection page is useless in smooks new file wizard , hide it is good. -- 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

14 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5398) BPEL Editor should re-validate artifacts wsdl when updating PartnerLinkTypes, etc. on save

by Jeff DeLong (JIRA)

BPEL Editor should re-validate artifacts wsdl when updating PartnerLinkTypes, etc. on save ------------------------------------------------------------------------------------------ Key: JBIDE-5398 URL: https://jira.jboss.org/jira/browse/JBIDE-5398 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: bpm Reporter: Jeff DeLong BPEL Editor does not re-validate artifacts wsdl when updating PartnerLinkTypes, etc. and user save, WSDL files is only re-vaidated when user cleans project. So when user creates a new PartnerLInk / PartnerLinkType, errors are reported, and the PartnerLinks cannot be referenced. It would be very useful if the WSDL was validated when the user saves, as opposed to only when the user cleans the project. -- 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

14 years, 6 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2009