[darnowsi]

Ted,

I chamge the jndi name as you suggested and now the lookup work and connection to the vdb works.

However the call statment is returned with a paser error from teiid sonce the procedure name is never loaded correctly. This appears to be related to the fact that the wsdl queue operation name is returned as a null from the wsdl. Could this be something wrong with the WSDL that was generated?                 

Object wsdlOperationQName =

webServiceContext.getMessageContext().get(MessageContext.WSDL_OPERATION

);

Also I noticed in the web service procedure generated by desinger the following error:

CREATE VIRTUAL PROCEDURE

BEGIN

DECLARE string

VARIABLES.IN_exampleVar;

SELECT * FROM

wrtsview_Output_View.base_OutputView;

END

The SELECT transformation is valid, but NOT fully reconciled:

- The number of transformation output symbols is zero.

It generated and output parameter for this procedure as well.

Is this something that should be changed manually?

[tejones]

Steve,

That second error was corrected with Teiid Designer 8.1.alpha2 (just released today). I would recommend giving that a try: http://www.jboss.org/teiiddesigner/downloads.html

Last I looked, the page says Aplha1 but the download link is really Alpha2 (we will correct that).

Thanks,

Ted

[darnowsi]

Ted,

I updated to Alpha2 and it did correct the second problem. BTW it was named Alpha 2.

Any insight on the first problem? I noticed the following in code. When I set braekpoint at this location it never gets hit????

@

javax.annotation.

Resource

protected void

setWebServiceContext(WebServiceContext wsc) {

webServiceContext

= wsc;

}

[darnowsi]

Ted,

Some more info that maybe helpful.

When I add the following else statment to the code I can see the expected response from my data source in xml format returned in response buffer. However if a remove all breakpoints to avoid a timeout only a SOAP message is returned to my SOAP UI client however the body of the message is empty??

// Get procedure name from properties object based on operation name

if (wsdlOperationQName != null

) {

wsdlOperation

= ((QName) wsdlOperationQName).getLocalPart();

procedureName =

properties.getProperty(wsdlOperation

);

}

else

procedureName =

properties.getProperty("getNYC_HEAP_CASES"

);

[tejones]

Steve,

It looks like there is an issue when there is no parameter defined for the procedure. I get a parsing issue when I execute a procedure without parameters in the generated WAR, but a procedure with a parameter work just fine. I will log this and fix for the next iteration (which should be Beta1 in the next week or so).

In the meantime, try adding a parameter to your web service procedure as a workaround. You can also add a primary key to the table you are generating the web service for and that will be added as a parameter for you.

Thanks for discovering this.

Ted

[darnowsi]

Ted,

I added a primary key to the table in the view used to generate the web service and it now works!

Thanks to you and Ramesh for all your help! I will try the beta when available.

A copy of questions. I still have to copy the xsd files for the wsdl from the project folder to the data folder for my configuration. Is this the case in your testing as well? If so will it be addressed in the beta as well?. Also I am still building the war manually since the teiid desigenr does not have access to a jdk. Are you adding the -vm startup parameter to eclipse so that the war is generated by teiid wizard? Is the only way to enable this to add the eclipse startup parameter. Does this work as well as long as there is an input parmeter for the web service? Also do you have any insight if these problems are resovled in Read Hat 5.3. We have a customer who is in the process of getting licenses for Red Hat Data Services 5.3?

Steve

[tejones]

Steve,

That's great you were able to get it working.

A copy of questions. I still have to copy the xsd files for the wsdl from the project folder to the data folder for my configuration. Is this the case in your testing as well? If so will it be addressed in the beta as well?.

I am not seeing this behavior. What OS are you running on? I'm on a Mac.

Also I am still building the war manually since the teiid desigenr does not have access to a jdk. Are you adding the -vm startup parameter to eclipse so that the war is generated by teiid wizard? Is the only way to enable this to add the eclipse startup parameter. Does this work as well as long as there is an input parameter for the web service?

The -vm parameter will work every time.. but if the IDE has access to a JDK, this is not needed. An alternative is to add the -vm option in the eclipse.ini that point to a JDK. The input   parameter is an un-related issue.

Also do you have any insight if these problems are resolved in Read Hat 5.3. We have a customer who is in the process of getting licenses for Red Hat Data Services 5.3?

There is another rollup for 5.3 in approx 6-8 weeks. I will backport a fix for the "no parameter" issue in that rollup.

Thanks,

Ted

[darnowsi]

Ted,

I went and used the -vm option in the eclipse shortcut and verified that worked for me. However, I still had to copy the xsd files into the data/wsdl/<warname>folder manually. This was after copying the war to the deployment folder. My OS is  Windows 7 Enterprise. These fules are in the war generated from designer.

Will you be backporting to 5.3  the fixes for the problem in 7.8 with deployment exceptions ( see begining of this thread) and the fix to 8.1 alpha for the problem of non-reconciliation of procedure parameters as well?

Steve

[tejones]

Steve,

The issue with the XSD files not be copied into the generated WAR seems to be Windows specific when the workspace location includes spaces. The work-around is to choose a workspace location without spaces when using Windows. I have logged a Jira to capture the issue and will backport for a future 5.3 rollup when resolved: https://issues.jboss.org/browse/TEIIDDES-1642. I also suspect your deployment errors may have be related to this as well.

The parameter-less procedure issue has been resolved (https://issues.jboss.org/browse/TEIIDDES-1498) and will be in the next Designer 8.1 release. I will also backport the fix for a future 5.3 rollup.

Thanks,

Ted