There is another way, it is still a pain in the a$$, but just about
anything you do in the 5.5 studio is. You just have to choose which
PITA you are most comfortable with. I have used the beta, I don't
think that is going to be a solution for a long time.
I am using mysql for instance. It is possible to setup ODBC on the
intel machine for witango and mysql. It is a pain, because the studio
crashes with many configurations. You have to use a PowerPC binary
for the mysql odbc driver on intel, because the studio is powerpc,
and the mysql drivers are not universal. I wish I could use the
actualtech drivers, but witango crashes.
When you create a taf with a datasource called "MyDSN" for instance,
it creates an xml node within the datasources node in the xml of the
taf, like this.
<DataSource ID="MyDSN">
<DSType>ODBC</DSType>
<DSN>MyDSN</DSN>
<DBMS />
<Host>MyDSN</Host>
<Database>Some Vendor Driver Name</Database>
<UserInfo Encrypted="True">
<UserName>@[EMAIL PROTECTED]@[EMAIL
PROTECTED]@#$</UserName>
<Password>@[EMAIL PROTECTED]@[EMAIL
PROTECTED]@@%</Password>
</UserInfo>
</DataSource>
Now if you had a mysql JDBC driver on the server, and the Datasource
setup on the server as "MyDSN" but using JDBC, all you would have to
do to this taf, to get it to work on the server, is change value of
the DSN node to JDBC, so it looks like this:
<DataSource ID="MyDSN">
<DSType>JDBC</DSType>
<DSN>MyDSN</DSN>
<DBMS />
<Host>MyDSN</Host>
<Database>Some Vendor Driver Name</Database>
<UserInfo Encrypted="True">
<UserName>@[EMAIL PROTECTED]@[EMAIL
PROTECTED]@#$</UserName>
<Password>@[EMAIL PROTECTED]@[EMAIL
PROTECTED]@@%</Password>
</UserInfo>
</DataSource>
Thats it. The userid and the password will work, and the table and
column definitions built from the studio using odbc will work just
fine, they are the same as long as you were using the same db as odbc
dsn.
I have done this with mysql, mssql, oracle, and primebase. If you are
not using one of those, I imagine it would work if your DB has both
jdbc and odbc drivers.
Now the REAL PITA comes in when you want to deploy, or then edit
after deployment, you have to open the thing in a text editor and
manually edit.
However, it would be REALLY easy to create a drag and drop little
app, that would do this for you. So imagine you had an app, that you
drug onto it any number of tafs. It was called "DSN - ODBC to JDBC".
It would quickly parse and change the DSN nodes to JDBC. You would
just drag your taf on it, and commit to your server.
You could have another app, called "DSN - JDBC to ODBC" for when you
had to edit a taf from the server in the studio.
Now don't complain to me about how a$$backwards this is. ;-) I am
just the messenger, but it would work.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
On Oct 25, 2007, at 6:07 AM, Stephen Su wrote:
thank you all, we are running on intel machines, and have tried
parallels which caused more problems than using the mac os without
DB connection.
: ( stephen
On Oct 25, 2007, at 6:29 AM, Dale Graham wrote:
As a stop-gap, I have been using the Windows version of the editor
on Parallels.... testing with Mac server version on the same
computer. Weird but works. (The irony is that because it's Intel,
it runs Parallels very well, and the INTEL (Windows) JDBC works
just fine, though setting up Java/JDBC on Windows can be a
definite problem.)
On Oct 25, 2007, at 2:59 AM, Stephen Su wrote:
Has anyone successfully configured witango studio 5.5 to connect
up with data sources via. JDBC on an intel based MacBook Pro?
- stephen
____________________________________________________________________
____
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
_____________________________________________________________________
___
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf