Sunday, November 17, 2002

Java: Problems Connecting to EJBs from Single-Frame Movies The simple summary: If you're having problems maintaining a connection to an EJB from a single-frame movie, add a few extra frames. The technical explanation: Due to some glitch, this allows you to call methods on the NetServiceProxy object that acts as a client-side reference to your EJB. (The NetServiceProxy object is the result of the call to the EJBHome's create method.) 7:35:31 PM    comment []

.NET: Problems Converting From Developer Version If you develop apps using the trial version, get downgraded to the developer version after 30 days, then buy a license, you may find that your apps still only work with one IP address. Here's the fix: Update your apps' license files (/bin/frconfig.txt) so that the license number matches the one found in Macromedia's sample apps' frconfig.txt file. Each app must have a valid license file. For some reason, the installer updates the samples' licenses only. 7:34:27 PM    comment []

Java: Problems with Passing JDBC ResultSets from Server to Flash. It appears that if you're not using the JRun version of Flash Remoting, passing RecordSets to a Flash client fails unless the ResultSet is still connected to the Database. As leaving ResultSets connected to a database is a truly bad practice, passing Java RecordSets via FR (without JRun) isn't practical. Our Slideshow Demo's Java code shows one possible workaround using CachedRowSet instead. This returns non-fatal errors but seems to work otherwise. Another workaround is to translate your RecordSet into Arrays, pass the Arrays, then translate them back into Flash RecordSets once they arrive at the client. Rumor has it that Macromedia will be releasing a patch that supports RowSets and fails more gracefully for ResultSets sometime soon. If you have information on other possible workarounds, please send us a post. 7:33:03 PM    comment []