Data Management console listing tables but not columns? - Data Management

Welcome Guest

Search | Active Topics | Members | Log In | Register

Midnight Coders Forums » WebORB for Java » Data Management » Data Management console listing tables but not columns?

Data Management console listing tables but not columns?

Options · View

Previous Topic · Next Topic

shane

Posted: Tuesday, October 12, 2010 6:40:50 PM

Rank: Newbie Coder
Groups: Member

Joined: 10/12/2010
Posts: 4
Points: 12

Hi,

I am attempting to build a simple app with Flash builder, WebOrb 4.03, and Oracle 10g.

I am able to conenct the the database and see a list of tables, and I am able to see the relation properties for the tables, but the tables are 'empty'. No columns are listed.

I have tried the following all with the same result:

- different oracle databases on different servers (Oracle XE 10g on local machine, Oracle 10g on dev server)
- different weborb instances on different machines (local machine, deployed in jboss server)
- new and old weborb for java versions (4.02 and 4.03 I beleive)
- different database schemas (from a single table with 1 row, through to our production backup with 50+ tables)

Below is a extract from the logs following as I create a new oracle database connection, and add a dable to a data model. No exceptions are thrown but the column names remain unlisted.

Quote:

[WEBORB INFO, btpool0-6, 10:13:10 12:37:11] Delegating invocation to handler Java Object Handler
[WEBORB INFO, btpool0-6, 10:13:10 12:37:11] Processing method invocation in Java Object Handler
[WEBORB INFO, btpool0-6, 10:13:10 12:37:11] Java Object Handler handler successfully invoked method GetDatabaseTypes on the service weborb.management.datamanagement.DataManagementService
[WEBORB INFO, btpool0-6, 10:13:10 12:37:11] V3 Dispatcher successfully handled request processing
[WEBORB INFO, btpool0-6, 10:13:10 12:37:11] Starting response serialization
[WEBORB INFO, btpool0-6, 10:13:10 12:37:24] Received request for /console/weborb.wo
[WEBORB INFO, btpool0-6, 10:13:10 12:37:24] Content type - application/x-amf
[WEBORB INFO, btpool0-6, 10:13:10 12:37:24] Session - 1oq9eqvcslux0
[WEBORB INFO, btpool0-6, 10:13:10 12:37:24] Request has been successfully parsed.
[WEBORB INFO, btpool0-6, 10:13:10 12:37:24] Dispatching request.
[WEBORB INFO, btpool0-6, 10:13:10 12:37:24] Dispatching request processing to V3 Dispatcher
[WEBORB SECURITY, btpool0-6, 10:13:10 12:37:24] access allowed. resource name - 'weborb.handler.JavaObjectHandler'. reason -
[WEBORB INFO, btpool0-6, 10:13:10 12:37:24] Delegating invocation to handler Java Object Handler
[WEBORB INFO, btpool0-6, 10:13:10 12:37:24] Processing method invocation in Java Object Handler
[WEBORB INFO, btpool0-6, 10:13:10 12:37:24] Java Object Handler handler successfully invoked method GetDatabases on the service weborb.management.datamanagement.DataManagementService
[WEBORB INFO, btpool0-6, 10:13:10 12:37:24] V3 Dispatcher successfully handled request processing
[WEBORB INFO, btpool0-6, 10:13:10 12:37:24] Starting response serialization
[WEBORB INFO, btpool0-6, 10:13:10 12:37:25] Received request for /console/weborb.wo
[WEBORB INFO, btpool0-6, 10:13:10 12:37:25] Content type - application/x-amf
[WEBORB INFO, btpool0-6, 10:13:10 12:37:25] Session - 1oq9eqvcslux0
[WEBORB INFO, btpool0-6, 10:13:10 12:37:25] Request has been successfully parsed.
[WEBORB INFO, btpool0-6, 10:13:10 12:37:25] Dispatching request.
[WEBORB INFO, btpool0-6, 10:13:10 12:37:25] Dispatching request processing to V3 Dispatcher
[WEBORB SECURITY, btpool0-6, 10:13:10 12:37:25] access allowed. resource name - 'weborb.handler.JavaObjectHandler'. reason -
[WEBORB INFO, btpool0-6, 10:13:10 12:37:25] Delegating invocation to handler Java Object Handler
[WEBORB INFO, btpool0-6, 10:13:10 12:37:25] Processing method invocation in Java Object Handler
[WEBORB INFO, btpool0-6, 10:13:10 12:37:25] Java Object Handler handler successfully invoked method CreateDatabaseConnection on the service weborb.management.datamanagement.DataManagementService
[WEBORB INFO, btpool0-6, 10:13:10 12:37:25] V3 Dispatcher successfully handled request processing
[WEBORB INFO, btpool0-6, 10:13:10 12:37:25] Starting response serialization
[WEBORB INFO, btpool0-6, 10:13:10 12:37:27] Received request for /console/weborb.wo
[WEBORB INFO, btpool0-6, 10:13:10 12:37:27] Content type - application/x-amf
[WEBORB INFO, btpool0-6, 10:13:10 12:37:27] Session - 1oq9eqvcslux0
[WEBORB INFO, btpool0-6, 10:13:10 12:37:27] Request has been successfully parsed.
[WEBORB INFO, btpool0-6, 10:13:10 12:37:27] Dispatching request.
[WEBORB INFO, btpool0-6, 10:13:10 12:37:27] Dispatching request processing to V3 Dispatcher
[WEBORB SECURITY, btpool0-6, 10:13:10 12:37:27] access allowed. resource name - 'weborb.handler.JavaObjectHandler'. reason -
[WEBORB INFO, btpool0-6, 10:13:10 12:37:27] Delegating invocation to handler Java Object Handler
[WEBORB INFO, btpool0-6, 10:13:10 12:37:27] Processing method invocation in Java Object Handler
[WEBORB INFO, btpool0-6, 10:13:10 12:37:27] Java Object Handler handler successfully invoked method GetTables on the service weborb.management.datamanagement.DataManagementService
[WEBORB INFO, btpool0-6, 10:13:10 12:37:27] V3 Dispatcher successfully handled request processing
[WEBORB INFO, btpool0-6, 10:13:10 12:37:27] Starting response serialization
[WEBORB INFO, btpool0-6, 10:13:10 12:37:28] Received request for /console/weborb.wo
[WEBORB INFO, btpool0-6, 10:13:10 12:37:28] Content type - application/x-amf
[WEBORB INFO, btpool0-6, 10:13:10 12:37:28] Session - 1oq9eqvcslux0
[WEBORB INFO, btpool0-6, 10:13:10 12:37:28] Request has been successfully parsed.
[WEBORB INFO, btpool0-6, 10:13:10 12:37:28] Dispatching request.
[WEBORB INFO, btpool0-6, 10:13:10 12:37:28] Dispatching request processing to V3 Dispatcher
[WEBORB SECURITY, btpool0-6, 10:13:10 12:37:28] access allowed. resource name - 'weborb.handler.JavaObjectHandler'. reason -
[WEBORB INFO, btpool0-6, 10:13:10 12:37:28] Delegating invocation to handler Java Object Handler
[WEBORB INFO, btpool0-6, 10:13:10 12:37:28] Processing method invocation in Java Object Handler
[WEBORB INFO, btpool0-6, 10:13:10 12:37:28] Java Object Handler handler successfully invoked method GetTableMeta on the service weborb.management.datamanagement.DataManagementService
[WEBORB INFO, btpool0-6, 10:13:10 12:37:28] V3 Dispatcher successfully handled request processing
[WEBORB INFO, btpool0-6, 10:13:10 12:37:28] Starting response serialization
[WEBORB INFO, btpool0-6, 10:13:10 12:37:29] Received request for /console/weborb.wo
[WEBORB INFO, btpool0-6, 10:13:10 12:37:29] Content type - application/x-amf
[WEBORB INFO, btpool0-6, 10:13:10 12:37:29] Session - 1oq9eqvcslux0
[WEBORB INFO, btpool0-6, 10:13:10 12:37:29] Request has been successfully parsed.
[WEBORB INFO, btpool0-6, 10:13:10 12:37:29] Dispatching request.
[WEBORB INFO, btpool0-6, 10:13:10 12:37:29] Dispatching request processing to V3 Dispatcher
[WEBORB SECURITY, btpool0-6, 10:13:10 12:37:29] access allowed. resource name - 'weborb.handler.JavaObjectHandler'. reason -
[WEBORB INFO, btpool0-6, 10:13:10 12:37:29] Delegating invocation to handler Java Object Handler
[WEBORB INFO, btpool0-6, 10:13:10 12:37:29] Processing method invocation in Java Object Handler
[WEBORB INFO, btpool0-6, 10:13:10 12:37:29] Java Object Handler handler successfully invoked method GetServerLanguages on the service weborb.management.datamanagement.DataManagementService
[WEBORB INFO, btpool0-6, 10:13:10 12:37:29] V3 Dispatcher successfully handled request processing
[WEBORB INFO, btpool0-6, 10:13:10 12:37:29] Starting response serialization
[WEBORB INFO, btpool0-6, 10:13:10 12:37:32] Received request for /console/weborb.wo
[WEBORB INFO, btpool0-6, 10:13:10 12:37:32] Content type - application/x-amf
[WEBORB INFO, btpool0-6, 10:13:10 12:37:32] Session - 1oq9eqvcslux0
[WEBORB INFO, btpool0-6, 10:13:10 12:37:32] Request has been successfully parsed.
[WEBORB INFO, btpool0-6, 10:13:10 12:37:32] Dispatching request.
[WEBORB INFO, btpool0-6, 10:13:10 12:37:32] Dispatching request processing to V3 Dispatcher
[WEBORB SECURITY, btpool0-6, 10:13:10 12:37:32] access allowed. resource name - 'weborb.handler.JavaObjectHandler'. reason -
[WEBORB INFO, btpool0-6, 10:13:10 12:37:32] Delegating invocation to handler Java Object Handler
[WEBORB INFO, btpool0-6, 10:13:10 12:37:32] Processing method invocation in Java Object Handler
[WEBORB INFO, btpool0-6, 10:13:10 12:37:32] Java Object Handler handler successfully invoked method SaveDataModel on the service weborb.management.datamanagement.DataManagementService
[WEBORB INFO, btpool0-6, 10:13:10 12:37:32] V3 Dispatcher successfully handled request processing
[WEBORB INFO, btpool0-6, 10:13:10 12:37:32] Starting response serialization
[WEBORB INFO, btpool0-6, 10:13:10 12:37:33] Received request for /console/weborb.wo
[WEBORB INFO, btpool0-6, 10:13:10 12:37:33] Content type - application/x-amf
[WEBORB INFO, btpool0-6, 10:13:10 12:37:33] Session - 1oq9eqvcslux0
[WEBORB INFO, btpool0-6, 10:13:10 12:37:33] Request has been successfully parsed.
[WEBORB INFO, btpool0-6, 10:13:10 12:37:33] Dispatching request.
[WEBORB INFO, btpool0-6, 10:13:10 12:37:33] Dispatching request processing to V3 Dispatcher
[WEBORB SECURITY, btpool0-6, 10:13:10 12:37:33] access allowed. resource name - 'weborb.handler.JavaObjectHandler'. reason -
[WEBORB INFO, btpool0-6, 10:13:10 12:37:33] Delegating invocation to handler Java Object Handler
[WEBORB INFO, btpool0-6, 10:13:10 12:37:33] Processing method invocation in Java Object Handler
[WEBORB INFO, btpool0-6, 10:13:10 12:37:33] Java Object Handler handler successfully invoked method GetDataModelTables on the service weborb.management.datamanagement.DataManagementService
[WEBORB SECURITY, btpool0-6, 10:13:10 12:37:33] access allowed. resource name - 'weborb.handler.JavaObjectHandler'. reason -
[WEBORB INFO, btpool0-6, 10:13:10 12:37:33] Delegating invocation to handler Java Object Handler
[WEBORB INFO, btpool0-6, 10:13:10 12:37:33] Processing method invocation in Java Object Handler
[WEBORB INFO, btpool0-6, 10:13:10 12:37:33] Java Object Handler handler successfully invoked method AddTableToDataModel on the service weborb.management.datamanagement.DataManagementService
[WEBORB INFO, btpool0-6, 10:13:10 12:37:33] V3 Dispatcher successfully handled request processing
[WEBORB INFO, btpool0-6, 10:13:10 12:37:33] Starting response serialization

shane

Posted: Wednesday, October 13, 2010 2:58:58 PM

Rank: Newbie Coder
Groups: Member

Joined: 10/12/2010
Posts: 4
Points: 12

I just tried the data management in weborb for java v3.0.2. Column names are loaded correctly.

Any ideas on why this would not work in v4.0.x ?

Mark Piller

Posted: Friday, October 15, 2010 6:10:54 AM

Rank: Administration
Groups: Administration

Joined: 8/21/2006
Posts: 1,607
Points: 4,082
Location: Frisco, TX

It looks like there was regression in 4.03 specifically with Oracle support. We're looking into it. Thank you for bringing this to our attention.

Regards,
Mark

Mark Piller
Midnight Coders, Inc.
twitter: midnightcoder
blog: blog.themidnightcoders.com
website: www.themidnightcoders.com

shane

Posted: Monday, March 14, 2011 5:49:47 PM

Rank: Newbie Coder
Groups: Member

Joined: 10/12/2010
Posts: 4
Points: 12

Hi Mark, recently I have been evaluating WebOrb again and I am continuing to have problems using the WDMF with Oracle.

Here is my setup:
WebOrb 4.0.3 Dev Mode
Oracle 10.2.0.5
Flash Builder 4 with generated Test Drive in Air App

The data modeller appears to struggle loading table columns (had to reload the management console approx. 5 times to get a tables added to the data model with columns loaded).

Codegen failed (WebOrb v4.3, Oracle 10g data model), I had to remove a few 'throws Exception' clauses from the code templates to get it to compile. I’m sure there is a better approach but I will leave that to you guys, see below for the changes I had to make:

“\weborb40\webapp\weborbassets\codegen\wdm\server\java\data\oracle\codegen.server.java.data.oracle.xslt”
32: public Db()
122: public _DataMapper()
127: public _DataMapper( Database database )

Finally it appears that WebOrb is using a transaction level unsupported by Oracle. I am getting the following error when using the WDMF generated test drive: “READ_COMMITTED and SERIALIZABLE are the only valid transaction levels”. See the full trace below:

Quote:

[RPC Fault faultString="READ_COMMITTED and SERIALIZABLE are the only valid transaction levels" faultCode="Server.Processing" faultDetail="java.sql.SQLException: READ_COMMITTED and SERIALIZABLE are the only valid transaction levels

at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:208)
at oracle.jdbc.driver.PhysicalConnection.setTransactionIsolation(PhysicalConnection.java:1608)
at weborb.data.management.Database.getConnection(Unknown Source)
at weborb.data.management.Database.open(Unknown Source)
at weborb.data.management.DatabaseConnectionMonitor.(Unknown Source)
at weborb.data.management.DataMapper.getQueryPage(Unknown Source)
at weborb.data.management.DataMapper.findAll(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at weborb.util.Invocation.invoke(Unknown Source)
at weborb.handler.JavaObjectHandler.invoke(Unknown Source)
at weborb.handler.Handlers.invokeWithHandler(Unknown Source)
at weborb.handler.Handlers.invoke(Unknown Source)
at weborb.dispatch.Invoker.handleInvoke(Unknown Source)
at weborb.v3types.ReqMessage.execute(Unknown Source)
at weborb.dispatch.V3Dispatcher.dispatch(Unknown Source)
at weborb.dispatch.Dispatchers.dispatch(Unknown Source)
at weborb.ORBServlet.service(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:491)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1074)
at weborb.util.upload.MultiPartFilter.doFilter(Unknown Source)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:185)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:689)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:391)
at org.mortbay.jetty.handler.HandlerList.handle(HandlerList.java:49)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:285)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:457)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:765)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:627)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:357)
at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:217)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)
"]
at mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::faultHandler()[E:\dev\4.x\frameworks\projects\rpc\src\mx\rpc\AbstractInvoker.as:345]
at mx.rpc::Responder/fault()[E:\dev\4.x\frameworks\projects\rpc\src\mx\rpc\Responder.as:68]
at mx.rpc::AsyncRequest/fault()[E:\dev\4.x\frameworks\projects\rpc\src\mx\rpc\AsyncRequest.as:113]
at NetConnectionMessageResponder/statusHandler()[E:\dev\4.x\frameworks\projects\rpc\src\mx\messaging\channels\NetConnectionChannel.as:604]
at mx.messaging::MessageResponder/status()[E:\dev\4.x\frameworks\projects\rpc\src\mx\messaging\MessageResponder.as:264]

Cyril

Posted: Tuesday, March 15, 2011 12:10:19 PM

Rank: Administration
Groups: Administration , Member

Joined: 9/10/2009
Posts: 320
Points: 778
Location: US

Hi Shane,

thanks for detailed description. I will handle it during next few business days. I will update the status asap

Regards,
Cyril

shane

Posted: Tuesday, March 22, 2011 4:12:50 PM

Rank: Newbie Coder
Groups: Member

Joined: 10/12/2010
Posts: 4
Points: 12

Cyril, any updates?

Cyril

Posted: Wednesday, March 23, 2011 5:53:10 PM

Rank: Administration
Groups: Administration , Member

Joined: 9/10/2009
Posts: 320
Points: 778
Location: US

Hi,

I am waiting for the answer from our developers. I hope I will receive it tomorrow

Regards,
Cyril

Cyril

Posted: Friday, March 25, 2011 9:14:39 AM

Rank: Administration
Groups: Administration , Member

Joined: 9/10/2009
Posts: 320
Points: 778
Location: US

Hi shane,

could you please update WebORB to the latest version (4.3.0.2), and let me know if the problem is still there.

Regards,
Cyril

javierjc

Posted: Monday, August 22, 2011 12:58:10 AM

Rank: Newbie Coder
Groups: Member

Joined: 8/19/2011
Posts: 3
Points: 9
Location: madrid, spain

Hi,

I have the same problem evaluating weborb for java versions 4.2 and 4.3. Oracle version is 10.2.0.4.0

Thanks in advance.

Users browsing this topic

Guest

Midnight Coders Forums » WebORB for Java » Data Management » Data Management console listing tables but not columns?

Forum Jump

You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Main Forum RSS :

YAFVision Theme Created by Jaben Cargman (Tiny Gecko)
Powered by Yet Another Forum.net version 1.9.1.8 (NET v2.0) - 3/29/2008
Copyright © 2003-2008 Yet Another Forum.net. All rights reserved.
This page was generated in 0.188 seconds.