[jira] Created: (UIMA-1734) UIMA-AS Deployment Descriptor doesn't work with Eclipse 3.4.2
UIMA-AS Deployment Descriptor doesn't work with Eclipse 3.4.2 - Key: UIMA-1734 URL: https://issues.apache.org/jira/browse/UIMA-1734 Project: UIMA Issue Type: Bug Components: Eclipse plugins Affects Versions: 2.3 Reporter: Tong Fin Assignee: Tong Fin There is a problem when running DDE in Eclipse 3.4.2: 3.4.2 Linux - fail 3.4.2 Windows - fail 3.5.1 Linux OK 3.5.1 Windows OK 3.3.2 Windows OK Look like there are some images used by the form are missing. These images are belong to some plugins that might not be the same for Eclipse 3.4.2 and 3.5.x. Stack Trace --- eclipse.buildId=M20090211-1700 java.version=1.6.0_16 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Command-line arguments: -os win32 -ws win32 -arch x86 -clean !ENTRY org.eclipse.ui.workbench.texteditor 4 0 2010-02-04 09:07:23.657 !MESSAGE The 'org.eclipse.wst.jsdt.web.ui.internal.hyperlink.script.JSPJavaHyperlinkDetector' extension from plug-in 'org.eclipse.wst.jsdt.web.ui' to the 'org.eclipse.ui.workbench.texteditor.hyperlinkDetectors' extension point will be ignored because it contains invalid attributes. !ENTRY org.eclipse.ui.workbench.texteditor 4 0 2010-02-04 09:07:23.657 !MESSAGE The 'org.eclipse.wst.jsdt.web.ui.internal.hyperlink.script.event.JSPJavaHyperlinkDetector' extension from plug-in 'org.eclipse.wst.jsdt.web.ui' to the 'org.eclipse.ui.workbench.texteditor.hyperlinkDetectors' extension point will be ignored because it contains invalid attributes. !ENTRY org.eclipse.ui 4 0 2010-02-04 09:07:46.388 !MESSAGE Unable to create editor ID taeconfigurator.editors.MultiPageEditor: An unexpected exception was thrown. !STACK 0 java.lang.NullPointerException at org.eclipse.ui.internal.forms.widgets.FormImages$ImageIdentifier.hashCode(FormImages.java:69) at org.eclipse.ui.internal.forms.widgets.FormImages$ComplexImageIdentifier.hashCode(FormImages.java:138) at java.util.HashMap.get(HashMap.java:300) at org.eclipse.ui.internal.forms.widgets.FormImages.getGradient(FormImages.java:187) at org.eclipse.ui.internal.forms.widgets.FormHeading.updateGradientImage(FormHeading.java:868) at org.eclipse.ui.internal.forms.widgets.FormHeading.setTextBackground(FormHeading.java:718) at org.eclipse.ui.forms.widgets.Form.setTextBackground(Form.java:315) at org.apache.uima.dde.internal.page.OverviewPage.createFormContent(OverviewPage.java:375) at org.eclipse.ui.forms.editor.FormPage$1.run(FormPage.java:151) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.forms.editor.FormPage.createPartControl(FormPage.java:149) at org.eclipse.ui.forms.editor.FormEditor.pageChange(FormEditor.java:488) at org.apache.uima.taeconfigurator.editors.MultiPageEditor.pageChangeSuper(MultiPageEditor.java:615) at org.apache.uima.dde.internal.DeploymentDescriptorEditor.pageChangeForCurrentEditor(DeploymentDescriptorEditor.java:308) at org.apache.uima.taeconfigurator.editors.MultiPageEditor.pageChange(MultiPageEditor.java:1118) at org.eclipse.ui.part.MultiPageEditorPart.setActivePage(MultiPageEditorPart.java:973) at org.eclipse.ui.forms.editor.FormEditor.setActivePage(FormEditor.java:623) at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:314) 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.EditorReference.getEditor(EditorReference.java:266) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2820) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2729) at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2721) at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2673) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2668) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2652) at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:337) at org.eclipse.ui.actions.OpenWithMenu.access$0(OpenWithMenu.java:325) at org.eclipse.ui.actions.OpenWithMenu$2.handleEvent(OpenWithMenu.java:187) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422) at
[jira] Closed: (UIMA-1076) In DDE, CAS pool size setting is Not Applicable when Top AE is a primitive AE
[ https://issues.apache.org/jira/browse/UIMA-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin closed UIMA-1076. -- Fixed and resolved In DDE, CAS pool size setting is Not Applicable when Top AE is a primitive AE - Key: UIMA-1076 URL: https://issues.apache.org/jira/browse/UIMA-1076 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2 Reporter: Tong Fin Assignee: Tong Fin Priority: Trivial Fix For: 2.3AS Attachments: DDE_PATCH_1of2_JIRA1076_08-19-2008.txt, DDE_Replaced_PATCH_2of2_JIRA1076_08-19-2008.txt In DDE, CAS pool size setting is Not Applicable (should be disable) when Top AE is a primitive AE -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (UIMA-848) DDE should not use local replyQueue with http broker
[ https://issues.apache.org/jira/browse/UIMA-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin reassigned UIMA-848: - Assignee: Tong Fin defer to after 2.3.0 release Will revisit the issue DDE should not use local replyQueue with http broker Key: UIMA-848 URL: https://issues.apache.org/jira/browse/UIMA-848 Project: UIMA Issue Type: Bug Components: Eclipse plugins Reporter: Burn Lewis Assignee: Tong Fin Priority: Minor In DDE when a broker URL starts with http the replyQueue value must be remote or omitted. Perhaps hide or gray-out the Service client is inside firewall field. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-848) DDE should not use local replyQueue with http broker
[ https://issues.apache.org/jira/browse/UIMA-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-848: -- Affects Version/s: 2.3AS DDE should not use local replyQueue with http broker Key: UIMA-848 URL: https://issues.apache.org/jira/browse/UIMA-848 Project: UIMA Issue Type: Bug Components: Eclipse plugins Affects Versions: 2.3AS Reporter: Burn Lewis Assignee: Tong Fin Priority: Minor In DDE when a broker URL starts with http the replyQueue value must be remote or omitted. Perhaps hide or gray-out the Service client is inside firewall field. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1332) [DDE] Allow an empty value for the Broker URL for input queue field (related to UIMA-1288)
[ https://issues.apache.org/jira/browse/UIMA-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin closed UIMA-1332. -- Resolution: Invalid This JIRA is not valid anymore (see UIMA-1288) [DDE] Allow an empty value for the Broker URL for input queue field (related to UIMA-1288) -- Key: UIMA-1332 URL: https://issues.apache.org/jira/browse/UIMA-1332 Project: UIMA Issue Type: Improvement Components: Eclipse plugins Reporter: Tong Fin Assignee: Tong Fin Priority: Minor Fix For: 2.3AS Allow an empty value for the Broker URL for input queue field in Overview page of DDE GUI. Right now, the value of this field is required. See UIMA-1288 for details. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1156) [SimpleServer] Add improvement to support UIMA-AS services
[ https://issues.apache.org/jira/browse/UIMA-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin closed UIMA-1156. -- Resolution: Fixed Fix Version/s: 2.3AS See Sandbox's SimpleUimaAsService project that has been developed as an extension of SimpleServer. [SimpleServer] Add improvement to support UIMA-AS services -- Key: UIMA-1156 URL: https://issues.apache.org/jira/browse/UIMA-1156 Project: UIMA Issue Type: Improvement Components: Sandbox-SimpleServer Reporter: Tong Fin Assignee: Tong Fin Priority: Minor Fix For: 2.3AS Currently, the Simple Server supports calling to PEAR-based and descriptor-based analysis engines. This improvement will add the support to call UIMA-AS services. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1288) Need a Better Approach For Specifying UIMA AS Broker URL in Deployment Descriptor
[
https://issues.apache.org/jira/browse/UIMA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12748857#action_12748857
]
Tong Fin commented on UIMA-1288:
When a new deployment descriptor for UIMA-AS is created, the current behavior
of the Deployment Descriptor Editor (DDE) GUI is to initialized the field of
the brokerURL with the tcp://localhost:61616 string.
With this JIRA, the initialized string of the brokerURL field will be
${defaultBrokerURL}. This string can be changed by a user to any string as
necessary.
Need a Better Approach For Specifying UIMA AS Broker URL in Deployment
Descriptor
-
Key: UIMA-1288
URL: https://issues.apache.org/jira/browse/UIMA-1288
Project: UIMA
Issue Type: Improvement
Components: Async Scaleout
Reporter: Jerry Cwiklik
Assignee: Tong Fin
Each UIMA AS deployment descriptor requires at least one Broker URL for the
connection factory. Instead of hard coding the URL, perhaps a placeholder for
it should be used. At runtime, the placeholder could be resolved to the
actual URL by Spring resolver component. The value could come from either an
external file or from an environment. The new approach should accommodate
specifying more than one placeholder, since an aggregate may have delegates
whose queues are managed by a different broker. The new approach would
simplify deployment of UIMA AS services, especially during testing.
A placeholder syntax could be inherited from Spring, where it looks like
${placeholder-name}.
dd2spring would need to change to handle a placeholder notation in addition
to supporting hard coded broker URL that we use now. A new bean must be added
to the generated xml. It will be :
bean
class=org.springframework.beans.factory.config.PropertyPlaceholderConfigurer
property name=systemPropertiesModeName
value=SYSTEM_PROPERTIES_MODE_OVERRIDE/
/bean
This bean is setup to resolve placeholders using system variables, like
-Dplaceholder-name=placeholder-value
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1288) Need a Better Approach For Specifying UIMA AS Broker URL in Deployment Descriptor
[
https://issues.apache.org/jira/browse/UIMA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tong Fin closed UIMA-1288.
--
Resolution: Fixed
Fix Version/s: 2.3AS
Need a Better Approach For Specifying UIMA AS Broker URL in Deployment
Descriptor
-
Key: UIMA-1288
URL: https://issues.apache.org/jira/browse/UIMA-1288
Project: UIMA
Issue Type: Improvement
Components: Async Scaleout
Reporter: Jerry Cwiklik
Assignee: Tong Fin
Fix For: 2.3AS
Each UIMA AS deployment descriptor requires at least one Broker URL for the
connection factory. Instead of hard coding the URL, perhaps a placeholder for
it should be used. At runtime, the placeholder could be resolved to the
actual URL by Spring resolver component. The value could come from either an
external file or from an environment. The new approach should accommodate
specifying more than one placeholder, since an aggregate may have delegates
whose queues are managed by a different broker. The new approach would
simplify deployment of UIMA AS services, especially during testing.
A placeholder syntax could be inherited from Spring, where it looks like
${placeholder-name}.
dd2spring would need to change to handle a placeholder notation in addition
to supporting hard coded broker URL that we use now. A new bean must be added
to the generated xml. It will be :
bean
class=org.springframework.beans.factory.config.PropertyPlaceholderConfigurer
property name=systemPropertiesModeName
value=SYSTEM_PROPERTIES_MODE_OVERRIDE/
/bean
This bean is setup to resolve placeholders using system variables, like
-Dplaceholder-name=placeholder-value
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (UIMA-1373) SimpleUimaAsService needs a POM
[ https://issues.apache.org/jira/browse/UIMA-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin resolved UIMA-1373. Resolution: Fixed Hi Tommaso, Thank for the helps. I checked in your patch into UIMA svn. Please verify. If it works properly, please close this issue. -- Tong SimpleUimaAsService needs a POM --- Key: UIMA-1373 URL: https://issues.apache.org/jira/browse/UIMA-1373 Project: UIMA Issue Type: Bug Components: Sandbox-SimpleUimaAsService Affects Versions: 2.3 Reporter: Tommaso Teofili Fix For: 2.3 Attachments: 1373patch.txt The Simple UIMA As Service does not have a Project Object Model (POM) file -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1334) Sandbox - SimpleServer missing config-xml.jar
[ https://issues.apache.org/jira/browse/UIMA-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12702548#action_12702548 ] Tong Fin commented on UIMA-1334: I think the exception is not related to the non-existence of config-xml.jar (which should be uima-simple-server-xbean.jar I think). The exception occurs when the pear is being installed and verifed. It looks like you have Apache xerces in Tomcat classpath which may cause the parsing problem. -- Tong Sandbox - SimpleServer missing config-xml.jar - Key: UIMA-1334 URL: https://issues.apache.org/jira/browse/UIMA-1334 Project: UIMA Issue Type: Bug Components: Sandbox-SimpleServer Environment: Ubuntu Linux 8.10, JDK 1.5.0_16. Reporter: Himanshu Rathod The SimpleServer tutorial mentions a config-xml.jar file to be copied into the CATALINA_HOME/shared/lib directory. However, that file does not exist when using a subversion checkout of the sandbox trunk. I am not sure if this is related, but starting the Tomcat instance without this file results in the following exception: Apr 24, 2009 2:06:59 PM org.apache.uima.simpleserver.servlet.SimpleServerServlet initServer SEVERE: UIMA Simple Service configuaration failed org.apache.uima.pear.tools.PackageInstallerException: The following error occurred during the installation verification of component WhitespaceTokenizer: org.apache.uima.util.InvalidXMLException: Invalid descriptor at file:/opt/cagrid/jakarta-tomcat-5.0.28/webapps/uima/resources/./WhitespaceTokenizer/desc/WhitespaceTokenizer.xml. at org.apache.uima.util.impl.XMLParser_impl.parse(XMLParser_impl.java:193) at org.apache.uima.util.impl.XMLParser_impl.parseResourceManagerConfiguration(XMLParser_impl.java:760) at org.apache.uima.util.impl.XMLParser_impl.parseResourceManagerConfiguration(XMLParser_impl.java:748) at org.apache.uima.pear.util.UIMAUtil.identifyUimaComponentCategory(UIMAUtil.java:246) at org.apache.uima.pear.util.UIMAUtil.identifyUimaComponentCategory(UIMAUtil.java:126) at org.apache.uima.pear.tools.InstallationTester.init(InstallationTester.java:97) at org.apache.uima.pear.tools.InstallationController.verifyComponentInstallation(InstallationController.java:1109) at org.apache.uima.pear.tools.InstallationController.verifyComponent(InstallationController.java:1993) at org.apache.uima.pear.tools.PackageInstaller.installPackage(PackageInstaller.java:233) at org.apache.uima.pear.tools.PackageInstaller.installPackage(PackageInstaller.java:67) at org.apache.uima.simpleserver.Service.loadPear(Service.java:294) at org.apache.uima.simpleserver.Service.configurePear(Service.java:141) at org.apache.uima.simpleserver.servlet.SimpleServerServlet.initServer(SimpleServerServlet.java:277) at org.apache.uima.simpleserver.servlet.SimpleServerServlet.init(SimpleServerServlet.java:228) at javax.servlet.GenericServlet.init(GenericServlet.java:211) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1029) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:687) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:144) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) at
[jira] Created: (UIMA-1332) [DDE] Allow an empty value for the Broker URL for input queue field (related to UIMA-1288)
[DDE] Allow an empty value for the Broker URL for input queue field (related to UIMA-1288) -- Key: UIMA-1332 URL: https://issues.apache.org/jira/browse/UIMA-1332 Project: UIMA Issue Type: Improvement Components: Eclipse plugins Reporter: Tong Fin Assignee: Tong Fin Priority: Minor Fix For: 2.3AS Allow an empty value for the Broker URL for input queue field in Overview page of DDE GUI. Right now, the value of this field is required. See UIMA-1288 for details. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1314) Add OSGI support to uima-as
[ https://issues.apache.org/jira/browse/UIMA-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12695396#action_12695396 ] Tong Fin commented on UIMA-1314: Jörn, I suggest that you try to wrap UIMA-AS as a fragment of uimaj-ep-runtime plugin instead of a plugin. -- Tong Add OSGI support to uima-as --- Key: UIMA-1314 URL: https://issues.apache.org/jira/browse/UIMA-1314 Project: UIMA Issue Type: New Feature Components: Async Scaleout Reporter: Jörn Kottmann Assignee: Jörn Kottmann Priority: Minor UIMA AS should support running in an OSGI container. To achieve this an uimaj-as-ep-runtime plugin is added to the uima-as project which creates an osgi bundle which wraps all uima-as jar files, like it is done for the uimaj-ep-runtime plugin. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1260) [SimpleServer] Expose some private variables and method as protected so that new subclasses for UIMA-AS can be defined
[ https://issues.apache.org/jira/browse/UIMA-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin closed UIMA-1260. -- Resolution: Fixed [SimpleServer] Expose some private variables and method as protected so that new subclasses for UIMA-AS can be defined -- Key: UIMA-1260 URL: https://issues.apache.org/jira/browse/UIMA-1260 Project: UIMA Issue Type: Improvement Components: Sandbox-SimpleServer Reporter: Tong Fin Assignee: Tong Fin Priority: Minor Fix For: 2.3 See comment in UIMA-1156 (http://issues.apache.org/jira/browse/UIMA-1156) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1261) [SimpleUimaAsService] Document on Wiki on how to use SimpleServer for UIMA-AS by using some examples
[SimpleUimaAsService] Document on Wiki on how to use SimpleServer for UIMA-AS by using some examples Key: UIMA-1261 URL: https://issues.apache.org/jira/browse/UIMA-1261 Project: UIMA Issue Type: Improvement Components: Sandbox-SimpleUimaAsService Reporter: Tong Fin Assignee: Tong Fin Priority: Minor Fix For: 2.3 Document on Wiki on how to use SimpleServer for UIMA-AS by using some examples. Will include the same example as SimpleServer which is already documented in Wiki by Thilo, but will extend it to UIMA-AS. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1261) [SimpleUimaAsService] Document in Wiki on how to use SimpleServer for UIMA-AS by using some examples
[ https://issues.apache.org/jira/browse/UIMA-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-1261: --- Description: Document in Wiki on how to use SimpleServer for UIMA-AS by using some examples. Will include the same example as SimpleServer which is already documented in Wiki by Thilo, but will extend it to UIMA-AS. was: Document on Wiki on how to use SimpleServer for UIMA-AS by using some examples. Will include the same example as SimpleServer which is already documented in Wiki by Thilo, but will extend it to UIMA-AS. Summary: [SimpleUimaAsService] Document in Wiki on how to use SimpleServer for UIMA-AS by using some examples (was: [SimpleUimaAsService] Document on Wiki on how to use SimpleServer for UIMA-AS by using some examples) [SimpleUimaAsService] Document in Wiki on how to use SimpleServer for UIMA-AS by using some examples Key: UIMA-1261 URL: https://issues.apache.org/jira/browse/UIMA-1261 Project: UIMA Issue Type: Improvement Components: Sandbox-SimpleUimaAsService Reporter: Tong Fin Assignee: Tong Fin Priority: Minor Fix For: 2.3 Document in Wiki on how to use SimpleServer for UIMA-AS by using some examples. Will include the same example as SimpleServer which is already documented in Wiki by Thilo, but will extend it to UIMA-AS. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1078) Pool size and heap size for CAS Multiplier should NOT be displayed (be disable) for Top Analysis Engine running as AS aggregate
[ https://issues.apache.org/jira/browse/UIMA-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin closed UIMA-1078. -- Resolution: Fixed Fix Version/s: 2.3AS Fixed Pool size and heap size for CAS Multiplier should NOT be displayed (be disable) for Top Analysis Engine running as AS aggregate --- Key: UIMA-1078 URL: https://issues.apache.org/jira/browse/UIMA-1078 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2 Reporter: Tong Fin Assignee: Tong Fin Priority: Trivial Fix For: 2.3AS In DDE 2nd page, if the aggregate CAS Mutiplier runs as an AS aggregate, the pool size and heap size for CAS Multiplier fields should NOT be displayed when Top Analysis Engine is selected. It means that the pool size and heap size for CAS Multiplier fields are only displayed when the delegate CAS Multiplier is selected. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1102) CAS Viewer submission
[ https://issues.apache.org/jira/browse/UIMA-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin closed UIMA-1102. -- Resolution: Fixed Done CAS Viewer submission - Key: UIMA-1102 URL: https://issues.apache.org/jira/browse/UIMA-1102 Project: UIMA Issue Type: New Feature Components: Tools Reporter: Tong Fin Assignee: Tong Fin Priority: Minor Attachments: CAS Viewer Functionality Comparison.doc, CAS Viewer User Guide-07-02-2008.doc, DotCorpusReader.java, uima-casviewer-07-01-2008.zip, uima-casviewer-07-01-2008.zip.md5 The CAS Viewer is a tool for exploring the contents of the CAS that contains types, feature structures, feature values, and indices created when analysis engines are run over some input text documents. It unlocks and visualizes the CAS content by providing the following information: - Annotations with associated types - Indices that reside in the index repository -Annotated text document UIMA developers can take benefits of the visualization and navigation capabilities inside the CAS content to debug and accelerate the development of their UIMA components. The CAS Viewer runs as an Eclipse's plug-in and provides a GUI for visualizing serialized CAS saved as XMI (XML Metadata Interchange) format. It also provides APIs for other tools to customize and extend its functionality and its user interface. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1240) Deployment Descriptor Editor resets CAS Pool size for aggregates when you change number of instances of a delegate
[ https://issues.apache.org/jira/browse/UIMA-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin closed UIMA-1240. -- Resolution: Fixed Fix Version/s: 2.3AS Fixed Deployment Descriptor Editor resets CAS Pool size for aggregates when you change number of instances of a delegate -- Key: UIMA-1240 URL: https://issues.apache.org/jira/browse/UIMA-1240 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Reporter: Adam Lally Assignee: Tong Fin Fix For: 2.3AS I have an async aggregate with multiple delegates. When I set the number of instances of one of the delegates (it happened to be a CAS Multiplier, but I'm not sure that matters), the DDE automatically reset the CAS Pool size of the entire aggregate to the same value! It took me quite a while to figure out that this was the reason my application started running more slowly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1260) [SimpleServer] Expose some private variables and method as protected so that new subclasses for UIMA-AS can be defined
[SimpleServer] Expose some private variables and method as protected so that new subclasses for UIMA-AS can be defined -- Key: UIMA-1260 URL: https://issues.apache.org/jira/browse/UIMA-1260 Project: UIMA Issue Type: Improvement Components: Sandbox-SimpleServer Reporter: Tong Fin Assignee: Tong Fin Priority: Minor Fix For: 2.3 See comment in UIMA-1156 (http://issues.apache.org/jira/browse/UIMA-1156) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1156) [SimpleServer] Add improvement to support UIMA-AS services
[ https://issues.apache.org/jira/browse/UIMA-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12660374#action_12660374 ] Tong Fin commented on UIMA-1156: When extending SimpleServer to support UIMA-AS, the following design will be taken: 1. SimpleServer project will NOT depend on UIMA-AS, i.e. users that run SimpleServer will not require to include UIMA-AS runtime 2. UIMA-AS support for SimpleServer will be an ADD-ON to SimpleServer. We will create a project in Sandbox for this add-on To meet above design creteria, we will: - expose some private variables and method as protected so that new subclasses for UIMA-AS can be defined (a new JIRA will be created [UIMA-1260]) [SimpleServer] Add improvement to support UIMA-AS services -- Key: UIMA-1156 URL: https://issues.apache.org/jira/browse/UIMA-1156 Project: UIMA Issue Type: Improvement Components: Sandbox-SimpleServer Reporter: Tong Fin Assignee: Tong Fin Priority: Minor Currently, the Simple Server supports calling to PEAR-based and descriptor-based analysis engines. This improvement will add the support to call UIMA-AS services. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1176) JCasGen shouldn't generate types for imported type systems (or at least it should be an option)
[
https://issues.apache.org/jira/browse/UIMA-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12631629#action_12631629
]
Tong Fin commented on UIMA-1176:
Good point Adam !
How about this:
- Start from the top-level descriptor
- if ( the imported descriptor belong to different project AND this
different project is NOT in the dependency project list ) {
* generate class for this imported descriptor
} else {
* do nothing
}
Not sure about the implementation !
JCasGen shouldn't generate types for imported type systems (or at least it
should be an option)
---
Key: UIMA-1176
URL: https://issues.apache.org/jira/browse/UIMA-1176
Project: UIMA
Issue Type: Improvement
Components: Eclipse plugins, Tools
Affects Versions: 2.3
Reporter: Adam Lally
Our project reuses a common type system that we got from a different source.
The common type system descriptor is imported into our main type system
descriptor. The common type system has its own JCas types, in a jar file.
When we generate JCas types for our main type system descriptor, it currently
generates all of the classes for all of the imported type systems as well.
We don't want this behavior, so we have to manually go through and delete
those classes.
I think JCasGen should only generate types for the type system descriptor
that you run it on, not on imported type system descriptors.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1146) Setting the number of concurrent listeners of a reply queue for Co-located Delegates
[ https://issues.apache.org/jira/browse/UIMA-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin closed UIMA-1146. -- Verified Setting the number of concurrent listeners of a reply queue for Co-located Delegates Key: UIMA-1146 URL: https://issues.apache.org/jira/browse/UIMA-1146 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Tong Fin Fix For: 2.3AS Attachments: DDE_Patch_1of2_JIRA-1146.txt, DDE_Patch_2of2Modified08-25-2008_JIRA-1146.txt, queue-listeners.jpg JIRA-1130 has improved UIMA-AS to allow users to set the number of concurrent listeners of a reply queue for each remote delegate. The following is the syntax in the xml deployment descriptor (as an example): analysisEngine async=true delegates remoteAnalysisEngine key=RoomNumber inputQueue brokerURL=tcp://localhost:61616 endpoint=RoomNumberAnnotatorQueue/ replyQueue concurrentConsumers=2 location=remote/ ... /remoteAnalysisEngine /delegates ... /analysisEngine This JIRA will do the similar thing by allowing users to set the number of concurrent listeners of a reply queue for co-located delegates inside the UIMA-AS aggregate. The following is the proposed syntax: analysisEngine async=true !-- Top aggregate -- replyQueue concurrentConsumers=2 ... delegates analysisEngine key=NamesAndPersonTitlesTAE async=true !-- co-located aggregate -- replyQueue concurrentConsumers=3 ... /analysisEngine ... /delegates ... /analysisEngine -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (UIMA-1136) [DDE] Support editing of Prefetch value and set default value to 0 (instead of 1)
[ https://issues.apache.org/jira/browse/UIMA-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin reassigned UIMA-1136: -- Assignee: Marshall Schor (was: Tong Fin) Marshall, Pls help to apply the patch (2 files). -- Tong [DDE] Support editing of Prefetch value and set default value to 0 (instead of 1) - Key: UIMA-1136 URL: https://issues.apache.org/jira/browse/UIMA-1136 Project: UIMA Issue Type: Improvement Components: Async Scaleout Reporter: Tong Fin Assignee: Marshall Schor Priority: Trivial Fix For: 2.3AS Attachments: DDE_Patch_1of2_JIRA-1136.txt, DDE_Patch_2of2_JIRA-1136.txt, screenshot-1.jpg For the current version of DDE, to change the value of the Prefetch of the Top AE, the user needs to modify the value in the source XML. Until now, the default value is set to 1. We will modify the DDE as follows: 1. Allow user to modify the prefetch value with GUI (in the 1st page of DDE) 2. Set the default value to 0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1136) [DDE] Support editing of Prefetch value and set default value to 0 (instead of 1)
[ https://issues.apache.org/jira/browse/UIMA-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-1136: --- Attachment: screenshot-1.jpg The UI of updating prefetch value (default is 0) [DDE] Support editing of Prefetch value and set default value to 0 (instead of 1) - Key: UIMA-1136 URL: https://issues.apache.org/jira/browse/UIMA-1136 Project: UIMA Issue Type: Improvement Components: Async Scaleout Reporter: Tong Fin Assignee: Tong Fin Priority: Trivial Fix For: 2.3AS Attachments: DDE_Patch_1of2_JIRA-1136.txt, DDE_Patch_2of2_JIRA-1136.txt, screenshot-1.jpg For the current version of DDE, to change the value of the Prefetch of the Top AE, the user needs to modify the value in the source XML. Until now, the default value is set to 1. We will modify the DDE as follows: 1. Allow user to modify the prefetch value with GUI (in the 1st page of DDE) 2. Set the default value to 0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1156) [SimpleServer] Add improvement to support UIMA-AS services
[SimpleServer] Add improvement to support UIMA-AS services -- Key: UIMA-1156 URL: https://issues.apache.org/jira/browse/UIMA-1156 Project: UIMA Issue Type: Improvement Components: Sandbox-SimpleServer Reporter: Tong Fin Assignee: Tong Fin Priority: Minor Currently, the Simple Server supports calling to PEAR-based and descriptor-based analysis engines. This improvement will add the support to call UIMA-AS services. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1146) Setting the number of concurrent listeners of a reply queue for Co-located Delegates
[ https://issues.apache.org/jira/browse/UIMA-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-1146: --- Attachment: queue-listeners.jpg Screen-shot for supporting queue listeners for AS aggregate BTW, I am testing the Wiki style markup for image. Setting the number of concurrent listeners of a reply queue for Co-located Delegates Key: UIMA-1146 URL: https://issues.apache.org/jira/browse/UIMA-1146 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Marshall Schor Attachments: DDE_Patch_1of2_JIRA-1146.txt, DDE_Patch_2of2_JIRA-1146.txt JIRA-1130 has improved UIMA-AS to allow users to set the number of concurrent listeners of a reply queue for each remote delegate. The following is the syntax in the xml deployment descriptor (as an example): analysisEngine async=true delegates remoteAnalysisEngine key=RoomNumber inputQueue brokerURL=tcp://localhost:61616 endpoint=RoomNumberAnnotatorQueue/ replyQueue concurrentConsumers=2 location=remote/ ... /remoteAnalysisEngine /delegates ... /analysisEngine This JIRA will do the similar thing by allowing users to set the number of concurrent listeners of a reply queue for co-located delegates inside the UIMA-AS aggregate. The following is the proposed syntax: analysisEngine async=true !-- Top aggregate -- replyQueue concurrentConsumers=2 ... delegates analysisEngine key=NamesAndPersonTitlesTAE async=true !-- co-located aggregate -- replyQueue concurrentConsumers=3 ... /analysisEngine ... /delegates ... /analysisEngine -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1146) Setting the number of concurrent listeners of a reply queue for Co-located Delegates
[ https://issues.apache.org/jira/browse/UIMA-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-1146: --- Attachment: (was: queue-listeners.jpg) Setting the number of concurrent listeners of a reply queue for Co-located Delegates Key: UIMA-1146 URL: https://issues.apache.org/jira/browse/UIMA-1146 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Marshall Schor Attachments: DDE_Patch_1of2_JIRA-1146.txt, DDE_Patch_2of2_JIRA-1146.txt JIRA-1130 has improved UIMA-AS to allow users to set the number of concurrent listeners of a reply queue for each remote delegate. The following is the syntax in the xml deployment descriptor (as an example): analysisEngine async=true delegates remoteAnalysisEngine key=RoomNumber inputQueue brokerURL=tcp://localhost:61616 endpoint=RoomNumberAnnotatorQueue/ replyQueue concurrentConsumers=2 location=remote/ ... /remoteAnalysisEngine /delegates ... /analysisEngine This JIRA will do the similar thing by allowing users to set the number of concurrent listeners of a reply queue for co-located delegates inside the UIMA-AS aggregate. The following is the proposed syntax: analysisEngine async=true !-- Top aggregate -- replyQueue concurrentConsumers=2 ... delegates analysisEngine key=NamesAndPersonTitlesTAE async=true !-- co-located aggregate -- replyQueue concurrentConsumers=3 ... /analysisEngine ... /delegates ... /analysisEngine -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1146) Setting the number of concurrent listeners of a reply queue for Co-located Delegates
[ https://issues.apache.org/jira/browse/UIMA-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-1146: --- Attachment: queue-listeners.jpg UI for queue listeners of an AS aggregate Setting the number of concurrent listeners of a reply queue for Co-located Delegates Key: UIMA-1146 URL: https://issues.apache.org/jira/browse/UIMA-1146 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Marshall Schor Attachments: DDE_Patch_1of2_JIRA-1146.txt, DDE_Patch_2of2_JIRA-1146.txt, queue-listeners.jpg JIRA-1130 has improved UIMA-AS to allow users to set the number of concurrent listeners of a reply queue for each remote delegate. The following is the syntax in the xml deployment descriptor (as an example): analysisEngine async=true delegates remoteAnalysisEngine key=RoomNumber inputQueue brokerURL=tcp://localhost:61616 endpoint=RoomNumberAnnotatorQueue/ replyQueue concurrentConsumers=2 location=remote/ ... /remoteAnalysisEngine /delegates ... /analysisEngine This JIRA will do the similar thing by allowing users to set the number of concurrent listeners of a reply queue for co-located delegates inside the UIMA-AS aggregate. The following is the proposed syntax: analysisEngine async=true !-- Top aggregate -- replyQueue concurrentConsumers=2 ... delegates analysisEngine key=NamesAndPersonTitlesTAE async=true !-- co-located aggregate -- replyQueue concurrentConsumers=3 ... /analysisEngine ... /delegates ... /analysisEngine -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1146) Setting the number of concurrent listeners of a reply queue for Co-located Delegates
[ https://issues.apache.org/jira/browse/UIMA-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12625483#action_12625483 ] Tong Fin commented on UIMA-1146: The following is the UI for the queue listeners of an AS aggregate. I used the Wiki markup. Does someone have the problem to see the screen-shot ? !queue-listeners.jpg! -- Tong Setting the number of concurrent listeners of a reply queue for Co-located Delegates Key: UIMA-1146 URL: https://issues.apache.org/jira/browse/UIMA-1146 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Marshall Schor Attachments: DDE_Patch_1of2_JIRA-1146.txt, DDE_Patch_2of2_JIRA-1146.txt, queue-listeners.jpg JIRA-1130 has improved UIMA-AS to allow users to set the number of concurrent listeners of a reply queue for each remote delegate. The following is the syntax in the xml deployment descriptor (as an example): analysisEngine async=true delegates remoteAnalysisEngine key=RoomNumber inputQueue brokerURL=tcp://localhost:61616 endpoint=RoomNumberAnnotatorQueue/ replyQueue concurrentConsumers=2 location=remote/ ... /remoteAnalysisEngine /delegates ... /analysisEngine This JIRA will do the similar thing by allowing users to set the number of concurrent listeners of a reply queue for co-located delegates inside the UIMA-AS aggregate. The following is the proposed syntax: analysisEngine async=true !-- Top aggregate -- replyQueue concurrentConsumers=2 ... delegates analysisEngine key=NamesAndPersonTitlesTAE async=true !-- co-located aggregate -- replyQueue concurrentConsumers=3 ... /analysisEngine ... /delegates ... /analysisEngine -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1146) Setting the number of concurrent listeners of a reply queue for Co-located Delegates
[ https://issues.apache.org/jira/browse/UIMA-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-1146: --- Attachment: DDE_Patch_2of2Modified08-25-2008_JIRA-1146.txt Marshall, I replaced the 2nd patch file to add some additional wording for the hover text. It is safer to apply my 2 patches one more time. Thanks, Tong Setting the number of concurrent listeners of a reply queue for Co-located Delegates Key: UIMA-1146 URL: https://issues.apache.org/jira/browse/UIMA-1146 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Marshall Schor Attachments: DDE_Patch_1of2_JIRA-1146.txt, DDE_Patch_2of2Modified08-25-2008_JIRA-1146.txt, queue-listeners.jpg JIRA-1130 has improved UIMA-AS to allow users to set the number of concurrent listeners of a reply queue for each remote delegate. The following is the syntax in the xml deployment descriptor (as an example): analysisEngine async=true delegates remoteAnalysisEngine key=RoomNumber inputQueue brokerURL=tcp://localhost:61616 endpoint=RoomNumberAnnotatorQueue/ replyQueue concurrentConsumers=2 location=remote/ ... /remoteAnalysisEngine /delegates ... /analysisEngine This JIRA will do the similar thing by allowing users to set the number of concurrent listeners of a reply queue for co-located delegates inside the UIMA-AS aggregate. The following is the proposed syntax: analysisEngine async=true !-- Top aggregate -- replyQueue concurrentConsumers=2 ... delegates analysisEngine key=NamesAndPersonTitlesTAE async=true !-- co-located aggregate -- replyQueue concurrentConsumers=3 ... /analysisEngine ... /delegates ... /analysisEngine -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1146) Setting the number of concurrent listeners of a reply queue for Co-located Delegates
[ https://issues.apache.org/jira/browse/UIMA-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-1146: --- Attachment: DDE_Patch_2of2_JIRA-1146.txt DDE_Patch_1of2_JIRA-1146.txt This patch is also for JIRA-1130 since the syntax for the remote reply queue listeners has changes. Setting the number of concurrent listeners of a reply queue for Co-located Delegates Key: UIMA-1146 URL: https://issues.apache.org/jira/browse/UIMA-1146 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Tong Fin Attachments: DDE_Patch_1of2_JIRA-1146.txt, DDE_Patch_2of2_JIRA-1146.txt JIRA-1130 has improved UIMA-AS to allow users to set the number of concurrent listeners of a reply queue for each remote delegate. The following is the syntax in the xml deployment descriptor (as an example): analysisEngine async=true delegates remoteAnalysisEngine key=RoomNumber inputQueue brokerURL=tcp://localhost:61616 endpoint=RoomNumberAnnotatorQueue/ replyQueue concurrentConsumers=2 location=remote/ ... /remoteAnalysisEngine /delegates ... /analysisEngine This JIRA will do the similar thing by allowing users to set the number of concurrent listeners of a reply queue for co-located delegates inside the UIMA-AS aggregate. The following is the proposed syntax: analysisEngine async=true !-- Top aggregate -- replyQueue concurrentConsumers=2 ... delegates analysisEngine key=NamesAndPersonTitlesTAE async=true !-- co-located aggregate -- replyQueue concurrentConsumers=3 ... /analysisEngine ... /delegates ... /analysisEngine -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (UIMA-1146) Setting the number of concurrent listeners of a reply queue for Co-located Delegates
[ https://issues.apache.org/jira/browse/UIMA-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin reassigned UIMA-1146: -- Assignee: Marshall Schor (was: Tong Fin) Marshall, Please help to apply the patch. If the work in DD2Spring is done, please re-assign back to me for testing. -- Tong Setting the number of concurrent listeners of a reply queue for Co-located Delegates Key: UIMA-1146 URL: https://issues.apache.org/jira/browse/UIMA-1146 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Marshall Schor Attachments: DDE_Patch_1of2_JIRA-1146.txt, DDE_Patch_2of2_JIRA-1146.txt JIRA-1130 has improved UIMA-AS to allow users to set the number of concurrent listeners of a reply queue for each remote delegate. The following is the syntax in the xml deployment descriptor (as an example): analysisEngine async=true delegates remoteAnalysisEngine key=RoomNumber inputQueue brokerURL=tcp://localhost:61616 endpoint=RoomNumberAnnotatorQueue/ replyQueue concurrentConsumers=2 location=remote/ ... /remoteAnalysisEngine /delegates ... /analysisEngine This JIRA will do the similar thing by allowing users to set the number of concurrent listeners of a reply queue for co-located delegates inside the UIMA-AS aggregate. The following is the proposed syntax: analysisEngine async=true !-- Top aggregate -- replyQueue concurrentConsumers=2 ... delegates analysisEngine key=NamesAndPersonTitlesTAE async=true !-- co-located aggregate -- replyQueue concurrentConsumers=3 ... /analysisEngine ... /delegates ... /analysisEngine -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1146) Setting the number of concurrent listeners of a reply queue for Co-located Delegates
[ https://issues.apache.org/jira/browse/UIMA-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12624966#action_12624966 ] Tong Fin commented on UIMA-1146: It looks like the following is the preferred syntax: attributes on analysisEngine itself: analysisEngine async=true internalReplyQueueScaleout=nn1 inputQueueScaleout=nn2 /analysisEngine And, for JIRA-1130: remoteAnalysisEngine remoteReplyQueueScaleout=nn1 /remoteAnalysisEngine I will start to do the work based on the above syntax if there is no objection :) -- Tong Setting the number of concurrent listeners of a reply queue for Co-located Delegates Key: UIMA-1146 URL: https://issues.apache.org/jira/browse/UIMA-1146 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Tong Fin JIRA-1130 has improved UIMA-AS to allow users to set the number of concurrent listeners of a reply queue for each remote delegate. The following is the syntax in the xml deployment descriptor (as an example): analysisEngine async=true delegates remoteAnalysisEngine key=RoomNumber inputQueue brokerURL=tcp://localhost:61616 endpoint=RoomNumberAnnotatorQueue/ replyQueue concurrentConsumers=2 location=remote/ ... /remoteAnalysisEngine /delegates ... /analysisEngine This JIRA will do the similar thing by allowing users to set the number of concurrent listeners of a reply queue for co-located delegates inside the UIMA-AS aggregate. The following is the proposed syntax: analysisEngine async=true !-- Top aggregate -- replyQueue concurrentConsumers=2 ... delegates analysisEngine key=NamesAndPersonTitlesTAE async=true !-- co-located aggregate -- replyQueue concurrentConsumers=3 ... /analysisEngine ... /delegates ... /analysisEngine -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1130) Deployment Descriptor should allow setting the number of concurrent listeners for a reply queue
[ https://issues.apache.org/jira/browse/UIMA-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12624967#action_12624967 ] Tong Fin commented on UIMA-1130: To be consistent with the preferred syntax in JIRA-1146, we will adopt the following syntax: remoteAnalysisEngine remoteReplyQueueScaleout=nn1 /remoteAnalysisEngine I will start to do the work based on the above syntax if there is no objection :) -- Tong Deployment Descriptor should allow setting the number of concurrent listeners for a reply queue --- Key: UIMA-1130 URL: https://issues.apache.org/jira/browse/UIMA-1130 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.2 Reporter: Adam Lally Assignee: Marshall Schor Attachments: DDE_PATCH_JIRA_1130_A.txt, DDE_PATCH_JIRA_1130_B.txt The Spring XML allows setting a concurrentConsumers property for a reply queue (either an aggregate's collocated reply queue or a remote reply queue): property name=concurrentConsumers value=1/ The deployment descriptor should allow setting this property. In some deployments where remote delegates are scaled out many times, the bottleneck can become the aggregate deserializing CASes from the reply queue. If the aggregate is running on a multicore machine it helps to increase the number of threads that can process the reply queue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1130) Deployment Descriptor should allow setting the number of concurrent listeners for a reply queue
[ https://issues.apache.org/jira/browse/UIMA-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin closed UIMA-1130. -- Testing after the patch is done. Work properly. Deployment Descriptor should allow setting the number of concurrent listeners for a reply queue --- Key: UIMA-1130 URL: https://issues.apache.org/jira/browse/UIMA-1130 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.2 Reporter: Adam Lally Assignee: Tong Fin Attachments: DDE_PATCH_JIRA_1130_A.txt, DDE_PATCH_JIRA_1130_B.txt The Spring XML allows setting a concurrentConsumers property for a reply queue (either an aggregate's collocated reply queue or a remote reply queue): property name=concurrentConsumers value=1/ The deployment descriptor should allow setting this property. In some deployments where remote delegates are scaled out many times, the bottleneck can become the aggregate deserializing CASes from the reply queue. If the aggregate is running on a multicore machine it helps to increase the number of threads that can process the reply queue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (UIMA-1076) In DDE, CAS pool size setting is Not Applicable when Top AE is a primitive AE
[ https://issues.apache.org/jira/browse/UIMA-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin reassigned UIMA-1076: -- Assignee: Marshall Schor (was: Tong Fin) Hi Marshall, Please help to apply the patch. -- Tong In DDE, CAS pool size setting is Not Applicable when Top AE is a primitive AE - Key: UIMA-1076 URL: https://issues.apache.org/jira/browse/UIMA-1076 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2 Reporter: Tong Fin Assignee: Marshall Schor Priority: Trivial Attachments: DDE_PATCH_1of2_JIRA1076_08-19-2008.txt, DDE_PATCH_2of2_JIRA1076_08-19-2008.txt In DDE, CAS pool size setting is Not Applicable (should be disable) when Top AE is a primitive AE -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1076) In DDE, CAS pool size setting is Not Applicable when Top AE is a primitive AE
[ https://issues.apache.org/jira/browse/UIMA-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-1076: --- Attachment: DDE_PATCH_2of2_JIRA1076_08-19-2008.txt DDE_PATCH_1of2_JIRA1076_08-19-2008.txt If the Top AE is a primitive (i.e., async=false), the setting of the CAS pool size in GUI is disable. This pool size is suggested to be the same as the number of instances. After this patch, DDE will behave as follows: 1. When the deployment descriptor is open, if Top AE is primitive (i.e., async=false) and the CAS pool size is NOT equal to the specified number of instances, a Warning Dialog will be displayed with the OK and CANCEL options for modifying the CAS pool size to the same value as the number of instances. If OK is selected, DDE will modify the CAS pool size. If CANCEL is selected, DDE will not modify the value. 2. If Top AE is primitive, the CAS pool size in GUI is disable and its value will be SYNC with the value of the number of instances. In DDE, CAS pool size setting is Not Applicable when Top AE is a primitive AE - Key: UIMA-1076 URL: https://issues.apache.org/jira/browse/UIMA-1076 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2 Reporter: Tong Fin Assignee: Tong Fin Priority: Trivial Attachments: DDE_PATCH_1of2_JIRA1076_08-19-2008.txt, DDE_PATCH_2of2_JIRA1076_08-19-2008.txt In DDE, CAS pool size setting is Not Applicable (should be disable) when Top AE is a primitive AE -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1034) [DDE] Dirty flag is not set when environment parameters are edited
[ https://issues.apache.org/jira/browse/UIMA-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin closed UIMA-1034. -- Resolution: Fixed This bug is fixed as the result of applying the patch for JIRA-1130. [DDE] Dirty flag is not set when environment parameters are edited -- Key: UIMA-1034 URL: https://issues.apache.org/jira/browse/UIMA-1034 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Tong Fin Priority: Trivial User has reported that, when environment parameters are edited, the save command is not enable. Bug: When environment parameters are edited, the dirty flag is not set (that is why save is not enable). Work-around: Until the fix is released, user can make the save enable by editing fields other than the environment parameters. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1146) Setting the number of concurrent listeners off a reply queue for Co-located Delegates
Setting the number of concurrent listeners off a reply queue for Co-located Delegates - Key: UIMA-1146 URL: https://issues.apache.org/jira/browse/UIMA-1146 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Tong Fin JIRA-1130 has improved UIMA-AS to allow users to set the number of concurrent listeners of a reply queue for each remote delegate. The following is the syntax in the xml deployment descriptor (as an example): analysisEngine async=true delegates remoteAnalysisEngine key=RoomNumber inputQueue brokerURL=tcp://localhost:61616 endpoint=RoomNumberAnnotatorQueue/ replyQueue concurrentConsumers=2 location=remote/ ... /remoteAnalysisEngine /delegates ... /analysisEngine This JIRA will do the similar thing by allowing users to set the number of concurrent listeners of a reply queue for co-located delegates inside the UIMA-AS aggregate. The following is the proposed syntax: analysisEngine async=true !-- Top aggregate -- replyQueue concurrentConsumers=2 ... delegates analysisEngine key=NamesAndPersonTitlesTAE async=true !-- co-located aggregate -- replyQueue concurrentConsumers=3 ... /analysisEngine ... /delegates ... /analysisEngine -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1146) Setting the number of concurrent listeners of a reply queue for Co-located Delegates
[ https://issues.apache.org/jira/browse/UIMA-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-1146: --- Summary: Setting the number of concurrent listeners of a reply queue for Co-located Delegates (was: Setting the number of concurrent listeners off a reply queue for Co-located Delegates) Correct spelling Setting the number of concurrent listeners of a reply queue for Co-located Delegates Key: UIMA-1146 URL: https://issues.apache.org/jira/browse/UIMA-1146 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Tong Fin JIRA-1130 has improved UIMA-AS to allow users to set the number of concurrent listeners of a reply queue for each remote delegate. The following is the syntax in the xml deployment descriptor (as an example): analysisEngine async=true delegates remoteAnalysisEngine key=RoomNumber inputQueue brokerURL=tcp://localhost:61616 endpoint=RoomNumberAnnotatorQueue/ replyQueue concurrentConsumers=2 location=remote/ ... /remoteAnalysisEngine /delegates ... /analysisEngine This JIRA will do the similar thing by allowing users to set the number of concurrent listeners of a reply queue for co-located delegates inside the UIMA-AS aggregate. The following is the proposed syntax: analysisEngine async=true !-- Top aggregate -- replyQueue concurrentConsumers=2 ... delegates analysisEngine key=NamesAndPersonTitlesTAE async=true !-- co-located aggregate -- replyQueue concurrentConsumers=3 ... /analysisEngine ... /delegates ... /analysisEngine -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1130) Deployment Descriptor should allow setting the number of concurrent listeners for a reply queue
[ https://issues.apache.org/jira/browse/UIMA-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-1130: --- Attachment: DDE_PATCH_JIRA_1130_B.txt DDE_PATCH_JIRA_1130_A.txt Deployment Descriptor should allow setting the number of concurrent listeners for a reply queue --- Key: UIMA-1130 URL: https://issues.apache.org/jira/browse/UIMA-1130 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.2 Reporter: Adam Lally Attachments: DDE_PATCH_JIRA_1130_A.txt, DDE_PATCH_JIRA_1130_B.txt The Spring XML allows setting a concurrentConsumers property for a reply queue (either an aggregate's collocated reply queue or a remote reply queue): property name=concurrentConsumers value=1/ The deployment descriptor should allow setting this property. In some deployments where remote delegates are scaled out many times, the bottleneck can become the aggregate deserializing CASes from the reply queue. If the aggregate is running on a multicore machine it helps to increase the number of threads that can process the reply queue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (UIMA-1130) Deployment Descriptor should allow setting the number of concurrent listeners for a reply queue
[ https://issues.apache.org/jira/browse/UIMA-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin reassigned UIMA-1130: -- Assignee: Marshall Schor Deployment Descriptor should allow setting the number of concurrent listeners for a reply queue --- Key: UIMA-1130 URL: https://issues.apache.org/jira/browse/UIMA-1130 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.2 Reporter: Adam Lally Assignee: Marshall Schor Attachments: DDE_PATCH_JIRA_1130_A.txt, DDE_PATCH_JIRA_1130_B.txt The Spring XML allows setting a concurrentConsumers property for a reply queue (either an aggregate's collocated reply queue or a remote reply queue): property name=concurrentConsumers value=1/ The deployment descriptor should allow setting this property. In some deployments where remote delegates are scaled out many times, the bottleneck can become the aggregate deserializing CASes from the reply queue. If the aggregate is running on a multicore machine it helps to increase the number of threads that can process the reply queue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1136) [DDE] Support editing of Prefetch value and set default value to 0 (instead of 1)
[DDE] Support editing of Prefetch value and set default value to 0 (instead of 1) - Key: UIMA-1136 URL: https://issues.apache.org/jira/browse/UIMA-1136 Project: UIMA Issue Type: Improvement Components: Async Scaleout Reporter: Tong Fin Assignee: Tong Fin Priority: Trivial Fix For: 2.3AS For the current version of DDE, to change the value of the Prefetch of the Top AE, the user needs to modify the value in the source XML. Until now, the default value is set to 1. We will modify the DDE as follows: 1. Allow user to modify the prefetch value with GUI (in the 1st page of DDE) 2. Set the default value to 0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1102) CAS Viewer submission
[ https://issues.apache.org/jira/browse/UIMA-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-1102: --- Attachment: DotCorpusReader.java The following steps describe how to build the CAS Viewer and how to build and use the CAS Viewer inside the CAS Editor RCP: 1. To build and test the Cas Viewer, follow the following steps (how I did): 1.a Install Eclipse 3.3.2 1.b Install EMF 2.3.2 1.c Install UIMA runtime plugin org.apache.uima.runtime_2.2.2.incubating.jar into Eclipse's plugins directory. 1.d Restart Eclipse with -clean option. 1.e Import to attached ZIP file from this JIRA into thw workspace as Existing Projects into Workspace. Double check that there is no errors. 1.f Use Run as... to test the plugins. 2. To use the CAS Viewer inside the CAS Editor RCP, follow the following steps: 2.a Un-comment the body of tjhe method findTypesystemmFileInNLPProject () in the class org.apache.uima.casviewer.viewer.internal.GenericCasViewer.java 2.b Add the attached class DotCorpusReader.java into the package org.apache.uima.casviewer.viewer.internal 2.c Export the CAS Viewer plugins as Deployable plugins 2.d Copy the two plugins org.apache.uima.casviewer.core_0.0.0.1.jar and org.apache.uima.casviewer_0.0.0.1.jar into the Cas Editor RCP's plugins directory. (Note that the CAS Editor RCP might need to include more plugins required by the CAS Viewer). CAS Viewer submission - Key: UIMA-1102 URL: https://issues.apache.org/jira/browse/UIMA-1102 Project: UIMA Issue Type: New Feature Components: Tools Reporter: Tong Fin Assignee: Marshall Schor Priority: Minor Attachments: CAS Viewer Functionality Comparison.doc, CAS Viewer User Guide-07-02-2008.doc, DotCorpusReader.java, uima-casviewer-07-01-2008.zip, uima-casviewer-07-01-2008.zip.md5 The CAS Viewer is a tool for exploring the contents of the CAS that contains types, feature structures, feature values, and indices created when analysis engines are run over some input text documents. It unlocks and visualizes the CAS content by providing the following information: - Annotations with associated types - Indices that reside in the index repository -Annotated text document UIMA developers can take benefits of the visualization and navigation capabilities inside the CAS content to debug and accelerate the development of their UIMA components. The CAS Viewer runs as an Eclipse's plug-in and provides a GUI for visualizing serialized CAS saved as XMI (XML Metadata Interchange) format. It also provides APIs for other tools to customize and extend its functionality and its user interface. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1102) CAS Viewer submission
[ https://issues.apache.org/jira/browse/UIMA-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-1102: --- Attachment: (was: CAS Viewer User Guide-07-01-2008.doc) CAS Viewer submission - Key: UIMA-1102 URL: https://issues.apache.org/jira/browse/UIMA-1102 Project: UIMA Issue Type: New Feature Components: Tools Reporter: Tong Fin Assignee: Marshall Schor Priority: Minor Attachments: CAS Viewer Functionality Comparison.doc, uima-casviewer-07-01-2008.zip, uima-casviewer-07-01-2008.zip.md5 The CAS Viewer is a tool for exploring the contents of the CAS that contains types, feature structures, feature values, and indices created when analysis engines are run over some input text documents. It unlocks and visualizes the CAS content by providing the following information: - Annotations with associated types - Indices that reside in the index repository -Annotated text document UIMA developers can take benefits of the visualization and navigation capabilities inside the CAS content to debug and accelerate the development of their UIMA components. The CAS Viewer runs as an Eclipse's plug-in and provides a GUI for visualizing serialized CAS saved as XMI (XML Metadata Interchange) format. It also provides APIs for other tools to customize and extend its functionality and its user interface. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1102) CAS Viewer submission
CAS Viewer submission - Key: UIMA-1102 URL: https://issues.apache.org/jira/browse/UIMA-1102 Project: UIMA Issue Type: New Feature Components: Tools Reporter: Tong Fin Priority: Minor The CAS Viewer is a tool for exploring the contents of the CAS that contains types, feature structures, feature values, and indices created when analysis engines are run over some input text documents. It unlocks and visualizes the CAS content by providing the following information: - Annotations with associated types - Indices that reside in the index repository -Annotated text document UIMA developers can take benefits of the visualization and navigation capabilities inside the CAS content to debug and accelerate the development of their UIMA components. The CAS Viewer runs as an Eclipse's plug-in and provides a GUI for visualizing serialized CAS saved as XMI (XML Metadata Interchange) format. It also provides APIs for other tools to customize and extend its functionality and its user interface. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1102) CAS Viewer submission
[ https://issues.apache.org/jira/browse/UIMA-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-1102: --- Attachment: CAS Viewer User Guide-07-01-2008.doc uima-casviewer-07-01-2008.zip.md5 uima-casviewer-07-01-2008.zip CAS Viewer submission - Key: UIMA-1102 URL: https://issues.apache.org/jira/browse/UIMA-1102 Project: UIMA Issue Type: New Feature Components: Tools Reporter: Tong Fin Priority: Minor Attachments: CAS Viewer User Guide-07-01-2008.doc, uima-casviewer-07-01-2008.zip, uima-casviewer-07-01-2008.zip.md5 The CAS Viewer is a tool for exploring the contents of the CAS that contains types, feature structures, feature values, and indices created when analysis engines are run over some input text documents. It unlocks and visualizes the CAS content by providing the following information: - Annotations with associated types - Indices that reside in the index repository -Annotated text document UIMA developers can take benefits of the visualization and navigation capabilities inside the CAS content to debug and accelerate the development of their UIMA components. The CAS Viewer runs as an Eclipse's plug-in and provides a GUI for visualizing serialized CAS saved as XMI (XML Metadata Interchange) format. It also provides APIs for other tools to customize and extend its functionality and its user interface. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1102) CAS Viewer submission
[ https://issues.apache.org/jira/browse/UIMA-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-1102: --- Attachment: CAS Viewer Functionality Comparison.doc CAS Viewer submission - Key: UIMA-1102 URL: https://issues.apache.org/jira/browse/UIMA-1102 Project: UIMA Issue Type: New Feature Components: Tools Reporter: Tong Fin Priority: Minor Attachments: CAS Viewer Functionality Comparison.doc, CAS Viewer User Guide-07-01-2008.doc, uima-casviewer-07-01-2008.zip, uima-casviewer-07-01-2008.zip.md5 The CAS Viewer is a tool for exploring the contents of the CAS that contains types, feature structures, feature values, and indices created when analysis engines are run over some input text documents. It unlocks and visualizes the CAS content by providing the following information: - Annotations with associated types - Indices that reside in the index repository -Annotated text document UIMA developers can take benefits of the visualization and navigation capabilities inside the CAS content to debug and accelerate the development of their UIMA components. The CAS Viewer runs as an Eclipse's plug-in and provides a GUI for visualizing serialized CAS saved as XMI (XML Metadata Interchange) format. It also provides APIs for other tools to customize and extend its functionality and its user interface. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1078) Pool size and heap size for CAS Multiplier should NOT be displayed (be disable) for Top Analysis Engine running as AS aggregate
Pool size and heap size for CAS Multiplier should NOT be displayed (be disable) for Top Analysis Engine running as AS aggregate --- Key: UIMA-1078 URL: https://issues.apache.org/jira/browse/UIMA-1078 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2 Reporter: Tong Fin Assignee: Tong Fin Priority: Trivial In DDE 2nd page, if the aggregate CAS Mutiplier runs as an AS aggregate, the pool size and heap size for CAS Multiplier fields should NOT be displayed when Top Analysis Engine is selected. It means that the pool size and heap size for CAS Multiplier fields are only displayed when the delegate CAS Multiplier is selected. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1076) In DDE, CAS pool size setting is Not Applicable when Top AE is a primitive AE
In DDE, CAS pool size setting is Not Applicable when Top AE is a primitive AE - Key: UIMA-1076 URL: https://issues.apache.org/jira/browse/UIMA-1076 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2 Reporter: Tong Fin Assignee: Tong Fin Priority: Trivial In DDE, CAS pool size setting is Not Applicable (should be disable) when Top AE is a primitive AE -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1034) [DDE] Dirty flag is not set when environment parameters are edited
[DDE] Dirty flag is not set when environment parameters are edited -- Key: UIMA-1034 URL: https://issues.apache.org/jira/browse/UIMA-1034 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Tong Fin Priority: Trivial User has reported that, when environment parameters are edited, the save command is not enable. Bug: When environment parameters are edited, the dirty flag is not set (that is why save is not enable). Work-around: Until the fix is released, user can make the save enable by editing fields other than the environment parameters. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1027) Classes from uima-document-annotator.jar are not in Eclipse plugin
[ https://issues.apache.org/jira/browse/UIMA-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12596782#action_12596782 ] Tong Fin commented on UIMA-1027: Hi Mikhail, Please see comments from Marshall about some issues that we may have with DocumentAnnotation: http://www.mail-archive.com/uima-dev@incubator.apache.org/msg07146.html The following is my summary of the issues surrounding the DocumentAnnotation class: 1. If we INCLUDE the uima-document-annotation.jar in the runtime plug-in as your suggestion (which is valid), we have the following issue: If developers need to substitute this class with their own version in their own plug-in (Bundle in OSGi term), it is possible (from my experience, most likely) that the custom DocumentAnnotation in the developers plugin cannot be reached because the DocumentAnnotation class can come from two different plugins (UIMA runtime plug-in and user's plug-in) and OSGi uses the package org.apache.uima.jcas.tcas in UIMA runtime plug-in for wiring. 2. if we DON'T include the uima-document-annotation.jar in the runtime plug-in, the custom DocumentAnnotation in the developers plugin will be used (there is a complicated situation that this approach still has the problem as (1) above). From the above summary, it looks like the above (2) approach is the reasonable choice for now. One small thing that we may do for the next release is to create a fragment containing the uima-document-annotation.jar so that developers can add this fragment to UIMA runtime plugin to cover your use-case. BTW, if you have any specific problem, please bring up and we can discuss in the mailing list. - Tong Classes from uima-document-annotator.jar are not in Eclipse plugin -- Key: UIMA-1027 URL: https://issues.apache.org/jira/browse/UIMA-1027 Project: UIMA Issue Type: Bug Components: Eclipse plugins Affects Versions: 2.2.2AS, 2.2.2S Reporter: Mikhail Sogrin Eclipse plugin org.apache.uima.runtime previously contained jars inside a plugin. Version 2.2.2 has jars unzipped. But contents of uima-document-annotator.jar were not added to 2.2.2 plugin. I've previously submitted a report (UIMA-400) about the same jar which was not added to 2.1.0 plugin by mistake, and it was fixed in 2.2.0, and now broken again in 2.2.2. In addition, there's a circular dependency for the package org.apache.uima.jcas.tcas, i.e. the same package is exported and imported in manifest. Probably, it's caused by the same missing classes from that jar. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1011) [DDE] When switching backward and forward between C++ and Java top-AE, Custom Settings are not properly handled
[DDE] When switching backward and forward between C++ and Java top-AE, Custom Settings are not properly handled --- Key: UIMA-1011 URL: https://issues.apache.org/jira/browse/UIMA-1011 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Tong Fin Priority: Minor Fix For: 2.2.2AS Replicate the bug: - Open a DD for C++. The Custom check-box button is enable. Check this Custom button - In the Overview page, replace the top AE with a Java AE - Bug: The Custom check-box button is still enable and selected. All the custom settings for C++ are still there which are supposed to be disable and removed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1011) [DDE] When switching backward and forward between C++ and Java top-AE, Custom Settings are not properly handled
[ https://issues.apache.org/jira/browse/UIMA-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-1011: --- Attachment: UIMA-1011-DDE-04-23-2008-Patch-2-of-2.txt UIMA-1011-DDE-04-23-2008-Patch-1-of-2.txt [DDE] When switching backward and forward between C++ and Java top-AE, Custom Settings are not properly handled --- Key: UIMA-1011 URL: https://issues.apache.org/jira/browse/UIMA-1011 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Tong Fin Priority: Minor Fix For: 2.2.2AS Attachments: UIMA-1011-DDE-04-23-2008-Patch-1-of-2.txt, UIMA-1011-DDE-04-23-2008-Patch-2-of-2.txt Replicate the bug: - Open a DD for C++. The Custom check-box button is enable. Check this Custom button - In the Overview page, replace the top AE with a Java AE - Bug: The Custom check-box button is still enable and selected. All the custom settings for C++ are still there which are supposed to be disable and removed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (UIMA-1011) [DDE] When switching backward and forward between C++ and Java top-AE, Custom Settings are not properly handled
[ https://issues.apache.org/jira/browse/UIMA-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin reassigned UIMA-1011: -- Assignee: Marshall Schor (was: Tong Fin) Need help from Marshall to verify and apply the patches. [DDE] When switching backward and forward between C++ and Java top-AE, Custom Settings are not properly handled --- Key: UIMA-1011 URL: https://issues.apache.org/jira/browse/UIMA-1011 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Marshall Schor Priority: Minor Fix For: 2.2.2AS Attachments: UIMA-1011-DDE-04-23-2008-Patch-1-of-2.txt, UIMA-1011-DDE-04-23-2008-Patch-2-of-2.txt Replicate the bug: - Open a DD for C++. The Custom check-box button is enable. Check this Custom button - In the Overview page, replace the top AE with a Java AE - Bug: The Custom check-box button is still enable and selected. All the custom settings for C++ are still there which are supposed to be disable and removed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1011) [DDE] When switching backward and forward between C++ and Java top-AE, Custom Settings are not properly handled
[ https://issues.apache.org/jira/browse/UIMA-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-1011: --- Attachment: (was: UIMA-1011-DDE-04-23-2008-Patch-2-of-2.txt) [DDE] When switching backward and forward between C++ and Java top-AE, Custom Settings are not properly handled --- Key: UIMA-1011 URL: https://issues.apache.org/jira/browse/UIMA-1011 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Marshall Schor Priority: Minor Fix For: 2.2.2AS Attachments: UIMA-1011-DDE-04-23-2008-Patch-1-of-2.txt Replicate the bug: - Open a DD for C++. The Custom check-box button is enable. Check this Custom button - In the Overview page, replace the top AE with a Java AE - Bug: The Custom check-box button is still enable and selected. All the custom settings for C++ are still there which are supposed to be disable and removed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1011) [DDE] When switching backward and forward between C++ and Java top-AE, Custom Settings are not properly handled
[ https://issues.apache.org/jira/browse/UIMA-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-1011: --- Attachment: UIMA-1011-DDE-04-23-2008-Patch-2-of-2-VERSION2.txt Re-create the patch to include the border problem in Linux for the Env Variable table [DDE] When switching backward and forward between C++ and Java top-AE, Custom Settings are not properly handled --- Key: UIMA-1011 URL: https://issues.apache.org/jira/browse/UIMA-1011 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Marshall Schor Priority: Minor Fix For: 2.2.2AS Attachments: UIMA-1011-DDE-04-23-2008-Patch-1-of-2.txt, UIMA-1011-DDE-04-23-2008-Patch-2-of-2-VERSION2.txt Replicate the bug: - Open a DD for C++. The Custom check-box button is enable. Check this Custom button - In the Overview page, replace the top AE with a Java AE - Bug: The Custom check-box button is still enable and selected. All the custom settings for C++ are still there which are supposed to be disable and removed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (UIMA-1001) [DDE] In Linux, the border of some controls used in Form are is visible
[ https://issues.apache.org/jira/browse/UIMA-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin reassigned UIMA-1001: -- Assignee: Marshall Schor (was: Tong Fin) Will need help from Marshall to apply and verify the patch. [DDE] In Linux, the border of some controls used in Form are is visible --- Key: UIMA-1001 URL: https://issues.apache.org/jira/browse/UIMA-1001 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2AS Environment: Linux Reporter: Tong Fin Assignee: Marshall Schor Priority: Minor Fix For: 2.2.2AS Attachments: UIMA-1001 DDE-Patch-04-18-2008.txt In Linux, the border of some controls used in Form is not visible. Need to add SWT.BORDER style to the control (which is not necessary in Windows) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1001) [DDE] In Linux, the border of some controls used in Form are is visible
[ https://issues.apache.org/jira/browse/UIMA-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-1001: --- Attachment: UIMA-1001 DDE-Patch-04-18-2008.txt [DDE] In Linux, the border of some controls used in Form are is visible --- Key: UIMA-1001 URL: https://issues.apache.org/jira/browse/UIMA-1001 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2AS Environment: Linux Reporter: Tong Fin Assignee: Tong Fin Priority: Minor Fix For: 2.2.2AS Attachments: UIMA-1001 DDE-Patch-04-18-2008.txt In Linux, the border of some controls used in Form is not visible. Need to add SWT.BORDER style to the control (which is not necessary in Windows) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1001) [DDE] In Linux, the border of some controls used in Form are is visible
[DDE] In Linux, the border of some controls used in Form are is visible --- Key: UIMA-1001 URL: https://issues.apache.org/jira/browse/UIMA-1001 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2AS Environment: Linux Reporter: Tong Fin Assignee: Tong Fin Priority: Minor Fix For: 2.2.2AS In Linux, the border of some controls used in Form is not visible. Need to add SWT.BORDER style to the control (which is not necessary in Windows) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Work stopped: (UIMA-986) [DDE] Improve DDE to support the settings for AE implemented in C++
[ https://issues.apache.org/jira/browse/UIMA-986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on UIMA-986 stopped by Tong Fin. [DDE] Improve DDE to support the settings for AE implemented in C++ Key: UIMA-986 URL: https://issues.apache.org/jira/browse/UIMA-986 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Tong Fin Priority: Minor Fix For: 2.2.2AS Improve DDE to support the settings for C++ by recognizing the custom ... tag and environmentVariables... The following is an example settings that can be used when the top-level AE is implemented in C++: custom name=run_top_level_CPP_service_as_separate_process/ environmentVariables environmentVariable name=PathC:\Program files/apache-uima/uimacpp/bin/environmentVariable environmentVariable name=LD_LIBRARY_PATHC:\Program Files/apache-uima/uimacpp/bin/environmentVariable environmentVariable name=UIMACPP_DATAPATHC:/mydata/environmentVariable /environmentVariables -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-986) [DDE] Improve DDE to support the settings for AE implemented in C++
[ https://issues.apache.org/jira/browse/UIMA-986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-986: -- Attachment: UIMA-986-Patch-02.txt UIMA-986-Patch-01.txt - UIMA-986-Patch-01.txt is to support UI in DDE - UIMA-986-Patch-02.txt is to support parsing of tag in XML [DDE] Improve DDE to support the settings for AE implemented in C++ Key: UIMA-986 URL: https://issues.apache.org/jira/browse/UIMA-986 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Tong Fin Priority: Minor Fix For: 2.2.2AS Attachments: UIMA-986-Patch-01.txt, UIMA-986-Patch-02.txt Improve DDE to support the settings for C++ by recognizing the custom ... tag and environmentVariables... The following is an example settings that can be used when the top-level AE is implemented in C++: custom name=run_top_level_CPP_service_as_separate_process/ environmentVariables environmentVariable name=PathC:\Program files/apache-uima/uimacpp/bin/environmentVariable environmentVariable name=LD_LIBRARY_PATHC:\Program Files/apache-uima/uimacpp/bin/environmentVariable environmentVariable name=UIMACPP_DATAPATHC:/mydata/environmentVariable /environmentVariables -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (UIMA-986) [DDE] Improve DDE to support the settings for AE implemented in C++
[ https://issues.apache.org/jira/browse/UIMA-986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin resolved UIMA-986. --- Resolution: Fixed Assignee: Marshall Schor (was: Tong Fin) The patches are submitted. Waiting for Marshall to verify the patches. [DDE] Improve DDE to support the settings for AE implemented in C++ Key: UIMA-986 URL: https://issues.apache.org/jira/browse/UIMA-986 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Marshall Schor Priority: Minor Fix For: 2.2.2AS Attachments: UIMA-986-Patch-01.txt, UIMA-986-Patch-02.txt Improve DDE to support the settings for C++ by recognizing the custom ... tag and environmentVariables... The following is an example settings that can be used when the top-level AE is implemented in C++: custom name=run_top_level_CPP_service_as_separate_process/ environmentVariables environmentVariable name=PathC:\Program files/apache-uima/uimacpp/bin/environmentVariable environmentVariable name=LD_LIBRARY_PATHC:\Program Files/apache-uima/uimacpp/bin/environmentVariable environmentVariable name=UIMACPP_DATAPATHC:/mydata/environmentVariable /environmentVariables -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-993) Improving the readability of XML Deployment Descriptor source generated by AEDeploymentDescriptor.toXML()
Improving the readability of XML Deployment Descriptor source generated by AEDeploymentDescriptor.toXML() - Key: UIMA-993 URL: https://issues.apache.org/jira/browse/UIMA-993 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Tong Fin Priority: Minor Fix For: 2.2.2AS Currently, the XML source generated by DDE contains some XML elements that can be omitted when their attributes have the default values. For example, the following element can be omitted from the XML source for Delegate AE: asyncAggregateErrorConfiguration getMetadataErrors maxRetries=0 timeout=0 errorAction=terminate/ processCasErrors maxRetries=0 timeout=0 continueOnRetryFailure=false thresholdCount=0 thresholdWindow=0 thresholdAction=terminate/ collectionProcessCompleteErrors timeout=0 additionalErrorAction=terminate/ /asyncAggregateErrorConfiguration By supporting not to generate XML elements having default values, it will improve the readability of the XML source of the Deployment Descriptor. As the first step, we will start the elimination of the XML elements related to error handling. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-993) [DDE] Improving the readability of XML Deployment Descriptor source generated by AEDeploymentDescriptor.toXML()
[ https://issues.apache.org/jira/browse/UIMA-993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-993: -- Summary: [DDE] Improving the readability of XML Deployment Descriptor source generated by AEDeploymentDescriptor.toXML() (was: Improving the readability of XML Deployment Descriptor source generated by AEDeploymentDescriptor.toXML()) Just would like to include [DDE] in the subject [DDE] Improving the readability of XML Deployment Descriptor source generated by AEDeploymentDescriptor.toXML() --- Key: UIMA-993 URL: https://issues.apache.org/jira/browse/UIMA-993 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Tong Fin Priority: Minor Fix For: 2.2.2AS Currently, the XML source generated by DDE contains some XML elements that can be omitted when their attributes have the default values. For example, the following element can be omitted from the XML source for Delegate AE: asyncAggregateErrorConfiguration getMetadataErrors maxRetries=0 timeout=0 errorAction=terminate/ processCasErrors maxRetries=0 timeout=0 continueOnRetryFailure=false thresholdCount=0 thresholdWindow=0 thresholdAction=terminate/ collectionProcessCompleteErrors timeout=0 additionalErrorAction=terminate/ /asyncAggregateErrorConfiguration By supporting not to generate XML elements having default values, it will improve the readability of the XML source of the Deployment Descriptor. As the first step, we will start the elimination of the XML elements related to error handling. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-986) [DDE] Improve DDE to support the settings for AE implemented in C++
[ https://issues.apache.org/jira/browse/UIMA-986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-986: -- Attachment: (was: UIMA-986-Patch-01.txt) [DDE] Improve DDE to support the settings for AE implemented in C++ Key: UIMA-986 URL: https://issues.apache.org/jira/browse/UIMA-986 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Marshall Schor Priority: Minor Fix For: 2.2.2AS Attachments: UIMA-986-Patch-02.txt Improve DDE to support the settings for C++ by recognizing the custom ... tag and environmentVariables... The following is an example settings that can be used when the top-level AE is implemented in C++: custom name=run_top_level_CPP_service_as_separate_process/ environmentVariables environmentVariable name=PathC:\Program files/apache-uima/uimacpp/bin/environmentVariable environmentVariable name=LD_LIBRARY_PATHC:\Program Files/apache-uima/uimacpp/bin/environmentVariable environmentVariable name=UIMACPP_DATAPATHC:/mydata/environmentVariable /environmentVariables -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-986) [DDE] Improve DDE to support the settings for AE implemented in C++
[ https://issues.apache.org/jira/browse/UIMA-986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-986: -- Attachment: UIMA-986-Patch-01-Version 2.txt This file replaces the previous UIMA-986-Patch-01.txt that is already deleted. [DDE] Improve DDE to support the settings for AE implemented in C++ Key: UIMA-986 URL: https://issues.apache.org/jira/browse/UIMA-986 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Marshall Schor Priority: Minor Fix For: 2.2.2AS Attachments: UIMA-986-Patch-01-Version 2.txt, UIMA-986-Patch-02.txt Improve DDE to support the settings for C++ by recognizing the custom ... tag and environmentVariables... The following is an example settings that can be used when the top-level AE is implemented in C++: custom name=run_top_level_CPP_service_as_separate_process/ environmentVariables environmentVariable name=PathC:\Program files/apache-uima/uimacpp/bin/environmentVariable environmentVariable name=LD_LIBRARY_PATHC:\Program Files/apache-uima/uimacpp/bin/environmentVariable environmentVariable name=UIMACPP_DATAPATHC:/mydata/environmentVariable /environmentVariables -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Work started: (UIMA-986) [DDE] Improve DDE to support the settings for AE implemented in C++
[ https://issues.apache.org/jira/browse/UIMA-986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on UIMA-986 started by Tong Fin. [DDE] Improve DDE to support the settings for AE implemented in C++ Key: UIMA-986 URL: https://issues.apache.org/jira/browse/UIMA-986 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Tong Fin Priority: Minor Fix For: 2.2.2AS Improve DDE to support the settings for C++ by recognizing the custom ... tag and environmentVariables... The following is an example settings that can be used when the top-level AE is implemented in C++: custom name=run_top_level_CPP_service_as_separate_process/ environmentVariables environmentVariable name=PathC:\Program files/apache-uima/uimacpp/bin/environmentVariable environmentVariable name=LD_LIBRARY_PATHC:\Program Files/apache-uima/uimacpp/bin/environmentVariable environmentVariable name=UIMACPP_DATAPATHC:/mydata/environmentVariable /environmentVariables -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-986) [DDE] Improve DDE to support the settings for AE implemented in C++
[DDE] Improve DDE to support the settings for AE implemented in C++ Key: UIMA-986 URL: https://issues.apache.org/jira/browse/UIMA-986 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Tong Fin Priority: Minor Fix For: 2.2.2AS Improve DDE to support the settings for C++ by recognizing the custom ... tag and environmentVariables... The following is an example settings that can be used when the top-level AE is implemented in C++: custom name=run_top_level_CPP_service_as_separate_process/ environmentVariables environmentVariable name=PathC:\Program files/apache-uima/uimacpp/bin/environmentVariable environmentVariable name=LD_LIBRARY_PATHC:\Program Files/apache-uima/uimacpp/bin/environmentVariable environmentVariable name=UIMACPP_DATAPATHC:/mydata/environmentVariable /environmentVariables -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-976) [DDE] Collection Reader embedded in an aggregate is not handle as a CAS Multiplier
[DDE] Collection Reader embedded in an aggregate is not handle as a CAS Multiplier -- Key: UIMA-976 URL: https://issues.apache.org/jira/browse/UIMA-976 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Tong Fin Priority: Minor Fix For: 2.2.2AS When a Collection Reader is embedded in an aggregate, it should be handled as a CAS Multiplier in the Deployment Configurations page of the DDE, i.e. all its possible settings should be the SAME as the CAS Multiplier. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-976) [DDE] Collection Reader embedded in an aggregate is not handle as a CAS Multiplier
[ https://issues.apache.org/jira/browse/UIMA-976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-976: -- Attachment: UIMA-976-Path-02.txt UIMA-976-Path-01.txt There are two places to be fixed: 1. UI of DDE to handle a Collection Reader as a CAS Multiplier 2. In the UIMA runtime's fragment, the API to check if the component is a CAS Multiplier. [DDE] Collection Reader embedded in an aggregate is not handle as a CAS Multiplier -- Key: UIMA-976 URL: https://issues.apache.org/jira/browse/UIMA-976 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Tong Fin Priority: Minor Fix For: 2.2.2AS Attachments: UIMA-976-Path-01.txt, UIMA-976-Path-02.txt When a Collection Reader is embedded in an aggregate, it should be handled as a CAS Multiplier in the Deployment Configurations page of the DDE, i.e. all its possible settings should be the SAME as the CAS Multiplier. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (UIMA-976) [DDE] Collection Reader embedded in an aggregate is not handle as a CAS Multiplier
[ https://issues.apache.org/jira/browse/UIMA-976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin resolved UIMA-976. --- Resolution: Fixed Assignee: Marshall Schor (was: Tong Fin) Wait for Marshall to verify the patch. - Tong [DDE] Collection Reader embedded in an aggregate is not handle as a CAS Multiplier -- Key: UIMA-976 URL: https://issues.apache.org/jira/browse/UIMA-976 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Tong Fin Assignee: Marshall Schor Priority: Minor Fix For: 2.2.2AS Attachments: UIMA-976-Path-01.txt, UIMA-976-Path-02.txt When a Collection Reader is embedded in an aggregate, it should be handled as a CAS Multiplier in the Deployment Configurations page of the DDE, i.e. all its possible settings should be the SAME as the CAS Multiplier. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-939) PEAR packaging eclipse plugin not visible after installation
[ https://issues.apache.org/jira/browse/UIMA-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12582808#action_12582808 ] Tong Fin commented on UIMA-939: --- Hi Michael, I tested the PEAR plugin with: - Redhat 5 Enterprise Linux - Eclipse 3.3.2 It works for me ! Please make sure that you have added UIMA Nature to the project that you would like to PEAR. - Tong PEAR packaging eclipse plugin not visible after installation Key: UIMA-939 URL: https://issues.apache.org/jira/browse/UIMA-939 Project: UIMA Issue Type: Bug Components: Eclipse plugins Environment: Linux only Eclipse 3.3.2 Reporter: Michael Baessler Fix For: 2.2.2 After installing the plugin, it is not available. The log file does not contain any entries. The error occurs only on Linux in eclipse 3.3.2. When using eclipse 3.2.2 all works fine Is there anything I can check to see what's wrong? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-935) [UIMA eclipse plugins] Possible WRONG wiring of imported packages for UIMA Eclipse plugins
[UIMA eclipse plugins] Possible WRONG wiring of imported packages for UIMA Eclipse plugins -- Key: UIMA-935 URL: https://issues.apache.org/jira/browse/UIMA-935 Project: UIMA Issue Type: Bug Components: Eclipse plugins Affects Versions: 2.2.2 Environment: Linux Redhat 5 Enterprise Reporter: Tong Fin Priority: Minor Problem: -- The current UIMA Eclipse plugins (runtime, CDE, etc.) use Imported Packages for declaring dependencies instead of Required Plug-ins. This declaration is automatically generated by Maven (I think ?) and gives more fine grained controls on what to depend on. But, there are some side-effects from this approach which may cause the problems. The imported packages may wired to the correct packages from the wrong plugins. If there are, for example, two bundles (plug-ins) A and B export the same package name and B is resolved before A, OSGi will pick B bundle for wiring. This wrong wiring issue is happen when I tested CDE and DDE with Eclipse 3.2 in Linux Redhat 5 (Note that the problem can be happen with any Eclipse and platform). The following describes this particular case. CDE uses an Xml editor for source editing and this Xml editor requires a class called: org.eclipse.jface.text.source.SourceViewerConfiguration from org.eclipse.jface.text plugin Inside Eclipse installation, there is another plugin called org.eclipse.text that also exports this org.eclipse.jface.text.source which doesn't have the class SourceViewerConfiguration. When Eclipse runs, the org.eclipse.text plugin is resolved before the org.eclipse.jface.text plugin which causes CDE to be wired to the org.eclipse.text plugin. The expectation is to wire CDE to org.eclipse.jface.text.source. Possible Resolution: One possible resolution is posted by Marshall in response to the thread in uima-dev: [UIMA eclipse plugins] Possible WRONG wiring between UIMA Eclipse plugins The following is the quote: On Fri, Mar 14, 2008 at 4:58 PM, Marshall Schor [EMAIL PROTECTED] wrote: OSGi does provide a mechanism to have the import-package include specifying which bundle it should come from. See section 3.6.8 Provider Selection in the r4.core.pdf doc for OSGi for details. The POMs we use don't generate this though. Do you see that allowing multiple bundles to export the same package name, and then having our configuration be more explicit about which bundle to wire to, is (or may be) a design requirement? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-928) [DDE] For Linux platform, Deployment Descriptor Editor's table border is not visible
[DDE] For Linux platform, Deployment Descriptor Editor's table border is not visible Key: UIMA-928 URL: https://issues.apache.org/jira/browse/UIMA-928 Project: UIMA Issue Type: Improvement Components: Eclipse plugins Affects Versions: 2.2.2S Environment: Linux Redhat Enterprise Edition Reporter: Tong Fin Priority: Trivial Fix For: 2.2.2S For Linux platform, the table border of the Deployment Descriptor Editor's is not visible. For Windows, it is displayed correctly -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (UIMA-928) [DDE] For Linux platform, Deployment Descriptor Editor's table border is not visible
[ https://issues.apache.org/jira/browse/UIMA-928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin resolved UIMA-928. --- Resolution: Fixed In Linux platform, the table border is made visible by the following fixes: - If C is the parent composite that contains the table control, set the margin of width and height of the layout of C to have a few dots value (e.g., 2) instead of 0. - The following is an example: Composite c = toolkit.createComposite(section); GridLayout layout = new GridLayout(1, false); layout.marginHeight = 2; layout.marginWidth = 2; c.setLayout(layout); [DDE] For Linux platform, Deployment Descriptor Editor's table border is not visible Key: UIMA-928 URL: https://issues.apache.org/jira/browse/UIMA-928 Project: UIMA Issue Type: Improvement Components: Eclipse plugins Affects Versions: 2.2.2S Environment: Linux Redhat Enterprise Edition Reporter: Tong Fin Priority: Trivial Fix For: 2.2.2S For Linux platform, the table border of the Deployment Descriptor Editor's is not visible. For Windows, it is displayed correctly -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-928) [DDE] For Linux platform, Deployment Descriptor Editor's table border is not visible
[ https://issues.apache.org/jira/browse/UIMA-928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-928: -- Attachment: UIMA-928-DDE-Patch.txt In Linux platform, the table border is made visible by the following fixes: - If C is the parent composite that contains the table control, set the margin of width and height of the layout of C to have a few dots value (e.g., 2) instead of 0. - The following is an example: Composite c = toolkit.createComposite(section); GridLayout layout = new GridLayout(1, false); layout.marginHeight = 2; layout.marginWidth = 2; c.setLayout(layout); [DDE] For Linux platform, Deployment Descriptor Editor's table border is not visible Key: UIMA-928 URL: https://issues.apache.org/jira/browse/UIMA-928 Project: UIMA Issue Type: Improvement Components: Eclipse plugins Affects Versions: 2.2.2S Environment: Linux Redhat Enterprise Edition Reporter: Tong Fin Priority: Trivial Fix For: 2.2.2S Attachments: UIMA-928-DDE-Patch.txt For Linux platform, the table border of the Deployment Descriptor Editor's is not visible. For Windows, it is displayed correctly -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-933) [CDE] In CDE GUI, the border of some tables and combobox is not visible
[CDE] In CDE GUI, the border of some tables and combobox is not visible Key: UIMA-933 URL: https://issues.apache.org/jira/browse/UIMA-933 Project: UIMA Issue Type: Improvement Components: Eclipse plugins Affects Versions: 2.2.2 Environment: Windows and Linux Reporter: Tong Fin Priority: Trivial Fix For: 2.2.2 The border of CCombo and TableTree's widgets is not visible in the CDE GUI (same problem for Windows and Linux platforms). The reason is that these widgets are not directly supported by FormToolkit. To make the border visible, one way is to use the following setting: widget.setData(FormToolkit.KEY_DRAW_BORDER, FormToolkit.TREE_BORDER); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-933) [CDE] In CDE GUI, the border of some tables and combobox is not visible
[ https://issues.apache.org/jira/browse/UIMA-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-933: -- Attachment: UIMA-933-CDE-Patch.txt The issue is fixed by adding the following settings to the CCombo and TableTree widgets used by CDE, for example: // Make the CCombo's border visible since CCombo is NOT a widget // supported by FormToolkit. flowControllerChoice = newCComboWithTip(sectionClient. ...); flowControllerChoice.setData(FormToolkit.KEY_DRAW_BORDER, FormToolkit.TREE_BORDER); // Make the TableTree's border visible since TableTree is NOT a widget // supported by FormToolkit. tt = newTableTree(sectionClient, ...); tt.setData(FormToolkit.KEY_DRAW_BORDER, FormToolkit.TREE_BORDER); [CDE] In CDE GUI, the border of some tables and combobox is not visible Key: UIMA-933 URL: https://issues.apache.org/jira/browse/UIMA-933 Project: UIMA Issue Type: Improvement Components: Eclipse plugins Affects Versions: 2.2.2 Environment: Windows and Linux Reporter: Tong Fin Priority: Trivial Fix For: 2.2.2 Attachments: UIMA-933-CDE-Patch.txt The border of CCombo and TableTree's widgets is not visible in the CDE GUI (same problem for Windows and Linux platforms). The reason is that these widgets are not directly supported by FormToolkit. To make the border visible, one way is to use the following setting: widget.setData(FormToolkit.KEY_DRAW_BORDER, FormToolkit.TREE_BORDER); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (UIMA-933) [CDE] In CDE GUI, the border of some tables and combobox is not visible
[ https://issues.apache.org/jira/browse/UIMA-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin resolved UIMA-933. --- Resolution: Fixed Hi Marshall, Please verify the patch. - Tong [CDE] In CDE GUI, the border of some tables and combobox is not visible Key: UIMA-933 URL: https://issues.apache.org/jira/browse/UIMA-933 Project: UIMA Issue Type: Improvement Components: Eclipse plugins Affects Versions: 2.2.2 Environment: Windows and Linux Reporter: Tong Fin Priority: Trivial Fix For: 2.2.2 Attachments: UIMA-933-CDE-Patch.txt The border of CCombo and TableTree's widgets is not visible in the CDE GUI (same problem for Windows and Linux platforms). The reason is that these widgets are not directly supported by FormToolkit. To make the border visible, one way is to use the following setting: widget.setData(FormToolkit.KEY_DRAW_BORDER, FormToolkit.TREE_BORDER); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-801) Support specification of initialFsHeapSize for Cas Multiplier delegate
[ https://issues.apache.org/jira/browse/UIMA-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-801: -- Attachment: UIMA-801-B-patch-02-26-2008.txt UIMA-801-A-patch-02-26-2008.txt - Add the parsing capability for the attribute initialFsHeapSize in the casMultiplier poolSize=/ element when processing AEDeploymentMetaData and RemoteAEDeploymentMetaData objects. - Add UI support for editing initialFsHeapSize in the DD editor Support specification of initialFsHeapSize for Cas Multiplier delegate Key: UIMA-801 URL: https://issues.apache.org/jira/browse/UIMA-801 Project: UIMA Issue Type: Improvement Components: Async Scaleout Reporter: Tong Fin Priority: Minor Attachments: UIMA-801-A-patch-02-26-2008.txt, UIMA-801-B-patch-02-26-2008.txt The current Deployment Descriptor Editor for UIMA-AS only supports the specification of initialFsHeapSize at the top-level service. This improvement will extend the support to the Cas Multiplier delegate. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-816) maven build - Eclipse plugin build improvements
[ https://issues.apache.org/jira/browse/UIMA-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12571525#action_12571525 ] Tong Fin commented on UIMA-816: --- Hi Marshall, (Sorry, might be the wrong JIRA to add comment) My understanding is that the manifest.mf of each plug-in is generated by maven. The following is some observations after I try to create a new Eclipse workspace to work with Apache UIMA. - Each line of the manifest.mf file has a max 70 chars - Each package in the Export -Package section contains a uses directive and some lines are very long (more than 500 chars) which cause an error (the line is too long) in Manifest editor. Is it the expected behavior ? If I need to edit the manifest.mf file, how to do that ? Edit pom.xml or edit manifest.mf as usual ? The the line is too long error may prevent user to edit manidest.mf. -- Tong maven build - Eclipse plugin build improvements --- Key: UIMA-816 URL: https://issues.apache.org/jira/browse/UIMA-816 Project: UIMA Issue Type: Improvement Components: Build, Packaging and Test Reporter: Marshall Schor Assignee: Marshall Schor Fix For: 2.2.2 The current Eclipse plugins have complex maven poms - simplify by factoring out common things to a common super pom for the eclipse plugins, which will, in turn, inherit from the uimaj super pom. Put this new pom in the uimaj project - no need for another project just for this. Add configuration info so the eclipse:eclipse plugin does the right class path setup even when it is run from the top level. This will allow cd to the uimaj project, and running eclipse:eclipse there, and having it work, as well as working in individual project directories. For POMs which inherit from our project poms, replace the groupId with a comment saying it is inherited from the super pom, and replace the version with a comment saying it's inherited from the super pom. Make the eclipse plugin super pom have the right form of the version (the one with the . instead of the - in front of the incubator token). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-801) Support specification of initialFsHeapSize for Cas Multiplier delegate
Support specification of initialFsHeapSize for Cas Multiplier delegate Key: UIMA-801 URL: https://issues.apache.org/jira/browse/UIMA-801 Project: UIMA Issue Type: Improvement Components: Async Scaleout Reporter: Tong Fin Priority: Minor The current Deployment Descriptor Editor for UIMA-AS only supports the specification of initialFsHeapSize at the top-level service. This improvement will extend the support to the Cas Multiplier delegate. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-755) Expose per CAS statistics to the application from uima-as client
[ https://issues.apache.org/jira/browse/UIMA-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12567886#action_12567886 ] Tong Fin commented on UIMA-755: --- It would be nice to have a constant (e.g., UIMA_AS_xxx) defined by some class instead of exposing and quoting like UimaEE string. Expose per CAS statistics to the application from uima-as client Key: UIMA-755 URL: https://issues.apache.org/jira/browse/UIMA-755 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.1 Reporter: Jerry Cwiklik Attachments: uimaj-as-activemq-test-resources-UIMA-755-patch.txt, uimaj-as-activemq-test-src-UIMA-755-patch.txt, uimaj-as-activemq-UIMA-755-patch.txt, uimaj-as-core-UIMA-755-patch.txt, uimaj-as-jms-UIMA-755-patch.txt Modify the uima-as client to pass per CAS statistics via the entityProcessComplete callback. Use ProcessTrace object as a container for statistics. Statistics to be passed to the application include: time spent in process, time spent serializing CAS, time spent de-serializing CAS, service idle time, service host ip, CAS latency (total time spent waiting for reply) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-744) Improved the XML parsing of the Deployment Descriptor
Improved the XML parsing of the Deployment Descriptor - Key: UIMA-744 URL: https://issues.apache.org/jira/browse/UIMA-744 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.1 Reporter: Tong Fin Priority: Minor - Improved the XML parsing of the Deployment Descriptor: - added support for parsing initialFSHeapSize attribute of CAS pool size - checked the values of GetMetadataError and ProcessCasErrors for consistency - Fixed the bug when parsing the boolean value of ContinueOnRetryFailure - Removed irrelevant comments from the source files - Delete unused file org.apache.uima.application.metadata.ConfigParamSettingsSets_1.java -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-745) Improved the UI when editing GetMetadataError and ProcessCasError, added support for edting initialFsHeapSize
Improved the UI when editing GetMetadataError and ProcessCasError, added support for edting initialFsHeapSize --- Key: UIMA-745 URL: https://issues.apache.org/jira/browse/UIMA-745 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.1 Reporter: Tong Fin Priority: Minor - Improved the UI when displaying and editing the following elements of Deployment Descriptor: - GetMetadataError - ProcessCasError - Added the capability to edit the initial size of CAS FS heap in Overview page - Moved messages.properties file to resources folder to conform to Maven convention - Modified the manifest.mf file to contain the right classpath -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-745) Improved the UI when editing GetMetadataError and ProcessCasError, added support for edting initialFsHeapSize
[ https://issues.apache.org/jira/browse/UIMA-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-745: -- Attachment: uimaj-ep-deployeditor-01-31-2008.patch.txt Hi Marshall, Please review the attached patch. - Tong Improved the UI when editing GetMetadataError and ProcessCasError, added support for edting initialFsHeapSize --- Key: UIMA-745 URL: https://issues.apache.org/jira/browse/UIMA-745 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.1 Reporter: Tong Fin Priority: Minor Attachments: uimaj-ep-deployeditor-01-31-2008.patch.txt - Improved the UI when displaying and editing the following elements of Deployment Descriptor: - GetMetadataError - ProcessCasError - Added the capability to edit the initial size of CAS FS heap in Overview page - Moved messages.properties file to resources folder to conform to Maven convention - Modified the manifest.mf file to contain the right classpath -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-744) Improved the XML parsing of the Deployment Descriptor
[ https://issues.apache.org/jira/browse/UIMA-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-744: -- Attachment: uimaj-ep-runtime-deployeditor-02-05-2008.patch.txt Hi Marshall, Please review the attached patch. - Tong Improved the XML parsing of the Deployment Descriptor - Key: UIMA-744 URL: https://issues.apache.org/jira/browse/UIMA-744 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.1 Reporter: Tong Fin Priority: Minor Attachments: uimaj-ep-runtime-deployeditor-02-05-2008.patch.txt - Improved the XML parsing of the Deployment Descriptor: - added support for parsing initialFSHeapSize attribute of CAS pool size - checked the values of GetMetadataError and ProcessCasErrors for consistency - Fixed the bug when parsing the boolean value of ContinueOnRetryFailure - Removed irrelevant comments from the source files - Delete unused file org.apache.uima.application.metadata.ConfigParamSettingsSets_1.java -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-745) Improved the UI when editing GetMetadataError and ProcessCasError, added support for edting initialFsHeapSize
[ https://issues.apache.org/jira/browse/UIMA-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-745: -- Attachment: messages-patch.txt When creating the previously submitted patch, the messages.properties is deleted from its original folder, but it is not moved to the resources folder. This patch is to add the messages.properties file to the resources (to conform to Maven's convention). Improved the UI when editing GetMetadataError and ProcessCasError, added support for edting initialFsHeapSize --- Key: UIMA-745 URL: https://issues.apache.org/jira/browse/UIMA-745 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.1 Reporter: Tong Fin Priority: Minor Attachments: messages-patch.txt, uimaj-ep-deployeditor-01-31-2008.patch.txt - Improved the UI when displaying and editing the following elements of Deployment Descriptor: - GetMetadataError - ProcessCasError - Added the capability to edit the initial size of CAS FS heap in Overview page - Moved messages.properties file to resources folder to conform to Maven convention - Modified the manifest.mf file to contain the right classpath -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-643) TypeSystemUtil.type2TypeDescription() throws NPE when the superType is null
[ https://issues.apache.org/jira/browse/UIMA-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-643: -- Fix Version/s: (was: 2.2.1) 2.3 Since it is not clear on how to handle this issue and TypeSystemUtil is just a Helper class, I modified the target to 2.3. Or someone may just close this issue so that it will not blocked the release of 2.2.1. TypeSystemUtil.type2TypeDescription() throws NPE when the superType is null --- Key: UIMA-643 URL: https://issues.apache.org/jira/browse/UIMA-643 Project: UIMA Issue Type: Bug Components: Core Java Framework Affects Versions: 2.2.1 Environment: Occurs in WIndows Reporter: Tong Fin Priority: Minor Fix For: 2.3 Attachments: TypeSystemUtil_patch-11-20-2007.txt If the aType type does NOT have superType, the method TypeSystemUtil.type2TypeDescription(Type aType, TypeSystem aTypeSystem) throwa a NULL pointer exception. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-643) TypeSystemUtil.type2TypeDescription() throws NPE when the superType is null
[ https://issues.apache.org/jira/browse/UIMA-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-643: -- Attachment: TypeSystemUtil_patch-11-20-2007.txt Suggest Thilo or Adam as the reviewer TypeSystemUtil.type2TypeDescription() throws NPE when the superType is null --- Key: UIMA-643 URL: https://issues.apache.org/jira/browse/UIMA-643 Project: UIMA Issue Type: Bug Components: Core Java Framework Affects Versions: 2.2.1 Environment: Occurs in WIndows Reporter: Tong Fin Priority: Minor Fix For: 2.2.1 Attachments: TypeSystemUtil_patch-11-20-2007.txt If the aType type does NOT have superType, the method TypeSystemUtil.type2TypeDescription(Type aType, TypeSystem aTypeSystem) throwa a NULL pointer exception. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-636) Improve CDE to allow other tools to re-use its functionality to edit a new UIMA Xml descriptor
[ https://issues.apache.org/jira/browse/UIMA-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-636: -- Attachment: cde_patch-11-20-2007.txt Re-attach the patch to include the documentation for the extension point and the new interface classes. Improve CDE to allow other tools to re-use its functionality to edit a new UIMA Xml descriptor -- Key: UIMA-636 URL: https://issues.apache.org/jira/browse/UIMA-636 Project: UIMA Issue Type: Improvement Components: Eclipse plugins Environment: Not target for 2.3 Reporter: Tong Fin Priority: Minor Attachments: cde_patch-11-20-2007.txt, cde_patch.txt Improve CDE to allow other tools to re-use its functionality to edit a new UIMA Xml Descriptor. With this improvement, other tools can edit a newly defined UIMA descriptor with the following characteristics: - End-user will see the currently existing single menu item of CDE to edit any UIMA Xml descriptor (including the newly defined descriptor) - Some features from CDE can be re-used by the new editor (XML source editing, dialogs, error handlings, etc.) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-636) Improve CDE to allow other tools to re-use its functionality to edit a new UIMA Xml descriptor
Improve CDE to allow other tools to re-use its functionality to edit a new UIMA Xml descriptor -- Key: UIMA-636 URL: https://issues.apache.org/jira/browse/UIMA-636 Project: UIMA Issue Type: Improvement Components: Eclipse plugins Environment: Not target for 2.3 Reporter: Tong Fin Priority: Minor Improve CDE to allow other tools to re-use its functionality to edit a new UIMA Xml Descriptor. With this improvement, other tools can edit a newly defined UIMA descriptor with the following characteristics: - End-user will see the currently existing single menu item of CDE to edit any UIMA Xml descriptor (including the newly defined descriptor) - Some features from CDE can be re-used by the new editor (XML source editing, dialogs, error handlings, etc.) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-636) Improve CDE to allow other tools to re-use its functionality to edit a new UIMA Xml descriptor
[ https://issues.apache.org/jira/browse/UIMA-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tong Fin updated UIMA-636: -- Attachment: cde_patch.txt Patch for the proposed CDE improvements Improve CDE to allow other tools to re-use its functionality to edit a new UIMA Xml descriptor -- Key: UIMA-636 URL: https://issues.apache.org/jira/browse/UIMA-636 Project: UIMA Issue Type: Improvement Components: Eclipse plugins Environment: Not target for 2.3 Reporter: Tong Fin Priority: Minor Attachments: cde_patch.txt Improve CDE to allow other tools to re-use its functionality to edit a new UIMA Xml Descriptor. With this improvement, other tools can edit a newly defined UIMA descriptor with the following characteristics: - End-user will see the currently existing single menu item of CDE to edit any UIMA Xml descriptor (including the newly defined descriptor) - Some features from CDE can be re-used by the new editor (XML source editing, dialogs, error handlings, etc.) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-50) Add version number to descriptors
[ http://issues.apache.org/jira/browse/UIMA-50?page=comments#action_12452536 ] Tong Fin commented on UIMA-50: -- I believe that having both versions (Framework and DTD/Schema) is useful for the following reason: 1) Tools will use Framework version to identify if the descriptors are appropriate for the Framework being used/targetting. If the tools don't have this info, we need a mapping from DTD/Schema version to Framework. 2) DTD/Schema version will be used when parsing/creating/validating the descriptor Add version number to descriptors - Key: UIMA-50 URL: http://issues.apache.org/jira/browse/UIMA-50 Project: UIMA Issue Type: Improvement Components: Core Java Framework Reporter: Adam Lally Priority: Minor It has been suggested that our component descriptor XML files should include a version number, so that it would be possible to give more meaningful error messages in the case of a version mismatch. I'm not sure whether this should just be the framework version number, or a different descriptor model version number that might change less frequently. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
