I lean toward adding the keep-alive as the default for Vinci because it
seems
to fix firewall issues which we've seen, with little or no down-side.
I would not complicate the UIMA descriptors with this detail at this point.
If we later get some kind of new, separate deployment details
Hi,
I am not sure, who is looking into this, but I assume that if you can
provide a small XMI sample file, which produces this error it might help a
lot.
-- Mirko
btw.: is the annotation correct in the XMI?
well, I think at least the XMI is correct. At least it has all the info
I am
[
https://issues.apache.org/jira/browse/UIMA-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thilo Goetz resolved UIMA-185.
--
Resolution: Fixed
Fix Version/s: 2.1
Assignee: Marshall Schor (was: Thilo Goetz)
Done.
On 1/19/07, Marshall Schor [EMAIL PROTECTED] wrote:
snip/
How about for now, making this a UIMA framework property - like the
logger to use, etc.
Good idea, I will plan to do that today if there are no objections.
-Adam
Eddie and I don't think we're going to get to this JIRA issue for 2.1:
Apache UIMA client should be able to communicate with IBM UIMA (1.x or
2.0) service
https://issues.apache.org/jira/browse/UIMA-125
As I noted in a JIRA comment, service compatibility between IBM UIMA
2.0 and Apache UIMA 2.x
Turn on socket keepAlive in jVinci
--
Key: UIMA-212
URL: https://issues.apache.org/jira/browse/UIMA-212
Project: UIMA
Issue Type: Improvement
Components: Transport Adapters - SOAP, Vinci
[
https://issues.apache.org/jira/browse/UIMA-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally reassigned UIMA-193:
---
Assignee: Adam Lally
PEAR Encoding Test gives NullPointerException under Sun Java 1.4.2
[
https://issues.apache.org/jira/browse/UIMA-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor reassigned UIMA-210:
---
Assignee: Marshall Schor
faulty use of .read(buffer...) in several places - not checking for
[EMAIL PROTECTED] wrote:
Author: alally
Date: Fri Jan 19 07:15:38 2007
New Revision: 497842
URL: http://svn.apache.org/viewvc?view=revrev=497842
Log:
Fixed FeatureStructure.equals to compare base CAS refs, not view refs.
UIMA-209: http://issues.apache.org/jira/browse/UIMA-209
Modified:
On 1/19/07, Thilo Goetz [EMAIL PROTECTED] wrote:
I'd vote for using the getBaseCAS() accessor instead of directly
accessing the baseCAS variable. That will make the eventual refactoring
into views and CASes easier (and improves on artistic impression ;-).
Done.
-Adam
The UIMA website on Apache ( http://incubator.apache.org/uima/ ) has
drafts of the Project Guidelines and Contributions Policies.
Please review and comment on their content, including saying you agree -
if you agree - so we can come to some concensus about this.
The goals of these are to
Marshall Schor wrote:
The UIMA website on Apache ( http://incubator.apache.org/uima/ ) has
drafts of the Project Guidelines and Contributions Policies. Please
review and comment on their content, including saying you agree - if you
agree - so we can come to some concensus about this.
The
Thilo Goetz wrote:
snip
+1 to the overall content, nice work Marshall.
Thanks!
Some minor comments:
- Since we have our mailing list addresses in plain text in other
places, I don't think it's necessary AT.DOT it on the project
guidelines page, it just makes it hard to read.
I saw this
[
https://issues.apache.org/jira/browse/UIMA-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally closed UIMA-212.
---
Resolution: Fixed
Turn on socket keepAlive in jVinci
--
[
https://issues.apache.org/jira/browse/UIMA-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally reassigned UIMA-213:
---
Assignee: Adam Lally
DocumentAnalyzer/RunAE tools don't support XML detagging and Remote Vinci AEs
DocumentAnalyzer/RunAE tools don't support XML detagging and Remote Vinci AEs
-
Key: UIMA-213
URL: https://issues.apache.org/jira/browse/UIMA-213
Project: UIMA
[
https://issues.apache.org/jira/browse/UIMA-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466142
]
Adam Lally commented on UIMA-213:
-
Unfortunately I don't think it's possible to make this work with any Sofa
mapping
On 1/19/07, Marshall Schor [EMAIL PROTECTED] wrote:
The UIMA website on Apache ( http://incubator.apache.org/uima/ ) has
drafts of the Project Guidelines and Contributions Policies.
Please review and comment on their content, including saying you agree -
if you agree - so we can come to some
[
https://issues.apache.org/jira/browse/UIMA-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally updated UIMA-125:
Fix Version/s: (was: 2.1)
2.2
As posted to uima-dev we're not going to get to this
[
https://issues.apache.org/jira/browse/UIMA-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally reassigned UIMA-98:
--
Assignee: Marshall Schor
Marshall, I know you've been looking into Mac issues lately. Just making sure
DocumentAnalyzer shouldn't have to re-contact service to get the typesystem
---
Key: UIMA-214
URL: https://issues.apache.org/jira/browse/UIMA-214
Project: UIMA
Issue
CasCopier constructor should take source CAS as argument
Key: UIMA-215
URL: https://issues.apache.org/jira/browse/UIMA-215
Project: UIMA
Issue Type: Improvement
Components:
[
https://issues.apache.org/jira/browse/UIMA-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally resolved UIMA-215.
-
Resolution: Fixed
Assignee: Eddie Epstein (was: Adam Lally)
CasCopier constructor should take
Add getSupportedXCasVersions to Vinci Services
--
Key: UIMA-216
URL: https://issues.apache.org/jira/browse/UIMA-216
Project: UIMA
Issue Type: Improvement
Components: Transport Adapters -
On 1/17/07, Marshall Schor [EMAIL PROTECTED] wrote:
What testing beyond the unit tests will we do for this release?
Here are some items to consider:
1) test that all the Jira changes that would affect the documentation
have had the documentation updated
2) Functional testing, Installation
On 1/19/07, Marshall Schor [EMAIL PROTECTED] wrote:
I think you may have forgotten to check in changes to jVinci project?
After I updated all the projects, build fails because
The method setSocketKeepAliveEnabled(boolean) is undefined for the
type VinciContext
Hmmm.. I
Adam Lally wrote:
snip
Hmmm.. I double-checked, and I have committed everything. And I can
see the subversion commits attached to the JIRA issue.
Right you are - turned out to be operator problem (that would be
me...) You see,
I have some non UIMA projects in my workspace, so I have a
27 matches
Mail list logo