from:"Tong Fin"

Re: I noticed that IntelliJ IDEA has a community edition that is now opensource (Apache license) and free

2010-02-22 Thread Tong Fin

How popular is IntelliJ IDEA ?

Tong

On Fri, Feb 19, 2010 at 5:48 PM, Tommaso Teofili
tommaso.teof...@gmail.comwrote:

 Hi Marshall,
 I also add that for Apache committers there is also the possibility to ask
 for a commercial license for free.
 I asked and got it.
 Cheers.
 Tommaso

 2010/2/19 Marshall Schor m...@schor.com

  In case anyone wants to add IDEA support for UIMA...
 
  -Marshall

[jira] Created: (UIMA-1734) UIMA-AS Deployment Descriptor doesn't work with Eclipse 3.4.2

2010-02-04 Thread Tong Fin (JIRA)

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 org.eclipse.ui.internal.Workbench.runEventLoop

Re: [VOTE] Release UIMA 2.3.0 RC9 as UIMA 2.3.0 incubating

2010-01-11 Thread Tong Fin

+1  Tong

On Mon, Jan 11, 2010 at 11:27 AM, Marshall Schor m...@schor.com wrote:



 Marshall Schor wrote:
  This build keeps the uimacpp and sandbox components from the previous
 release
  candidate (the download site on 
  people.apache.org/~schorhttp://people.apache.org/%7Eschorhas hard links 
  to the
  previous artifacts - so they are guaranteed to be identical).
 
  We've had a few sanity checks for the RC9 build, including installing the
  Eclipse plugins via the RC9 update site on both linux and windows, and
 running
  downloading  installing the base uima and uima-as binary components and
 running
  the installation verification tests - and everything looks good.
 
 
  This build consists of 4 major components: the core UIMA framework
  (uimaj), the C++ enablement (uimacpp), the Asynchronous Scaleout
  component (uima-as) and a set of annotators and other add-ons (sandbox).
 
  These have been through more than 3 months of validation and testing
 (counting
  the previous release candidates).  The build process was strengthened to
 include
  running RAT (the Release Audit tool) automatically and verifying no RAT
 issues
  are found (except for the uimacpp part, where it is still run and
 verified
  manually).
 
  The release artifacts are available on
  http://people.apache.org/~schor/uima-release-candidates/2.3.0-RC9/http://people.apache.org/%7Eschor/uima-release-candidates/2.3.0-RC9/
 
  These artifacts include a partial version of the Eclipse Update Site for
  the Eclipse plugins, but is complete for the 2.3.0 release.
 
  The release is digitally signed by Marshall Schor for all the components
  except for the C++ component, which is signed by Edward Epstein.
 
  No new export control issues are needed for the components; only the
 uima-as
  component continues to be classified as 5D002 because it includes Apache
  ActiveMQ which is so classified (see
 http://www.apache.org/licenses/exports/ )
 
  Please vote on approving this release.  This vote is for all 4
  components, together. After the UIMA committers vote, we will ask the
  IPMC to vote.
 
  [ ] +1 Release RC9, it's ready
  [ ] -1 Don't release yet because of these issues which need to be
  addressed first: ...
 
  --Marshall
 
 
 +1   -Marshall

Re: [VOTE] Release UIMA 2.3.0 release candidate 7 as UIMA 2.3.0 incubating

2009-12-10 Thread Tong Fin

+1

-- Tong

Re: [Apache UIMA 2.3 RC] - Missing Eclipse fragment org.apache.uima.runtime.fragments.deployeditor ?

2009-11-15 Thread Tong Fin

On Sun, Nov 15, 2009 at 9:09 AM, Marshall Schor m...@schor.com wrote:



 Tong Fin wrote:
  It looks like we don't have the Eclipse fragment
  org.apache.uima.runtime.fragments.deployeditor which is required by the
  Deployment Descriptor Editor.
 
 I see it in eclipsePlugins directory of my test dir built by unzipping
 the uimaj binary distribution, and then the uima-as binary distribution
 (on top of the uimaj base - as is now required).  (It is true it is not
 provided with the base uima bin distribution, but it is provided with
 the uima-as distribution.)

OK. Now, I understand why I cannot see it in the base uimaj bin
distribution's eclipsePlugins directory unless I overlay uima-as
distribution.

I think we should not put DDE in the base uima bin distribution if we don't
expect it to work in that way. It will create a confusion for the end-users
that only use the base uima bin distribution unless we have a good raison to
put there.

-- Tong

Re: [Apache UIMA 2.3 RC] - Missing Eclipse fragment org.apache.uima.runtime.fragments.deployeditor ?

2009-11-15 Thread Tong Fin

Sorry, it is a false alarm !

After repeating the operations and double checking the Eclipse Extension
Sites of my testing Eclipse, I really that there are two copy of uima
related plugins in different extension sites.

The distribution builds of the UIMA RC is CORRECT.

Sorry, Marshall !

-- Tong

On Sun, Nov 15, 2009 at 1:44 PM, Marshall Schor m...@schor.com wrote:



 Tong Fin wrote:
  On Sun, Nov 15, 2009 at 9:09 AM, Marshall Schor m...@schor.com wrote:
 
 
  Tong Fin wrote:
 
  It looks like we don't have the Eclipse fragment
  org.apache.uima.runtime.fragments.deployeditor which is required by
 the
  Deployment Descriptor Editor.
 
 
  I see it in eclipsePlugins directory of my test dir built by unzipping
  the uimaj binary distribution, and then the uima-as binary distribution
  (on top of the uimaj base - as is now required).  (It is true it is not
  provided with the base uima bin distribution, but it is provided with
  the uima-as distribution.)
 
 
  OK. Now, I understand why I cannot see it in the base uimaj bin
  distribution's eclipsePlugins directory unless I overlay uima-as
  distribution.
 
  I think we should not put DDE in the base uima bin distribution if we
 don't
  expect it to work in that way.

 Sounds correct.  I looked in the bin distr for base UIMA, in the
 eclipsePlugins folder, and don't see the DDE there - but it sounds like
 you are seeing it somewhere it shouldn't be.  Can you be more speciifc?

 -Marshall

  It will create a confusion for the end-users
  that only use the base uima bin distribution unless we have a good raison
 to
  put there.
 
  -- Tong

[Apache UIMA 2.3 RC] - Missing Eclipse fragment org.apache.uima.runtime.fragments.deployeditor ?

2009-11-14 Thread Tong Fin

It looks like we don't have the Eclipse fragment
org.apache.uima.runtime.fragments.deployeditor which is required by the
Deployment Descriptor Editor.

-- Tong

[jira] Closed: (UIMA-1076) In DDE, CAS pool size setting is Not Applicable when Top AE is a primitive AE

2009-10-22 Thread Tong Fin (JIRA)


 [ 
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

2009-10-14 Thread Tong Fin (JIRA)


 [ 
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

2009-10-14 Thread Tong Fin (JIRA)


 [ 
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)

2009-08-31 Thread Tong Fin (JIRA)


 [ 
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

2009-08-31 Thread Tong Fin (JIRA)


 [ 
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

2009-08-28 Thread Tong Fin (JIRA)

[
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

2009-08-28 Thread Tong Fin (JIRA)

[
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

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.

Re: issue with adding source to jars

2009-08-12 Thread Tong Fin

On Wed, Aug 12, 2009 at 4:12 PM, Marshall Schor m...@schor.com wrote:

 https://issues.apache.org/jira/browse/UIMA-1356 wants to have source
 with jars used in the Eclipse plugins.  After fiddling with doing that,
 I got things working up to adding to the runtime jars.  Then I
 realized, that these jars have other jars inside them... and things were
 already pretty complex.

 An alternative would be to have just one jar with all the sources in it,
 and we would get rid of add-sources-to-jar things. Users wanting to have
 Eclipse (and maybe other IDEs?) locate the source would be pointed to
 this jar.  Eclipse supports this, AFAIK.

 The add-sources-to-jar would be replaced with a script to build all the
 sources into one jar.

 Opinions?

 -Marshall


Just for info, starting from Eclipse 3.5, the preferred approach is to
create a source plugin that will behave and be installed as ordinary
plugin. But, since we are using maven, we may have some difficulty to build
those source plugins.

(BTW, I never try to create the source plugin).

-- Tong

Re: [VOTE] graduate UIMA-AS from sandbox

2009-08-03 Thread Tong Fin

  On Fri, Jul 31, 2009 at 11:55 AM, Marshall Schorm...@schor.com wrote:
   I would like to propose graduating UIMA-AS from the sandbox, making it
 a
   separately downloadable add-on to base UIMA. It has been extensively
   used in several projects and has undergone (as a result) a lot of
   bug-fixing and hardening.  With the upcoming release, I think it would
   make sense to graduate it from the sandbox.  Other opinions?
  
   If there is general consensus around this, then I will kick off some
   other discussion topics on details of how to do this.
  
   -Marshall


+1

-- Tong

Re: maven build problem

2009-07-07 Thread Tong Fin

I really wonder if we're doing ourselves a favor by using
 maven for the eclipse plugin and eclipse update site builds.
 In eclipse we have all the tooling that we need at our
 disposal.  We could maintain the plugin dependencies in the
 manifest files, where they belong.


I completely agree with this concern.
It looks like we are over done in this area and trying to shoot a moving
target.

For example, some time ago, some users have the problem to attach the source
code with the plugin and there is no easy solution. Different versions of
Eclipse have different way to build the source code and the recently
released Eclipse 3.5 has a new way to build the source plug-in.
This is just one of the example that we have to deal with multiple versions
of Eclipse and try to catch up what Eclipse can do with maven.

I feel that we and the users have more problems than the benefits that  we
get by having a single tool maven to build everything.

-- Tong

[jira] Resolved: (UIMA-1373) SimpleUimaAsService needs a POM

2009-06-09 Thread Tong Fin (JIRA)


 [ 
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.

Re: [jira] Resolved: (UIMA-1373) SimpleUimaAsService needs a POM

2009-06-09 Thread Tong Fin

Yes, good suggestion.
I just completely forgot it !

-- Tong

On Tue, Jun 9, 2009 at 11:12 AM, Jörn Kottmann kottm...@gmail.com wrote:

 Hi Tong,

 please mention the jira issue in the commit comment. I think now you
 can still add it by modifying svn properties.

 Jörn


 On Jun 9, 2009, at 5:04 PM, Tong Fin (JIRA) wrote:


[
 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.

Re: SimpleUimaAsService

2009-06-05 Thread Tong Fin

Yes, it is missing a pom.xml since I am still learning maven.

Thank Tommaso for the helps.
If you have any problem/issue with the code, please let me know.

Thanks,
Tong

On Fri, Jun 5, 2009 at 6:04 AM, Tommaso Teofili
tommaso.teof...@gmail.comwrote:

 I can do it.Regards,
 Tommaso Teofili

 2009/6/5 Thilo Goetz twgo...@gmx.de

  Anyone planning on working on SimpleUimaAsService?  It's
  missing a pom.xml.
 
  --Thilo

Re: [VOTE] Graduate the Cas Editor out of the sandbox

2009-05-19 Thread Tong Fin

Great work!. It's time to take it out of the box and put it into the main
stream.

+1

-- Tong

On Tue, May 19, 2009 at 1:11 PM, Jörn Kottmann kottm...@gmail.com wrote:

 Please cast your vote to graduate the Cas Editor out of the sandbox
 into uimaj.

  [ ] +1 Graduate the Cas Editor out of the sandbox into uimaj
  [ ] 0 don't care
  [ ] -1 Leave the Cas Editor in the sandbox

 Jörn

[jira] Commented: (UIMA-1334) Sandbox - SimpleServer missing config-xml.jar

2009-04-24 Thread Tong Fin (JIRA)


[ 
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

[jira] Created: (UIMA-1332) [DDE] Allow an empty value for the Broker URL for input queue field (related to UIMA-1288)

2009-04-20 Thread Tong Fin (JIRA)

[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.

Re: [jira] Closed: (UIMA-1314) Add OSGI support to uima-as

2009-04-17 Thread Tong Fin

2009/4/17 Jörn Kottmann (JIRA) uima-dev@incubator.apache.org


 [
 https://issues.apache.org/jira/browse/UIMA-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]

 Jörn Kottmann closed UIMA-1314.
 ---

   Resolution: Fixed
Fix Version/s: 2.3AS

 Added the uimaj-as-osgi-runtime project to uim-as which is a fragment and
 attaches the uima-as to the existing uimaj-ep-runtime plugin. The new
 sub-project was added to the uima-as eclipse plugin super pom and to the
 uima-as distribution.


Jörn,
This is a great work !

Any chance that we may have some examples for users to try ?

-- Tong

Re: [jira] Closed: (UIMA-1314) Add OSGI support to uima-as

2009-04-17 Thread Tong Fin

On Fri, Apr 17, 2009 at 12:10 PM, Jörn Kottmann kottm...@gmail.com wrote:

 I created the plugin because I needed access to uima as from
 a Apache Camel component which triggers tagging of documents
 in our database, but all the component does is sending a CAS with a URL
 to the annotator pipeline which is then used by a cas multiplier to fetch
 the
 actual document from a database.

 If there is interested it should be possible to contribute it to uima as.

 I did not create any examples because the OSGI support does not change
 much the only thing it does for a user is that he can now write a OSGI
 component
 which uses uima as.


I think this is a good use-case that shows that uima-as can be used to
expose the UIMA's analysis engines running inside OSGi (by using ActiveMQ
?).

Other approach is to access UIMA's AEs through the web container (Servlet)
like Uima SimpleServer in sandbox.

Do you have something in mind you would like to see demonstrated in an
 example ?

 Maybe it makes sense to document which dependencies the uima
 as osgi runtime plugin has.


Yes, I agree with you that we need to show the benefits of using OSGi
compared to other approaches for the examples.
In the past, there are some UIMA works related to OSGi. But, there are many
issues to be addressed and there is no generic solution for that.


 We should also think about converting the existing uima as eclipse plugin
 to use the
 new osgi runtime plugin, if I have seen it correctly they currently just
 embed uima as, right ?


Currently, the Deployment Descriptor Editor is the only Eclipse plugin
specific for uima-as. It doesn't depend on uima-as runtime.
But, we are thinking to extend it (or as another Eclipse plugin) to support
the deployment of uima-as services in multiple machines environment.
When the time comes, the uima-as fragment that you just created will help.
It is also true for any Eclipse-based work that requires access to uima-as
runtime.

--  Tong

[jira] Commented: (UIMA-1314) Add OSGI support to uima-as

2009-04-03 Thread Tong Fin (JIRA)


[ 
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.

Re: [VOTE] Accept contribution of Lucene CAS Indexer into the sandbox

2009-03-09 Thread Tong Fin

+1

-- Tong

On Sun, Mar 8, 2009 at 8:58 AM, Marshall Schor m...@schor.com wrote:

 +1   Contribution looks quite impressive!

 -Marshall

 Rico Landefeld wrote:
  Hi,
 
  I've attached the corrected POM without parent POM to the issue. This
  should solve the problem.
 
  best regards,
  Rico Landefeld
 
 
  Hi - I tried to use maven to build this, but it seems to have a parent
  POM which is not found.  Any suggestions for how to get the build to go?
 
  The error reported was:
 
  [ERROR] FATAL ERROR
  [INFO]
  
  [INFO] Error building POM (may not be this project's POM).
 
  Project ID: de.julielab:jules-lucene-indexer:jar:0.5-SNAPSHOT
 
  Reason: Cannot find parent: de.julielab:jules for project:
  de.julielab:jules-lucene-indexer:jar:0.5-SNAPSHOT for project
  de.julielab:jules-lucene-indexer:jar:0.5-SNAPSHOT
  ...
  Caused by: org.apache.maven.project.ProjectBuildingException: POM
  'de.julielab:jules' not found in repository: Unable to download the
  artifact from any repository
 
de.julielab:jules:pom:1.3
 
  from the specified remote repositories:
central (http://repo1.maven.org/maven2)
 
  Thanks.  -Marshall
 
  Thilo Goetz wrote:
 
 
  Please vote to accept the contribution of the Lucene
  CAS indexer into the sandbox.  See Jira issue UIMA-1299
  (https://issues.apache.org/jira/browse/UIMA-1299) for
  the tar ball.
 
[ ] +1 Accept Lucene CAS indexer into UIMA sandbox
[ ] -1 Do not accept contribution of Lucene CAS indexer
 
  You're all encouraged to vote, even if you're not a
  UIMA committer.  If you vote to reject the contribution,
  please remember to give a reason.
 
  --Thilo
 
 
 
 
 
 
 
 
 




-- 
 Tong

Re: UIMA : Task

2009-03-06 Thread Tong Fin

Hi,
When you do POST, do you use text as the parameter for setting the string
from your input text-file ?

It will help if you can give us more info about the parameters of your POST.

-- Tong

On Fri, Mar 6, 2009 at 3:46 PM, Balkrishnan. V balkrishna...@iiitb.netwrote:

 Hi,

 I am using the Simple-Server from the Sandbox.

 When I load a text-file of size 4MB to generate the corresponding
 annotation-xml
 then I get the following exception:


 ==
 org.apache.uima.simpleserver.servlet.SimpleServerServlet: POST request
 received:
 Sat Mar 07 00:51:48 IST 2009
 Mar 7, 2009 12:51:48 AM org.apache.catalina.core.StandardWrapperValve
 invoke
 SEVERE: Servlet.service() for servlet simple-server-test threw exception
 java.lang.NullPointerException
at org.apache.uima.simpleserver.servlet.SimpleServerServlet.analyze
 (SimpleServerServlet.java:194)
at org.apache.uima.simpleserver.servlet.SimpleServerServlet.doPost
 (SimpleServerServlet.java:181)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
 (ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter
 (ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke
 (StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke
 (StandardContextValve.java:191)
at org.apache.catalina.core.StandardHostValve.invoke
 (StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke
 (ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke
 (StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service
 (CoyoteAdapter.java:286)
at org.apache.coyote.http11.Http11Processor.process
 (Http11Processor.java:845)
at
 org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process
 (Http11Protocol.java:583)
at
 org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Unknown Source)

 ==

 Can you please let me know how I can resolve this error ?

 Thanks in Advance,

 --Balkrishnan.V





-- 
 Tong

[jira] Closed: (UIMA-1260) [SimpleServer] Expose some private variables and method as protected so that new subclasses for UIMA-AS can be defined

2009-01-04 Thread Tong Fin (JIRA)


 [ 
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

2009-01-04 Thread Tong Fin (JIRA)

[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

2009-01-04 Thread Tong Fin (JIRA)


 [ 
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

2009-01-02 Thread Tong Fin (JIRA)


 [ 
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

2009-01-02 Thread Tong Fin (JIRA)


 [ 
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

2009-01-02 Thread Tong Fin (JIRA)


 [ 
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

2009-01-02 Thread Tong Fin (JIRA)

[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

2009-01-02 Thread Tong Fin (JIRA)


[ 
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)

2008-09-16 Thread Tong Fin (JIRA)

[
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.

Re: [VOTE] Accept CAS Viewer source code into the sandbox

2008-08-28 Thread Tong Fin

+1 Tong

On Wed, Aug 27, 2008 at 10:08 AM, Eddie Epstein [EMAIL PROTECTED] wrote:

 With the following understanding:

 We should
 decide on one tool as the basis for viewing and editing
 CASes.  As we have already released the CAS Editor, it should
 be that one tool.  We should vote the CasViewer into the
 sandbox with the express understanding that it will never
 see a release, but ideas and code from the CasViewer will
 be used to improve and enhance the CAS Editor.  The CAS
 Editor will evolve into a tool that can be used either
 stand-alone (as it is now), or integrated into the rest
 of the UIMA tooling.

 Please cast your vote:

 [ ] +1 accept CAS viewer source code into sandbox
 [ ] 0 don't care
 [ ] -1 don't accept, I still have issues

 Thanks, Eddie




-- 
Tong

[jira] Closed: (UIMA-1146) Setting the number of concurrent listeners of a reply queue for Co-located Delegates

2008-08-27 Thread Tong Fin (JIRA)

[
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

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)

2008-08-27 Thread Tong Fin (JIRA)


 [ 
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)

2008-08-27 Thread Tong Fin (JIRA)


 [ 
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.

Re: Proposed API for CAS Journaling

2008-08-26 Thread Tong Fin

 -1 to returning internal CAS handles as FS IDs.  That's asking for
 trouble.  Why would you want to do that?  You're forcing the user
 to deal with low-level CAS APIs.

I think this FS ID is required by the tool to show the modification history
of a FS. For example, FS with id=10 is created by AE1 and is modified by
AE2, etc.. How we implement this FS ID is hidden from the tool and it can be
generated or get from some where.

-- Tong

Re: Proposed API for CAS Journaling

2008-08-26 Thread Tong Fin

Just to clarify...

My comment means that I suggest to have a new API to get FS from ID and not
to use the existing Low-level API. This ID is not related to any
implementation that we have or know about.

On Tue, Aug 26, 2008 at 12:22 PM, Tong Fin [EMAIL PROTECTED] wrote:


 -1 to returning internal CAS handles as FS IDs.  That's asking for
 trouble.  Why would you want to do that?  You're forcing the user
 to deal with low-level CAS APIs.

 I think this FS ID is required by the tool to show the modification history
 of a FS. For example, FS with id=10 is created by AE1 and is modified by
 AE2, etc.. How we implement this FS ID is hidden from the tool and it can be
 generated or get from some where.

 -- Tong




-- 
-- Tong

Re: Cad Editor splitting

2008-08-26 Thread Tong Fin

On Tue, Aug 26, 2008 at 5:17 AM, Thilo Goetz [EMAIL PROTECTED] wrote:

 Jörn Kottmann wrote:

 This does sound like a good direction. In order to use the CAS viewer it
 should be accepted into the sandbox. Any objection to resubmitting the
 vote?


 There is still no plan how to merge it with the Cas Editor, expect for a
 small
 part which handles how to open the Cas Viewer eclipse editor.

 We should decide this first, then we can resubmit the vote.

 In my opinion the only way to truly merge it with the Cas Editor is
  Level-2 sharing.
 If we do not want this we have many things duplicated and two tools which
 show a Cas in a slightly different way.

 Are there other options that we missed ? Other than Level-1 sharing
 which can only share ui widgets.

 Future work like Cas journaling ui has then also to be done
 twice if the plan is to build it directly into the Cas Viewer.

 Jörn


 First let me echo what others have said: it would be very
 good if we had a consistent Eclipse tooling strategy, not
 one with several competing tools.  It would be my hope that
 Joern and Tong can cooperate on that tooling strategy.

 Here's what I would suggest, as someone who will probably
 not write a single line of code for this effort.  We should
 decide on one tool as the basis for viewing and editing
 CASes.  As we have already released the CAS Editor, it should
 be that one tool.  We should vote the CasViewer into the
 sandbox with the express understanding that it will never
 see a release, but ideas and code from the CasViewer will
 be used to improve and enhance the CAS Editor.  The CAS
 Editor will evolve into a tool that can be used either
 stand-alone (as it is now), or integrated into the rest
 of the UIMA tooling.

Thilo,
I think we are moving into this direction to have one integrated tool.


 That's my suggestion after having watched this thread for
 a while.  Obviously, it will only work if both Joern and
 Tong can get behind this plan.

 Tong, I understand that you have put a lot of effort into
 the CAS Viewer, and I would fully understand if you didn't
 agree to this suggestion.  Still, I believe that for UIMA
 as a whole, it would be the best solution.


Well, you are right that I am not completely agree on the approach. But, if
we think as the community,  I will accept and support the majority
opinions for the best interest of UIMA community as you suggested.

-- Tong

Re: Proposed API for CAS Journaling

2008-08-26 Thread Tong Fin

The goal is to allow user to see the changed history of each feature
structure.
For example, the Fig 3.5 in the proposed GUI posted in Wiki
http://cwiki.apache.org/UIMA/cas-viewer-extension-for-provenance-tracking-of-uima-cas-content.html
show that the FS (of RoomNumber type) with id=61 is created by RoomNumber AE
and is modified by Meeting AE.
(hope that the link works !).

To implement the about UI, one way is to use the ID to identify the FS. This
ID can be created by the tool (outside of UIMA) or by the UIMA. I don't mind
where we implement that ID as long as the tool has a consistent way to
create the ID.

If we have other option to do that other than using ID to identify each FS,
it is fine with me too.

On Tue, Aug 26, 2008 at 1:28 PM, Thilo Goetz [EMAIL PROTECTED] wrote:

Tong Fin wrote:
Just to clarify...

Sorry, but this didn't really clarify anything for me. What's wrong
with just returning an array of FS objects?

My comment means that I suggest to have a new API to get FS from ID and
not
to use the existing Low-level API. This ID is not related to any
implementation that we have or know about.

On Tue, Aug 26, 2008 at 12:22 PM, Tong Fin [EMAIL PROTECTED] wrote:

-1 to returning internal CAS handles as FS IDs. That's asking for
trouble. Why would you want to do that? You're forcing the user
to deal with low-level CAS APIs.

I think this FS ID is required by the tool to show the modification
history
of a FS. For example, FS with id=10 is created by AE1 and is modified by
AE2, etc.. How we implement this FS ID is hidden from the tool and it
can be
generated or get from some where.

-- Tong

--
-- Tong

Re: Proposed API for CAS Journaling

2008-08-26 Thread Tong Fin

On Tue, Aug 26, 2008 at 2:53 PM, Adam Lally [EMAIL PROTECTED] wrote:

  With the proposed change to return an Iterator instead of an array of
  ints, you
  can get a reference to a FeatureStructure object and then call  the
  method hashCode()
  to get the id.
 

 I would not recommend relying on a hash code being a unique
 identifier.  There's no guarantee that that will always be the case.
 If the UI needs a unique integer for its own purpose it could generate
 its own and use a Map from FeatureStructure to integer to keep track.


I agree with Adam. The UI will not use a 20-digit, for example, to show to
the user !
The tool will use it own scheme that is best for end-user.

BTW, the proposed change to return an Iterator of FS is OK with me.

-- Tong

Re: Proposed API for CAS Journaling

2008-08-26 Thread Tong Fin

As I said, the Joern's use-case is at the application level. There is more
room to add supports. But, we need to put more code in the application side
(not in the UIMA framework). When I said keeping info in CAS, I mean that I
rely on the UIMA framework to provide API to do de/serialization and access
the CAS content. So, what I can do with the CAS is limited. And, it will not
be true when we do something at the tool/application level.

Since we are talking about doing something at the tool/application level,
there is another approach that I can think about (not sure how hard it is).
The beauty of UIMA is that its xmiCAS can be read by Ecore (EMF) and there
are some codes in the UIMA framework to support that. We may use UIMA+EMF to
support modification history for editing since Ecore has a good support
for changes. (Just my thinking)


On Tue, Aug 26, 2008 at 4:18 PM, Thilo Goetz [EMAIL PROTECTED] wrote:

 It's not directly supported, but don't you think it could help
 in such an application?  You would still need to keep the full
 intermediate CASes around, but the journal would be very helpful
 in determining where changes happened.  The actual difference
 for display could be computed on the fly.  So full CAS + journal
 and you've got most of the way to a CAS diff between versions, no?

 --Thilo

 Tong Fin wrote:
  In short answer, it is not possible since the context of creating CAS
  Journal that we are proposing is different from your use-case.
 
  In the current design, we try to minimize the overhead in the UIMA
 framework
  and less  modification  to the code. We keep track the changes by each
  analysis engine and we don't (at least now) preserve the intermediate
  values of changes to the same feature structure. For example, if the
 feature
  structure abc is changed by AE1 and  then by AE2, we only keep the
 value
  after AE2 modification. Other point that I should mention is that, since
 the
  CAS content is kept and is managed by UIMA framework, there are some
  limitations about the information that we would like to add and keep
  during running UIMA pipeline (without major modification to the UIMA
  framework). We are doing journaling at runtime.
 
  Your use-case is more at the application level and it is more flexible on
  how we remember the history. Maybe, there is other way on how to save
 the
  history (not just in the CAS).
 
  On Tue, Aug 26, 2008 at 3:35 PM, Jörn Kottmann [EMAIL PROTECTED]
 wrote:
 
  Does revision mean change between runs or between operations ?
  If it is, the current proposed format does not cover this use-case
  because
  there are issues on how to represent intermediate values of feature
  structures for example.
 
  A user opens a CAS in the editor and do changes to the CAS then he
  saves the editor and the changes are written to file. Each time he does
  this I would like to keep a revision like the history in eclipse.
 
  Would this be possible ?
 
  Jörn
 
 
 
 




-- 
 Tong

Re: [MAVEN] Plugin id of UIMA runtime fragment in UIMA-AS distribution

2008-08-25 Thread Tong Fin

Hi Marshall,
Thank for the explanation.
I do overlook UIMA-1123.

-- Tong

Re: Cas Viewer discussion

2008-08-25 Thread Tong Fin

Hi Adam,
Please see my in-line comments.

The point of the discussions was not primarily about UI but about
 integration with the CAS Editor (UI just got dragged into it since
 there are UI implications for how the integration is done).

Yes, you are right. We are still talking at the abstract level and we have
a small progress that makes me nervous since the time passes so quick
(maybe, I need to be more patient).

 I'd hoped
 that there could be some agreement between you and Joern about how
 integration might happen, but unfortunately the two of you appear to
 have very different views about at what level the sharing might take
 place, and there has been no progress resolving this.

At the abstract discussion, I think expressing opinions and concerns from
many peoples (as you, Joern, and I did) are very valuable and important. At
this moment, I think we do agree on the goals which include the one as you
mentioned in you post:

I don't like having such a confusing array of overlapping tools in UIMA
as a whole.

When we work on the details, the differences will be gone I think.



 I have mixed feelings about that -
 one one hand, I do like the CAS Viewer as a tool, on the other hand, I
 don't like having such a confusing array of overlapping tools in UIMA
 as a whole.

Thank you to know that the CAS Viewer has an additional happy user :)


 Maybe, it would help alleviate these concerns if your plan included
 more details on how you plan to acheive the integration.

 The first step that I try to do with this discussion is to get the CAS
Viewer accepted into the UIMA svn, to express my plan what to do next (like
supporting CAS Journaling), and to hear other people's opinions.
Regarding the integration with other tools (currently with the CAS Editor),
as I mentioned early, we do agree on the goals. For the details, we need to
work together to come out with the plan and propose to the community. I am
sure that all the issues can be resolved at the end.

Now, Joern starts another thread CAS editor spitting that is a good
starting point toward  the details plan for the integration. I will put my
opinions/comments there and I hope that Joern and I can come out with a
reasonable plan detailed enough to make you optimistic about tooling
integration.

-- Tong

Re: Cad Editor splitting

2008-08-25 Thread Tong Fin

 Jörn,
The plan looks good to me. I am happy to work with you for this integration.

Should we start at the high-level a little bit by discussing about the flow
? For example, assuming that the input is an xmiCAS or CAS, what is the flow
of the tool up to the point that users see something in Eclipse.

-- Tong

[jira] Created: (UIMA-1156) [SimpleServer] Add improvement to support UIMA-AS services

2008-08-25 Thread Tong Fin (JIRA)

[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

2008-08-25 Thread Tong Fin (JIRA)

[
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

--
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

2008-08-25 Thread Tong Fin (JIRA)

[
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

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [jira] Updated: (UIMA-1146) Setting the number of concurrent listeners of a reply queue for Co-located Delegates

2008-08-25 Thread Tong Fin

When I try to attach the screen-shot, I cannot find the place to grant the
licence.
I may miss something.

-- Tong

[jira] Updated: (UIMA-1146) Setting the number of concurrent listeners of a reply queue for Co-located Delegates

2008-08-25 Thread Tong Fin (JIRA)

[
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

--
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

2008-08-25 Thread Tong Fin (JIRA)

[
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

--
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

2008-08-25 Thread Tong Fin (JIRA)

[
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

--
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

2008-08-24 Thread Tong Fin (JIRA)

[
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

--
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

2008-08-24 Thread Tong Fin (JIRA)

[
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

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Cas Viewer discussion

2008-08-22 Thread Tong Fin

Hi,
It is almost 7 weeks now since I submitted the CAS Viewer. There are some
discussions about various issues related to GUI, sharing code, etc. Some are
related to CAS Viewer itself and some are general issues related to Eclipse
UI.

If the CAS Viewer is accepted by Apache UIMA, my original plan is to:
 1. Release the CAS Viewer as it is since I believe that it is good enough
for Uima users to try (based on the feedbacks from internal users)
 2. Maintain and improve the CAS Viewer by adding new functionality (like
CAS Journaling as I put my proposal in the UIMA Wiki)
 3. Integrate with other UIMA tools

Unfortunately, the discussion is slow and doesn't go anywhere (most of the
discussions are related to UI that is hard to say if it is right or wrong).
I think it is time to conclude if the CAS Viewer contribution makes sense or
not so that I can move on what to do next.

Thanks,
-- Tong

[jira] Commented: (UIMA-1146) Setting the number of concurrent listeners of a reply queue for Co-located Delegates

2008-08-22 Thread Tong Fin (JIRA)


[ 
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

2008-08-22 Thread Tong Fin (JIRA)


[ 
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

2008-08-19 Thread Tong Fin (JIRA)


 [ 
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

2008-08-19 Thread Tong Fin (JIRA)


 [ 
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

2008-08-19 Thread Tong Fin (JIRA)

[
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

2008-08-19 Thread Tong Fin (JIRA)


 [ 
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

2008-08-19 Thread Tong Fin (JIRA)

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

2008-08-19 Thread Tong Fin (JIRA)

[
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

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Cas Viewer discussion

2008-08-15 Thread Tong Fin


 In addition, I tend to rearrange the views in a perspective to suit
 my needs.  I like some views stacked, others get their own area.
 My workspace will remember those changes for me.

I do the some way as you. This is the way that Eclipse User Guideline
recommends.

I don't think you
 can do these sorts of things with a single, integrated editor.

It depends on the contents. There are some cases that the users cannot
freely arrange the views. For example, the details part in the
master/details block in a form editor (in CAS Viewer, Plugin/Manifest
Editor, etc.), is tight to the master part. Eclipse's Form recommends some
way on how to arrange those parts.

So all in all, it's just much more flexible to have several views,
 and to unite them all under a (optional) perspective.


We should try to estimate the efforts and go through some screen-mockups by
using some use-cases.

-- Tong

[jira] Updated: (UIMA-1130) Deployment Descriptor should allow setting the number of concurrent listeners for a reply queue

2008-08-12 Thread Tong Fin (JIRA)


 [ 
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

2008-08-12 Thread Tong Fin (JIRA)


 [ 
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.

Re: Cas Viewer discussion

2008-08-07 Thread Tong Fin

On Fri, Aug 1, 2008 at 2:40 PM, Adam Lally [EMAIL PROTECTED] wrote:

 On Fri, Aug 1, 2008 at 2:33 PM, Jörn Kottmann [EMAIL PROTECTED] wrote:
  I still think that the huge benefit of doing it the Cas Editor way with
  multiple views:
 
  + Its easier to explore a CAS file because there is more screen space to
 see
  things.
 

 I agree with that.  I've used the CAS Editor a few times, and
 basically always need to maximize that editor window in order to see
 anything.  It basically always needs to take over all of the screen
 real-estate in order to be useful to me,

Maximize is the shortest way to take over the whole space. If the multiple
views are used, either you maximize the view (which is very similar the
maximize the CAS Viewer) or resize the view which will affect the sizes of
other views/editors (that will take more operation to restore them back).
Basically, I don't see how multiple views can solve the real-estate
problem and I feel that double-click to maximize and restore the CAS
Viewer is still the best and the short-cut operation to switch the tasks
between viewing the CAS and do something else.

so it might as well be its
 own perspective.

Having its own perspective for the CAS Viewer won't solve the problem either
for the following reason.
If there are some files (like Java source files) opened in the editor area,
they will show up in the new perspective (we just come back to the original
issue). Most of the cases, users will have multiple files opened in the
editor area.

The approach taken by the CAS Viewer is not new. The GUI design of the CAS
Viewer is based on multiple-page form editor like plug-in/manifest editor.
In CAS Viewer, each page corresponds to each CAS view (sofa). In each page
(or CAS view), I use sash form, master/details block, and sections to
represent/separate the logical structure of the CAS and to show the
relationship and interaction between parts. For example, when user selects
some type in the CAS Types section, the annotations of that selected
type will be highlighted in the Document section.
These sections are very related with each other. I don't see much benefit
from moving from section to view. If we have multiple-view
(multiple-sofa) in the CAS, the situation becomes more complicated.

We need to do the integration step-by-step, prioritize the works, and try to
avoid over-design.

-- Tong

Re: [DISCUSS] holding a vote on the Cas Viewer submission

2008-08-07 Thread Tong Fin

On Wed, Aug 6, 2008 at 5:45 PM, Jörn Kottmann [EMAIL PROTECTED] wrote:

 Does the community wish to have more discussion about this before I call
 for the vote?



 I think there are still open questions which should be answered before a
 new vote.

 I would like to know if we merge with the Cas Editor, does this makes sense
 for us ?
 In my opinion this means technically that the Cas Viewer uses multiple
 views like
 the Cas Editor. Do we want this ? There is still a discussion about this in
 another thread

Related to multiple views, I posted my opinion as a reply to Adam in
another thread.



 Who will work on the code once it is in the sandbox ?

I will maintain the code of the CAS Viewer, extend it to support CAS
Journaling, and other integration that will benefit to the community.


- Tong

Re: Cas Viewer discussion

2008-08-07 Thread Tong Fin

On Thu, Aug 7, 2008 at 4:24 PM, Adam Lally [EMAIL PROTECTED] wrote:

 On Thu, Aug 7, 2008 at 12:05 PM, Tong Fin [EMAIL PROTECTED] wrote:
  The approach taken by the CAS Viewer is not new. The GUI design of the
 CAS
  Viewer is based on multiple-page form editor like plug-in/manifest
 editor.
  In CAS Viewer, each page corresponds to each CAS view (sofa). In each
 page
  (or CAS view), I use sash form, master/details block, and sections
 to
  represent/separate the logical structure of the CAS and to show the
  relationship and interaction between parts. For example, when user
 selects
  some type in the CAS Types section, the annotations of that selected
  type will be highlighted in the Document section.
  These sections are very related with each other. I don't see much benefit
  from moving from section to view. If we have multiple-view
  (multiple-sofa) in the CAS, the situation becomes more complicated.
 

 Okay, from a real-estate perspective, I guess there is not that much
 difference between the two approaches.  I think the main point of
 having a perspective with multiple views or editors is exactly to
 support integration of different components (views and editors).  That
 seems to be exactly the situation that we're in now with the CAS
 Viewer and CAS Editor.  Wouldn't it be easier to mesh the different
 parts of the Viewer and Editor if they were separate views/editors?


About Perspective, I look at the Eclipse's User Guideline at:
http://wiki.eclipse.org/User_Interface_Guidelines
The recommendation is to think carefully before creating a new
perspective.

*Guideline 8.1
*Create a new perspective type for long lived tasks, which involve the
performance of smaller, non-modal tasks.

We need to think about how users will use CAS Viewer and CAS Editor. My
thinking is that they will use the CAS Viewer when they are developing or
debugging their Java codes which are in Java or Debug perspective. The time
they spent with the CAS Viewer is short (a short task) so it may not a
good idea to have the CAS Viewer in its own perspective.

Another suggestion from the Guideline is that, before switch to the new
perspective, always ask the user which can create an extra overhead.
*Guideline 8.7*
A new perspective should be opened only if the user explicitly states a
desire to do so. In making this statement, the user agrees to leave their
old context, and create a new one.

For the CAS Editor, editing a CAS is a tedious operation that can take long
time, for example, when users try to create gold standard CAS files. It
may make sense to have it own perspective for the CAS Editor.

-- Tong

Re: Cas Viewer discussion

2008-08-07 Thread Tong Fin

On Thu, Aug 7, 2008 at 6:01 PM, Adam Lally [EMAIL PROTECTED] wrote:

 On Thu, Aug 7, 2008 at 5:16 PM, Tong Fin [EMAIL PROTECTED] wrote:
  For the CAS Editor, editing a CAS is a tedious operation that can take
 long
  time, for example, when users try to create gold standard CAS files. It
  may make sense to have it own perspective for the CAS Editor.
 

 Are you suggesting, then, that the CAS Editor and CAS Viewer should
 not be integrated into a single tool?

  -Adam


I don't mean that.
From the end-user's point of view, it is a good idea for users to see only
one tool (like the way users edit the UIMA-AS Deployment Descriptor). Under
the cover, it may switch to View mode or Edit mode according to some
preference or setting (or dynamically switch).
The question here is what is the UI of View mode and Edit mode. That is the
subject of the discussion.
Since it is a difficult issue, I prefer to do step-by-step toward the full
integration.

- Tong

Re: [jira] Commented: (UIMA-1130) Deployment Descriptor should allow setting the number of concurrent listeners for a reply queue

2008-08-06 Thread Tong Fin

It looks like we agree on the Eddie's original proposal and Marshall's
suggestion to add concurrentConsumers (NOT  concurrantConsumers ?) as an
attribute to replyQueue element.

I will proceed to modify DDE and submit the patch unless someone speaks up
:)

- Tong

On Wed, Aug 6, 2008 at 10:42 AM, Adam Lally (JIRA) 
uima-dev@incubator.apache.org wrote:


[
 https://issues.apache.org/jira/browse/UIMA-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12620271#action_12620271]

 Adam Lally commented on UIMA-1130:
 --

 I think Eddie is probably right that increasing the number of listeners
 should eliminate my need to set a prefetch  0.  A thread that's being used
 to execute prefetch isn't doing anything that an additional listener thread
 wouldn't also do, as far as I understand it.  So I'm +1 to proceed with the
 plan as Eddie outlined it.

  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
 
  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)

2008-08-06 Thread Tong Fin (JIRA)

[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.

Re: [jira] Created: (UIMA-1136) [DDE] Support editing of Prefetch value and set default value to 0 (instead of 1)

2008-08-06 Thread Tong Fin

If we agree that the default value of the prefetch is 0 (instead of 1), we
may need to modify the documentation as well.

Should I create a new JIRA so that we don't forget ?

- Tong

On Wed, Aug 6, 2008 at 12:12 PM, Tong Fin (JIRA) 
uima-dev@incubator.apache.org wrote:

 [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.

Re: Cas Viewer discussion

2008-07-31 Thread Tong Fin

On Thu, Jul 31, 2008 at 9:55 AM, Jörn Kottmann [EMAIL PROTECTED] wrote:

 I definitely think the CAS Editor and CAS Viewer should be merged, and
 I think the merged tool could become the primary tool for viewing and
 editing CASes.  We could refer to it in our documentation and
 tutorials, and it would become more popular than both the Document
 Analyzer and CAS Visual Debugger.  Of course, that'll be some work to
 pull off...



 I also think so. In my opinion we should create a new plugin
 which has the responsibility of viewing and editing of CAS files.
 This new plugin should offer an API for opening an eclipse editor
 which shows a CAS file, these editors would be for now the
 CAS Editor and the CAS Viewer.
 This API can the be used by the RCP CAS Editor and a new UIMA development
 plugin to show a CAS file.

 This new plugin can also be used by others for integration into UIMA
 related products.


Good suggestion to have a new plugin to switch the underline tools (CAS
Editor or CAS Viewer). We just provide some customization (through Eclipse
preference ?) for users to select what is the default mode they would like
to have since different users may have different usage pattern.

Actually, we did take this integrated approach to have only ONE tool to
edit UIMA component descriptors and the deployment descriptor used in
UIMA-AS deployment. That is the CDE which is used to edit all UIMA XML
descriptors.

Also, we plan to use the same approach to extend the CAS Viewer to support
CAS journaling as described in the Wiki. Any comment or suggestion about
this debugging tool will be appreciated.



 The CAS Editor and the CAS Viewer have a different style of viewing a CAS
 file.


because the way that users use the tool is different and the information
shown on the screen is different. For example, in CAS Viewer, users may want
to inspect the Index Repository but not to do editing. When users do editing
the CAS, they want to have the user interface (e.g., drag-and-drop) that is
easy to manipulate the content.



 The CAS Editor shows the text of the document in one editor with
 annotations
 and exposes other informations about the CAS in multiple views.
 The CAS Viewer shows the text and all other available informations about
 the CAS
 in one editor.

 In my opinion the way the CAS Editor solves this is superior to the way the
 CAS Viewer
 does it, because it makes it easier to reuse existing code and uses more
 space of the screen which
 makes it easier to see the contents of the CAS.

Users that use CAS Viewer are also editing or debugging their Java/Plugin
perspective (CVD gives us a good example of Run, Debug code, and Inspect
CAS). The primary usage of CAS Viewer is to inspect the CAS after running
their analysis engine. Because of that, they prefer not to have many views
floated around. By encapsulating the information into one tab, it is easy to
hide the CAS Viewer. This approach can be easily changed since the CAS
Viewer is modular and is composed of UI parts. But, until now, I don't get
any feedbacks to be in this way (having multiple views to show different
information).



 Sure this means that there is always a special eclipse perspective for
 viewing CAS files.
 Thats only what I think.

 Jörn

Yes, it makes sense for the CAS Editor to have its own perspective. It is
hard to imagine that we have some users that try to do CAS editing and look
at (or debug) their Java code at the  same time. Maybe, there are some
super users that I don't know :)

-- Tong

Re: storing particular release documentation in SVN in our project web-site pages

2008-07-25 Thread Tong Fin

Let's look at this from the user's perspective.  Who of our users
 needs access to all the old documentation?

+1 I agree. I only has a link and access to current document.

If there is a significant
 number of people who would benefit from this, then I'm for it.

If I need the old documents, I will download that old released package !

Instead of the old versions, I have more interested on the BETA version to
know what new APIs are coming and what old APIs will be gone or depreciated.
I don't think we have this BETA section (yet ?).

- Tong

Re: Cas Viewer discussion

2008-07-24 Thread Tong Fin

 According to the previous note on the history of the work here, there is
 some desire to take advantage of the Eclipse plugin packaging of this
 component and reuse it in further Eclipse-based tooling being considered,
 such as debugging tools.


One of the debugging tools is Provenance Tracking of UIMA CAS
Contenthttp://cwiki.apache.org/UIMA/improving-uima-debug-capabilities.html
as described in the Wiki.

The following is the summary of the proposal:

To improve the ability to debug and maintain UIMA components, we propose to
add the ability to log the updates to the CAS and the Index Repository as
follows:

   - track which Analysis Engines (AEs) created or modified the feature
   structures in a CA
   - track the operations (add and delete) by each AE to index feature
   structures

For the user interface part of the tool, I have posted the initial
proposalhttp://cwiki.apache.org/UIMA/cas-viewer-extension-for-provenance-tracking-of-uima-cas-content.htmlfor
further discussions in our Wiki. This Wiki page includes the screen
mock-ups as an extension to the user interface of the CAS Viewer.

Please take a look and comment/discuss on the proposal.

Regards,
Tong

Re: Cas Viewer discussion

2008-07-24 Thread Tong Fin

Hi Thilo,
Yes, I expect that we will have APIs independent from how we visualize the
information so that tools in different environments (e.g., based on Swing
like CVD or on Eclipse like CAS Viewer) will benefit from that.

We need a discussion on that.

-- Tong

On Thu, Jul 24, 2008 at 2:20 PM, Thilo Goetz [EMAIL PROTECTED] wrote:

 Are you planning to make a general API available so that
 the CVD, for example, could also benefit from this information?

 --Thilo

 Tong Fin wrote:

 According to the previous note on the history of the work here, there is
 some desire to take advantage of the Eclipse plugin packaging of this
 component and reuse it in further Eclipse-based tooling being considered,
 such as debugging tools.


  One of the debugging tools is Provenance Tracking of UIMA CAS
 Content
 http://cwiki.apache.org/UIMA/improving-uima-debug-capabilities.html
 as described in the Wiki.

 The following is the summary of the proposal:

 To improve the ability to debug and maintain UIMA components, we propose
 to
 add the ability to log the updates to the CAS and the Index Repository as
 follows:

   - track which Analysis Engines (AEs) created or modified the feature
   structures in a CA
   - track the operations (add and delete) by each AE to index feature
   structures

 For the user interface part of the tool, I have posted the initial
 proposal
 http://cwiki.apache.org/UIMA/cas-viewer-extension-for-provenance-tracking-of-uima-cas-content.html
 for
 further discussions in our Wiki. This Wiki page includes the screen
 mock-ups as an extension to the user interface of the CAS Viewer.

 Please take a look and comment/discuss on the proposal.

 Regards,
 Tong

Re: [VOTE] [DISCUSS] Accept Cas Viewer Eclipse Plugin for inclusion in the Sandbox

2008-07-07 Thread Tong Fin

Hi Jörn,
Please see my comments in-line below.

- Tong

On Thu, Jul 3, 2008 at 9:09 PM, Jörn Kottmann [EMAIL PROTECTED] wrote:
 We can make a list of Viewer features not in the Editor.

 Yeah that would be great. Please explain the internal requirements so
 that I (as non IBM guy) can understand the motivation behind the features.
 Then I would like to understand why it does not make sense to put
 these features into the Editor (if not clear).


I cannot remember all the details of the requirements.
Most of the requirements and feedbacks that I got so far were implemented
in the CAS Viewer 1-2 years ago. The best way to understand more is to
play around with the CAS Viewer and look at the user guide and
functionality comparison documentation.
The following are some examples of requirements:
 - ability to inspect the CAS by navigating the type system or
 the index repository (e.g., show the annotations of specific types, show
 the feature structures in specific index, etc.)
 - easy to inspect a large type system (a few hundred types)
 - color coding support as other UIMA tools (Annotation Viewer and CVD)
 and the ability to reuse existing style map file
 - multi-sofa support
 - provide APIs to reuse CAS Viewer by other tools (currently used by
 some internal UIMA tools and an IBM product)
 ...

Most of the requests are related to UI. For example, some users require
a quick way to see the feature structures without details (the CAS Viewer
provides a flat or tree structure to support this). The challenge is
to provide a customizable way to show the contents with a few mouse clicks
for different users.

 It could turn out that a good read-write interface is different enough
 from
 a good read-only interface to keep them separate. On the other hand, there
 should be common components that could be used for both. More discussion
 needed.


 Please make a list of the components/parts you want to reuse. I will support
 this.


CAS Viewer and CAS Editor may have different goals and target users.
What I can think right now is, for example, the color coding and some easy way
to support big type system may help. Multi-sofa may have low priority.
One way is to get feedbacks from UIMA users about what are good or missing
with respect to the current functionality. Then, we can work together
to find out
what can be re-used.

- Tong

Re: [VOTE] [DISCUSS] Accept Cas Viewer Eclipse Plugin for inclusion in the Sandbox

2008-07-03 Thread Tong Fin

Hi Jörn,
It is great idea that you can review the CAS Viewer and give the
comments/feedbacks.

I will use the zip file in Jira, will build with a clean Eclipse, and will
post back the steps on how to build. Also, I will post some patch to make it
work in your CAS Editor RCP.

-- Tong

On Thu, Jul 3, 2008 at 11:18 AM, Jörn Kottmann [EMAIL PROTECTED] wrote:

 I will review the Cas Viewer and then tell here what I think we can do.


 Can someone please provide instructions how to build it from the code
 in the sandbox ? If I try to open a CAS file I get a NullPointerException
 and then the eclipse instance is crashing.

 Jörn

Re: [VOTE] [DISCUSS] Accept Cas Viewer Eclipse Plugin for inclusion in the Sandbox

2008-07-03 Thread Tong Fin

Great to know that you can build.
The Cas Viewer assumes that there is a type system file with name ending
withtypesystem.xml in the same folder as the xmi file. Because of that, by
putting a small code to look at the type system folder in your Cas Editor
RCP, it is possible to put the Cas Viewer in your RCP.
I did have this small piece of code. Do you like me to submit that ?

-- Tong

On Thu, Jul 3, 2008 at 11:18 AM, Jörn Kottmann [EMAIL PROTECTED] wrote:

 I will review the Cas Viewer and then tell here what I think we can do.


 Can someone please provide instructions how to build it from the code
 in the sandbox ? If I try to open a CAS file I get a NullPointerException
 and then the eclipse instance is crashing.

 Jörn

[jira] Updated: (UIMA-1102) CAS Viewer submission

2008-07-03 Thread Tong Fin (JIRA)


 [ 
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.

Re: [VOTE] Accept Cas Viewer Eclipse Plugin for inclusion in the Sandbox

2008-07-02 Thread Tong Fin

That's a good idea to have consistent UI across multiple tools.

Also, as someone mentioned before in the mailing list, if we can run CAS
Editor as a plug-in instead of RCP, it will help.

-- Tong

On Wed, Jul 2, 2008 at 2:04 PM, Jörn Kottmann [EMAIL PROTECTED] wrote:

 Hello,

 a huge part of the Cas Editor is dedicated to view a Cas in an editor.
 Actually I think it do not make sense to duplicate this.

 Should we make plans to merge the code and have only one eclipse cas
 viewing
 plugin ? What do others think ?

 Jörn


 On Jul 2, 2008, at 5:28 PM, Marshall Schor wrote:

  Tong Fin has attached the code and documentation for a Cas Viewer Eclipse
 Plugin to a Jira issue http://issues.apache.org/jira/browse/uima-1102

 The documentation includes a table that compares the functionality of this
 with other tooling (see the 4th attachment on the Jira issue).

 A software grant for this code has been received and recorded.

 Please vote as follows:
 [ ] +1  In favor of accepting the submission into the Sandbox.
 [ ] +0  Abstain / No Opinion
 [ ] -0  Have some concerns (please state) but won't block acceptance
 into the Sandbox
 [ ] -1  Have serious issue (please state) that needs resolution before
 proceeding.

 -Marshall

[jira] Updated: (UIMA-1102) CAS Viewer submission

2008-07-02 Thread Tong Fin (JIRA)


 [ 
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

2008-07-01 Thread Tong Fin (JIRA)

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

2008-07-01 Thread Tong Fin (JIRA)


 [ 
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

2008-07-01 Thread Tong Fin (JIRA)


 [ 
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

2008-06-13 Thread Tong Fin (JIRA)

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

2008-06-12 Thread Tong Fin (JIRA)

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

2008-05-16 Thread Tong Fin (JIRA)

[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

2008-05-14 Thread Tong Fin (JIRA)


[ 
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.

Re: [jira] Created: (UIMA-1027) Classes from uima-document-annotator.jar are not in Eclipse plugin

2008-05-12 Thread Tong Fin

If we revisit the following discussion:

http://mail.google.com/mail/?zx=25gscog697fgshva=1#inbox/118aa0b8fb76fb3e
it is a difficult issue to be resolved.

- Tong

On Mon, May 12, 2008 at 10:17 AM, Mikhail Sogrin (JIRA) 
uima-dev@incubator.apache.org wrote:

 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.

Re: Getting Started: Writing my first UIMA annotator

2008-05-07 Thread Tong Fin

Hi Michael,
I read that Getting Started Guide. It is very good !
One thing that is very interesting and helpful is that, when I went through
the tutorial, there is a short explanation about the concept behind each
step and there is a hyper-link to the UIMA documentation.

At the end of the tutorial, the user get a PEAR file. It looks like another
tutorial on how to install and run PEAR with DocumentAnalyzer or CVD will be
interesting (to complete the story).

Very good work!

- Tong


On Wed, May 7, 2008 at 4:00 AM, Michael Baessler [EMAIL PROTECTED]
wrote:

 Michael Baessler wrote:
  Hi,
 
  I just published the first version of the next Getting Started Guide:
 Writing My First UIMA
  Annotator. It is available in the documentation section or directly when
 using the following link:
 
  http://incubator.apache.org/uima/doc-uima-annotator.html
 
  Feel free give some feedback or to improve the guide.
 
  -- Michael

 Does anyone had the chance to look at the getting started guide? I would
 like to post the
 availability on the users list.

 Thanks Michael

[jira] Created: (UIMA-1011) [DDE] When switching backward and forward between C++ and Java top-AE, Custom Settings are not properly handled

2008-04-23 Thread Tong Fin (JIRA)

[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

2008-04-23 Thread Tong Fin (JIRA)


 [ 
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

2008-04-23 Thread Tong Fin (JIRA)


 [ 
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.

1 2 >

1 - 100 of 166 matches

Mail list logo