<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.apache.uima.general">
    <title>gmane.comp.apache.uima.general</title>
    <link>http://blog.gmane.org/gmane.comp.apache.uima.general</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.apache.uima.general/1472"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.apache.uima.general/1471"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.apache.uima.general/1470"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.apache.uima.general/1469"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.apache.uima.general/1468"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.apache.uima.general/1467"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.apache.uima.general/1466"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.apache.uima.general/1465"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.apache.uima.general/1464"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.apache.uima.general/1463"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.apache.uima.general/1462"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.apache.uima.general/1461"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.apache.uima.general/1460"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.apache.uima.general/1459"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.apache.uima.general/1458"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.apache.uima.general/1457"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.apache.uima.general/1456"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.apache.uima.general/1455"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.apache.uima.general/1454"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.apache.uima.general/1453"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.apache.uima.general/1472">
    <title>Re: UimaASProcessCasTimeout exception hangs application</title>
    <link>http://permalink.gmane.org/gmane.comp.apache.uima.general/1472</link>
    <description>I meant that if you used:

runRemoteAsyncAE tcp://localhost:61616 RoomNumberAnnotatorQueue –c
&lt;DIR&gt;FileSystemCollectionReader.xml -p 1 -t 6 -i

then CASes would be sent one at a time (-p 1) and the 6 sec timeout would
never be reached since each CAS takes 5 secs to process.  But with a larger
CAS pool, say -p 3, the -t value would have to be &gt; 3 x 5, say -p 16, to
ensure that the 3rd CAS does not timeout while waiting for the 1st two to
complete.  All this just to avoid errors since as Jerry said there is a bug
in the handling of errors when -i is specified.

Yes, a crash in a service looks just the same as a slow service ... no
result returned in the allotted time.  Timeouts are usually used to prevent
the application from hanging when a service dies, so are often set much
larger than the expected processing time to avoid abandoning those CASes
that take longer than the average.

When your application is an asynchronous aggregate with multiple remote
delegates, you can set queue-specific timeouts in the deployment descriptor,
e.g.

          &lt;remoteAnalysisEngine key="RoomNumber"&gt;
            &lt;inputQueue endpoint="RoomNumberAnnotatorQueue"
brokerURL="tcp://localhost:61616"/&gt;
            &lt;serializer method="xmi"/&gt;
            &lt;asyncAggregateErrorConfiguration&gt;
              &lt;getMetadataErrors maxRetries="0" timeout="60000"
errorAction="disable"/&gt;
              &lt;processCasErrors maxRetries="0" timeout="300000"
continueOnRetryFailure="true" thresholdCount="1" thresholdWindow="0"
thresholdAction="disable"/&gt;
              &lt;collectionProcessCompleteErrors timeout="60000"
additionalErrorAction="terminate"/&gt;
            &lt;/asyncAggregateErrorConfiguration&gt;
          &lt;/remoteAnalysisEngine&gt;

See section 3.10 in the uima_async_scaleout document.  You can use the CDE
in Eclipse to edit deployment descriptors.

- Burn.

On Tue, Oct 7, 2008 at 4:22 PM, Charles Proefrock &lt;chas.pro-PkbjNfxxIARBDgjK7y7TUQ&lt; at &gt;public.gmane.org&gt;wrote:

</description>
    <dc:creator>Burn Lewis</dc:creator>
    <dc:date>2008-10-07T21:36:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.apache.uima.general/1471">
    <title>RE: UimaASProcessCasTimeout exception hangs application</title>
    <link>http://permalink.gmane.org/gmane.comp.apache.uima.general/1471</link>
    <description>I don't have ready access to the test environment, so I'll have to go back and play with the -t value.  It isn't clear if you are saying that a longer timeout "will succeed" in avoiding the hanging problem, or "will succeed" in repeating the problem we've observed.  Clarification on that would help, especially if some min or max timeout avoids the problem.
 
Yes, the queue name should match the name configured in the deploy descriptor.  I think we had a more complex example running and then simplified it before posting, so the queue name documented here was probably just a mistype.
To be a little more specific, we are testing both the natural timeout when a deployed process runs too long, and also the scenario where a deployed process crashes/exits with ^C.  Both seem to generate the same exception when the client timeout occurs, so the nature of the remote failure does not seem to be in play.  This makes sense since the remote is on the other side of a message queue, the client does not see a direct connection dropped on the crash.  It must also mean that the remote is not connected to the anything while it is running, so nothing detects the crash itself.  Confirmation of this understanding would help as well. Are there any options on the message queue (initiation or response queues) that would allow for configuring timeouts for specific named queues?
- Charles
 



_________________________________________________________________
See how Windows Mobile brings your life together—at home, work, or on the go.
http://clk.atdmt.com/MRT/go/msnnkwxp1020093182mrt/direct/01/</description>
    <dc:creator>Charles Proefrock</dc:creator>
    <dc:date>2008-10-07T20:22:40</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.apache.uima.general/1470">
    <title>Re: Imports with '_pear.xml' in aggregate prevent annotators to work on the right Sofa</title>
    <link>http://permalink.gmane.org/gmane.comp.apache.uima.general/1470</link>
    <description>Baptiste,

This issue has been fixed in SVN, and the fix will be in the next release.

https://issues.apache.org/jira/browse/UIMA-1107

-Aaron


Baptiste.GAILLARD-s/S/64wAxt+H1Tvi1vFFB9BPR1lH4CV8&lt; at &gt;public.gmane.org wrote:


</description>
    <dc:creator>Aaron Kaplan</dc:creator>
    <dc:date>2008-10-07T14:53:08</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.apache.uima.general/1469">
    <title>Imports with '_pear.xml' in aggregate prevent annotators to work on the right Sofa</title>
    <link>http://permalink.gmane.org/gmane.comp.apache.uima.general/1469</link>
    <description>Hi, 
 
I have to integrate 2 annotators in 
an aggregate, the first creates a new Sofa and the second work on this created 
Sofa. 
 
My problem is that when I use the 
Annotators descriptors in the imports everything works, but when I specify the 
‘_pear.xml’ descriptors the second annotator continue to work on the ‘DEFAULT’ 
Sofa. 
 
For example with this descriptor my 
second annotator (InfomagicXipFrench) annotates the Sofa ‘txt’ : 

 
&lt;?xml version="1.0" 
encoding="UTF-8"?&gt;
&lt;analysisEngineDescription 
xmlns="http://uima.apache.org/resourceSpecifier"&gt;
  &lt;frameworkImplementation&gt;org.apache.uima.java&lt;/frameworkImplementation&gt;
  
&lt;primitive&gt;false&lt;/primitive&gt;
  
&lt;delegateAnalysisEngineSpecifiers&gt;
    &lt;delegateAnalysisEngine 
key="XmlStripAnnotator"&gt;
      &lt;import 
location="../../XmlStripAnnotator/XmlStripAnnotator_pear.xml"/&gt;
    
&lt;/delegateAnalysisEngine&gt;
    &lt;delegateAnalysisEngine 
key="InfomagicXipFrench"&gt;
      &lt;import 
location="../../InfomagicXipFrench/desc/InfomagicXipFrench.xml"/&gt;
    
&lt;/delegateAnalysisEngine&gt;
  
&lt;/delegateAnalysisEngineSpecifiers&gt;
  
&lt;analysisEngineMetaData&gt;
    
&lt;name&gt;AggregateXeroxIGM&lt;/name&gt;
    
&lt;description/&gt;
    
&lt;version&gt;1.0&lt;/version&gt;
    
&lt;vendor/&gt;
    &lt;configurationParameters 
searchStrategy="language_fallback"/&gt;
    
&lt;configurationParameterSettings/&gt;
    
&lt;flowConstraints&gt;
      
&lt;fixedFlow&gt;
        
&lt;node&gt;XmlStripAnnotator&lt;/node&gt;
        &lt;node&gt;InfomagicXipFrench&lt;/node&gt;
      
&lt;/fixedFlow&gt;
    
&lt;/flowConstraints&gt;
    
&lt;typePriorities/&gt;
    
&lt;fsIndexCollection/&gt;
    
&lt;capabilities&gt;
      
&lt;capability&gt;
        
&lt;inputs/&gt;
        
&lt;outputs/&gt;
        
&lt;outputSofas&gt;
          
&lt;sofaName&gt;txt&lt;/sofaName&gt;
        
&lt;/outputSofas&gt;
        
&lt;languagesSupported/&gt;
      
&lt;/capability&gt;
    
&lt;/capabilities&gt;
    
&lt;operationalProperties&gt;
      
&lt;modifiesCas&gt;true&lt;/modifiesCas&gt;
      
&lt;multipleDeploymentAllowed&gt;false&lt;/multipleDeploymentAllowed&gt;
      
&lt;outputsNewCASes&gt;false&lt;/outputsNewCASes&gt;
    
&lt;/operationalProperties&gt;
  
&lt;/analysisEngineMetaData&gt;
  
&lt;resourceManagerConfiguration/&gt;
  
&lt;sofaMappings&gt;
            
&lt;sofaMapping&gt;
      
&lt;componentKey&gt;XmlStripAnnotator&lt;/componentKey&gt;
      
&lt;componentSofaName&gt;txt&lt;/componentSofaName&gt;
      
&lt;aggregateSofaName&gt;txt&lt;/aggregateSofaName&gt;
    
&lt;/sofaMapping&gt;
    
&lt;sofaMapping&gt;
      
&lt;componentKey&gt;InfomagicXipFrench&lt;/componentKey&gt;
      
&lt;aggregateSofaName&gt;txt&lt;/aggregateSofaName&gt;
    
&lt;/sofaMapping&gt;
  
&lt;/sofaMappings&gt;
&lt;/analysisEngineDescription&gt;
 
But when I use this import : 

&lt;delegateAnalysisEngine 
key="InfomagicXipFrench"&gt;
      &lt;import 
location="../../InfomagicXipFrench/InfomagicXipFrench_pear.xml"/&gt;
    
&lt;/delegateAnalysisEngine&gt;
 
Instead of 

&lt;delegateAnalysisEngine 
key="InfomagicXipFrench"&gt;
      &lt;import 
location="../../InfomagicXipFrench/desc/InfomagicXipFrench.xml"/&gt;
    
&lt;/delegateAnalysisEngine&gt;
 
The annotator works only on the 
‘DEFAULT’ Sofa. 
 
This is very problematic because 
UIMA does not built the correct CLASSPATH when I use the import based on 
“../../InfomagicXipFrench/desc/InfomagicXipFrench.xml”. As I have to integrate 
other annotators (with a lot of JAR dependencies) I must use the ‘_pear.xml’ 
descriptor. 
 
Do you know how can I force my 
annotators to use the right Sofa using ‘_pear.xml’ imports in my aggregate ? 

 
Thanks, 

 
Baptiste 
GAILLARD.
_________________________________________________________________
Installez gratuitement les 20 émôticones Windows Live Messenger les plus fous ! Cliquez ici !
http://www.emoticones-messenger.fr/</description>
    <dc:creator>Baptiste Gaillard</dc:creator>
    <dc:date>2008-10-07T14:32:20</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.apache.uima.general/1468">
    <title>Re: UimaASProcessCasTimeout exception hangs application</title>
    <link>http://permalink.gmane.org/gmane.comp.apache.uima.general/1468</link>
    <description>I also see that the -t process timeout value has to be &gt; 10 for this to
succeed ... I'd have assumed anything &gt; 5 secs would be safe, but the
default value of -p 2 means that the client's timeout must be 2x the service
process time when 2 CASes are in play, since the 2nd is queued immediately
behind the first.  Perhaps the default should be -p 1 for simplicity.

P.S. I assume you meant RoomNumberAnnotatorQueue as the 2nd arg in step 4.

On Tue, Oct 7, 2008 at 9:34 AM, Jaroslaw Cwiklik &lt;cwiklik-r/Jw6+rmf7HQT0dZR+AlfA&lt; at &gt;public.gmane.org&gt; wrote:

</description>
    <dc:creator>Burn Lewis</dc:creator>
    <dc:date>2008-10-07T14:10:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.apache.uima.general/1467">
    <title>Imports with '_pear.xml' in aggregate prevent annotators to work on the right Sofa</title>
    <link>http://permalink.gmane.org/gmane.comp.apache.uima.general/1467</link>
    <description>Hi, 

 

I have to integrate 2 annotators in an aggregate, the first creates a new
Sofa and the second work on this created Sofa. 

 

My problem is that when I use the Annotators descriptors in the imports
everything works, but when I specify the '_pear.xml' descriptors the second
annotator continue to work on the 'DEFAULT' Sofa. 

 

For example with this descriptor my second annotator (InfomagicXipFrench)
annotates the Sofa 'txt' : 

 

&lt;?xml version="1.0" encoding="UTF-8"?&gt;

&lt;analysisEngineDescription xmlns="http://uima.apache.org/resourceSpecifier"&gt;

  &lt;frameworkImplementation&gt;org.apache.uima.java&lt;/frameworkImplementation&gt;

  &lt;primitive&gt;false&lt;/primitive&gt;

  &lt;delegateAnalysisEngineSpecifiers&gt;

    &lt;delegateAnalysisEngine key="XmlStripAnnotator"&gt;

      &lt;import
location="../../XmlStripAnnotator/XmlStripAnnotator_pear.xml"/&gt;

    &lt;/delegateAnalysisEngine&gt;

    &lt;delegateAnalysisEngine key="InfomagicXipFrench"&gt;

      &lt;import
location="../../InfomagicXipFrench/desc/InfomagicXipFrench.xml"/&gt;

    &lt;/delegateAnalysisEngine&gt;

  &lt;/delegateAnalysisEngineSpecifiers&gt;

  &lt;analysisEngineMetaData&gt;

    &lt;name&gt;AggregateXeroxIGM&lt;/name&gt;

    &lt;description/&gt;

    &lt;version&gt;1.0&lt;/version&gt;

    &lt;vendor/&gt;

    &lt;configurationParameters searchStrategy="language_fallback"/&gt;

    &lt;configurationParameterSettings/&gt;

    &lt;flowConstraints&gt;

      &lt;fixedFlow&gt;

        &lt;node&gt;XmlStripAnnotator&lt;/node&gt;

        &lt;node&gt;InfomagicXipFrench&lt;/node&gt;

      &lt;/fixedFlow&gt;

    &lt;/flowConstraints&gt;

    &lt;typePriorities/&gt;

    &lt;fsIndexCollection/&gt;

    &lt;capabilities&gt;

      &lt;capability&gt;

        &lt;inputs/&gt;

        &lt;outputs/&gt;

        &lt;outputSofas&gt;

          &lt;sofaName&gt;txt&lt;/sofaName&gt;

        &lt;/outputSofas&gt;

        &lt;languagesSupported/&gt;

      &lt;/capability&gt;

    &lt;/capabilities&gt;

    &lt;operationalProperties&gt;

      &lt;modifiesCas&gt;true&lt;/modifiesCas&gt;

      &lt;multipleDeploymentAllowed&gt;false&lt;/multipleDeploymentAllowed&gt;

      &lt;outputsNewCASes&gt;false&lt;/outputsNewCASes&gt;

    &lt;/operationalProperties&gt;

  &lt;/analysisEngineMetaData&gt;

  &lt;resourceManagerConfiguration/&gt;

  &lt;sofaMappings&gt;

            &lt;sofaMapping&gt;

      &lt;componentKey&gt;XmlStripAnnotator&lt;/componentKey&gt;

      &lt;componentSofaName&gt;txt&lt;/componentSofaName&gt;

      &lt;aggregateSofaName&gt;txt&lt;/aggregateSofaName&gt;

    &lt;/sofaMapping&gt;

    &lt;sofaMapping&gt;

      &lt;componentKey&gt;InfomagicXipFrench&lt;/componentKey&gt;

      &lt;aggregateSofaName&gt;txt&lt;/aggregateSofaName&gt;

    &lt;/sofaMapping&gt;

  &lt;/sofaMappings&gt;

&lt;/analysisEngineDescription&gt;

 

But when I use this import : 

&lt;delegateAnalysisEngine key="InfomagicXipFrench"&gt;

      &lt;import
location="../../InfomagicXipFrench/InfomagicXipFrench_pear.xml"/&gt;

    &lt;/delegateAnalysisEngine&gt;

 

Instead of 

&lt;delegateAnalysisEngine key="InfomagicXipFrench"&gt;

      &lt;import
location="../../InfomagicXipFrench/desc/InfomagicXipFrench.xml"/&gt;

    &lt;/delegateAnalysisEngine&gt;

 

The annotator works only on the 'DEFAULT' Sofa. 

 

This is very problematic because UIMA does not built the correct CLASSPATH
when I use the import based on
"../../InfomagicXipFrench/desc/InfomagicXipFrench.xml". As I have to
integrate other annotators (with a lot of JAR dependencies) I must use the
'_pear.xml' descriptor. 

 

Do you know how can I force my annotators to use the right Sofa using
'_pear.xml' imports in my aggregate ? 

 

Thanks, 

 

Baptiste GAILLARD.

 

</description>
    <dc:creator>Baptiste.GAILLARD-s/S/64wAxt+H1Tvi1vFFB9BPR1lH4CV8&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2008-10-07T13:42:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.apache.uima.general/1466">
    <title>Re: UimaASProcessCasTimeout exception hangs application</title>
    <link>http://permalink.gmane.org/gmane.comp.apache.uima.general/1466</link>
    <description/>
    <dc:creator>Jaroslaw Cwiklik</dc:creator>
    <dc:date>2008-10-07T13:34:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.apache.uima.general/1465">
    <title>VNS Server with private IP</title>
    <link>http://permalink.gmane.org/gmane.comp.apache.uima.general/1465</link>
    <description>Hi,

I just came across an issue while setting up a VINCI Service on a server
that doesn't have a public IP.

The server that host the Vinci Service is accesible through a public IP, but
doesn't actually know it. (Load Balancer)

Here is the scheme of the process.

The CPE call the VNS Host through a public IP

CPE ---------- Internet ------- Load Balancer --------&gt; VNS Server (
192.168.0.1:9000)

For now everything is ok.

The VNS Server then send to the CPE the IP and Port of the service that the
CPE wanted to call.

CPE &lt;---------- Internet ------- Load Balancer -------- VNS Server

The the CPE try to call the service via 192.168.0.1:10000 but this IP is not
reachable from internet.

I tried to get around this by setting up the variable VNS_HOST to the domain
that linked to the public IP, but it didn't worked.
The VNS Server still convert the domain into an IP.

I also tried to set the VNS_HOST to the public IP, but their is a security
feature on Load balancers that you can not call yourself with the public IP
within the private network.
So the service wasn't able to connect to the VNS Server.

So my question is, is anybody encountered that same issue ?

Is their anything that I can do to get around this ?

Thanks for your help.

Regards.
</description>
    <dc:creator>Nassim Jammal</dc:creator>
    <dc:date>2008-10-07T09:02:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.apache.uima.general/1464">
    <title>UimaASProcessCasTimeout exception hangs application</title>
    <link>http://permalink.gmane.org/gmane.comp.apache.uima.general/1464</link>
    <description>

When experimenting with the UIMA-AS examples and how the error handling mechanisms work in terms of timeouts due to AS Aggregates taking too long or going offline, we came across a situation in which the RunRemoteAsyncAE hangs and never returns after receiving and processing a UimaASProcessCasTimeout exception.  Ultimately, we simply want the system to recover and try the next CAS or return gracefully without having to call a hard System.exit(1).
 
Our tests are based on the Deploy_MeetingDetectorTAE_RemoteRoomNumber.xml example.  All we did was the following:
(1)   added “Thread.sleep(5000);” to RoomNumberAnnotator.java process to simulate  a longer process.
(2)   Executed: startBroker.bat
(3)   Executed: deployAsyncService &lt;DIR&gt;\Deploy_RoomNumberAnnotator.xml
(4)   Executed: runRemoteAsyncAE tcp://localhost:61616 MeetingDetectorTaeQueue –c &lt;DIR&gt;\FileSystemCollectionReader.xml -t 4 -i
 
In summary: when setting and triggering the time outs on the RoomNumber remoteAnalysisEngine, the exception is thrown and caught, each additional CAS is tried, and the system exists gracefully.  If the UimaAsynchronousEngine within the runRemoteAsyncAE times out, then the system hangs and never returns. 
 
Is there a trick that we’re missing? Is this expected?
 
- Charles
 
 
_________________________________________________________________
See how Windows Mobile brings your life together—at home, work, or on the go.
http://clk.atdmt.com/MRT/go/msnnkwxp1020093182mrt/direct/01/</description>
    <dc:creator>Charles Proefrock</dc:creator>
    <dc:date>2008-10-06T21:59:47</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.apache.uima.general/1463">
    <title>Re: Order of CASes after multiplier</title>
    <link>http://permalink.gmane.org/gmane.comp.apache.uima.general/1463</link>
    <description>Hi Aaron,

Yes, for a synchronous UIMA aggregate the parent CAS is released only after
all its children are released.

When deployed asynchronously in UIMA AS, the parent CAS is released from the
CM when hasNext returns false, and is then available to be routed. If the
parent CAS comes into an async aggregate on a process call (that it, it is
not itself generated by a CM inside), it will not be returned until all of
its children CAS have been released; this allows an error on a child CAS to
[optionally] generate an error on its parent CAS.

Eddie

On Thu, Oct 2, 2008 at 3:48 PM, Aaron Kaplan &lt;aaron.kaplan-axt8Ybl0NPViK979QBapAg&lt; at &gt;public.gmane.org&gt;wrote:

</description>
    <dc:creator>Eddie Epstein</dc:creator>
    <dc:date>2008-10-02T22:38:12</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.apache.uima.general/1462">
    <title>Order of CASes after multiplier</title>
    <link>http://permalink.gmane.org/gmane.comp.apache.uima.general/1462</link>
    <description>I can't find this documented anywhere, but I observe empirically that
components downstream of a CAS multiplier receive all of the new CASes
generated by that multiplier before receiving the original CAS that was
the input to the multiplier.  Can I rely on that order?

-Aaron

</description>
    <dc:creator>Aaron Kaplan</dc:creator>
    <dc:date>2008-10-02T19:48:33</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.apache.uima.general/1461">
    <title>Re: [UIMA] How to remove a feature structure from a CAS</title>
    <link>http://permalink.gmane.org/gmane.comp.apache.uima.general/1461</link>
    <description>
True.  If you have a potentially long-running interactive
application, you need to consider that issue.  What you
can do is once in a while copy your current content into
a clean CAS, using the CasCopier.  Kinda clumsy...


You have to call addToIndexes().  After that, it's both
on the annotation and the default bag index.


</description>
    <dc:creator>Thilo Goetz</dc:creator>
    <dc:date>2008-10-02T14:14:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.apache.uima.general/1460">
    <title>Re: [UIMA] How to remove a feature structure from a CAS</title>
    <link>http://permalink.gmane.org/gmane.comp.apache.uima.general/1460</link>
    <description>Thanks again,
if I understand well, the best we can do is to prevent the feature structure
from being saved. I think I cannot use this strategy since it can leak
memory (until one saves and reload).
A little question again, after I create a FS, is it added to the default
unnamed bag index? (or I have to add it manually)

Manuel Fiorelli
</description>
    <dc:creator>Manuel Fiorelli</dc:creator>
    <dc:date>2008-10-02T13:11:59</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.apache.uima.general/1459">
    <title>Re: [UIMA] How to remove a feature structure from a CAS</title>
    <link>http://permalink.gmane.org/gmane.comp.apache.uima.general/1459</link>
    <description>
Sort of.  You can remove the annotation from the index.  The
annotation will continue to exist for the lifetime of the
CAS, but it will no longer be accessible.  If you then save
the CAS to disk, the deleted annotation will not be saved.

If you use the JCas, you can do removeFromIndexes() on the
annotation itself.  If using the base CAS, you need to use
cas.removeFsFromIndexes(annotation) -- of course this will
work with the JCas as well.

--Thilo

</description>
    <dc:creator>Thilo Goetz</dc:creator>
    <dc:date>2008-10-02T13:01:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.apache.uima.general/1458">
    <title>[UIMA] How to remove a feature structure from a CAS</title>
    <link>http://permalink.gmane.org/gmane.comp.apache.uima.general/1458</link>
    <description>Hello,
I am developing an interactive annotator, which should produce a corpus of
annotated documents for AE training. Since a human annotator can decide to
remove an annotation, I would like to know if there were an API for remove a
feature structure from the CAS after it was created.

Manuel Fiorelli
</description>
    <dc:creator>Manuel Fiorelli</dc:creator>
    <dc:date>2008-10-02T12:51:37</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.apache.uima.general/1457">
    <title>Re: [UIMA] Annotated corpus</title>
    <link>http://permalink.gmane.org/gmane.comp.apache.uima.general/1457</link>
    <description>Thank you for the answer. Since I am new to UIMA, I wanted to verify that
there isn't a better solution.

Manuel Fiorelli
</description>
    <dc:creator>Manuel Fiorelli</dc:creator>
    <dc:date>2008-10-02T12:26:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.apache.uima.general/1456">
    <title>Re: [UIMA] Annotated corpus</title>
    <link>http://permalink.gmane.org/gmane.comp.apache.uima.general/1456</link>
    <description>Hi Manuel,

how about storing the individual documents in XCAS or XMI
format?  That's probably the simplest and best supported
way, though not very compact.

--Thilo

Manuel Fiorelli wrote:

</description>
    <dc:creator>Thilo Goetz</dc:creator>
    <dc:date>2008-10-02T12:03:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.apache.uima.general/1455">
    <title>CFP open for ApacheCon Europe 2009</title>
    <link>http://permalink.gmane.org/gmane.comp.apache.uima.general/1455</link>
    <description>If you only have thirty seconds:

The Call for Papers for ApacheCon Europe 2009, to be held in
Amsterdam, from 23rd to 27th March, is now open! Submit your proposals
at http://eu.apachecon.com/c/aceu2009/cfp/ before 24th October.

Remember that early bird prices for ApacheCon US 2008, to be held in
New Orleans, from 3rd to 7th November, will go up this Friday, at
midnight Eastern time!

Sponsorship opportunities for ApacheCon US 2008 and ApacheCon EU 2009
are still available. If you or your company are interested in becoming
a sponsor, please contact Delia Frees at delia-tNYnu+yeWK6aMJb+Lgu22Q&lt; at &gt;public.gmane.org for
details.

*******

If you want all the details:

ApacheCon Europe 2009 - Leading the Wave of Open Source
Amsterdam, The Netherlands
23rd to 27th March, 2009

Call for Papers Opens for ApacheCon Europe 2009

The Apache Software Foundation (ASF) invites submissions to its
official conference, ApacheCon Europe 2009. To be held 23rd to 27th
March, 2009 at the Mövenpick Hotel Amsterdam City Centre, ApacheCon
serves as a forum for showcasing the ASF's latest developments,
including its projects, membership, and community. ApacheCon offers
unparalleled educational opportunities, with dedicated presentations,
hands-on trainings, and sessions that address core technology,
development, business/marketing, and licensing issues in Open Source.

ApacheCon's wide range of activities are designed to promote the
exchange of ideas amongst ASF Members, innovators, developers,
vendors, and users interested in the future of Open Source technology.
The conference program includes competitively selected presentations,
trainings/workshops, and a small number of invited speakers. All
sessions undergo a peer review process by the ApacheCon Conference
Planning team. The following information provides presentation
category descriptions, and information about how to submit your
proposal.

Conference Themes and Topics

APACHECON 2009 - LEADING THE WAVE OF OPEN SOURCE

Building on the success of the last two years, we are excited to
return to Amsterdam in 2009. We'll be continuing to offer our very
popular two-day trainings, including certifications of completion for
those who fulfill all the requirements of these trainings.

The ASF comprises some of the most active and recognized developers in
the Open Source community. By bringing together the pioneers,
developers, and users of flagship Open Source technologies, ApacheCon
provides an influential platform for dialogue, between the speaker and
the audience, between project contributors and the community at large,
traversing a wide range of ideas, expertise, and personalities.

ApacheCon welcomes submissions from like-minded delegates across many
fields, geographic locations, and areas of development. The breadth
and loosely-structured nature of the Apache community lends itself to
conference content that is also somewhat loosely-structured. Common
themes of interest address groundbreaking technologies and emerging
trends, successful practices (from development to deployment), and
lessons learned (tips, tools, and tricks). In addition to technical
content, ApacheCon invites Business Track submissions that address
Open Source business, marketing, and legal/licensing issues.

Topics appropriate for submission to this conference are manifold, and
may include but are not restricted to:

- Apache HTTP server topics such as installation, configuration, and migration
- ASF-wide projects such as Lucene, SpamAssassin, Jackrabbit, and Maven
- Scripting languages and dynamic content such as Java, Perl, Python,
Ruby, XSL, and PHP
- Security and e-commerce
- Performance tuning, load balancing and high availability
- New technologies and broader initiatives such as Web Services and Web 2.0
- ASF-Incubated projects such as Sling, UIMA, and Shindig


Submission Guidelines
Submissions must include
- Title
- Speaker name, with affiliation and email address
- Speaker bio (100 words or less)
- Short description (50 words or less)
- Full description including abstract and objectives (200 words or
less)
- Expertise level (beginner to advanced)
- Format and duration (trainings vs. general presentation; half-,
full- or two-day workshop, etc.)
- Intended audience and maximum number of participants (trainings only)
- Background knowledge expected of the participants (trainings only)


Types of Presentations

- Trainings/Workshops
- General Sessions
- Case Studies/Industry Profiles
- Invited Keynotes/Panels/Speakers
- Corporate Showcases &amp; Demonstrations

BoF sessions and Fast Feather Track talks will be selected separately

Pre Conference Trainings/Workshops
Held on the first and second day of the conference – 2008-03-23 and
2008-03-24, Trainings require a registration fee beyond the regular
conference fee. Proposals may be submitted for half-day (3 hours),
full-day (6 hours), or two-day (12 hours) training sessions, aimed at
providing in-depth, hands-on development experience or related
continuing education. Training submissions are welcome at beginner,
intermediate, and expert levels.

General Sessions
General Sessions include presentations on practical development
applications, insight into high-interest projects, best practices and
key advances, overcoming implementation challenges, and industry
innovations. Especially welcome are submissions that extend
participants' understanding the role of ASF projects and their
influence on the Open Source community at large. General Sessions are
scheduled for 50 minutes and are accessible to all conference
delegates.

Case Study/Industry Profile
Practitioners are invited to submit presentations that focus on how
implementing particular ASF technologies led to improved
products/solutions, service offerings, changes in work practices,
among other successes. Proposals that highlight overcoming interesting
challenges in application design and developing innovative frameworks
using multiple ASF projects are particularly encouraged. NOTE:
Marketing-oriented submissions aimed at promoting specific
organizations or products will not be accepted.

Invited Keynotes/Panels/Speakers
Each conference the ApacheCon Planning team invites select presenters
dealing with engaging, dialectical, and challenging subjects to
present in keynote and/or panel formats. Topics include cutting-edge
technology development, industry leadership, hot or emerging trends,
opinions on controversial issues, insight on technology paradigms, and
contrasting viewpoints in complementary professional areas. Those
interested in suggesting a candidate for an invited speaker
opportunity should submit a brief proposal with the speaker's name,
affiliation, background/bio, overview of topics of interest, and
contact information.

Important Dates
Please submit your completed proposal, at
http://eu.apachecon.com/c/aceu2009/cfp/ before Friday, 24th October,
2008 Midnight GMT.

About ApacheCon 2009
ApacheCon is co-produced by the Apache Software Foundation and Stone
Circle Productions. The ApacheCon Planning team comprises ASF Members
from all over the world working on a wholly-volunteer basis. For more
information, visit
http://eu.apachecon.com/c/aceu2009/

</description>
    <dc:creator>Thilo Goetz</dc:creator>
    <dc:date>2008-10-02T11:57:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.apache.uima.general/1454">
    <title>[UIMA] Annotated corpus</title>
    <link>http://permalink.gmane.org/gmane.comp.apache.uima.general/1454</link>
    <description>Hi,
I know that the UIMA architecture provides the CAS (common analysis system)
to share analysis data about a single artifact. Is there a standard way to
store an annotated corpus, which could be used, for example, to train an AE?

Regards,
Manuel Fiorelli
</description>
    <dc:creator>Manuel Fiorelli</dc:creator>
    <dc:date>2008-09-29T19:06:50</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.apache.uima.general/1453">
    <title>FYI: New UIMA Development Environment available on Alphaworks -- LanguageWare Resource Workbench</title>
    <link>http://permalink.gmane.org/gmane.comp.apache.uima.general/1453</link>
    <description>
Hello all,

My apologies for the wide broadcast, however I wanted to let everyone know
of a new development environment that is now available on Alphaworks. It is
an Eclipse Workbench that allows you to create UIMA Annotators without
writing a line of code (for the lazy folks like me that don't want to
bother ;-)  We have also uploaded a Demonstrator that contains a lot of
dictionaries, rules, UIMA pipelines, etc. that you can use to bootstrap
your development process, and some instructional videos to get you
up-and-running.

I would love to hear your feedback and hopefully it may prove to be useful
for some of you.

Below is the announcement:


   This week, the IBM® LanguageWare®  team announces the availability of an
   innovative LanguageWare NLP development environment, the "IBM
   LanguageWare Resource Workbench". This Workbench, which will be
   delivered with a Demonstrator that contains a comprehensive set of
   language and domain models across English, Spanish, Portuguese, German,
   Arabic, and Japanese, brings a new and exciting way of building
   high-performance text analysis applications to the market, using
   LanguageWare's unique example-based visualization techniques and
   patented parsing technology. The Demonstrator gives customers a
   pre-built set of analyzers - spanning healthcare, law enforcement,
   finance, legal, and pharma domains - on which they can build their own
   LanguageWare UIMA Analyzers. Also provided is a set of instructional
   videos to help get customers up-and-running.

   All this is now available at no charge for evaluation and prototyping
   purposes, under the terms and conditions of the IBM International
   License Agreement for Early Release of Programs, on IBM alphaWorks at:
   http://alphaworks.ibm.com/tech/lrw.

   LanguageWare now also provides Domain Modelling and Integration Services
   to help IBM's customers and partners successfully exploit LanguageWare's
   text analysis capabilities. IBM LanguageWare consultants are ready to
   work with customers to develop the necessary domain extraction models
   specifically tailored to their business requirements, and provide
   integration support for IBM products, including IBM Content Analyzer,
   IBM Entity Analytics, IBM Global Name Recognition, IBM Lotus®
   Connections, IBM Lotus Notes®, IBM OmniFind, IBM InfoSphere Warehouse,
   and others.

   IBM, LanguageWare, Lotus, and Lotus Notes are registered trademarks of
   International Business Machines Corporation in the United States, other
   countries, or both.

   InfoSphere and OmniFind are trademarks of International Business
   Machines Corporation in the United States, other countries, or both.

   Other company, product, or service names may be trademarks or service
   marks of others.

Regards,
Marie
-------------------
Marie Wallace
Senior Manager, IBM LanguageWare
Office: +353-1-815-3687 (Tieline: 7513687)
Mobile: +353-86-3805-482
E-mail: marie.wallace-g5DgMFWsQ8jQT0dZR+AlfA&lt; at &gt;public.gmane.org

... our internal blog:
http://blogs.tap.ibm.com/weblogs/page/mwallace-g5DgMFWsQ8jQT0dZR+AlfA&lt; at &gt;public.gmane.org
... our internal website: http://w3-03.ibm.com/globalization/page/2504
... our external website:
http://www-306.ibm.com/software/globalization/topics/languageware/index.jsp
... our Alphaworks: http://www.alphaworks.ibm.com/tech/lrw
... our Wikipedia: http://en.wikipedia.org/wiki/Languageware

"IBM Ireland Product Distribution Limited registered in Ireland with number
92815.  Registered office: Oldbrook House, 24-32 Pembroke Road,
Ballsbridge, Dublin 4".


</description>
    <dc:creator>Marie Wallace</dc:creator>
    <dc:date>2008-09-29T12:47:43</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.apache.uima.general/1452">
    <title>Re: image support on uima</title>
    <link>http://permalink.gmane.org/gmane.comp.apache.uima.general/1452</link>
    <description>Hi,

UIMA has the following features that support analyzing large volumes of
image data:

1. The UIMA framework provides a standardized framework for analysis code
written
    in Java, C++ and several scripting languages.
2. The framework includes a common analysis structure, the CAS, which is
used
    to share information between different analysis components. The most
common
    application scenario is to initialize a CAS with an artifact, like an
image, text string,
    segment of audio, etc, and then pass the CAS to a series of components
    which use the artifact and/or the previous results for further analysis.
3. The UIMA flow controller component allows complex, user defined routing
of the
    CAS between components.
4. Given a set of UIMA compliant components, UIMA has mechanisms to scale
out
    the number of each component on one or more machines to cooperatively
process
    a large number of artifacts. UIMA scale out is also useful for creating
real-time
    services.

There are some available UIMA components that would be useful in searching
the results
of your analysis, see for example "Semantic Search for Apache UIMA" on
http://www.alphaworks.ibm.com/tech/uima/download.

Eddie


On Fri, Sep 26, 2008 at 10:32 AM, rohan singh &lt;rohansingh238-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt;wrote:

</description>
    <dc:creator>Eddie Epstein</dc:creator>
    <dc:date>2008-09-26T21:20:37</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.apache.uima.general">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.apache.uima.general</link>
  </textinput>
</rdf:RDF>
