Accessing Tamino

Post by **mob** » Wed Jun 21, 2006 11:28 am

Hello,

I have coded some simple XQuery Tamino extenstion classes (for Saxonica) which work when I run stand alone. When I try to integrate with Oxygen (run my query from within oxygen) I am getting strange exception (com.softwareag.tamino.db.api.invocation.http.THTTPCommunicationException) although I set up the necessary jars)
I actually put all jars (except saxon8.jar and log4j.jar) I used in the standalone test to oxygen/lib folder.

Has anyone some suggestion how to do this integration ?

(I am using Mac OS X 10.4.6, JVM 1.5, Oxygen 7.2, Tamino API 4.2.xxx)

thanks in advance,
Balazs

Post by **sorin_ristache** » Wed Jun 21, 2006 12:33 pm

Hello,

Is com.softwareag.tamino.db.api.invocation.http.THTTPCommunicationException contained in one of the jars copied in [oXygen7.2-install-folder]/lib ? Did you restart <oXygen/> after copying the jar files ?

Copying them in [oXygen7.2-install-folder]/lib and restarting is one way of configuring XQuery or XSLT extensions in <oXygen/> but there is an easier way: configure them directly in the transformation scenario using the Extensions button of the Edit scenario dialog. This way you don't have to restart the application and you can change the actual files on disk between two transformations which use the extensions, because they are loaded and used only for the current transformation.

Regards,
Sorin

Post by **mob** » Wed Jun 21, 2006 1:44 pm

Hello,
Yes, the Exception class is in the jar I put in the lib folder. The reason I used the lib folder is that during xquery debugging the extension jars I added were lost after each restart of oxygen.

regards,
Balazs

Post by **mob** » Wed Jun 21, 2006 1:46 pm

I also did restart oxygen.
Balazs

Post by **mob** » Wed Jun 21, 2006 1:54 pm

This is the last/innermost part of the exception:
com.softwareag.tamino.db.api.invocation.http.THTTPCommunicationException( message: HTTP communication failure. ResponseCode: 0, messageText: null, tag: JavaTaminoAPI_4_2_0_60, java: 1.5.0_06, os: Mac OS X 10.4.6 ):

at com.softwareag.tamino.db.api.invocation.http.THTTPInvocation.getInputStream(Unknown Source)
at com.softwareag.tamino.db.api.invocation.http.THTTPInvocation.doGetInvoke(Unknown Source)
at com.softwareag.tamino.db.api.invocation.http.THTTPInvocation.doInvokeReal(Unknown Source)
at com.softwareag.tamino.db.api.invocation.http.THTTPInvocation.doInvoke(Unknown Source)

Post by **sorin_ristache** » Wed Jun 21, 2006 2:01 pm

Hello,

mob wrote:The reason I used the lib folder is that during xquery debugging the extension jars I added were lost after each restart of oxygen.

You should apply the same transformation in the Debugger perspective as in the main Editor perspective, that is you should start the Debugger using the "Debug Scenario" action. This way the extensions are stored in the scenario and preserved when the application is restarted. Usually you add the extensions directly in the Debugger perspective for a one time test when you don't run a scenario.

What is the error message of the HTTP exception ? Does the connection have to go through a proxy server ? In this case is the proxy configured correctly in Options -> Preferences -> HTTP/FTP/Proxy Configuration ? Can you run a simple XQuery against the Tamino server without the extensions which you coded ?

Regards,
Sorin

Post by **sorin_ristache** » Wed Jun 21, 2006 2:10 pm

mob wrote:com.softwareag.tamino.db.api.invocation.http.THTTPCommunicationException( message: HTTP communication failure. ResponseCode: 0, messageText: null

I think you will have to provide a more detailed reason for the exception. A null message text is not helpful. What does the 0 response code mean ?

Regards,
Sorin

Post by **mob** » Wed Jun 21, 2006 2:11 pm

Thanks for the suggestion on extension settings.

On Tamino: I do not understand your suggestion: I am not aware of any Tamino connection capability in oxygen. Is there ?

My scenario is the following:

I have scripted some generic XQuery code (not Tamino XQuery)
I am accessing my Java classes using Saxonica extension capabilities
The constructor of my class gets called alright, (I have put logging messages) it recieves the correct connection parameters and attempts to call: this.i_TConnection = TConnectionFactory.getInstance()
.newConnection(this.i_DatabaseURL, this.i_UserID,
this.i_Password);

At this point I receive the exception I have posted. This same code executes fine if I directly call it via java command line embedding the construction in a test class.

regards,
Balazs

Post by **mob** » Wed Jun 21, 2006 2:13 pm

Sorr: this is Tamino internals. I have no means of getting more on this. My hope was that someone inside Oxygen has already done some experiments with Tamino - as I have seen there is some support of other XML database servers like eXist.

regards,
Balazs

Post by **mob** » Wed Jun 21, 2006 2:15 pm

The thread on Http may lead somewhere. I have seen there are some settings available in Oxygen. Could there be any interference between Tamino classes wanting to do some Http invocations and Oxygen classes/settings ?

My environment is quite simple: no proxies, no specialties.

regards,
Balazs

Post by **sorin_ristache** » Wed Jun 21, 2006 2:45 pm

mob wrote:I do not understand your suggestion: I am not aware of any Tamino connection capability in oxygen. Is there ?

There is no special configuration for the Tamino server. I was talking about HTTP connections in general.

mob wrote:I have seen there are some settings available in Oxygen. Could there be any interference between Tamino classes wanting to do some Http invocations and Oxygen classes/settings ?

The HTTP communication between <oXygen/> and Tamino server should go without errors as long as you use the correct URL and Tamino conforms to the HTTP protocol. Please contact us to support at oxygenxml dot com to help you check that by enabling logging of the HTTP traffic from <oXygen/>.

Before that you should see this thread on the Tamino forum and check that the URL for connecting to Tamino is correct by trying the same URL in a Web browser but adding _diagnose=ping to your URL as instructed on the Tamino forum.

Regards,
Sorin

Post by **mob** » Thu Jun 22, 2006 10:25 am

Hello Sorin,

I did try the pinging as suggested by the Tamino forum you pointed me to. This was the result:
<ino:response>
<ino:request>
<ino:diagnose ino:request-type="ping"/>
</ino:request>
<ino:message>
<ino:messageline ino:subject="Server">is alive</ino:messageline>
</ino:message>
</ino:response>

I have copy/pasted the URL from my XQuery to the browser url and put the ?_diagnose=ping at the end of the url and got this fine message.

As I wrote in my initial mail - the same XQuery scipt when invoked from outside Oxygen (a java test class calling Saxonica) my query works fine - so that suggests to me the problem might be some incompatible class references, missing jars, or some configuration problem. The most likely was classpath but I guess I did succeed to copy the 4 jars from my eclipse lib folder to oxygen. I tried both methods (oxygen lib folder and configuration of extension classes) but each case I got back the server not available exception. That is where I am now.

regards,
Balazs

Post by **sorin_ristache** » Thu Jun 22, 2006 10:32 am

Hello,

sorin wrote:The HTTP communication between <oXygen/> and Tamino server should go without errors as long as you use the correct URL and Tamino conforms to the HTTP protocol. Please contact us to support at oxygenxml dot com to help you check that by enabling logging of the HTTP traffic from <oXygen/>.

Please contact us at support at oxygenxml dot com.

Regards,
Sorin