Hi Michael,
I'm seeing that I was doing things in a way that probably was not recommended.
I had:
1. installed jetty sudo yum install jetty 2. downloaded the war file to /usr/share/jetty/webapps/BaseX73.war 3. Create context xml here /usr/share/jetty/contexts/contexts/BaseX73.xml 4. started the server cd /usr/share/jetty/ and java -jar start.jar
This gave me access through at 8080 and I've been loading data using curl calls without issue. I had been using the jar file standalone and so I thought using the war file in a similar way would be fine. I suppose it might but I could not connect using oxygen this way.
I've since changed my approach to using the complete basex distribution although I've run into a few other issues. I suppose the first was that oxygen was asking for woodstox-core jars so I downloaded those and added them to the lib directory. Secondly the complete distribution doesn't come with the basex-xqj-0.9.2.jar so I've put that into the lib with the other jars, it makes me wonder though if the instructions "Add the following JAR files above with the *Add* Button: xqj-api-1.0.jar, xqj2-0.0.1.jar and basex-xqj-0.9.2.jar (the version names of the JAR file may differ) " are accurate give only the first 2 files are included in the zip.
Finally now I'm getting an error "Description: Could not initialize class net.xqj.basex.bin.m" I'm not sure how to resolve this one although I assume I'm missing something.
I've started the server using the gui, loaded files into a db and used the gui server administration interface to start the server.
Thoughts?
Thanks Much Alex
On Thu, Nov 22, 2012 at 1:12 PM, Michael Seiferle ms@basex.org wrote:
Hi Alex,
I can only help you with two quick guesses at the moment:
port 8080
looks like a kind of HTTP Port; the server by default runs on port: 1984 does this change anything?
- does changing your query to:
let $content := //MessageHeader return $content[1]
change anything?
I just tried to set up the oxygen integration as depicted in our wiki and it worked on Mac OS, using the 7.3 ZIP and the XQJ Drivers found @xqj.net I know this "it works on my machine" probably does not help you much, but I am confident we can find the cause of your problem :-)
Best Michael
Am 22.11.2012 um 00:47 schrieb Alex Muir alex.g.muir@gmail.com:
Same response...
On Wed, Nov 21, 2012 at 6:26 PM, Christian Grün <christian.gruen@gmail.com
wrote:
let $content := //MessageHeader return $content
You could try to directly address the database in your query:
let $content := db:open('DDEX')//MessageHeader return $content
Does this help? Christian ___________________________
I've got basex set up using jetty and can query within the firefox
browser
to return data for example using the url
http://localhost:8080/rest/DDEX?query=//MessageHeader
however my equivalent oxygen xquery does not return data and rather continues to run not stopping
I've recently downloaded the jars and configured the Data Source
Drivers as
file:/mnt/xslt_volume/i4EnrichV7/analysis/resources/libs/basex-xqj-1.2.3.jar
file:/mnt/xslt_volume/i4EnrichV7/analysis/resources/libs/xqj-api-1.0.jar file:/mnt/xslt_volume/i4EnrichV7/analysis/resources/libs/xqj2-0.1.0.jar
In the basex connection which is enabled I've got the following
settings
port 8080 databaseName DDEX logLevel description loginTimeout 6000 serverName localhost user admin password admin
I set up a trasformation scenario with BaseX transformer with the
following
xquery
--
Alex G. Muir Software Engineering Consultant Linkedin Profile : http://ca.linkedin.com/pub/alex-muir/36/ab7/125 Love African Kora Music? Take a moment to listen to Gambia's - Amadu Diabarte & Jali Bakary Konteh www.bafila.bandcamp.com Your support keeps Africa's griot tradition alive... Cheers!
BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk