October 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2708) DataRolePolicyDecider configuration

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2708?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2708. ----------------------------------- Resolution: Done Defaulted the bean properties to system properties and updated the admin guide. > DataRolePolicyDecider configuration > ----------------------------------- > > Key: TEIID-2708 > URL: https://issues.jboss.org/browse/TEIID-2708 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.6 > > > In the conversion over to AS 7 the bean properties for DataRolePolicyDecider were not added to the configuration. More than likely this was because the bean itself is pluggable. > We either need to add these properties to the configuration or add an alternative mechanism for setting them (system and/or vdb properties would probably be just fine). -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2694) Support for Blob Input in Teiid REST services

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2694?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2694: ------------------------------------- I may have done it due to simplicity as we are dynamically generating the byte code for the WAR file > Support for Blob Input in Teiid REST services > --------------------------------------------- > > Key: TEIID-2694 > URL: https://issues.jboss.org/browse/TEIID-2694 > Project: Teiid > Issue Type: Enhancement > Affects Versions: 8.5 > Environment: EAP 6.1 Alpha , Teiid 8.5 > Reporter: Madhu Garimilla > Assignee: Steven Hawkins > > We are trying to upload large files as Blobs using Teiid REST service through VDB. Though we are writing the Blob objects to HttpUrlConnection object, it is not received on REST method. As per the conversation in the thread "https://community.jboss.org/thread/232840" Current parameter handling is done through strings and needs be enhanced to support Blob objects. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2708) DataRolePolicyDecider configuration

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2708?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2708: ------------------------------------- ok, sounds good > DataRolePolicyDecider configuration > ----------------------------------- > > Key: TEIID-2708 > URL: https://issues.jboss.org/browse/TEIID-2708 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.6 > > > In the conversion over to AS 7 the bean properties for DataRolePolicyDecider were not added to the configuration. More than likely this was because the bean itself is pluggable. > We either need to add these properties to the configuration or add an alternative mechanism for setting them (system and/or vdb properties would probably be just fine). -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2708) DataRolePolicyDecider configuration

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2708?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2708: --------------------------------------- Ok, given that these properties basically exist to preserve backwards compatibility it seems easiest to just convert them to system properties. Any objections? > DataRolePolicyDecider configuration > ----------------------------------- > > Key: TEIID-2708 > URL: https://issues.jboss.org/browse/TEIID-2708 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.6 > > > In the conversion over to AS 7 the bean properties for DataRolePolicyDecider were not added to the configuration. More than likely this was because the bean itself is pluggable. > We either need to add these properties to the configuration or add an alternative mechanism for setting them (system and/or vdb properties would probably be just fine). -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2696) Update Teiid datasource examples to be fully parameterized

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2696?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2696: --------------------------------------- Should this be resolved? > Update Teiid datasource examples to be fully parameterized > ---------------------------------------------------------- > > Key: TEIID-2696 > URL: https://issues.jboss.org/browse/TEIID-2696 > Project: Teiid > Issue Type: Enhancement > Components: Build/Kits > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > Fix For: 8.4.1, 8.6 > > > Change the example datasources to be parameterized, and add an associated properties file so that to install, run: > jboss-cli.sh -c --file={datasource}-ds.cli --properties=/{datasource}-ds.properties -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2709) Quickstart - drools-integration uses drools 5 instead of drools 6

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2709?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2709: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1022650|https://bugzilla.redhat.com/show_bug.cgi?id=1022650] from NEW to ASSIGNED > Quickstart - drools-integration uses drools 5 instead of drools 6 > ------------------------------------------------------------------- > > Key: TEIID-2709 > URL: https://issues.jboss.org/browse/TEIID-2709 > Project: Teiid > Issue Type: Enhancement > Components: Quick Starts > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > > The drools-integration quick start uses drools 5, instead of drools 6. > And its not a matter of swapping out the versions due to api changes drools 6. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2709) Quickstart - drools-integration uses drools 5 instead of drools 6

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2709?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2709: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1022650 > Quickstart - drools-integration uses drools 5 instead of drools 6 > ------------------------------------------------------------------- > > Key: TEIID-2709 > URL: https://issues.jboss.org/browse/TEIID-2709 > Project: Teiid > Issue Type: Enhancement > Components: Quick Starts > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > > The drools-integration quick start uses drools 5, instead of drools 6. > And its not a matter of swapping out the versions due to api changes drools 6. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2709) Quickstart - drools-integration uses drools 5 instead of drools 6

by Van Halbert (JIRA)

Van Halbert created TEIID-2709: ---------------------------------- Summary: Quickstart - drools-integration uses drools 5 instead of drools 6 Key: TEIID-2709 URL: https://issues.jboss.org/browse/TEIID-2709 Project: Teiid Issue Type: Enhancement Components: Quick Starts Affects Versions: 8.4.1 Reporter: Van Halbert Assignee: Van Halbert The drools-integration quick start uses drools 5, instead of drools 6. And its not a matter of swapping out the versions due to api changes drools 6. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2708) DataRolePolicyDecider configuration

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2708?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2708: ---------------------------------- Workaround Description: The new default for allow create temporary tables can be worked around by adding the create temporary table permission to an any authenticated role for each vdb. The workaround for function access is similar, but requires a permission for each udf. Workaround: Workaround Exists > DataRolePolicyDecider configuration > ----------------------------------- > > Key: TEIID-2708 > URL: https://issues.jboss.org/browse/TEIID-2708 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.6 > > > In the conversion over to AS 7 the bean properties for DataRolePolicyDecider were not added to the configuration. More than likely this was because the bean itself is pluggable. > We either need to add these properties to the configuration or add an alternative mechanism for setting them (system and/or vdb properties would probably be just fine). -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2656) Teiid OData Servlet throws java.lang.NullPointerException on every GET

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2656?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2656: ------------------------------------- BTW, for development only version of DV6 (production version of Teiid ) can also be downloaded at http://www.jboss.org/products/datavirt.html, but no community version. But as Steve mentions, using EAP 6 alpha, has same terms and conditions as 7.1.1 as per the licensing concerns. > Teiid OData Servlet throws java.lang.NullPointerException on every GET > ---------------------------------------------------------------------- > > Key: TEIID-2656 > URL: https://issues.jboss.org/browse/TEIID-2656 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.3, 8.4 > Environment: Windows 7 64 bit > Oracle JDK 1.7.0 update 17 > JBoss AS 7.1.1 + Teiid 8.3 (both resteasy-jaxrs 2.3.5 and 2.3.7) > JBoss EAP 6.1 + Teiid 8.4 (resteasy-jaxrs 2.3.6) > Reporter: John Muller > Assignee: Steven Hawkins > Labels: final > Fix For: 8.4.1, 8.5 > > Attachments: server.log, Teiid_8.4_on_JBoss_EAP_6.1Alpha_RHEL6.log > > > A simple GET on any Teiid 8.3 or 8.4 OData ReST resource results in a Null Pointer: > 11:43:20,166 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/odata].[Resteasy]] (http-localhost-127.0.0.1-8080-2) Servlet.service() for servlet Resteasy threw exception: java.lang.NullPointerException > at com.ctc.wstx.sw.BaseStreamWriter.writeCharacters(BaseStreamWriter.java:447) > at org.codehaus.stax2.ri.Stax2EventWriterImpl.add(Stax2EventWriterImpl.java:124) > at org.odata4j.stax2.staximpl.StaxXMLWriter2.writeText(StaxXMLWriter2.java:108) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:] > at org.odata4j.format.xml.AtomErrorFormatWriter.writeError(AtomErrorFormatWriter.java:31) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:] > at org.odata4j.format.xml.AtomErrorFormatWriter.write(AtomErrorFormatWriter.java:20) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:] > at org.odata4j.format.xml.AtomErrorFormatWriter.write(AtomErrorFormatWriter.java:15) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:] > at org.teiid.odata.ODataExceptionMappingProvider.toResponse(ODataExceptionMappingProvider.java:55) [classes:] > at org.teiid.odata.ODataExceptionMappingProvider.toResponse(ODataExceptionMappingProvider.java:42) [classes:] > at org.jboss.resteasy.core.SynchronousDispatcher.executeExceptionMapper(SynchronousDispatcher.java:344) [resteasy-jaxrs-2.3.7.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.unwrapException(SynchronousDispatcher.java:373) [resteasy-jaxrs-2.3.7.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:362) [resteasy-jaxrs-2.3.7.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:233) [resteasy-jaxrs-2.3.7.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:209) [resteasy-jaxrs-2.3.7.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:557) [resteasy-jaxrs-2.3.7.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:524) [resteasy-jaxrs-2.3.7.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:126) [resteasy-jaxrs-2.3.7.Final.jar:] > at org.teiid.odata.ODataServletContainerDispatcher.service(ODataServletContainerDispatcher.java:97) [classes:] > at org.teiid.odata.ODataServlet.service(ODataServlet.java:61) [classes:] > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.7.Final.jar:] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:489) [jbossweb-7.0.13.Final.jar:] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] > at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_17] -- 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

11 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2013