Jar file issues

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Jar file issues

Daniel Elenius
I have a question about how to handle jar files needed by Protege plugins.

I have a plugin which needs axis.jar, wsdl4j.jar, and jaxrpc.jar.
protege-owl already comes with axis.jar, but not the others. In my code,
some method in axis.jar needs to call some methods in wsdl4j.jar and
jaxrpc.jar. However, if I just put jaxrpc.jar and wsdl4j.jar in my own
plugin directory, axis.jar can't find them (I get a
ClassNotFoundException). Also putting axis.jar in my own plugin dir
doesn't help: Protege wants to use the axis.jar in the protege-owl
plugin dir anyway. Putting wsdl4j.jar and jaxrpc.jar in the protege-owl
plugin dir solves the problem, but I would like to be able to just zip
up my plugin dir and give it to people as a binary distribution.

Is there any good solution to this?

Daniel Elenius
Computer Scientist
SRI International
http://csl.sri.com/people/elenius/



_______________________________________________
protege-owl mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-owl

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
Reply | Threaded
Open this post in threaded view
|

Re: Jar file issues

Timothy Redmond

This is an awkward problem.  Protege 3 uses a home brewed plugin
architecture (it was done before the current powerful solutions
existed).  So there is no simple way to mask the axis.jar from the
protege owl directory.

But perhaps we can help you with this.  My first reaction is that it is
not clear why axis.jar is needed in the protege-owl directory.  Does it
work if it is removed?  Perhaps we should have a build without the
axis.jar.  I am not sure if this is safe.  I will talk to Tania about
this and see if I can do some analysis.

Alternatively, if axis.jar is needed then we could make a build that
adds wsdl4j.jar and jaxrpc.jar.  This might be redundant but might not
require the analysis.

Finally, you could build your zip file one directory up so that when
unzipped it adds the wsdl4j.jar and the jaxrpc.jar files to the
protege-owl plugin.

The second solution is the safest but the first solution might be better.

-Timothy



On 02/22/2012 06:18 PM, Daniel Elenius wrote:

> I have a question about how to handle jar files needed by Protege
> plugins.
>
> I have a plugin which needs axis.jar, wsdl4j.jar, and jaxrpc.jar.
> protege-owl already comes with axis.jar, but not the others. In my
> code, some method in axis.jar needs to call some methods in wsdl4j.jar
> and jaxrpc.jar. However, if I just put jaxrpc.jar and wsdl4j.jar in my
> own plugin directory, axis.jar can't find them (I get a
> ClassNotFoundException). Also putting axis.jar in my own plugin dir
> doesn't help: Protege wants to use the axis.jar in the protege-owl
> plugin dir anyway. Putting wsdl4j.jar and jaxrpc.jar in the
> protege-owl plugin dir solves the problem, but I would like to be able
> to just zip up my plugin dir and give it to people as a binary
> distribution.
>
> Is there any good solution to this?
>
> Daniel Elenius
> Computer Scientist
> SRI International
> http://csl.sri.com/people/elenius/
>
>
>
> _______________________________________________
> protege-owl mailing list
> [hidden email]
> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>
> Instructions for unsubscribing:
> http://protege.stanford.edu/doc/faq.html#01a.03

_______________________________________________
protege-owl mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-owl

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
Reply | Threaded
Open this post in threaded view
|

Re: Jar file issues

Martin O'Connor

Some of the SWRLTab's built-in libraries use axis.jar so unfortunately it does have to be in the protege-owl plugins directory. If you are not using these libraries (temporal and swrlb, though perhaps others too) then you could (at least temporarily) substitute your axis.jar for the one that comes with the distribution - though obviously this is not a general solution.

Martin

----- Original Message -----
From: "Timothy Redmond" <[hidden email]>
To: [hidden email]
Sent: Thursday, February 23, 2012 9:54:30 AM
Subject: Re: [protege-owl] Jar file issues


This is an awkward problem.  Protege 3 uses a home brewed plugin
architecture (it was done before the current powerful solutions
existed).  So there is no simple way to mask the axis.jar from the
protege owl directory.

But perhaps we can help you with this.  My first reaction is that it is
not clear why axis.jar is needed in the protege-owl directory.  Does it
work if it is removed?  Perhaps we should have a build without the
axis.jar.  I am not sure if this is safe.  I will talk to Tania about
this and see if I can do some analysis.

Alternatively, if axis.jar is needed then we could make a build that
adds wsdl4j.jar and jaxrpc.jar.  This might be redundant but might not
require the analysis.

Finally, you could build your zip file one directory up so that when
unzipped it adds the wsdl4j.jar and the jaxrpc.jar files to the
protege-owl plugin.

The second solution is the safest but the first solution might be better.

-Timothy



On 02/22/2012 06:18 PM, Daniel Elenius wrote:

> I have a question about how to handle jar files needed by Protege
> plugins.
>
> I have a plugin which needs axis.jar, wsdl4j.jar, and jaxrpc.jar.
> protege-owl already comes with axis.jar, but not the others. In my
> code, some method in axis.jar needs to call some methods in wsdl4j.jar
> and jaxrpc.jar. However, if I just put jaxrpc.jar and wsdl4j.jar in my
> own plugin directory, axis.jar can't find them (I get a
> ClassNotFoundException). Also putting axis.jar in my own plugin dir
> doesn't help: Protege wants to use the axis.jar in the protege-owl
> plugin dir anyway. Putting wsdl4j.jar and jaxrpc.jar in the
> protege-owl plugin dir solves the problem, but I would like to be able
> to just zip up my plugin dir and give it to people as a binary
> distribution.
>
> Is there any good solution to this?
>
> Daniel Elenius
> Computer Scientist
> SRI International
> http://csl.sri.com/people/elenius/
>
>
>
> _______________________________________________
> protege-owl mailing list
> [hidden email]
> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>
> Instructions for unsubscribing:
> http://protege.stanford.edu/doc/faq.html#01a.03

_______________________________________________
protege-owl mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-owl

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
_______________________________________________
protege-owl mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-owl

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
Reply | Threaded
Open this post in threaded view
|

Re: Jar file issues

Daniel Elenius
In reply to this post by Timothy Redmond
On 02/23/2012 09:54 AM, Timothy Redmond wrote:
>
> This is an awkward problem.  Protege 3 uses a home brewed plugin
> architecture (it was done before the current powerful solutions existed).


Ok, phew, I thought I was going crazy for a while there.

> So there is no simple way to mask the axis.jar from the protege owl
> directory.
>
> But perhaps we can help you with this.  My first reaction is that it
> is not clear why axis.jar is needed in the protege-owl directory.  
> Does it work if it is removed?  Perhaps we should have a build without
> the axis.jar.  I am not sure if this is safe.  I will talk to Tania
> about this and see if I can do some analysis.
>
That would be great if possible. It certainly "works", but I haven't
tried every Protege-OWL feature without it. I imagine it was put there
for a reason.

> Alternatively, if axis.jar is needed then we could make a build that
> adds wsdl4j.jar and jaxrpc.jar.  This might be redundant but might not
> require the analysis.
>
Yeah, IF it is needed, I think this is the right solution.

> Finally, you could build your zip file one directory up so that when
> unzipped it adds the wsdl4j.jar and the jaxrpc.jar files to the
> protege-owl plugin.
>
I'm doing that for now, but it's not ideal for a couple of reasons:
People might accidentally overwrite the whole protege-owl plugin folder
depending on their zip program, and just generally it seems like a bad
idea to put stuff into other plugin directories.

> The second solution is the safest but the first solution might be better.
>
Yeah, let me know which one it ends up being.

> -Timothy
>
>
>
> On 02/22/2012 06:18 PM, Daniel Elenius wrote:
>> I have a question about how to handle jar files needed by Protege
>> plugins.
>>
>> I have a plugin which needs axis.jar, wsdl4j.jar, and jaxrpc.jar.
>> protege-owl already comes with axis.jar, but not the others. In my
>> code, some method in axis.jar needs to call some methods in
>> wsdl4j.jar and jaxrpc.jar. However, if I just put jaxrpc.jar and
>> wsdl4j.jar in my own plugin directory, axis.jar can't find them (I
>> get a ClassNotFoundException). Also putting axis.jar in my own plugin
>> dir doesn't help: Protege wants to use the axis.jar in the
>> protege-owl plugin dir anyway. Putting wsdl4j.jar and jaxrpc.jar in
>> the protege-owl plugin dir solves the problem, but I would like to be
>> able to just zip up my plugin dir and give it to people as a binary
>> distribution.
>>
>> Is there any good solution to this?
>>
>> Daniel Elenius
>> Computer Scientist
>> SRI International
>> http://csl.sri.com/people/elenius/
>>
>>
>>
>> _______________________________________________
>> protege-owl mailing list
>> [hidden email]
>> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>>
>> Instructions for unsubscribing:
>> http://protege.stanford.edu/doc/faq.html#01a.03
>
> _______________________________________________
> protege-owl mailing list
> [hidden email]
> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>
> Instructions for unsubscribing:
> http://protege.stanford.edu/doc/faq.html#01a.03

_______________________________________________
protege-owl mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-owl

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
Reply | Threaded
Open this post in threaded view
|

Re: Jar file issues

Timothy Redmond
In reply to this post by Martin O'Connor

Thanks Martin!

This suggests that maybe adding the jar files is the right solution:

> Alternatively, if axis.jar is needed then we could make a build that
> adds wsdl4j.jar and jaxrpc.jar.  This might be redundant but might not
> require the analysis.

-Timothy



On 02/23/2012 10:02 AM, Martin O'Connor wrote:

> Some of the SWRLTab's built-in libraries use axis.jar so unfortunately it does have to be in the protege-owl plugins directory. If you are not using these libraries (temporal and swrlb, though perhaps others too) then you could (at least temporarily) substitute your axis.jar for the one that comes with the distribution - though obviously this is not a general solution.
>
> Martin
>
> ----- Original Message -----
> From: "Timothy Redmond"<[hidden email]>
> To: [hidden email]
> Sent: Thursday, February 23, 2012 9:54:30 AM
> Subject: Re: [protege-owl] Jar file issues
>
>
> This is an awkward problem.  Protege 3 uses a home brewed plugin
> architecture (it was done before the current powerful solutions
> existed).  So there is no simple way to mask the axis.jar from the
> protege owl directory.
>
> But perhaps we can help you with this.  My first reaction is that it is
> not clear why axis.jar is needed in the protege-owl directory.  Does it
> work if it is removed?  Perhaps we should have a build without the
> axis.jar.  I am not sure if this is safe.  I will talk to Tania about
> this and see if I can do some analysis.
>
> Alternatively, if axis.jar is needed then we could make a build that
> adds wsdl4j.jar and jaxrpc.jar.  This might be redundant but might not
> require the analysis.
>
> Finally, you could build your zip file one directory up so that when
> unzipped it adds the wsdl4j.jar and the jaxrpc.jar files to the
> protege-owl plugin.
>
> The second solution is the safest but the first solution might be better.
>
> -Timothy
>
>
>
> On 02/22/2012 06:18 PM, Daniel Elenius wrote:
>> I have a question about how to handle jar files needed by Protege
>> plugins.
>>
>> I have a plugin which needs axis.jar, wsdl4j.jar, and jaxrpc.jar.
>> protege-owl already comes with axis.jar, but not the others. In my
>> code, some method in axis.jar needs to call some methods in wsdl4j.jar
>> and jaxrpc.jar. However, if I just put jaxrpc.jar and wsdl4j.jar in my
>> own plugin directory, axis.jar can't find them (I get a
>> ClassNotFoundException). Also putting axis.jar in my own plugin dir
>> doesn't help: Protege wants to use the axis.jar in the protege-owl
>> plugin dir anyway. Putting wsdl4j.jar and jaxrpc.jar in the
>> protege-owl plugin dir solves the problem, but I would like to be able
>> to just zip up my plugin dir and give it to people as a binary
>> distribution.
>>
>> Is there any good solution to this?
>>
>> Daniel Elenius
>> Computer Scientist
>> SRI International
>> http://csl.sri.com/people/elenius/
>>
>>
>>
>> _______________________________________________
>> protege-owl mailing list
>> [hidden email]
>> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>>
>> Instructions for unsubscribing:
>> http://protege.stanford.edu/doc/faq.html#01a.03
> _______________________________________________
> protege-owl mailing list
> [hidden email]
> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
> _______________________________________________
> protege-owl mailing list
> [hidden email]
> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03

_______________________________________________
protege-owl mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-owl

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
Reply | Threaded
Open this post in threaded view
|

Re: Jar file issues

Daniel Elenius
I am having similar issues with a dependency on a newer version of
jena.jar. While we're at it, would it be possible to bump up the version
of jena.jar that Protege-OWL uses to the current version (same with
arq.jar, etc)? I suspect that these things are at least more
backwards-compatible than forwards-compatible...


On 02/23/2012 10:48 AM, Timothy Redmond wrote:

>
> Thanks Martin!
>
> This suggests that maybe adding the jar files is the right solution:
>
>> Alternatively, if axis.jar is needed then we could make a build that
>> adds wsdl4j.jar and jaxrpc.jar.  This might be redundant but might not
>> require the analysis.
>
> -Timothy
>
>
>
> On 02/23/2012 10:02 AM, Martin O'Connor wrote:
>> Some of the SWRLTab's built-in libraries use axis.jar so
>> unfortunately it does have to be in the protege-owl plugins
>> directory. If you are not using these libraries (temporal and swrlb,
>> though perhaps others too) then you could (at least temporarily)
>> substitute your axis.jar for the one that comes with the distribution
>> - though obviously this is not a general solution.
>>
>> Martin
>>
>> ----- Original Message -----
>> From: "Timothy Redmond"<[hidden email]>
>> To: [hidden email]
>> Sent: Thursday, February 23, 2012 9:54:30 AM
>> Subject: Re: [protege-owl] Jar file issues
>>
>>
>> This is an awkward problem.  Protege 3 uses a home brewed plugin
>> architecture (it was done before the current powerful solutions
>> existed).  So there is no simple way to mask the axis.jar from the
>> protege owl directory.
>>
>> But perhaps we can help you with this.  My first reaction is that it is
>> not clear why axis.jar is needed in the protege-owl directory.  Does it
>> work if it is removed?  Perhaps we should have a build without the
>> axis.jar.  I am not sure if this is safe.  I will talk to Tania about
>> this and see if I can do some analysis.
>>
>> Alternatively, if axis.jar is needed then we could make a build that
>> adds wsdl4j.jar and jaxrpc.jar.  This might be redundant but might not
>> require the analysis.
>>
>> Finally, you could build your zip file one directory up so that when
>> unzipped it adds the wsdl4j.jar and the jaxrpc.jar files to the
>> protege-owl plugin.
>>
>> The second solution is the safest but the first solution might be
>> better.
>>
>> -Timothy
>>
>>
>>
>> On 02/22/2012 06:18 PM, Daniel Elenius wrote:
>>> I have a question about how to handle jar files needed by Protege
>>> plugins.
>>>
>>> I have a plugin which needs axis.jar, wsdl4j.jar, and jaxrpc.jar.
>>> protege-owl already comes with axis.jar, but not the others. In my
>>> code, some method in axis.jar needs to call some methods in wsdl4j.jar
>>> and jaxrpc.jar. However, if I just put jaxrpc.jar and wsdl4j.jar in my
>>> own plugin directory, axis.jar can't find them (I get a
>>> ClassNotFoundException). Also putting axis.jar in my own plugin dir
>>> doesn't help: Protege wants to use the axis.jar in the protege-owl
>>> plugin dir anyway. Putting wsdl4j.jar and jaxrpc.jar in the
>>> protege-owl plugin dir solves the problem, but I would like to be able
>>> to just zip up my plugin dir and give it to people as a binary
>>> distribution.
>>>
>>> Is there any good solution to this?
>>>
>>> Daniel Elenius
>>> Computer Scientist
>>> SRI International
>>> http://csl.sri.com/people/elenius/
>>>
>>>
>>>
>>> _______________________________________________
>>> protege-owl mailing list
>>> [hidden email]
>>> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>>>
>>> Instructions for unsubscribing:
>>> http://protege.stanford.edu/doc/faq.html#01a.03
>> _______________________________________________
>> protege-owl mailing list
>> [hidden email]
>> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>>
>> Instructions for unsubscribing:
>> http://protege.stanford.edu/doc/faq.html#01a.03
>> _______________________________________________
>> protege-owl mailing list
>> [hidden email]
>> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>>
>> Instructions for unsubscribing:
>> http://protege.stanford.edu/doc/faq.html#01a.03
>
> _______________________________________________
> protege-owl mailing list
> [hidden email]
> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>
> Instructions for unsubscribing:
> http://protege.stanford.edu/doc/faq.html#01a.03

_______________________________________________
protege-owl mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-owl

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03