[JBoss JIRA] (TEIIDDES-1641) Eclipse Juno 4.0 freezes while generating JBossWS-CXF war
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1641?page=com.atlassian.jira.plu... ]
Ted Jones commented on TEIIDDES-1641:
-------------------------------------
Re-assigned to Lucie for further testing.
> Eclipse Juno 4.0 freezes while generating JBossWS-CXF war
> ---------------------------------------------------------
>
> Key: TEIIDDES-1641
> URL: https://issues.jboss.org/browse/TEIIDDES-1641
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 7.8
> Environment: fedora 17, x86_64,
> eclipse juno 4.0, sr1
> teiid designer 8.1.alpha2 (also 7.8)
> Abridged JBoss Tools 4.0 -> JBossAS Tools 2.4.1
> server: SOA 5.3.1.GA + eds 5.3.1.GA or JBossAS 7.1.1
> java jdk 1.6.0_33
> Reporter: Lucie Fabrikova
> Assignee: Lucie Fabrikova
> Fix For: 8.2
>
> Attachments: WebServ.zip
>
>
> !ENTRY org.teiid.designer.webservice 4 5 2013-04-08 10:36:50.278
> !MESSAGE An error occurred while creating WAR file, check log for detail
> !STACK 0
> java.lang.RuntimeException: org.xml.sax.SAXParseException: The element type "meta" must be terminated by the matching end-tag "</meta>".
> at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.generateWsdl(DefaultWebArchiveBuilderImpl.java:718)
> at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.createWebArchive(DefaultWebArchiveBuilderImpl.java:236)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.execute(WarDeploymentInfoDialog.java:195)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog$1.run(WarDeploymentInfoDialog.java:150)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
> at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.okPressed(WarDeploymentInfoDialog.java:159)
> at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:472)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1276)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
> at org.eclipse.jface.window.Window.open(Window.java:801)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.open(WarDeploymentInfoDialog.java:171)
> at org.teiid.designer.runtime.ui.actions.GenerateWarAction.run(GenerateWarAction.java:116)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1276)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> 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:353)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
> 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:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 1 month
[JBoss JIRA] (TEIIDDES-1641) Eclipse Juno 4.0 freezes while generating JBossWS-CXF war
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1641?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-1641:
--------------------------------
Assignee: Lucie Fabrikova (was: Ted Jones)
> Eclipse Juno 4.0 freezes while generating JBossWS-CXF war
> ---------------------------------------------------------
>
> Key: TEIIDDES-1641
> URL: https://issues.jboss.org/browse/TEIIDDES-1641
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 7.8
> Environment: fedora 17, x86_64,
> eclipse juno 4.0, sr1
> teiid designer 8.1.alpha2 (also 7.8)
> Abridged JBoss Tools 4.0 -> JBossAS Tools 2.4.1
> server: SOA 5.3.1.GA + eds 5.3.1.GA or JBossAS 7.1.1
> java jdk 1.6.0_33
> Reporter: Lucie Fabrikova
> Assignee: Lucie Fabrikova
> Fix For: 8.2
>
> Attachments: WebServ.zip
>
>
> !ENTRY org.teiid.designer.webservice 4 5 2013-04-08 10:36:50.278
> !MESSAGE An error occurred while creating WAR file, check log for detail
> !STACK 0
> java.lang.RuntimeException: org.xml.sax.SAXParseException: The element type "meta" must be terminated by the matching end-tag "</meta>".
> at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.generateWsdl(DefaultWebArchiveBuilderImpl.java:718)
> at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.createWebArchive(DefaultWebArchiveBuilderImpl.java:236)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.execute(WarDeploymentInfoDialog.java:195)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog$1.run(WarDeploymentInfoDialog.java:150)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
> at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.okPressed(WarDeploymentInfoDialog.java:159)
> at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:472)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1276)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
> at org.eclipse.jface.window.Window.open(Window.java:801)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.open(WarDeploymentInfoDialog.java:171)
> at org.teiid.designer.runtime.ui.actions.GenerateWarAction.run(GenerateWarAction.java:116)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1276)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> 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:353)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
> 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:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 1 month
[JBoss JIRA] (TEIIDDES-1591) Improve the default eclipse dialog for entering the secure storage password
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1591?page=com.atlassian.jira.plu... ]
Paul Richardson commented on TEIIDDES-1591:
-------------------------------------------
Took a while to remember but here it is ...
The dialog is only relevant to linux since Eclipse provides fragments for Windows and OSX that overrides the default password provider with their own internal authentication frameworks. Consequently, users on those platforms never see the password dialog as their own OS credentials are used instead. Thus, this fragment is limited to the host being a linux system.
> Improve the default eclipse dialog for entering the secure storage password
> ---------------------------------------------------------------------------
>
> Key: TEIIDDES-1591
> URL: https://issues.jboss.org/browse/TEIIDDES-1591
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Eclipse Integration
> Affects Versions: 8.1
> Reporter: Paul Richardson
> Assignee: Max Rydahl Andersen
> Fix For: 8.2
>
> Attachments: password-provider-dialog.jpg
>
>
> Both JBossTools and Designer use secure storage for storing passwords. As such, when opening the application and accessing secure storage for the first time (usually on starting a JBoss server), the default password dialog is displayed. However, this dialog is unintuitive since it provides little explanation of what password it is requesting and is easily confused for the JBoss / Teiid admin password or the Teiid jdbc password. Ironically, this password will allow access to both of them!
> Investigation shows that the default password provider can be overridden using the org.eclipse.equinox.security.secureStorage extension point.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 1 month
[JBoss JIRA] (TEIIDDES-1591) Improve the default eclipse dialog for entering the secure storage password
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1591?page=com.atlassian.jira.plu... ]
Rob Stryker commented on TEIIDDES-1591:
---------------------------------------
Any reason why a plugin fragment was chosen over a traditional plugin?
> Improve the default eclipse dialog for entering the secure storage password
> ---------------------------------------------------------------------------
>
> Key: TEIIDDES-1591
> URL: https://issues.jboss.org/browse/TEIIDDES-1591
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Eclipse Integration
> Affects Versions: 8.1
> Reporter: Paul Richardson
> Assignee: Max Rydahl Andersen
> Fix For: 8.2
>
> Attachments: password-provider-dialog.jpg
>
>
> Both JBossTools and Designer use secure storage for storing passwords. As such, when opening the application and accessing secure storage for the first time (usually on starting a JBoss server), the default password dialog is displayed. However, this dialog is unintuitive since it provides little explanation of what password it is requesting and is easily confused for the JBoss / Teiid admin password or the Teiid jdbc password. Ironically, this password will allow access to both of them!
> Investigation shows that the default password provider can be overridden using the org.eclipse.equinox.security.secureStorage extension point.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 1 month
[JBoss JIRA] (TEIIDDES-1591) Improve the default eclipse dialog for entering the secure storage password
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1591?page=com.atlassian.jira.plu... ]
Rob Stryker commented on TEIIDDES-1591:
---------------------------------------
I think this would fit nicely in org.jboss.tools.foundation. Unfortunately, foundation is not yet created ;) (There's a PR for it).
Foundation is intended to be a new location for all sorts of well-tested utilities, split up by framework (platform, wtp, egit, etc). It's an effort to get our code under strict organization (we'll see how that works ;))
However, for this dialog to be placed there, I think we shouldn't mention JBossTools or Teiid Designer specifically. I think we should be more vague and state that "Several installed features use secure storage for storing passwords and other sensitive data."
There's no harm to this, and it ensures that our lowest level plugin is agnostic as to what is running along-side it, whether its JBT, JBDS, TD, etc.
> Improve the default eclipse dialog for entering the secure storage password
> ---------------------------------------------------------------------------
>
> Key: TEIIDDES-1591
> URL: https://issues.jboss.org/browse/TEIIDDES-1591
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Eclipse Integration
> Affects Versions: 8.1
> Reporter: Paul Richardson
> Assignee: Max Rydahl Andersen
> Fix For: 8.2
>
> Attachments: password-provider-dialog.jpg
>
>
> Both JBossTools and Designer use secure storage for storing passwords. As such, when opening the application and accessing secure storage for the first time (usually on starting a JBoss server), the default password dialog is displayed. However, this dialog is unintuitive since it provides little explanation of what password it is requesting and is easily confused for the JBoss / Teiid admin password or the Teiid jdbc password. Ironically, this password will allow access to both of them!
> Investigation shows that the default password provider can be overridden using the org.eclipse.equinox.security.secureStorage extension point.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 1 month
[JBoss JIRA] (TEIIDDES-1647) Multiple NODEFAULT and DEFAULT NS Added to Generated Procedure When Importing WSDL
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1647?page=com.atlassian.jira.plu... ]
Ted Jones resolved TEIIDDES-1647.
---------------------------------
Resolution: Done
Changed to correctly identify default namespace and add to the SQL transformation.
> Multiple NODEFAULT and DEFAULT NS Added to Generated Procedure When Importing WSDL
> ----------------------------------------------------------------------------------
>
> Key: TEIIDDES-1647
> URL: https://issues.jboss.org/browse/TEIIDDES-1647
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Import/Export
> Affects Versions: 8.1
> Reporter: Ted Jones
> Assignee: Ted Jones
> Fix For: 8.2
>
> Attachments: WSDL XSDs Imported.zip
>
>
> Ex:
> CREATE VIRTUAL PROCEDURE
> BEGIN
> SELECT
> XMLELEMENT(NAME "soap:Envelope", XMLNAMESPACES('http://schemas.xmlsoap.org/soap/envelope/' AS soap, DEFAULT 'http://otda.ny.gov/intake/caseinqwsdl/1_0', DEFAULT 'http://otda.ny.gov/intake/caseinquiryin/1_0'), XMLELEMENT(NAME "soap:Header"), XMLELEMENT(NAME "soap:Body", XMLELEMENT(NAME CaseInquiry, XMLELEMENT(NAME CaseNumber, XMLNAMESPACES(NO DEFAULT), NYCWMSServiceView.CaseInquiry_request.CaseNumber), XMLELEMENT(NAME DistrictNumber, XMLNAMESPACES(NO DEFAULT), NYCWMSServiceView.CaseInquiry_request.DistrictNumber)))) AS
> xml_out;
> END
>
> ERROR: At most only one NO DEFAULT or DEFAULT namespace may be specified.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 1 month
[JBoss JIRA] (TEIIDDES-1647) Multiple NODEFAULT and DEFAULT NS Added to Generated Procedure When Importing WSDL
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1647?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-1647:
--------------------------------
https://github.com/Teiid-Designer/teiid-designer/pull/156
> Multiple NODEFAULT and DEFAULT NS Added to Generated Procedure When Importing WSDL
> ----------------------------------------------------------------------------------
>
> Key: TEIIDDES-1647
> URL: https://issues.jboss.org/browse/TEIIDDES-1647
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Import/Export
> Affects Versions: 8.1
> Reporter: Ted Jones
> Assignee: Ted Jones
> Fix For: 8.2
>
> Attachments: WSDL XSDs Imported.zip
>
>
> Ex:
> CREATE VIRTUAL PROCEDURE
> BEGIN
> SELECT
> XMLELEMENT(NAME "soap:Envelope", XMLNAMESPACES('http://schemas.xmlsoap.org/soap/envelope/' AS soap, DEFAULT 'http://otda.ny.gov/intake/caseinqwsdl/1_0', DEFAULT 'http://otda.ny.gov/intake/caseinquiryin/1_0'), XMLELEMENT(NAME "soap:Header"), XMLELEMENT(NAME "soap:Body", XMLELEMENT(NAME CaseInquiry, XMLELEMENT(NAME CaseNumber, XMLNAMESPACES(NO DEFAULT), NYCWMSServiceView.CaseInquiry_request.CaseNumber), XMLELEMENT(NAME DistrictNumber, XMLNAMESPACES(NO DEFAULT), NYCWMSServiceView.CaseInquiry_request.DistrictNumber)))) AS
> xml_out;
> END
>
> ERROR: At most only one NO DEFAULT or DEFAULT namespace may be specified.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 1 month
[JBoss JIRA] (TEIIDDES-1667) Ability to define UDF with vararg to be used in a static VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1667?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1667:
-----------------------------------
Release Notes Docs Status: Not Yet Documented
Release Notes Text: Teiid runtime does not load Function Model Indexes so any extension data (aka VARARGS="TRUE") will not get picked up. For this release a user will need to be use a source model procedure as a function instead.
> Ability to define UDF with vararg to be used in a static VDB
> ------------------------------------------------------------
>
> Key: TEIIDDES-1667
> URL: https://issues.jboss.org/browse/TEIIDDES-1667
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 8.0
> Environment: JBoss AS 7.1.1
> Teiid 8.3.0
> Teiid Designer 8.0.0
> Reporter: Shakir Shaik
> Assignee: Mark Drilling
> Fix For: 8.2
>
> Attachments: FunctionMethodDescriptor.patch, FunctionPlugin.patch, MyMathFunctions.jar, MyMathFunctions.java, RelationalPlugin.patch, UdfManager.patch
>
>
> I am not able to use a UDF with vararg and deploy the same in a static VDB.
> Please see the details in the following thread of Teiid Designer User forum discussions:
> https://community.jboss.org/thread/223823?tstart=0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 1 month