Thanks a lot. I'm going to see how to play with the java nature and the
class path. Concerning your other solution, a priori, It is less
interesting to me as the classes are not in the workspace but in the plugin.
I'll let you know.
Marshall Schor wrote:
Christian Mauceri wrote:
I answer, both of your questions (I'm referring to your previous
mail), so:
1. The Eclipse version I'm using is 3.2,
2. Concerning, the architecture of my application it is the
following: I have a first plugin containing an automaton toolkit I
use for text analysis, a second plugin contains the UIMA
components using classes of the first plugin, finally I have a
third plugin using the UIMA ones and EMF plugins to implement a
GUI. This third plugin will be integrated in a RCP application but
at the moment in the development phase I test it running the
workbench application I call using the run menu. When I'm in the
workbench I create a general project where I put UIMA descriptors
which use classes of the UIMA plugin.
Is it possible to change the "general project" where you put UIMA
descriptors
into a Java project, and set its build classpath to include those
classes / projects
which are the TAEs you reference below? If so, the existing mechanism
should
work, I think, and will restrict the view of possible classes shown in
the browse
button to just those available on the specified class path, which
could reduce
user error. What it's doing is what you would be doing by using the
"Search"
function in that project, looking for particular kinds of classes; the
Search function
can't search within a project for Java classes if it's not a Java
project.
The other thing that is doable, and I'll put in a change request for
this, is to handle
this particular case, where no classpath is available to restrict the
search, and just
search the entire workspace, rather than throwing this "unexpected
exception".
-Marshall
Depending the corpora and
the automata I want to use I change the parameters of these
descriptors or the CPE file in the project. So far, using the
buddy mechanism everything work fine.
Now I would like to add some flexibility allowing users to select
select different TAE defined in the UIMA plugin and it is when
things go wrong. To do that I use the browse button of the
Descriptor Editor and I get the message I told you. Indeed I could
reinvent the wheel and update the descriptor with an editor of my
own but I think it would be a pity. If it is mandatory to use a
java project I will obviously have to do that because exporting
all the PDE plugins to the RCP app will be too huge.
Forgive the length of this message, I wanted to be as exhaustive as
possible.
Marshall Schor wrote:
Christian Mauceri wrote:
Hi,
recently in the UIMA AlphaWorks forum Marshall Schor saved my life
explaining me how to use the buddy class loading in the Eclipse
Manifest file of a plugin to make UIMAFramework recognizes my
classes. It works fine and my class are recognized. However I still
cannot completly use the Descriptor Editor Component in my
application, indeed when I push the browse button in the Overview
Tab to get the list of available Analysis Engine Java classes I get
the following error message:
Unexpected exception while getting type information for type
'com.ibm.uima.analysis_component.AnalysisComponent'. FSATest does
not exist.
(FSATest is the Eclipse workplace project I put my xml descriptor in)
Any suggestion?
More thinking... When you click the "browse" button it does the
following:
It first goes to the Eclipse project containing the XML descriptor.
It then assumes (perhaps incorrectly) that this project is a "Java"
project, and that its classpath is set up to indicate all the
classes used in the project, including the UIMA framework classes.
Is this project a "Java" project, with its class path set up properly?
-Marshall
--
Cordialement/Regards
Christian Mauceri
http://hermeneute.com/Christian
