Workshop problem in building relationship

Question

Hi there,
It seems that workshop (comes with WebLogic 8.1) has problem building
relationship. It keeps saying that it cannot retrieve column info. from my
data source, when in fact creating entity beans from the exact data
source/table works fine.
Am I miss anything?
Thanks.
Yan

Answer 1

"Byron Foster" <[email protected]> wrote in message
news:[email protected]...
>
Thanks for the assist, your option B was the problem. It appears thatwhen using
the "create entity bean from database table" feature the data-source-nameproperty
is set by workshop to the JNDI data source name, and NOT the NAME. Whenusing
the 'Add Relation' feature the wizard uses this name, which of coursewon't work!
But, it has to be the JNDI name because in weblogic-cmp-rdbms-jar.xml
<weblogic-rdbms-jar>.<weblogic-rdbms-bean>.<data-source-name> has to be JNDI
name. EJBGen puts the name here...
So, I still think it is a bug:( A work-around is to name the NAME and JNDI
Name the same?
>
Now, I'm getting some error about can't find table!!! I guess it doesn'treally
matter since I can just use the "have workshop generate foreign keys"option,
since we don't use the appserver to create the tables. The "query table"option
is just a little more convenient.
Again, thanks for the help!
Michael Kovacs <[email protected]> wrote:
Hi Byron,
The error you're seeing is because the relation wizard
is unable to find your datasource on the server. It does
this by looking up the datasource mbeans on the server.
A couple of things:
A) Make sure that your datasource is created on the server.
There's a couple of different ways you can accomplish this:
1) Use workshop's datasource viewer under Tools->WebLogic
Server->Datasource Viewer...
and make sure you see your datasource.
2) Use the console or weblogic.Admin to make sure that your datasource
exists. In the console you'd look under Servcies->JDBC->Datasources.
With weblogic.Admin the MBean type that you would look for, and that
Workshop looks for, using the command line tool is: JDBCTxDataSource
So a sample command to get these MBean types would be:
java weblogic.Admin -url t3://localhost:7001 -username weblogic
-password weblogic get -type JDBCTxDataSource -pretty
(making sure of course that you have weblogic.jar on your classpath)
If you don't see the JDBCTxDataSource MBean that corresponds to your
datasource then workshop isn't going to find your datasource.
B) Make sure that the datasource NAME that you specify for
your entity beans match what the NAME of the datasource
is on the server. Not the JNDI name but the name of the datasource.
hope this helps,
-Michael
Byron Foster wrote:
I'm using workshop 8.1 SP2, and Adding relationships does NOT workwith the
same symptoms as described below.
Connection Info using DBVisualizer:
Oracle
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
Oracle JDBC driver
9.2.0.3.0
Using the same driver through DBVisualizer I'm ablie to browse thecolumn information,
so
that would lead me to believe it is not a driver issue.
"keith shacks" <[email protected]> wrote:
Carl
I have recently used relationships in workshop 8.1 sp2 and it seems
to
work fine.
- Keith
"Carl" <[email protected]> wrote:
Well, I upgraded to SP2. I tried to use the relationships again.
This
time around, they still don't work. I get a message "Unable to
retrieve
column information. Datasource xxx not found.":( Does anybody elsehave
luck creating relationships in Workshop SP2? I will be more than
happy
to
provide an example that illustrates this problem.
"Carl" <[email protected]> wrote in message
news:[email protected]...
>>>>>
I believe you have encountered a bug in workshop. So, I do myrelationships
manually. May be it will be fixed in sp2?
"Yan Zhou" <[email protected]_NoSpam> wrote in message
news:[email protected]...
Hi there,
It seems that workshop (comes with WebLogic 8.1) has problem
building
relationship. It keeps saying that it cannot retrieve column info.from
my
data source, when in fact creating entity beans from the exact data
source/table works fine.
Am I miss anything?
Thanks.
Yan