headers
Marvin | 1 Jan 2010 15:00
Picon
Favicon

uima-dev@...>)

Dear UIMA Developers,

This email was sent by an automated system on behalf of the Apache Incubator PMC.
It is an initial reminder to give you plenty of time to prepare your quarterly
board report.

The board meeting is scheduled for  Wed, 20 January 2010, 2 pm Pacific. The report 
for your podling will form a part of the Incubator PMC report. The Incubator PMC 
requires your report to be submitted one week before the board meeting, to allow 
sufficient time for review.

Please submit your report with sufficient time to allow the incubator PMC, and 
subsequently board members to review and digest. Again, the very latest you 
should submit your report is one week prior to the board meeting.

Thanks,

The Apache Incubator PMC

Submitting your Report
----------------------

Your report should contain the following:

 * Your project name
 * A brief description of your project, which assumes no knowledge of the project
   or necessarily of its field
 * A list of the three most important issues to address in the move towards 
   graduation.
 * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of
(Continue reading)

Permalink | Reply | 7 comments |
headers
Marshall Schor | 4 Jan 2010 20:00

digging into an issue with the Component Discriptor Editor (CDE) and RC8 with UIMA-AS components

A user has reported a CDE failure when editing a aggregate descriptor
that contains references to remote uima-as services.

The CDE attempts to acquire the remote services "metadata" to merge type
system information, and fails, because of a ClassCastException:

org.apache.activemq.ActiveMQConnectionFactory cannot be cast to
javax.jms.ConnectionFactory

In looking into this, I've come across the project:

    uimaj-as-osgi-runtime

and need to understand this project better.  I think it was added to
support the camel sandbox project.

This project is set up in its POM with a parent pom which is the common
superPom for all eclipse plugins. 

It's also put into the Eclipse plugin directory by the uima-as-distr
maven install step.

However, it is not included in the Eclipse update site building, and is
not part of any Uima Eclipse Feature.

So - first question: is this supposed to be an eclipse plugin? 

2nd question: does it need to be added to any "feature" set? if so,
which one?
(Continue reading)

Permalink | Reply | 2 comments |
headers
Marshall Schor | 5 Jan 2010 05:18

Re: digging into an issue with the Component Discriptor Editor (CDE) and RC8 with UIMA-AS components

More digging.  The previous post is a tangent to the real issue, but I
still want to learn if we're missing something with the osgi packaging
for uima-as.

Back to the original problem.  Instrumenting things shows that:

-

- the CDE is making lots of instances of ResourceManager -
classloaders.  The javadoc comment in fact says to make a new one
anytime one is needed in the CDE, to pick up any changes the user might
have made to the project's class path.  The use case comes from the
following kind of sequence:

user is trying to add an import of a delegate by name, and discovers
they forgot to add it to the class path; they fix the project build
path, and try to add it again (this time should work).

- The uima resources that are loaded via the Resource manager are loaded
with a class loader that does not first delegate.  Therefore, one should
not have things in the UIMA classpath which are core uima classes.  The
classpath loader builder in the CDE in fact filters the core uima
framework classes it uses, out of the classpath it builds.  But this
filter doesn't work for "custom resource specifiers" - which can be any
user defined class.

- The uima-as design for supporting uima-as services as remote delegates
makes use of these custom resource specifiers.  If we filtered these
out, then custom resource specifiers would generate a class-not-found
exception.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marshall Schor (JIRA | 5 Jan 2010 16:22
Picon
Favicon

[jira] Created: (UIMA-1713) Java and UIMA things holding on to objects loaded via Resource Manager fail when switching to another Resource Manager class loader instance

Java and UIMA things holding on to objects loaded via Resource Manager fail when switching to another
Resource Manager class loader instance
--------------------------------------------------------------------------------------------------------------------------------------------

                 Key: UIMA-1713
                 URL: https://issues.apache.org/jira/browse/UIMA-1713
             Project: UIMA
          Issue Type: Bug
          Components: Async Scaleout
    Affects Versions: 2.3AS
            Reporter: Marshall Schor
            Assignee: Jerry Cwiklik
            Priority: Blocker

JNDI and JMX both use "system-wide" "registries" of objects.  These objects, for uima-as, can be loaded
from a Resource Manager in cases where the uima-as classes are on the Resource Manager's classpath.  A use
case where this can occur is a UIMA aggregate containg 2 PEAR descriptors, each having a potentially
different version of uima-as in the PEAR's classpath, being used as a client to a remote uima-as service. 
(Note that the uima-as client for this is represented in UIMA as a "custom resource specifier", so this use
case can also apply to future "custom resources".)

The system-wide registries for JNDI and JMX use a string handle to locate objects, and cache found objects
in the registry.  The first use loads the object, using the class loader in effect at the place where the
lookup is requested.  For uima-as being used as a custom resource, the class loader used is the UIMA class
loader associated with the current resource manager.

If, subsequently, another resource manager instance (actually, another class loader instance within
the UIMA resource manager) is used to run the uima-as classes, the lookups by name for objects in these
registries will succeed, but will return objects that were loaded under a different class loader.  This
causes ClassCastExceptions, because the superclasses / interfaces used in the currently running code
(Continue reading)

Permalink | Reply | 1 comment |
headers
Marshall Schor (JIRA | 5 Jan 2010 16:26
Picon
Favicon

[jira] Created: (UIMA-1714) Message Bundles not visible when loaded under a UIMA Resource Manager class loader

Message Bundles not visible when loaded under a UIMA Resource Manager class loader
----------------------------------------------------------------------------------

                 Key: UIMA-1714
                 URL: https://issues.apache.org/jira/browse/UIMA-1714
             Project: UIMA
          Issue Type: Bug
          Components: Core Java Framework
            Reporter: Marshall Schor

UIMA-AS has message bundles.  When uima-as classes are loaded under a resource manager class loader, the
message bundle is not visible when logging occurs.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Permalink | Reply | 3 comments |
headers
Christoph Buescher (JIRA | 5 Jan 2010 16:38
Picon
Favicon

[jira] Commented: (UIMA-1707) String features in out-of-typesystem data not normalized on service replies


    [
https://issues.apache.org/jira/browse/UIMA-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796706#action_12796706
] 

Christoph Buescher commented on UIMA-1707:
------------------------------------------

Great. We were able to verify that your fix is working with for our test cases. Many thanks. Looking forward
to the offical UIMA 2.3. Release.

> String features in out-of-typesystem data not normalized on service replies
> ---------------------------------------------------------------------------
>
>                 Key: UIMA-1707
>                 URL: https://issues.apache.org/jira/browse/UIMA-1707
>             Project: UIMA
>          Issue Type: Bug
>          Components: C++ Framework
>    Affects Versions: 2.2.2
>            Reporter: Eddie Epstein
>            Assignee: Eddie Epstein
>             Fix For: 2.3C
>
>
> Christoph Büscher  to uima-user
> I currently encountered a problem with the XMI deserialization of a feature structure after calling a
remote C++ AS annotator from a CPE. The szenario is the following:
> 1. I add a custom feature structure "DocumentData" containing an String Feature (the document URL) to the
CAS in my CPE. The exact URL causing the problem is:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marshall Schor (JIRA | 5 Jan 2010 17:12
Picon
Favicon

[jira] Created: (UIMA-1715) uima-as client design contract for insuring proper cleanup not supported by core UIMA

uima-as client design contract for insuring proper cleanup not supported by core UIMA
-------------------------------------------------------------------------------------

                 Key: UIMA-1715
                 URL: https://issues.apache.org/jira/browse/UIMA-1715
             Project: UIMA
          Issue Type: Bug
          Components: Async Scaleout
    Affects Versions: 2.3AS
            Reporter: Marshall Schor
            Assignee: Jerry Cwiklik

The uima-as jms client design contract is to call "stop" after a call to "initialize", in order to clean up
sockets, etc.  However, base uima code has methods that call initialize just get client metadata, e.g., 
CasCreationUtilities.getMetaDataList, which are general purpose and are supposed to work for any
analysis engine resource.

I think the jms client should figure out how to clean up after itself.  Using finalize for this is not a good
idea, for the standard reasons (see end of article
http://java.sun.com/developer/technicalArticles/javase/finalization/ ).  Perhaps we need to call
destroy after the call to produceResource, and insure that destroy is implemented by
JmsAnalysisEngineServiceAdapter (and others) to release/cleanup

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Permalink | Reply | 2 comments |
headers
Marshall Schor (JIRA | 5 Jan 2010 17:40
Picon
Favicon

[jira] Resolved: (UIMA-1715) uima-as client design contract for insuring proper cleanup not supported by core UIMA


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

Marshall Schor resolved UIMA-1715.
----------------------------------

    Resolution: Invalid

I think this is invalid - reading the code for CasCreationUtils shows that if produceResource is called,
then destroy() is later called (except if an exception occurred - but in that case we have no resource to
call destroy on, anyways).

> uima-as client design contract for insuring proper cleanup not supported by core UIMA
> -------------------------------------------------------------------------------------
>
>                 Key: UIMA-1715
>                 URL: https://issues.apache.org/jira/browse/UIMA-1715
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>    Affects Versions: 2.3AS
>            Reporter: Marshall Schor
>            Assignee: Jerry Cwiklik
>
> The uima-as jms client design contract is to call "stop" after a call to "initialize", in order to clean up
sockets, etc.  However, base uima code has methods that call initialize just get client metadata, e.g., 
CasCreationUtilities.getMetaDataList, which are general purpose and are supposed to work for any
analysis engine resource.
> I think the jms client should figure out how to clean up after itself.  Using finalize for this is not a good
(Continue reading)

Permalink | Reply | 0 comments |
headers
Richard Eckart de Castilho (JIRA | 5 Jan 2010 17:44
Picon
Favicon

[jira] Created: (UIMA-1716) UIMA Sandbox components in tag 2.2.2 are 2.3.0-SNAPSHOT

UIMA Sandbox components in tag 2.2.2 are 2.3.0-SNAPSHOT
-------------------------------------------------------

                 Key: UIMA-1716
                 URL: https://issues.apache.org/jira/browse/UIMA-1716
             Project: UIMA
          Issue Type: Bug
          Components: Sandbox
    Affects Versions: 2.2.2
            Reporter: Richard Eckart de Castilho

All the POMs in the UIMA Sandbox tag 2.2.2-incubating claim that they are 2.3.0-incubating-SNAPSHOT. I
know that tags should not be changed, but I would still vote for fixing those versions and also have them
depend on UIMA 2.2.2-incubating if possible. Obviously Marshall Schor has changed this after the
tagging as part of UIMA-1461 in revision 798670, which unfortunately lacks any explanation.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Permalink | Reply | 6 comments |
headers
Richard Eckart de Castilho (JIRA | 5 Jan 2010 17:58
Picon
Favicon

[jira] Created: (UIMA-1717) Use Apache Hudson and Nexus repository facilities

Use Apache Hudson and Nexus repository facilities
-------------------------------------------------

                 Key: UIMA-1717
                 URL: https://issues.apache.org/jira/browse/UIMA-1717
             Project: UIMA
          Issue Type: Bug
            Reporter: Richard Eckart de Castilho

The ASF seems to provide a continuous integration facility (c.f.
http://wiki.apache.org/general/Hudson), as well as a Nexus Maven artifact repository (c.f.
http://wiki.apache.org/portals/FrontPage/HowtoUseNexusForRelease). It would be great if UIMA
would make use of these facilities, allowing for better testing as well as access to fresh snapshot
artifacts. It would hopefully also facilitate things for people compiling UIMA or the UIMA sandbox on
their private Hudson instances.

--

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

Gmane