July 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1091) Add remaining SQL/XML functions

by Steve Hawkins (JIRA)

Add remaining SQL/XML functions ------------------------------- Key: TEIID-1091 URL: https://jira.jboss.org/browse/TEIID-1091 Project: Teiid Issue Type: Sub-task Components: Query Engine Affects Versions: 7.1 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.1 We should add the remaining functions, xmlparse, xmlserialize, xmlroot, etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1138) Add support to call binary web services

by Steve Hawkins (JIRA)

Add support to call binary web services --------------------------------------- Key: TEIID-1138 URL: https://jira.jboss.org/browse/TEIID-1138 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Affects Versions: 7.1 Reporter: Steve Hawkins Assignee: Steve Hawkins We should add support to call http web services that return binary results. One problem is that JBoss WS does not support DataSource based calls. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIID-1027) Use i18n for internationalization

by Van Halbert (JIRA)

Use i18n for internationalization ---------------------------------- Key: TEIID-1027 URL: https://jira.jboss.org/jira/browse/TEIID-1027 Project: Teiid Issue Type: Feature Request Components: Documentation, Server Affects Versions: 6.0.0 Reporter: Van Halbert Assignee: Steven Hawkins Fix For: 7.1 The components should be internationalized according to I18N standards. However, initially it will be limited to making the doc and product I18N available in English. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

5
8
0 / 0

[JBoss JIRA] Created: (TEIID-1133) Error creating SSL Socket Factory for client invoker: Error initializing socket factory SSL context: Can not find truststore url.

by Ramesh Reddy (JIRA)

Error creating SSL Socket Factory for client invoker: Error initializing socket factory SSL context: Can not find truststore url. --------------------------------------------------------------------------------------------------------------------------------- Key: TEIID-1133 URL: https://jira.jboss.org/browse/TEIID-1133 Project: Teiid Issue Type: Bug Components: Salesforce Connector Affects Versions: 7.0 Reporter: Ramesh Reddy Fix For: 7.0 When SF query executed in the error message shows up in the in the log file. The query still works fine. Error creating SSL Socket Factory for client invoker: Error initializing socket factory SSL context: Can not find truststore url. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1055) Secure profile service access

by Ramesh Reddy (JIRA)

Secure profile service access ----------------------------- Key: TEIID-1055 URL: https://jira.jboss.org/jira/browse/TEIID-1055 Project: Teiid Issue Type: Task Components: AdminApi Affects Versions: 7.0 Reporter: Ramesh Reddy Fix For: 7.0 As of 7.0 M3 release, the "Profile Service" access is not secure. Currently the JOPR plug-in and Teiid Admin API, force users to authenticate with "jmx-console" security domain, both these do not prevent the direct access to the "Profile Service" EJB directly. Profile Service can be deployed as secure EJB, such that it would require a login context to be authenticated before user has access to this bean. This needs to be configured and tested. Also document, how to configure the profile service as secure service. Also, AdminFactory class, which provides Admin connections, need to work with secure "Profile Service". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

5
8
0 / 0

[JBoss JIRA] Created: (TEIID-1142) Teiid should work with EAP 5.1

by Ramesh Reddy (JIRA)

Teiid should work with EAP 5.1 ------------------------------- Key: TEIID-1142 URL: https://jira.jboss.org/browse/TEIID-1142 Project: Teiid Issue Type: Task Components: Build/Kits Affects Versions: 7.0 Reporter: Ramesh Reddy Priority: Critical Fix For: 7.1 Teiid kits must be able deploy inside the JBoss EAP 5.1 and work correctly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

4
7
0 / 0

[JBoss JIRA] Created: (TEIID-1159) Exception Creating Data Source Using Admin API

by Dan Florian (JIRA)

Exception Creating Data Source Using Admin API ---------------------------------------------- Key: TEIID-1159 URL: https://jira.jboss.org/browse/TEIID-1159 Project: Teiid Issue Type: Bug Components: AdminApi Affects Versions: 7.0 Environment: Macintosh OS X 10.6.4 Reporter: Dan Florian Assignee: Steve Hawkins Priority: Critical >From Teiid Designer code I am calling AdminApi method createDataSource(String, String, Properties) but I get the below exceptions. One problem I see in the FileNotFoundException messages is that the application is looking for a path that has spaces where the file system actually has plus signs. So for instance, on the file system this folder does exist: /var/folders/bm/bmFOC5C9EDeb7QfYSp1aWk+++TI/. [AdminComponentException]Failed to process template. 1 [AdminComponentException]Failed to process template. 2 [RuntimeException]Failed to process template. 3 [FileNotFoundException]/var/folders/bm/bmFOC5C9EDeb7QfYSp1aWk TI/-Tmp-/LocalJdbcConnectorTemplate5132020427731959654-ds.xml at org.teiid.client.util.ExceptionUtil.convertException(ExceptionUtil.java:72) at org.teiid.jboss.deployers.RuntimeEngineDeployer$1.invoke(RuntimeEngineDeployer.java:191) at $Proxy262.createDataSource(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.teiid.transport.ServerWorkItem.run(ServerWorkItem.java:81) at org.teiid.dqp.internal.process.DQPWorkContext$2.call(DQPWorkContext.java:190) at org.teiid.dqp.internal.process.DQPWorkContext$2.call(DQPWorkContext.java:187) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:176) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:187) at org.teiid.transport.SocketClientInstance.processMessagePacket(SocketClientInstance.java:160) at org.teiid.transport.SocketClientInstance.receivedMessage(SocketClientInstance.java:149) at org.teiid.transport.SSLAwareChannelHandler.messageReceived(SSLAwareChannelHandler.java:210) at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:98) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:560) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:796) at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:117) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:560) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:796) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:391) at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:317) at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:299) at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:216) at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:560) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:555) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:345) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:332) at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:323) at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:275) at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:196) at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:637) Caused by: [AdminComponentException]Failed to process template. 1 [RuntimeException]Failed to process template. 2 [FileNotFoundException]/var/folders/bm/bmFOC5C9EDeb7QfYSp1aWk TI/-Tmp-/LocalJdbcConnectorTemplate5132020427731959654-ds.xml at org.teiid.adminapi.jboss.Admin.createDataSource(Admin.java:630) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.teiid.logging.LogManager$LoggingProxy.invoke(LogManager.java:121) at org.teiid.jboss.deployers.RuntimeEngineDeployer$1.invoke(RuntimeEngineDeployer.java:185) ... 36 more Caused by: java.lang.RuntimeException: Failed to process template. at org.jboss.profileservice.management.AbstractTemplateCreator.checkComplete(AbstractTemplateCreator.java:197) at org.jboss.profileservice.management.AbstractTemplateCreator.distribute(AbstractTemplateCreator.java:164) at org.jboss.profileservice.management.AbstractTemplateCreator.applyTemplate(AbstractTemplateCreator.java:102) at org.jboss.profileservice.management.ManagementViewImpl.applyTemplate(ManagementViewImpl.java:1361) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:97) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891) at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) at org.jboss.remoting.Client.invoke(Client.java:1724) at org.jboss.remoting.Client.invoke(Client.java:629) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aop.generatedproxies.AOPProxy$3.applyTemplate(AOPProxy$3.java) at org.teiid.adminapi.jboss.Admin.createDataSource(Admin.java:626) ... 42 more Caused by: java.io.FileNotFoundException: /var/folders/bm/bmFOC5C9EDeb7QfYSp1aWk TI/-Tmp-/LocalJdbcConnectorTemplate5132020427731959654-ds.xml at org.jboss.net.protocol.file.FileURLConnection.connect(FileURLConnection.java:105) at org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:112) at org.jboss.virtual.plugins.context.AbstractURLHandler.openStream(AbstractURLHandler.java:203) at org.jboss.virtual.VirtualFile.openStream(VirtualFile.java:230) at org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.getInputStream(VirtualFileURLConnection.java:93) at java.net.URL.openStream(URL.java:1010) at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.distribute(StreamingDeploymentTarget.java:105) at org.jboss.profileservice.management.upload.DeploymentProgressImpl.distribute(DeploymentProgressImpl.java:177) at org.jboss.profileservice.management.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:82) at org.jboss.profileservice.management.AbstractTemplateCreator.distribute(AbstractTemplateCreator.java:161) at org.jboss.profileservice.management.AbstractTemplateCreator.applyTemplate(AbstractTemplateCreator.java:102) at org.jboss.profileservice.management.ManagementViewImpl.applyTemplate(ManagementViewImpl.java:1361) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:97) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891) at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) at org.jboss.remoting.Client.invoke(Client.java:1724) at org.jboss.remoting.Client.invoke(Client.java:629) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aop.generatedproxies.AOPProxy$3.applyTemplate(AOPProxy$3.java) at org.teiid.adminapi.jboss.Admin.createDataSource(Admin.java:626) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.teiid.logging.LogManager$LoggingProxy.invoke(LogManager.java:121) at org.teiid.jboss.deployers.RuntimeEngineDeployer$1.invoke(RuntimeEngineDeployer.java:185) at $Proxy262.createDataSource(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.teiid.transport.ServerWorkItem.run(ServerWorkItem.java:81) at org.teiid.dqp.internal.process.DQPWorkContext$2.call(DQPWorkContext.java:190) at org.teiid.dqp.internal.process.DQPWorkContext$2.call(DQPWorkContext.java:187) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:176) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:187) at org.teiid.transport.SocketClientInstance.processMessagePacket(SocketClientInstance.java:160) at org.teiid.transport.SocketClientInstance.receivedMessage(SocketClientInstance.java:149) at org.teiid.transport.SSLAwareChannelHandler.messageReceived(SSLAwareChannelHandler.java:210) at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:98) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:560) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:796) at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:117) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:560) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:796) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:391) at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:317) at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:299) at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:216) at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:560) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:555) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:345) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:332) at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:323) at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:275) at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:196) at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:637) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:72) ... 49 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (TEIID-1178) Jopr VDB loading error when Data Source is not available

by Ramesh Reddy (JIRA)

Jopr VDB loading error when Data Source is not available -------------------------------------------------------- Key: TEIID-1178 URL: https://jira.jboss.org/browse/TEIID-1178 Project: Teiid Issue Type: Bug Components: Jopr Plugin Affects Versions: 7.1 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.1 While loading a dynamic VDB, that does not have a DS file configured correctly or while the database is down, the following exception shows up when the "admin-console" is loaded. java.lang.IllegalStateException: Deployment file ':/home/rareddy/testing/jboss-5.1.0.GA/server/default/deploy/teiid-artifacts/portfolio-vdb.xml' for Teiid Virtual Database does not exist. at org.teiid.rhq.plugin.Facet.discoverDeployedPackages(Facet.java:429) at sun.reflect.GeneratedMethodAccessor375.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1030) Provide ability to retrieve a VDB archive from ModeShape repository and then deploy the Teiid runtime.

by Van Halbert (JIRA)

Provide ability to retrieve a VDB archive from ModeShape repository and then deploy the Teiid runtime. ------------------------------------------------------------------------------------------------------ Key: TEIID-1030 URL: https://jira.jboss.org/jira/browse/TEIID-1030 Project: Teiid Issue Type: Feature Request Components: Jopr Plugin Reporter: Van Halbert Assignee: Ted Jones Fix For: 7.1 Provide the ability to retrieve VDB archives from ModeShape repository and then deployed to Teiid runtime -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

4
4
0 / 0

[JBoss JIRA] Created: (TEIID-1177) Allow for implicit temp table definition with just a query, omitting the columns

by Steve Hawkins (JIRA)

Allow for implicit temp table definition with just a query, omitting the columns --------------------------------------------------------------------------------- Key: TEIID-1177 URL: https://jira.jboss.org/browse/TEIID-1177 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.1 Reporter: Steve Hawkins Assignee: Steve Hawkins Priority: Optional Fix For: 7.1 currently you must use target columns to define a temp table with a query expression: insert into #temp (x, y,z) select x, y, z from t but the following should be allowed as well: insert into #temp select x, y, z from t -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2010