Marshall Schor wrote:
Jörn Kottmann wrote:
The additionalParams Map has a String key and can contains
all kinds of Objects, so the correct generification would be
MapString, Object.
In the uima code base I found one invocation where a Properties object
was
passed as additionalParams
Marshall Schor wrote:
Jörn Kottmann wrote:
The additionalParams Map has a String key and can contains
all kinds of Objects, so the correct generification would be
MapString, Object.
In the uima code base I found one invocation where a Properties object
was
passed as additionalParams
The CasPool has a constructor
CasPool(int aNumInstances, Collection aComponentDescriptionsOrMetaData,
Properties aPerformanceTuningSettings, ResourceManager
aResourceManager)
where aComponentDescriptionsOrMetaData is a collection which can contain
according
to javadoc
On Aug 17, 2009, at 9:22 PM, Marshall Schor wrote:
This format takes a long time to generate, and seems on marginally
more
compressed than the tar.gz formats. We've never generated it for the
uima-as distr; I'd like to update our build to drop it from the uima
base and sandbox distrs too.
The javadoc says these methods return a List of
ProcessingResourceMetaData objects.
Inside the private method getMetaDataList, objects which do not have the
ProcessingResourceMetaData
type are added to the list. That can be seen in line 1749, there a
CasInitializerDescription object is added
Adam Lally wrote:
On Fri, Aug 14, 2009 at 12:10 PM, Jörn Kottmannkottm...@gmail.com wrote:
The javadoc says these methods return a List of ProcessingResourceMetaData
objects.
Inside the private method getMetaDataList, objects which do not have the
ProcessingResourceMetaData
type are added to
Jörn Kottmann wrote:
Jörn Kottmann wrote:
Jörn Kottmann wrote:
Hi,
after all the discussion we had I think thats the correct
way to generify FSIndexRepository:
interface FSIndexRepository {
FSIndexFeatureStructure getIndex(String label);
FSIteratorFeatureStructure getAllIndexedFS(Type aType
Thilo Goetz wrote:
Jörn Kottmann wrote:
Jörn Kottmann wrote:
Jörn Kottmann wrote:
Jörn Kottmann wrote:
Hi,
after all the discussion we had I think thats the correct
way to generify FSIndexRepository:
interface FSIndexRepository {
FSIndexFeatureStructure getIndex
Marshall Schor wrote:
Jörn Kottmann wrote:
Jörn Kottmann wrote:
Jörn Kottmann wrote:
Jörn Kottmann wrote:
Hi,
after all the discussion we had I think thats the correct
way to generify FSIndexRepository:
interface FSIndexRepository {
FSIndexFeatureStructure getIndex
Marshall Schor wrote:
On the normal scale of -1, 0, +1, to the proposition -
have the generic form of many methods that are in the public API for
UIMA that return UIMA objects, return a type which is inferred from the
receiving typed variable, versus having it return just one fixed type
not
Jörn Kottmann wrote:
Marshall Schor wrote:
I'll probably stop trying to convince others if they continue to feel
that the tradeoffs here should be in the direction of returning only
specific types (disallowing users from specifying downcasting in that
manner), versus using types of the form T
Adam Lally wrote:
On Fri, Aug 7, 2009 at 2:32 PM, Marshall Schorm...@schor.com wrote:
The createFilteredIterator method in CASImpl takes an FSIterator and an
FSMatchConstraint, and returns another iterator.
The generification of this is:
publicT extends FeatureStructure FSIteratorT
Thilo Goetz wrote:
Jörn Kottmann wrote:
Adam Lally wrote:
On Fri, Aug 7, 2009 at 2:32 PM, Marshall Schorm...@schor.com wrote:
The createFilteredIterator method in CASImpl takes an FSIterator and an
FSMatchConstraint, and returns another iterator.
The generification
Thilo Goetz wrote:
Jörn Kottmann wrote:
Thilo Goetz wrote:
Jörn Kottmann wrote:
Adam Lally wrote:
On Fri, Aug 7, 2009 at 2:32 PM, Marshall Schorm...@schor.com wrote:
The createFilteredIterator method in CASImpl takes an FSIterator
Adam Lally wrote:
On Wed, Aug 12, 2009 at 5:54 AM, Jörn Kottmannkottm...@gmail.com wrote:
Yes, but if someone writes it intentional he would get the same
exception during class casting. That means not doing it would only help
someone who picks the wrong type for the variable by accident,
The additionalParams Map has a String key and can contains
all kinds of Objects, so the correct generification would be MapString,
Object.
In the uima code base I found one invocation where a Properties object was
passed as additionalParams. Properties is a MapObject, Object which
will cause
Jörn Kottmann wrote:
Hi,
after all the discussion we had I think thats the correct
way to generify FSIndexRepository:
interface FSIndexRepository {
FSIndexFeatureStructure getIndex(String label);
FSIteratorFeatureStructure getAllIndexedFS(Type aType);
...
}
It generified now and also
Marshall Schor wrote:
Sounds right. But we should use bounded wildcards for arguments where
appropriate (of course, this doesn't apply to getViewIterator, which has
no arguments). The article,
http://www.ibm.com/developerworks/java/library/j-jtp07018.html?S_TACT=105AGX02S_CMP=EDU
has a nice
Jörn Kottmann wrote:
Jörn Kottmann wrote:
Hi,
after all the discussion we had I think thats the correct
way to generify FSIndexRepository:
interface FSIndexRepository {
FSIndexFeatureStructure getIndex(String label);
FSIteratorFeatureStructure getAllIndexedFS(Type aType);
...
}
It generified
Marshall Schor wrote:
I'll probably stop trying to convince others if they continue to feel
that the tradeoffs here should be in the direction of returning only
specific types (disallowing users from specifying downcasting in that
manner), versus using types of the form T extends X,
which allows
Adam Lally wrote:
On Mon, Aug 10, 2009 at 9:00 PM, Marshall Schorm...@schor.com wrote:
Here's a new thread to discuss just one particular issue - a generics
tradeoff.
In other posts, people have expressed misgivings about letting users
downcast ListsomeType to ListsomeSubType, if it cannot
Jukka Zitting wrote:
Hi,
I came across LEGAL-15 [1] that was filed last year over an unanswered
question [2] from the previous year. The question was about licensing
of some RCP build details. Is this issue still relevant to UIMA?
[1] https://issues.apache.org/jira/browse/LEGAL-15
[2]
On a related note, have you considered using Iterables instead of
Iterators? They make the looping constructs much nicer.
Its not possible to use Iterables instead of Itertors because
that will break backward compatibility of our API.
An option is to let FSIterator also extend Iterable,
Jörn Kottmann wrote:
The proposed changes would move the project model out
of the Cas Editor into a new project with the advantage that
it can be used by other tooling too. Like an analysis engine launcher
which needs a document collection to run the AE or a PEAR
runner.
Should we split
Marshall Schor wrote:
Adam Lally wrote:
On Sat, Aug 8, 2009 at 4:57 PM, Marshall Schorm...@schor.com wrote:
Jörn Kottmann wrote:
On Aug 7, 2009, at 8:57 PM, Marshall Schor wrote:
getViewIterator in CASImpl is written with the signature:
IteratorCAS
Here's another (probably weak) use case for returning T extends
AbstractCas kinds of things: If you have part of the code which
collects views and some of these views use one form of the AbstractCas
(e.g. CASImpl) and others use the JCas form, it would be nice to be able
to put these two uses
Marshall Schor wrote:
Jörn Kottmann wrote:
Here's another (probably weak) use case for returning T extends
AbstractCas kinds of things: If you have part of the code which
collects views and some of these views use one form of the AbstractCas
(e.g. CASImpl) and others use the JCas form
Adam Lally wrote:
So, bottom line, I say we stick with the recommendation of Brian
Goetz's article and don't use wildcards in return types.
Well after all this discussion I think thats only true
for cases like getViewIteraterator because of the reasons
given by Adam.
There are other cases
Jörn Kottmann wrote:
No I do not think that they could be changed to take type T.
Lets take the case of the contains method.
The javadoc says:
Check if the index contains an element equal to the given feature
structure according to the
ordering of the index. Note that this is in general
Marshall Schor wrote:
The generification of FSIndex currently specifies one type, T extends
FeatureStructure that is the type of item being returned.
The contains and find methods have arguments of type FeatureStructure.
These could be changed to take type T.
No I do not think that they
Marshall Schor wrote:
Marshall Schor wrote:
Adam Lally wrote:
On Mon, Aug 10, 2009 at 4:07 PM, Jörn Kottmannkottm...@gmail.com wrote:
Marshall Schor wrote:
The generification of FSIndex currently specifies one type, T extends
FeatureStructure
On Aug 8, 2009, at 10:57 PM, Marshall Schor wrote:
Jörn Kottmann wrote:
On Aug 7, 2009, at 8:57 PM, Marshall Schor wrote:
getViewIterator in CASImpl is written with the signature:
IteratorCAS getViewIterator()
If you are working with things needing CASImpl objects, you would
write
On Aug 7, 2009, at 8:57 PM, Marshall Schor wrote:
getViewIterator in CASImpl is written with the signature:
IteratorCAS getViewIterator()
If you are working with things needing CASImpl objects, you would
write:
IteratorCAS s = aCas.getViewIterator();
while (s.hasNext()) {
CASImpl ci
The current choice in generification doesn't support this; a fix would
be to change AnnotationIndex generification from
public interface AnnotationIndex extends FSIndexAnnotationFS to
public interface AnnotationIndex extends FSIndexAnnotationBaseFS
Is this correct?
The reason I choose
Thilo Goetz wrote:
Yes, AnnotationBaseFS has no built-in support in UIMA, afaik. The
annotation indexes only work on AnnotationFSs.
BTW, I'm getting a unnecessary cast warning on line 169 of
AnnotationIndexImpl, in case anybody goes in there to make those
changes.
There must be tons of
Marshall Schor wrote:
Jörn Kottmann (JIRA) wrote:
[ https://issues.apache.org/jira/browse/UIMA-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12740135#action_12740135 ]
Jörn Kottmann commented on UIMA-1479
marius wrote:
Hello,
how can i integrate a external tool such as gutime to UIMA?
I never heard of gutime it seems to be a tagger
which can recognize/detect time expressions in natural language.
Here is a link to a description:
http://www.timeml.org/site/tarsqi/modules/gutime/index.html
Marshall Schor 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
Thilo Goetz wrote:
Jörn Kottmann wrote:
Thilo Goetz wrote:
Jörn Kottmann wrote:
Jörn Kottmann wrote:
A collection of text documents that you can run
analysis on. If I understand correctly, the Cas
Editor currently requires XCAS/XmiCAS files. It
would be nice
Thilo Goetz wrote:
Jörn Kottmann wrote:
Thilo Goetz wrote:
Jörn Kottmann wrote:
Thilo Goetz wrote:
Jörn Kottmann wrote:
Jörn Kottmann wrote:
A collection of text documents that you can run
analysis on. If I
Thilo Goetz wrote:
Jörn Kottmann wrote:
Hi,
is there a reason why we do not use maven
to build the SimpleServer war file ?
Jörn
Sorry for the late reply. The reason is probably
that I originally contributed the SimpleServer, and
I try to stay as far away from maven as I can
Thilo Goetz wrote:
Jörn Kottmann wrote:
Thilo Goetz wrote:
Jörn Kottmann wrote:
Hi,
is there a reason why we do not use maven
to build the SimpleServer war file ?
Jörn
Sorry for the late reply. The reason is probably
that I originally contributed
Thilo Goetz wrote:
Sorry, did the reformat thing again. I only changed the static
paths to use System.getProperty(file.separator) instead of a
hard coded /. Sorry about that.
Why don't you use File.separatorChar ?
Jörn
Thilo Goetz wrote:
Rico,
have you sent in a contributor's license agreement (CLA) yet?
If not, please do. See
http://www.apache.org/licenses/#clas
If you have done so already, we need to find out why you're
not listed here:
http://people.apache.org/~jim/committers.html
Can we check in the
Thilo Goetz wrote:
- the pear packaging maven plugin project must be built first
and manually if it's not in the local repo yet. I find that
acceptable, but it would be nicer if it wasn't necessary.
If it needs to stay this way, it should be documented.
The pear packaging plugin is
Thilo Goetz wrote:
Jörn Kottmann wrote:
Jörn Kottmann wrote:
A collection of text documents that you can run
analysis on. If I understand correctly, the Cas
Editor currently requires XCAS/XmiCAS files. It
would be nice if users could just add their text
files and then either create
Marshall Schor wrote:
This is because it's binary compatible to go from --no generic info-- to
some-generic-info, but it is not binary compatible to change the
generic-info once it is there.
Thats true. I always changed everything or nothing.
At the places I did not change I tried to make
Jörn Kottmann wrote:
A collection of text documents that you can run
analysis on. If I understand correctly, the Cas
Editor currently requires XCAS/XmiCAS files. It
would be nice if users could just add their text
files and then either create annotations manually
with the Cas Editor
Marshall Schor wrote:
When adding generic type info to UIMA core, if there is a method which
is declared to return a List, and we change it to return a
ListofSomeType, and the method is part of the UIMA public API - does
that break the public API? Or will code that is already written to
use it
Marshall Schor wrote:
Is this OK or should we refrain from any changes which are the public
UIMA api's?
Here is something about the topic from the eclipse wiki:
http://wiki.eclipse.org/Evolving_Java-based_APIs_2
The section about turning non-gernic types and methods
into generic ones is
Thilo Goetz wrote:
2. The sandbox build requires the docbook-tools project
from the core to be in the same directory. That's not
nice, because you can't extract the core and the
sandbox into the same directory from svn, svn balks.
When I am working on a sandbox project I just add
it to my
The class uses nameMap as a Set can it be replaced with a HashSet ?
Jörn
I was hoping to work a bit on some of our UI tools, but
2 weeks passed before I even had a build where I could
run our eclipse tools from the within eclipse. Now I'm
in a state where I could do that, but I have no idea how
to proceed if I actually wanted to make changes. Normally,
if I wanted
A collection of text documents that you can run
analysis on. If I understand correctly, the Cas
Editor currently requires XCAS/XmiCAS files. It
would be nice if users could just add their text
files and then either create annotations manually
with the Cas Editor, or automatically by running
A few days ago I said its only possible to start the Cas Editor
and other plugins when the runtime plugin is manually deployed to the
eclipse
instance. That seems to be not true. The only modification needed
is the
correct Bundle-ClassPath to target/classes in the MANIFEST.MF file.
In my
At the end of the mentioned method is an exception created
in an error case but not thrown.
I guess that can be fixed by inserting throw e;.
Can somebody please have a look ?
...
if (this.allowPreexistingFS == AllowPreexistingFS.disallow) {
CASRuntimeException e = new
Tommaso Teofili wrote:
Hi Jörn,
I think you're right, the throws CASRuntimeException has to be declared in
the readFS method signature too
In my opinion its ok to not declare it, since its an internal
private method and the CASRuntimeException is usually
only thrown when there is a programming
Tommaso Teofili wrote:
Ok,I think throwing is ok (+1), but declaring in the public methods could be
useful for developers in my opinion cause it's thrown explicitly.
Based on your reply I did a quick search through uimaj-core code
and look for references for the CASRuntimeException.
There are
Marshall Schor wrote:
The debug plugin adds the capability for Eclipse to show structured
values in the debugger for UIMA objects.
It is briefly described here:
Marshall Schor wrote:
+1 to remove it, from me, but Thilo could take a look too...
I commented it out to test removing it, and didn't see any compile
errors. (didn't commit)
Actually I started to migrate the cas.impl package to our
new generic interfaces and have seen a few classes which
Should that method be deprecated since it returns a deprecated class ?
Jörn
Still not working (for reasons I have no idea) - the update site seems
to have the cas editor jar, but there is no plugin installed for it.
It would be good to have another pair of eyes look at this - maybe
there's some misspelling somewhere...
I followed the steps above to create the
I am wondering if it is a good idea to install the debug plugin over
the update site.
What is the purpose of this plugin ?
Jörn
enabledfalse/enabled
updatePolicynever/updatePolicy
/snapshots
/repository
/repositories
-Marshall
Marshall Schor wrote:
Jörn Kottmann wrote:
Marshall Schor wrote:
Trying to build uimaj - I get this build error on the Cas Editor
project:
Couldn't
Thilo Goetz wrote:
I was able to successfully build the update site and install
into Eclipse 3.5. I tested the CDE and JCasGen, seems to work
fine. Joern, what's a good way to quickly test the CAS Editor?
Create a NLP project and add a type system to it,
create a folder and add it as
The project model of the Cas Editor does not really fit what we
need now in my opinion. We have to rework that.
It was made for the RCP Cas Editor version, but now the Cas Editor
is more like a tool which just shows/edits CAS files.
We could try to make a general model where a user configures
Hi,
the class has private constructor which is never used.
Is there a reason for it ?
Otherwise I would suggest to delete it.
Jörn
Hello
Despite all this, I'm able to run our plugins from
eclipse. Everything seems to be working normally.
I get a small number of plugin-not-found warings at
startup, and continuous JDOM warnings throughout,
but that doesn't seem to affect functionality.
Everytime I try to run the Cas
Marshall Schor wrote:
Next issue:
There is a new feature for 2.3.0, the caseditor. In the current build
approach, each feature needs a separate feature project (Eclipse likes
this organization). There was no uimaj-eclipse-feature-caseditor
project, so I made one :-) and will check it in
I prefer simplicity, and would like the Cas Editor installed just like
all the other tooling, when you install the tooling. Then it is ready
if and when needed :-).
+1
Jörn
Marshall Schor wrote:
Jörn Kottmann wrote:
Marshall Schor wrote:
Trying to build uimaj - I get this build error on the Cas Editor
project:
Couldn't find a version in [3.2.1-v3235e, 3.3.0-v3345b, 3.3.0-v3346] to
match range [3.3.0,4.0.0)
org.eclipse:swt:jar:null
from the specified
Hi,
is there a reason why we do not use maven
to build the SimpleServer war file ?
Jörn
Marshall Schor wrote:
Trying to build uimaj - I get this build error on the Cas Editor project:
Couldn't find a version in [3.2.1-v3235e, 3.3.0-v3345b, 3.3.0-v3346] to
match range [3.3.0,4.0.0)
org.eclipse:swt:jar:null
from the specified remote repositories:
central
Hello,
thats the compiler error I get:
/home/joern/uima-dev/uimaj-as-activemq/src/test/java/org/apache/uima/ee/test/TestUimaASExtended.java:[217,4]
spinShutdownThread(org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl,long)
in org.apache.uima.ee.test.utils.BaseTestSupport
Thanks Jerry now it compiles.
Jörn
Hello,
thats the compiler error I get:
/home/joern/uima-dev/uimaj-as-activemq/src/test/java/org/apache/uima/ee/test/TestUimaASExtended.java:[217,4]
spinShutdownThread(org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl,long)
in
Fortunately, I have already finished a improved Lucas
version which comes already with documentation in docbook format. I
wish to deploy this Lucas version to the UIMA sandbox. How should I
proceed?
Usually we have issue for code modifications, only for very
small fixes its accepted to not
Rico Landefeld wrote:
For the documentation issue this would be easy. Checkout
the project from the sandbox, copy your docbook files to the
project, remove the old documentation, create a patch and
attach it to the documentation issue.
How significant are your changes to the source code ?
Rico Landefeld wrote:
Hi,
after all, although Lucas has arrived in the sandbox, it is not listed
on the uima web site. Maybe beacause of an open JIRA issue (1361)
regarding the convertion of the maven site based documentation to the
docbook format.
No that has nothing to do with a mention of
Adam Lally wrote:
FYI, a while back I posted some code we could consider adding for JCAS
that allow you to get iterators parameterized by specific JCAS types:
http://www.mail-archive.com/uima-dev@incubator.apache.org/msg04657.html
It might be interesting to consider adding something like that
I always use maven for my uima projects, this also works very well
together with eclipse through mvn eclipse:eclipse and I guess also
with other IDEs.
Maybe we should additionally create a maven archetype for the most
common types of uima
projects.
Jörn
Burn Lewis (JIRA) wrote:
[
Adam Lally wrote:
FYI, a while back I posted some code we could consider adding for JCAS
that allow you to get iterators parameterized by specific JCAS types:
http://www.mail-archive.com/uima-dev@incubator.apache.org/msg04657.html
It might be interesting to consider adding something like that
Tommaso Teofili wrote:
Hi,I opened a Jira (1373) issue and attached the patch file, should I mark
it as resolved by myself or wait someone else to do that (i.e.: for testing
purposes)?
The committer who checks in your patch will mark the issue as
resolved and then you verify it and mark the
Thilo Goetz wrote:
Jörn Kottmann wrote:
Hello,
right now every FSIndex uses FeatureStructure as the generics parameter for
the Iterator it can provide. That means that the AnnoationIndex also
must provide
an FeatureStructure Iterator and not an AnnotationFS Iterator which
would be much
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:
[
Hello,
right now every FSIndex uses FeatureStructure as the generics parameter for
the Iterator it can provide. That means that the AnnoationIndex also
must provide
an FeatureStructure Iterator and not an AnnotationFS Iterator which
would be much
nicer in client code.
I would like to suggest
On Jun 6, 2009, at 2:49 PM, Tommaso Teofili wrote:
Ok, done.
how can I submit it?
Just open a jira issue and attach your patch or pom.xml file.
Jörn
Hi,
when I am building our docbook on linux or mac os. I get this exception:
[java] SEVERE: Exception
[java] org.apache.fop.apps.FOPException: Failed to resolve font
with embed-url 'file:///c:/WINDOWS/Fonts/pala.TTF'
[java] at
This vote has been open for a week, and is now closed.
There were 3 binding +1s, 2 non-binding +1 and no 0s or -1s.
The vote passes.
The following people voted +1:
Marshall Schor (binding)
Michael Baessler (binding)
Jörn Kottmann (binding)
Jochen Leidner (non-binding)
Tommaso Teofili (non
+1
Jörn
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
Nikola Midich wrote:
Can someone please rename NOTICE:txt to NOTICE.txt.
It won't checkout in Windows environment.
Thanks for reporting this, I renamed it.
Jörn
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
It should be strings, actually. So the javadoc is wrong.
The constraint API is string based, so that a textual
representation (which used to exist but we lost sometime)
can be directly mapped to the API. I guess there is no
test case, else we would have noticed that sooner.
Ok, I changed
which are only implemented
by UIMA itself.
Jörn
On May 6, 2009, at 12:59 AM, Marshall Schor wrote:
+1, this would be very nice... -Marshall
Michael Baessler wrote:
+1, sounds good to me
-- Michael
Jörn Kottmann wrote:
Hallo,
I would love to start an initiative to add generics
* We have had some earlier discussions about changing
our release packaging a bit. This concerns the sandbox
in particular, as there are things in there that are
quite stable enough to graduate from there to a place
still to be created. This needs to be discussed, I don't
have a concrete
Thilo Goetz wrote:
Jörn Kottmann wrote:
Can I commit my changes ? The patch can be reviewed in UIMA1341.
+1. I have reviewed the patch, applied it to my
workspace and run some tests. I think this is a
big usability improvement. The change to FS iterators
alone is worth
Hallo,
I would love to start an initiative to add generics to the
interfaces in the uima core APIs. Since UIMA now depends
on java 5 all code which is written against our APIs is full
with warnings.
I will create a jira issue and attach a patch which should
be reviewed by someone else to make
On Apr 17, 2009, at 5:14 PM, Tong Fin wrote:
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
Hi,
I tried to deploy our uimaj-eg-runtime bundle in a spring dm-server,
but that did not works well because of the EMF dependency.
The EMF guys say it is possible to run EMF standalone with
4 jars, but that does not work in an OSGI environment,
because the necessary EMF bundles depend on
Hi,
I went to ApacheCon last week and one of the
Solr committers mentioned to me that they are considering
using UIMA for preprocessing of documents.
Mabye we can start a discussion with them about the topic
and make some advertisement for UIMA, if they integrate
we would get new users.
Jörn
Hello everyone,
I also vote +1 but the code has to be improved before I would
vote +1 for a release. Especially the exception handling should make
use of javas managed exceptions and in one place a I saw
some code which was copied over and over again.
Jörn
On Mar 4, 2009, at 11:32 AM, Thilo
101 - 200 of 360 matches
Mail list logo
