RE: MX Service Pack? was Re: Looking back - for those who have moved to CFMX...
I have no idea, but I would expect the release data is rather close since an early release version is available now. Matt Liotta President & CEO Montara Software, Inc. http://www.montarasoftware.com/ 888-408-0900 x901 > -Original Message- > From: Frank Mamone [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, September 11, 2002 7:30 AM > To: CF-Talk > Subject: Re: MX Service Pack? was Re: Looking back - for those who have > moved to CFMX... > > Thanks Matt. Do youb know if the rumored release date is indeed accurate? > > - Original Message - > From: "Matt Liotta" <[EMAIL PROTECTED]> > To: "CF-Talk" <[EMAIL PROTECTED]> > Sent: Wednesday, September 11, 2002 10:15 AM > Subject: RE: MX Service Pack? was Re: Looking back - for those who have > moved to CFMX... > > > > Since no one asked me to keep this a secret... I as well as others have > > been given access to an early release of the service pack. I'm not too > > thrilled with it as none of the issues I was interested in were fixed. > > Below are the notes associated with the service pack. > > > > > > > > > > COM-Related Issues > > > > The following issues with COM have been fixed: > > > > > > > > > > > > Issue > > > > ID > > > > > > COM objects with multiple IDispatch interfaces could not be used by > > ColdFusion MX. A "java.lang.IllegalArgumentException: Argument is not a > > COM object" error would occur. > > > > 46303 > > > > > > Attempting to use COM objects with read-only or write-only properties > > could fail. > > > > 46612 > > > > > > Looping over a COM collection object using a COM object that has > > com2Java-generated Java stubs could cause a method selection exception. > > > > 46150 > > > > > > Passing parameters to COM objects by reference did not work correctly. > > > > 46776 > > > > > > ColdFusion MX would not allow you to use a literal value in CFML code > > that calls a COM method that takes a simple value passed by reference. > > You were required to use a variable as the argument in your CFML code. > > > > 45605 > > > > > > Saving COM objects in shared variable scopes could cause a Null Pointer > > Exception when ColdFusion executed the CFDUMP tag or if debugging were > > enabled. > > > > 45733 > > > > > > > > > > The following additional COM-related changes and improvements have been > > made: > > > > > > > > > > > > Change > > > > ID > > > > > > Significant improvements have been made to COM object performance on > > second and subsequent references by caching object type information. > > > > NOTE: Due to this change, if the COM object interface definitions > > change, you must restart ColdFusion MX to use the new COM object > > interface type definitions. > > > > 37315 > > > > > > > > > > > > > > > > > > > > > > Database-Related Issues > > > > The following database-related issues have been fixed: > > > > > > > > > > > > Issue > > > > ID > > > > > > SELECT and DROP keywords contained in SQL could produce a "No ResultSet > > set was produced" error message. > > > > 45938 > > 45936 > > > > > > CFUPDATE did not work correctly when the target DB table has a compound > > primary key comprised of multiple columns. > > > > 46433 > > > > > > On upgrade from ColdFusion 5, MySQL and PostgreSQL data sources were > > erroneously migrated as "ODBC Socket" data sources on UNIX and cannot be > > deleted in the Administrator. This updater enables you to use the > > Administrator to delete the incorrect data sources and recreate them > > correctly. > > > > 46877 > > > > > > An exception message for CFUPDATE erroneously reversed the table and > > data source names. > > > > 45170 > > > > > > Invalid connections to Informix, Oracle, or DB2 data sources could > > erroneously be reused in the connection pool. > > > > 46251 > > > > > > > > > > > > > > > > > > > > > > Administrator-Related Issues > > > > The following issues with the ColdFusion MX Administrator have been > > fixed: > > > > > > > > Issue > >
Re: MX Service Pack? was Re: Looking back - for those who have moved to CFMX...
Thanks Matt. Do youb know if the rumored release date is indeed accurate? - Original Message - From: "Matt Liotta" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Wednesday, September 11, 2002 10:15 AM Subject: RE: MX Service Pack? was Re: Looking back - for those who have moved to CFMX... > Since no one asked me to keep this a secret... I as well as others have > been given access to an early release of the service pack. I'm not too > thrilled with it as none of the issues I was interested in were fixed. > Below are the notes associated with the service pack. > > > > > COM-Related Issues > > The following issues with COM have been fixed: > > > > > > Issue > > ID > > > COM objects with multiple IDispatch interfaces could not be used by > ColdFusion MX. A "java.lang.IllegalArgumentException: Argument is not a > COM object" error would occur. > > 46303 > > > Attempting to use COM objects with read-only or write-only properties > could fail. > > 46612 > > > Looping over a COM collection object using a COM object that has > com2Java-generated Java stubs could cause a method selection exception. > > 46150 > > > Passing parameters to COM objects by reference did not work correctly. > > 46776 > > > ColdFusion MX would not allow you to use a literal value in CFML code > that calls a COM method that takes a simple value passed by reference. > You were required to use a variable as the argument in your CFML code. > > 45605 > > > Saving COM objects in shared variable scopes could cause a Null Pointer > Exception when ColdFusion executed the CFDUMP tag or if debugging were > enabled. > > 45733 > > > > > The following additional COM-related changes and improvements have been > made: > > > > > > Change > > ID > > > Significant improvements have been made to COM object performance on > second and subsequent references by caching object type information. > > NOTE: Due to this change, if the COM object interface definitions > change, you must restart ColdFusion MX to use the new COM object > interface type definitions. > > 37315 > > > > > > > > > > > Database-Related Issues > > The following database-related issues have been fixed: > > > > > > Issue > > ID > > > SELECT and DROP keywords contained in SQL could produce a "No ResultSet > set was produced" error message. > > 45938 > 45936 > > > CFUPDATE did not work correctly when the target DB table has a compound > primary key comprised of multiple columns. > > 46433 > > > On upgrade from ColdFusion 5, MySQL and PostgreSQL data sources were > erroneously migrated as "ODBC Socket" data sources on UNIX and cannot be > deleted in the Administrator. This updater enables you to use the > Administrator to delete the incorrect data sources and recreate them > correctly. > > 46877 > > > An exception message for CFUPDATE erroneously reversed the table and > data source names. > > 45170 > > > Invalid connections to Informix, Oracle, or DB2 data sources could > erroneously be reused in the connection pool. > > 46251 > > > > > > > > > > > Administrator-Related Issues > > The following issues with the ColdFusion MX Administrator have been > fixed: > > > > Issue > > ID > > > Scheduled tasks were not running at the correct time. > > 46312 > > > ERROR.* variables were not available in the site-wide error handler. > > 46761 > > > A potential script-execution vulnerability existed. > > 47096 > > > When using web server Basic Authentication, the user was not prompted > for the Administrator password after logging in to the web server, even > when the ColdFusion MX Administrator password prompt is enabled. > > 47474 > > > > > > > > > > > Runtime and Debugging-Related Issues > > The issues with the ColdFusion runtime and debugging information have > been fixed: > > > > > > Issue > > ID > > > A potential cross-site scripting vulnerability existed in a handler > module. > > 46113 > > > A malformed mail file could cause the mail service to fail to start. > > 46502 > > > Client variables stored using the clientStorage="Cookie" option did not > work correctly if the case of the application name specified in the > CFAPPLICATION tag was not correct. > > 46656 > > > The DateDiff() function was not compatible with ColdFusion 5. > > 47153 >
RE: MX Service Pack? was Re: Looking back - for those who have moved to CFMX...
E tag did not upload files if their names used double-byte characters. 45673 ColdFusion MX ODBC Agent and Server services did not use the native OS Code Page on Japanese Windows systems. To correct this issue, the Updater automatically runs the cf_root/db/slserver52/admin/setcp.bat command file. 46048 Web Server Connector-Related Issues The following Jrun-specific issues have been fixed: Under some conditions, JRun could erroneously create a directory when a JSP page was requested. 47239 If a web server and JRun were on the same computer, and the Connector Wizard was run against a cluster, all the servers in the cluster were added using localhost:proxyport instead of IP:proxyport as appropriate. 44777 Setting verbose=false (default) in the jrun.ini file did not stop output and failure logging to the JRun connector logs when using the IIS/ISAPI filter. 46733 The following Apache-specific issues have been fixed: CFCHART did not work correctly with Apache 2.0 if the first servlet mapping was for CFCHART. 46774 The configuration setting modifications to Apache config files were not placed before the VirtualHosts sect ion. 44649 Apache 2.0.40 web server was not supported by the Apache 2.x connector. It is now required by the connector. 46424 47440 The wsconfig web server configuration did not work correctly with Apache StrongHold. 46689 If two servlet mappings differed only by a trailing slash, Apache server wouldn't start properly. 46691 The following IIS-specific issues have been fixed: Under some heavy load conditions, the IIS connector DLL might have produced an access violation with very large headers or URL's. This could make the server appear unresponsive. 45900 Under certain conditions, a heap overflow condition could occur with the IIS connector. 46706 The following general connector fixes and improvements have been made: A potential log file and .ini file disclosure issue has been fixed. 46562 The remove_ALL_connectors batch program didn't work properly. 46213 A new switch has been added to the wsconfig web server configuration tool. You can now use the "-upgrade" switch to upgrade web server connectors. The following syntax upgrades all configured connectors: java -jar wsconfig.jar -upgrade -v The Updater automatically runs this command to upgrade the web server connectors when you install an update. You can also upgrade a single website by using the following syntax: java -jar wsconfig.jar -upgrade -dir | -ws [-v] The command specifies the web server type to upgrade and the server configuration directory path (for Apache, Netscape, iPlanet or Zeus servers, or the server site for IIS. The optional -v switch produces expanded (verbose) output from the wsconfig tool. 46668 Matt Liotta President & CEO Montara Software, Inc. http://www.montarasoftware.com/ 888-408-0900 x901 > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, September 11, 2002 7:09 AM > To: CF-Talk > Subject: Re: MX Service Pack? was Re: Looking back - for those who have > moved to CFMX... > > A little birdie by the name of Foghorn Leghorn ...er.. I mean Vernon > Viehe. src: http://vvmx.blogspot.com/2002_09_01_vvmx_archive.html#81150105 > > It's not a secret. Spike W also posted something to similar wording on > the actual macromedia forums a week ago. I'm actually a little > disappointed in the CFMX community. It seems that the Flash community is > a little more open with information and well, there's flash communities, > blogs, etc all over the place but ... not so many one stop CFMX resources > that are actually worthwhile visiting and don't have ad banners all over > the place, etc. and apparently Blogs are now considered overrated. I have > been trying to keep up with cfm blogs and such, you can find a list of > them over at http://www.web-rat.com/ -- if anyone knows other great > resources, please let me know. > > >From what I've seen so far, the biggest issue that it'll address is com > support. I'm sure more information will be released by the appropriate > people soon. I do know more than I'm letting on, but .. it's not my > places to say. > > ~Todd > > On Wed, 11 Sep 2002, Dave Carabetta wrote: > > > >Only patch there is out right now is the Apache hot fix for 2.0.39 -- > CFMX > > >SP1 should see the daylight within the next two weeks or very end of > > >September. > > > > While not disputing your information, where did you get that info from? > By > > several accounts (including MM employees), a service pack wasn't even on > the > > timeline as of a few weeks ago. If there really
Re: MX Service Pack? was Re: Looking back - for those who have moved to CFMX...
A little birdie by the name of Foghorn Leghorn ...er.. I mean Vernon Viehe. src: http://vvmx.blogspot.com/2002_09_01_vvmx_archive.html#81150105 It's not a secret. Spike W also posted something to similar wording on the actual macromedia forums a week ago. I'm actually a little disappointed in the CFMX community. It seems that the Flash community is a little more open with information and well, there's flash communities, blogs, etc all over the place but ... not so many one stop CFMX resources that are actually worthwhile visiting and don't have ad banners all over the place, etc. and apparently Blogs are now considered overrated. I have been trying to keep up with cfm blogs and such, you can find a list of them over at http://www.web-rat.com/ -- if anyone knows other great resources, please let me know. >From what I've seen so far, the biggest issue that it'll address is com support. I'm sure more information will be released by the appropriate people soon. I do know more than I'm letting on, but .. it's not my places to say. ~Todd On Wed, 11 Sep 2002, Dave Carabetta wrote: > >Only patch there is out right now is the Apache hot fix for 2.0.39 -- CFMX > >SP1 should see the daylight within the next two weeks or very end of > >September. > > While not disputing your information, where did you get that info from? By > several accounts (including MM employees), a service pack wasn't even on the > timeline as of a few weeks ago. If there really is a service pack coming > out, any idea as to what issues it will address? > > Regards, > Dave. -- Todd Rafferty ([EMAIL PROTECTED]) - http://www.web-rat.com/ | Team Macromedia Volunteer for ColdFusion | http://www.macromedia.com/support/forums/team_macromedia/ | http://www.flashCFM.com/ - webRat (Moderator)| http://www.ultrashock.com/ - webRat (Back-end Moderator) | __ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
