Dear Witango Support,
Thank you for the follow up, however,using the new Studio BETA has
the following problems:
1) a key that expires and no replacement key (that situation now)
2) various bugs during use of it to develop with . . .
3) once a TAF is opened in the new studio, it is incompatible with
any other version of studio
4) the header related problem of deploying the TAFs on a 5.5 server
5) random save / deployment errors still be troubleshooted
Perhaps you have a newer version and key of the studio BETA that you
can send me that resolves some or all of the above.
At this point, each team member has to travel with at least 2
computers, sometimes 3 to make sure that we have the necessary
machines to allow us to work.
Please help out ASAP,
Stephen
On Oct 25, 2007, at 3:49 AM, Customer Support wrote:
As the 5.5 Dev Studio is a Carbon application running in the
rosetta emulator and Apple did not provide a bridge between Rosetta
and Java there is no way that the JVM can be instantiated.
The irony of this situatio is that Apple did not implement the odbc-
jdbc bridge either which is a standard API for Java so the new Dev
Studio which is written in Java uses JDBC and aliases a JDBC
connection to make it appear as ODBC to the dev studio.
If you need to use JDBC then it would be best to use the new dev
studio beta.
Regards
Witango Support
On 25/10/2007, at 4:59 PM, 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
