Re: [basex-talk] suddenly...java function x is unknown

[Erik Peterson]

Issue solved. I think it was java on my system...I updated and restarted
and it worked. When osx restarted it put me in an older basex directory, so
that sent me on rabbit trail. Still not sure why it lost the jars the first
time though.

On Thu, Mar 30, 2017 at 5:09 PM, Erik Peterson  wrote:

> I've been integrating basex with 3rd party java jar files by dropping them
> in the basex/lib directory. This has worked fine until today when I now git
> "java function x is unknown". I've...
> - re-pulled everything from our repo to make sure all binaries are as they
> were when working
> - restarted osx
> - updated java
>
> - using BaseX VERSION 8.6.1 (February 24, 2017)
>
> It's working on other dev machines but not mine. Why would BaseX stop
> loading the classes from the lib jar files? Is there a better way I should
> be deploying jars? Thanks.
>



-- 
*Erik Peterson*
President, Ardec LLC
281-804-9023 | e...@ardec.com

Re: [basex-talk] suddenly...java function x is unknown

[Joe Wicentowski]

A guess out of left field: do you have two versions of the same library on
your class path?

On Thu, Mar 30, 2017 at 7:10 PM Erik Peterson  wrote:

> I've been integrating basex with 3rd party java jar files by dropping them
> in the basex/lib directory. This has worked fine until today when I now git
> "java function x is unknown". I've...
> - re-pulled everything from our repo to make sure all binaries are as they
> were when working
> - restarted osx
> - updated java
>
> - using BaseX VERSION 8.6.1 (February 24, 2017)
>
> It's working on other dev machines but not mine. Why would BaseX stop
> loading the classes from the lib jar files? Is there a better way I should
> be deploying jars? Thanks.
>
-- 
Sent from my iPhone

[basex-talk] suddenly...java function x is unknown

[Erik Peterson]

I've been integrating basex with 3rd party java jar files by dropping them
in the basex/lib directory. This has worked fine until today when I now git
"java function x is unknown". I've...
- re-pulled everything from our repo to make sure all binaries are as they
were when working
- restarted osx
- updated java

- using BaseX VERSION 8.6.1 (February 24, 2017)

It's working on other dev machines but not mine. Why would BaseX stop
loading the classes from the lib jar files? Is there a better way I should
be deploying jars? Thanks.

Re: [basex-talk] BaseX hanging on REST/XQ pipelining

[Andy Bunce]

Hi Erik,

This thread may be relevant [1]. Have you tried  client:execute in place of
fetch REST?

/Andy

[1] http://www.mail-archive.com/basex-talk@mailman.uni-konstanz.de/msg08962.html


On 30 March 2017 at 22:31, Erik Peterson  wrote:

> It seems like on some RESTXQ/REST pipelining (restxq calling another
> restxq api) causes basex to hang. In this scenario a mock client was
> created to test the system. A test was written to automate mock client
> requests. A restxq path was created run tests. More specifically...
>
> 1) Browse to http://localhost:8984/unit-test/test where last parameter
> "test" maps the directiory where unit tests are located.
> 2) #1 is handled by a RESTXQ function where a REST URL is fetched:
> fetch(http://localhost:8984/rest?command=test+../webapp/mock-client/test)
> 3) #2 is handled by a unit-test that fetches a mock-client URL
> fetch(http://localhost:8984/mock-client/do-something)
> 4) #3 is handled by a the mock-client hitting the system
> fetch(http://localhost:8984/system/do-something)
>
> - #3 and #4 (mock-client) work great
> - #2 (the unit-test) work great when running tests from command line OR
> when the test is a simple unit:assert(). But basex hangs otherwise
>
> Thanks for any insight on why the system calling back to itself may cause
> a system hang.
>

[basex-talk] BaseX hanging on REST/XQ pipelining

[Erik Peterson]

It seems like on some RESTXQ/REST pipelining (restxq calling another restxq
api) causes basex to hang. In this scenario a mock client was created to
test the system. A test was written to automate mock client requests. A
restxq path was created run tests. More specifically...

1) Browse to http://localhost:8984/unit-test/test where last parameter
"test" maps the directiory where unit tests are located.
2) #1 is handled by a RESTXQ function where a REST URL is fetched:
fetch(http://localhost:8984/rest?command=test+../webapp/mock-client/test)
3) #2 is handled by a unit-test that fetches a mock-client URL
fetch(http://localhost:8984/mock-client/do-something)
4) #3 is handled by a the mock-client hitting the system
fetch(http://localhost:8984/system/do-something)

- #3 and #4 (mock-client) work great
- #2 (the unit-test) work great when running tests from command line OR
when the test is a simple unit:assert(). But basex hangs otherwise

Thanks for any insight on why the system calling back to itself may cause a
system hang.