[teiid-issues] [JBoss JIRA] (TEIID-2268) NullPointer Exception genetated while querying table built from WSDL query

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728631#comment-12728631 ] 

Steven Hawkins commented on TEIID-2268:
---------------------------------------

I had mistakenly thought this situation would have been handled automatically, since the parameter is optional.  However since we use the old metadata we don't know about the new parameter in the engine and aren't supplying the default to the translator.

Dynamic vdbs are unaffected.

So we should address this on the Teiid side.


                
> NullPointer Exception genetated while querying table built from WSDL query
> --------------------------------------------------------------------------
>
>                 Key: TEIID-2268
>                 URL: https://issues.jboss.org/browse/TEIID-2268
>             Project: Teiid
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 8.2
>            Reporter: Paul Richardson
>            Assignee: Steven Hawkins
>         Attachments: server.log
>
>
> Using designer 8, I deploy the state service example models (found [here|https://github.com/phantomjinx/teiid-soap-example]) to an 8.2 beta1 teiid server. The models deploy successfully and the teiid connection in designer displays the catalog and stateService/stateServiceView schemas.
> However, running the following query
> {{exec stateServiceView.getAllStateInfo();}}
> results in a generic TeiidException in designer's status view.
> This exception comes from a NullPointerException that is displayed in the jboss server log.
> The log of the jboss server is attached, detailing the following events:
> # start of the server with the stateService data source and USStates vdb already deployed
> # connection and execution of the query from designer

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira