New Java Release

I just got the J2SE 5.0 Release 4 in my Software Update.
Can anybody tell me if they are having any problems with it on a Rev A iMac 20”.

Hi, woodie.
Well, it works fine on my Power Mac G5 Dual 2.3 GHz.
Whenever a new update is available in Software Update, the Discussions are usually flooded with a raft of "should I install this?" questions.
There are also a set of related posts shortly thereafter claiming the update "Destroyed my Mac, ran off with my wife, and kicked my dog."
Usually both sets of issues can be avoided by following the guidelines in my "Installing Software Updates" FAQ.
And before someone raises the issue of the Photoshop / AFP problem that resulted from the 10.4.6 Update, I submit this is a Photoshop bug.
Adobe seems to have developed a practice of not testing their applications with the Developer Previews of Mac OS X. Adobe now seems to prefer to wait until an Update causes a problem, rather than finding problems in their code that will arise due to changes introduced in the Mac OS X Update. Third-party developers, such as Adobe, have both the opportunity — through membership in the Apple Developer Program — and the responsibility for testing their applications and identifying issues that may arise in Updates by testing with the Developer Previews of Mac OS X Updates.
Likewise, if folks would get in the habit of making backups of their running Mac OS X installation before installing Software Updates, as recommended in my FAQ cited above, they would have a fallback position in the event that an Update was either problematic, buggy, or failed to install properly. Using a computer without having implemented a proper Backup and Recovery solution, and using it regularly, is like driving without auto insurance.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

Similar Messages

How to get notified when new java SE update is released

We need to track security and performance bug fixes and features introduced in each new Java release that comes out. Is there a linked that we can monitor or feed that updates us when a new java version comes out? Do we need a support contract to receive these updates?
http://www.oracle.com/technetwork/java/javase/7u-relnotes-515228.html
Thanks,
Amer-netflix

Have you look at http://www.oracle.com/us/syndication/feeds/index.html ?

New Java 1.6.0_31 and Forms 11.1.2

After new java release 1.6.0_31, Java console is filling with trace:
oracle.ewt.swing.JBufferedFrame[JBufferedFrame0,0,0,2015x1061,invalid,layout=oracle.ewt.popup.PopupHandler,title=INTERSPORT ISI, D.O.O.,resizable,normal]
oracle.ewt.event.tracking.GlassMouseGrabProvider$Proxy[GlassMouseGrabProvider$Proxy0,0,0,2015x1061,invalid]
oracle.forms.ui.mdi.MDIContainer[MDIContainer1,8,30,1999x1023,layout=java.awt.BorderLayout]
oracle.ewt.EwtComponent[EwtComponent2,0,57,1999x924,layout=java.awt.BorderLayout]
oracle.ewt.scrolling.scrollBox.ScrollBox[ScrollBox3,0,0,1999x924,layout=oracle.ewt.scrolling.scrollBox.ScrollBoxLayout]
oracle.ewt.scrolling.scrollBox.ScrollBox$1[ScrollBox$14,0,0,1999x924,layout=oracle.ewt.scrolling.scrollBox.ScrollBoxClipLayout]
oracle.forms.ui.FormDesktopContainer[FormDesktopContainer5,0,0,1999x924,layout=oracle.ewt.lwAWT.lwWindow.DesktopLayout]
oracle.forms.ui.ExtendedFrame[ExtendedFrame6,0,0,487x409,hidden,layout=oracle.ewt.layout.MaximumBorderLayout, oracle.ewt.laf.generic.GenericWindowBorder@578073]
oracle.ewt.lwAWT.lwWindow.LWWindow$FocusTransferComp[LWWindow$FocusTransferComp7,-1,-1,0x0]
oracle.ewt.lwAWT.lwWindow.laf.TitleBar[TitleBar8,4,4,479x18,layout=oracle.ewt.layout.MaximumBorderLayout, oracle.ewt.painter.FixedBorderPainter@b20352]
oracle.ewt.lwAWT.lwWindow.laf.TitleBar$SystemMenuBar[TitleBar$SystemMenuBar9,2,1,18x16,layout=oracle.ewt.lwAWT.lwMenu.PreferredRowLayout]
oracle.ewt.lwAWT.LWComponent[LWComponent10,0,0,18x16,layout=oracle.ewt.lwAWT.lwMenu.PreferredRowLayout]
oracle.ewt.lwAWT.lwWindow.laf.TitleBar$SystemMenu[TitleBar$SystemMenu0,0,0,18x16, null]
oracle.ewt.lwAWT.LWComponent[LWComponent11,20,1,407x16,layout=oracle.ewt.layout.DirectionalBorderLayout]
oracle.ewt.lwAWT.LWLabel[LWLabel0,0,0,59x16,align=left,text=Moje Mape]
oracle.ewt.lwAWT.lwWindow.laf.TitleBar$CaptionComp[TitleBar$CaptionComp12,59,0,348x16]
oracle.ewt.toolBar.ToolBar[ToolBar13,427,1,50x16]
oracle.ewt.lwAWT.LWComponent[LWComponent14,4,22,479x383,layout=oracle.ewt.layout.MaximumBorderLayout]
oracle.ewt.EwtComponent[EwtComponent15,0,0,479x383,layout=java.awt.BorderLayout]
oracle.ewt.lwAWT.LWContainer[LWContainer16,0,0,479x0,layout=java.awt.BorderLayout]
oracle.ewt.lwAWT.LWContainer[LWContainer17,0,0,479x0,layout=java.awt.BorderLayout]
oracle.forms.ui.DrawnPanel[DrawnPanel18,0,0,479x383,hidden,layout=java.awt.BorderLayout, oracle.ewt.painter.NullPainter@f8395f]
oracle.ewt.lwAWT.LWContainer[LWContainer19,0,0,0x383,layout=java.awt.BorderLayout]
oracle.forms.ui.DrawnPanel[DrawnPanel20,0,0,479x383,hidden,layout=java.awt.BorderLayout, oracle.ewt.painter.NullPainter@f8395f]
oracle.forms.ui.FScrollBox[FScrollBox21,0,0,479x383,hidden,layout=oracle.ewt.scrolling.scrollBox.ScrollBoxLayout, oracle.ewt.painter.NullPainter@f8395f]
oracle.ewt.scrolling.scrollBox.ScrollBox$1[ScrollBox$122,0,0,479x383,layout=oracle.forms.ui.FScrollBoxClipLayout]
oracle.forms.ui.DrawnPanel[DrawnPanel23,0,0,479x383,hidden]
oracle.forms.ui.FScrollBox[FScrollBox24,0,0,226x28,hidden,layout=oracle.ewt.scrolling.scrollBox.ScrollBoxLayout, oracle.ewt.painter.NullPainter@f8395f]
oracle.ewt.scrolling.scrollBox.ScrollBox$1[ScrollBox$125,0,0,226x28,layout=oracle.forms.ui.FScrollBoxClipLayout]
oracle.forms.ui.DrawnPanel[DrawnPanel26,0,0,226x29,hidden]
oracle.forms.ui.FScrollBox[FScrollBox27,0,0,480x384,hidden,layout=oracle.ewt.scrolling.scrollBox.ScrollBoxLayout, oracle.ewt.painter.NullPainter@f8395f]
oracle.ewt.scrolling.scrollBox.ScrollBox$1[ScrollBox$128,0,0,480x384,layout=oracle.forms.ui.FScrollBoxClipLayout]
oracle.forms.ui.DrawnPanel[DrawnPanel29,0,0,480x384,hidden]
oracle.ewt.scrolling.scrollBox.ScrollBox[ScrollBox30,16,12,447x320,layout=oracle.ewt.scrolling.scrollBox.ScrollBoxLayout, oracle.ewt.laf.generic.GenericInsetBorderPainter@7e9ce2]
oracle.ewt.dTree.DTree[DTree31,2,2,443x316]
oracle.ewt.scrolling.scrollBox.EwtLWScrollbar[EwtLWScrollbar32,2,302,427x16,hidden,val=0,vis=1,min=0,max=1,horz]
oracle.ewt.button.ContinuousButton[ContinuousButton0,411,0,16x16]
New feature or something else?
Regards

New feature or something else?So, is there a problem/error or are you just curious about the classes listed in the stack trace? What ever the point of your post is, it is not clear! Please explain!
Craig...

New J2SE Release

I've heard about a new Java Release which is optimized concerning the size of the J2SE SDK Platform file.
The current file is about 51 MB big including a lot of languges. I'm searching for a smaller file (5MB) which only contains one supported language or even 3 specific languages.
At the moment I use J2SE v.1.4.2_05 SDK, but the download file is still available in multi-language
--> Windows Offline Installation, Multi-language (j2sdk-1_4_2_05-windows-i586-p.exe, 51.09 MB)
On our clients we use Java Webstart to install this java package. Now we want to gain performance in our network by using smaller files adapted to our required languages.
I'm very thankful for any help or reference where I can find something about this topic!

Language support is not what makes the JRE big.
Note you probably don't need the SDK, but only the JRE.
I've heard about a new Java Release which is optimized concerning the size of the J2SE SDK Platform file. Maybe you're refering to the class data sharing technology which optimizes the memory footprint:
see "Scalability and Performance" section here: http://java.sun.com/developer/technicalArticles/releases/j2se15/
-Alexis

When you will release a new java update ? With the last it doesn't work correctly ( java 3d )

I use java 3d, but with the last update it doesn't works with any browser

"When you will release a new java update ?"
"We" don't release anything; we're not Apple, we're just users like you.
Use the feedback form to send queries to Apple.
http://www.apple.com/feedback/macosx.html

Question about the new JAVA Update J2SE 5.0 Release 3

Here is some info about this update:
Java 2 Platform, Standard Edition (J2SE) 5.0 Release 3 allows applications and applets developed for the J2SE 5.0 platform to run on Mac OS X v 10.4.2 and later.
This update does NOT CHANGE the DEFAULT VERSION of Java on your Mac from Java 1.4.2 to J2SE 5.0, though Java applications that require J2SE 5.0 may specifically request it. You can change the preferred Java version for applications and applets by using the new Java Preferences utility. This utility is installed by the J2SE 5.0 update at /Applications/Utilities/Java/J2SE 5.0/.
http://docs.info.apple.com/article.html?artnum=302412
HERE IS MY QUESTION---
This update makes me nervous cause I don't know much about Java. IF I change my default version to this new 5.0 will it mean that some of the older Java stuff on the web won't work? Should I just download this and ignore it? What should I do about this update?
Thanks for the help!
Renée

I too seem to be suffering issues with loading web pages after the 10.4.3/Java 5.0 update. I have reinstalled both updates, changed the java settings, emptied all the caches, and tried various combinations thereof, and I still have problems with web pages loaded. most of the problems appear to be related to rendering frames and images - In fact a couple of web sites I navigate to (upon looking at the source for the page" state "It appears your browser does not support frames." I think this is something broken in the latest release. Unfortunately, I cannot reinstall the latest copy of Safari, because the installer states "This version of Safari cannot be installed. It requires version 10.4.2." I guess I am in a pickle until Apple comes out with another update. BTW I have some pages that Safari will not render but IE running on the same box will. I also noticed that the problem propagated to other applications that use Java....For instance the Dashboard widget from google (Google Maps) no longer renders the tiled (framed?) map pieces...instead you get the ubiquitous "?" icon.

Error after installing the new JSF release

I've got a problem to install the new JSF release. I downloaded the Web Services Developer Pack 1.3 from the homepage and installed it. Then, i downloaded the actual release of the JSF 1.0 as a zip file. I removed the existing jsf directory in the original WSDP and extracted the zip file into the home directory of the WSDP. Then I renamed the directory from jsf-1.0 to jsf and started the tomcat again.
But then I get the following errors and tomcat isn't working at all:
Mar 19, 2004 1:43:52 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on port 8080
Mar 19, 2004 1:43:52 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 3297 ms
Mar 19, 2004 1:43:52 PM org.apache.catalina.core.StandardService start
INFO: Starting service Java Web Services Developer Pack
Mar 19, 2004 1:43:52 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Java Web Services Developer Pack/1.3
Mar 19, 2004 1:43:52 PM org.apache.catalina.core.StandardHost getDeployer
INFO: Create Host deployer for direct deployment ( non-jmx )
Mar 19, 2004 1:43:53 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Processing Context configuration file URL file:H:\jwsdp-1.3\conf\Catalina\localhost\jwsdp-catalog.xml
Mar 19, 2004 1:43:54 PM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Skipped installing application listeners due to previous error(s)
Mar 19, 2004 1:43:54 PM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
Mar 19, 2004 1:43:54 PM org.apache.catalina.core.StandardContext start
SEVERE: Context startup failed due to previous errors
Mar 19, 2004 1:43:54 PM org.apache.catalina.logger.LoggerBase stop
INFO: unregistering logger Catalina:type=Logger,path=/jwsdp-catalog,host=localhost
Mar 19, 2004 1:43:54 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Processing Context configuration file URL file:H:\jwsdp-1.3\conf\Catalina\localhost\jstl-examples.xml
Mar 19, 2004 1:44:03 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Processing Context configuration file URL file:H:\jwsdp-1.3\conf\Catalina\localhost\jsf-cardemo.xml
Mar 19, 2004 1:44:14 PM com.sun.faces.config.rules.NavigationRuleRule end
WARNING: [NavigationRuleRule]{faces-config/navigation-rule} Merge(/confirmChoices.jsp)
Mar 19, 2004 1:44:16 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Processing Context configuration file URL file:H:\jwsdp-1.3\conf\Catalina\localhost\jsf-nonjsp.xml
Mar 19, 2004 1:44:27 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Processing Context configuration file URL file:H:\jwsdp-1.3\conf\Catalina\localhost\jsf-components.xml
Mar 19, 2004 1:44:40 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Processing Context configuration file URL file:H:\jwsdp-1.3\conf\Catalina\localhost\jsf-guessNumber.xml
Mar 19, 2004 1:44:52 PM com.sun.faces.config.ConfigureListener verifyObjects
INFO: Application object verification completed successfully
Mar 19, 2004 1:44:52 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Processing Context configuration file URL file:H:\jwsdp-1.3\conf\Catalina\localhost\admin.xml
Mar 19, 2004 1:44:53 PM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Skipped installing application listeners due to previous error(s)
Mar 19, 2004 1:44:53 PM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
Mar 19, 2004 1:44:53 PM org.apache.catalina.core.StandardContext start
SEVERE: Context startup failed due to previous errors
Mar 19, 2004 1:44:53 PM org.apache.catalina.logger.LoggerBase stop
INFO: unregistering logger Catalina:type=Logger,path=/admin,host=localhost
Mar 19, 2004 1:44:53 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Processing Context configuration file URL file:H:\jwsdp-1.3\conf\Catalina\localhost\manager.xml
Mar 19, 2004 1:44:54 PM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Skipped installing application listeners due to previous error(s)
Mar 19, 2004 1:44:54 PM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
Mar 19, 2004 1:44:54 PM org.apache.catalina.core.StandardContext start
SEVERE: Context startup failed due to previous errors
Mar 19, 2004 1:44:54 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path from URL file:H:\jwsdp-1.3\webapps\ROOT
Mar 19, 2004 1:44:54 PM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Skipped installing application listeners due to previous error(s)
Mar 19, 2004 1:44:54 PM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
Mar 19, 2004 1:44:54 PM org.apache.catalina.core.StandardContext start
SEVERE: Context startup failed due to previous errors
Mar 19, 2004 1:44:54 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /jsp-examples from URL file:H:\jwsdp-1.3\webapps\jsp-examples
Mar 19, 2004 1:44:55 PM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Skipped installing application listeners due to previous error(s)
Mar 19, 2004 1:44:55 PM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
Mar 19, 2004 1:44:55 PM org.apache.catalina.core.StandardContext start
SEVERE: Context startup failed due to previous errors
Mar 19, 2004 1:44:55 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /servlets-examples from URL file:H:\jwsdp-1.3\webapps\servlets-examples
Mar 19, 2004 1:44:56 PM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Skipped installing application listeners due to previous error(s)
Mar 19, 2004 1:44:56 PM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
Mar 19, 2004 1:44:56 PM org.apache.catalina.core.StandardContext start
SEVERE: Context startup failed due to previous errors
Mar 19, 2004 1:44:56 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on port 8080
Mar 19, 2004 1:44:56 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 63891 ms
So what's wrong with my installation.
kind regards, Ingo

Your server may be in an unstable state if you did not remove all of the old cached files.
I recommend you clear out your <JWSDP_HOME>/work directory and remove all the <JWSDP_HOME>/conf/Catalina/localhost/jsf* files and restart your server.
Thanks,
Justyna

New major release, JE 5.0, is available

Hi all,
We're pleased to announce a new major release, JE 5.0.34. The release contains a significant number of new features and performance enhancements. Complete information can be found in the JE documentation, specifically in the change log. The release is available via the download site or Maven.
Below is a copy of the major enhancements listed in the release notes. See the change log for a complete list.
<li> The new DiskOrderedCursor class can be used to iterate over all records in a database, for increased performance when transactional guarantees are not required. [#15260]
<li> A new Environment.preload method can be used to preload multiple databases at a time, for increased performance compared to preloading each database individually. [#18153]
<li> The JE environment can now be spread across multiple subdirectories to take advantage of multiple disks or file systems. [#19125]
<li> The new AppStateMonitor class lets the HA application add more application specific information to the notion of node state in a replication group. [#18046]
<li> New options have been added for changing the host of a JE replication node, and for moving a JE replication group. See the Utilities section of the change log.
<li> Replicated nodes can now be opened in UNKNOWN state, to support read only operations in a replicated system when a master is not available. [#19338]
<li> New Cursor methods were added to allow quickly skipping over a specified number of key/value pairs. [#19165]
<li> A per-Environment ClassLoader may now be configured and will be used by JE for loading all user-supplied classes. [#18368]
<li> The java.io.Closeable interface is now implemented by all JE classes and interfaces with a public void close() method. This allows using these objects with the Java 1.7 try-with-resources statement. [#20559]
<li> The Environment.flushLog method has been added. It can be used to make durable, by writing to the log, all preceding non-transactional write operations, without performing a checkpoint. [#19111]
<li> Performance of record update and deletion operations has been significantly improved when the record is not in the JE cache and the application does not need to read the record prior to performing the update or deletion. [#18633]
<li> An internal format change was made for databases with duplicate keys that improves operation performance, reduces memory and disk overhead, and increases concurrency. [#19165]
<li> An improvement has been made that requires significantly less writing per checkpoint, less writing during eviction, and less metadata overhead in the JE on-disk log files. [#19671]
<li> Improved DbCacheSize utility to take into account memory management enhancements and improve accuracy. Added support for key prefixing, databases configured for sorted duplicates, and replicated environments. [#20145]
<li> EnvironmentConfig.TREE_COMPACT_MAX_KEY_LENGTH was added for user configuration of the in-memory compaction of keys in the Btree. [#20120]
-- The JE Team

The format change is for BDB Java Edition 5.0 only, and does not apply to other BDB products. It's forward compatible, which means that a BDB JE application using JE 5.0 can use environments written with older versions of JE. However, it's not backwards compatible; once your environment has been opened by JE 5.0, it's been converted to the new format, and can no longer be readable by older versions of JE.
Just for the benefit of others who may not have read the changelog, here's the full text:
JE 5.0.34 has moved to on-disk file format 8.
The change is forward compatible in that JE files created with release 4.1 and earlier can be read when opened with JE 5.0.34. The change is not backward compatible in that files created with JE 5.0 cannot be read by earlier releases. Note that if an existing environment is opened read/write, a new log file is written by JE 5.0 and the environment can no longer be read by earlier releases.
There are two important notes about the file format change.
The file format change enabled significant improvements in the operation performance, memory and disk footprint, and concurrency of databases with duplicate keys. Environments which contain databases with duplicate keys must run an upgrade utility before opening an environment with this release. See the Performance section for more information.
An application which uses JE replication may not upgrade directly from JE 4.0 to JE 5.0. Instead, the upgrade must be done from JE 4.0 to JE 4.1 and then to JE 5.0. Applications already at JE 4.1 are not affected. Upgrade guidance can be found in the new chapter, "Upgrading a JE Replication Group", in the "Getting Started with BDB JE High Availability" guide.I may not have fully understood your question, so let us know if that doesn't answer it.
Edited by: Linda Lee on Dec 1, 2011 10:41 AM

ANN: XML Parser for Java Release 1.0.1.4

A new maintenance release of the Oracle Parser for Java is
available for download. It has the following fixes and changes:
Bug fixes for #893971, i.e XML parser cannot parse documents
from InputStream;
#900146 normalize() is wrong if the literal contains angle
brackets;
#898423, multiplicity info about elements enhancement.
New API in the following Classes:
1. oracle.xml.parser.ElementDecl
-getParseTree( Returns the root Node of Content Model
parse tree, which could then be traversed node by node using
getFirstChild() and getLastChild() ).
This is the fourth production patch release. Oracle XML Parser
1.0.1.4.0
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
null

The link has been fixed. You will go to the v2 download page
now. Sorry for the inconvience.
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
Renilton Oliveira (guest) wrote:
: I didn't find the file for version 2.0.0.0 as well.
: Renilton
: Andrei Filimonov (guest) wrote:
: : I tried to download XML Parser for Java v2 it seems that
only
: v
: : 1.0.1.4 is available. Could you please give an exact URL for
: v2
: : download?
: : Andrei Filimonov
: : Oracle XML Team wrote:
: : : The Oracle XML v2 parser is now available for download
here
: as
: : : an early beta release and is written in Java. It features
: an
: : : improved architecture over the Oracle XML v1 parser and
has
: : : shown better performance on small to large XML documents.
: It
: : : will also be able to format the XML document according to
a
: : : stylesheet, having integrated an XSLT processor.
: : : Version 2 of the XML Parser for Java, besides
incorporating
: an
: : : XSLT processor, has been re-architected from version 1.
This
: : has
: : : resulted in a number of changes to the class names
: especially
: : : those that support Namespaces. See v2changes.txt and
: the .diff
: : : difference files in the sample directory.
: : : Oracle XML Team
: : : http://technet.oracle.com
: : : Oracle Technology Network
null

Security 2009-01 and Java release 8 - which first?

Software update shows it's time for Security 2009-01 and Java Release 8. Java comes first on the list.
I do updates via downloads from Apple and install later. Should I install the Java release first?
Mrs H
BTW - The updates for Security used to indicate "Client" or "Server". This one just indicates Tiger PPC, Intel Tiger, Server Tiger, Leopard Server etc - has Client gone by the wayside?

Hi BDA,
A Safe Boot will prevent most of those from interfering, btw, this G4 I did the Alphabetically...
Alphabetically! Well, I'll be... I thought there was some secret significance here to the sequence - for example, you must do QT before iT.
...updating to had 5 Firewire Drives, 2 eSata Drives, 14 USB Devices besides the KB & Mouse, and four USB RAID Drives hooked up to it during the Updates... no problem here.
So maybe I don't have to disconnect my modem? (I leave the printer disconnected anyway, so I can connect to whichever Mac I need for printing)
Was that Klaus that told you that! (about points)? LOL
No, just my own thinking.
Yes indeed, thank you again, great news that you're getting more comfortable/knowledgeable about your Macs!
And it's only taken 20 years of working with Macs to do that!
Mrs H
To see where my current frustrations/confusions/issues lie check out:
http://discussions.apple.com/thread.jspa?threadID=1903870&tstart=0
and
http://discussions.apple.com/thread.jspa?threadID=1888621&tstart=0

ANN: New XDK release for 9.0.2B and 9.0.1.1.0A available

New XDK Releases for 9.0.2B Beta Version and 9.0.1.1.0A Procudtion Version are online at:
http://technet.oracle.com/tech/xml/xdkhome.html
What's new:
- Oracle9i XDK for C and C++ released on Linux
- Oracle TransX Utility Aids loading data and text.These release is part of the XDK for Java 9.0.2 Beta.
- Oracle SOAP APIs added to the XDK for Java
Support for the SOAP services have been added to the XDK for Java 9.0.1.1.0A Production.
- XML Schema Processor for Java supports both LAX Mode and STRICT Mode Validation
The XML Schema Processor for Java now supports both LAX Mode and STRICT
Mode Validation. Compared with STRICT Mode where every element from the root on down is required to be defined and validated, LAX Mode Schema validation provides developers the ability to limit the XML Schema
validation to the subsections of the XML document.
This will simplify XML Schema definitions and the validation process by skipping the ignorable content. Furthermore, with LAX mode, developers can divide their XML documents into small fragments and carry out the XML Schema validation in a parallel or progressive way. This results, in a much more flexible and productive schema validation process.
- SAX2 Extension support in the Java XML Parser
The XML Parser for Java now supports two new handlers - LexicalHandler and DeclHandler.
XML documents now can be parsed through Oracle XML Parser SAX APIs with full access
to the DTD declarations and the lexical items like comments and CDATA sections.
This ensures that the complete content model is preserved.
- JAXP 1.1 supports is now added to the XDK for Java
- New Differ Bean in the XDK for JavaBeans
A new bean has been added the the JavaBean XDK which analyses the differences between to XML documents and outputs the XSL sytlesheet that will convert one into the
other. This is extremely useful when converting an XML document retrieved from a SQL query into an xHTML page on the web.
Stylesheets can now be automaticly created for use in XSQL pages.
- XML Compression now supported in the Java XML Parser
Now developers can take advantage of a compressed XML stream when serializing their DOM and SAX outputs. This new functionality significantly reduces the size without losing any information. Both DOM and SAX compressed streams are fully compatible and the SAX stream can be used to generate a
corresponding DOM tree. These compressed streams can also be stored in Oracle as a CLOB for efficient storage and retrieval.

bump up for east cost.

New major release of Sun Storage 7000 software is available

I noticed a new major release of the Sun Storage 7000 software is available at the website below.
http://wikis.sun.com/display/FishWorks/Sun+Storage+7000+Series+Software+Updates.

The format change is for BDB Java Edition 5.0 only, and does not apply to other BDB products. It's forward compatible, which means that a BDB JE application using JE 5.0 can use environments written with older versions of JE. However, it's not backwards compatible; once your environment has been opened by JE 5.0, it's been converted to the new format, and can no longer be readable by older versions of JE.
Just for the benefit of others who may not have read the changelog, here's the full text:
JE 5.0.34 has moved to on-disk file format 8.
The change is forward compatible in that JE files created with release 4.1 and earlier can be read when opened with JE 5.0.34. The change is not backward compatible in that files created with JE 5.0 cannot be read by earlier releases. Note that if an existing environment is opened read/write, a new log file is written by JE 5.0 and the environment can no longer be read by earlier releases.
There are two important notes about the file format change.
The file format change enabled significant improvements in the operation performance, memory and disk footprint, and concurrency of databases with duplicate keys. Environments which contain databases with duplicate keys must run an upgrade utility before opening an environment with this release. See the Performance section for more information.
An application which uses JE replication may not upgrade directly from JE 4.0 to JE 5.0. Instead, the upgrade must be done from JE 4.0 to JE 4.1 and then to JE 5.0. Applications already at JE 4.1 are not affected. Upgrade guidance can be found in the new chapter, "Upgrading a JE Replication Group", in the "Getting Started with BDB JE High Availability" guide.I may not have fully understood your question, so let us know if that doesn't answer it.
Edited by: Linda Lee on Dec 1, 2011 10:41 AM

New patch releases: JE 5.0.48 and 4.1.20

All,
Please note that new patch releases for JE 5.0 and 4.1 are now available.
The JE 5.0.48 update contains a number of critical bug fixes that can cause corruption (data loss) under certain circumstances. We strongly recommend that anyone using JE 5 upgrade immediately to 5.0.48. This update also contains fixes for issues that prevent upgrading to JE 5 from an earlier release, or cause problems after upgrading.
Note that running the pre-upgrade utility is mandatory before upgrading to JE 5 from an earlier release, and the pre-upgrade utility must be run using JE 4.0.20. The JE 4.0.20 update contains fixes to the pre-upgrade utility as well as one critical bug fix. See the first section in the JE 5.0.48 change log for detailed information on upgrading and running the pre-upgrade utility.
We'd like to thank all the users who reported problems and especially those who worked with us over email, in some cases for long periods of time, to diagnose problems and test fixes. Some, but not all, of those who helped are mentioned in the change log. Thank you for contributing to the reliability of the product!
Complete information can be found in the JE documentation. The release is available via the download site or Maven.
--mark

Hi,
the biggest problem is that we are using bought application not made in our company. I have tried out this java application with JRE 1.4 and 1.5 and it just doesn't work. So the only solution is using JRE 1.3 on all intranet computers. This application uses digital certificate so why doesn't Sun allow digital signet java programs to run on older versions of JRE?
There could also be one more solution. I exactly know md5sum (or sha1sum) of 3 JAR files used by applet needing JRE 1.3. So if this sum would be enabled manualy (or I could send batch file to make this in registry or any other storage this would be good).
http://en.wikipedia.org/wiki/Md5sum
http://en.wikipedia.org/wiki/Sha1sum
Thanks,
Grofaty

Java 8: Pb with new java.time api

Hello,
I'm trying to use the new java.time api that comes with Java 8 (I already know joda-time).
I'm using the latest build B124.
I've a String "01/08/2012_00:00:01", I know that the time ref. is UTC, and I want to convert it to an 'Instant';
I tried:
DateTimeFormatter FORMAT_DT = DateTimeFormatter.ofPattern("dd/MM/yyyy_HH:mm:ss").withZone(ZoneOffset.UTC);
Instant instant = Instant.from(FORMAT_DT.parse("01/08/2012_00:00:01"));
But it fails with following error:
java.time.DateTimeException: Unable to obtain Instant from TemporalAccessor: {},ISO resolved to 2012-08-01T00:00:01 of type java.time.format.Parsed
at java.time.Instant.from(Unknown Source)
I don't understand what's wrong with my code, and I can't figure out how I should proceed to convert the String to an Instant ...
Any suggestion welcome,
Best regards,
Bernard.

Originally you stated this:
I don't understand what's wrong with my code,
So naturally we focused on how to "understand what's wrong' with your code.
You will never learn to troubleshoot problems if you just throw your hands up in the air and ask for help just because a complex series of steps doesn't complete successfully.
Break the process into its individual steps and check the results of each step to identify which step is FIRST producing an error.
When a complex or multi-step process has an error you start checking the individual steps of the process to see how far it gets successfully.
I would expect that converting a String to an Instant should be a basic/simple need, so it should be possible to do it in two lines of code; for the time being, the only way I found is to use a LocalDateTime intermediate variable, which seems quite verbose, and I'm wondering if someone knows a better way to do it, and would be willing to share it here.
Just a technical distinction: your latest example using a LocalDateTime intermediate variable CAN be done in one line of code by just using dot-notation to avoid creating an explicit intermediate variable. But that variable will still be created implicitly behind the scenes.
Converting a String to an Instant might be considered a basic/simple need but the set of functionality related to dealing with times, dates, calendars, etc is extremely complex. It makes much more sense to develop the requisite functionality in modules.
Especially when introducing new functionality such as the 'Instant' class are related package elements introduced in 1.8. That functionality builds on what came before and parsers already existing that know how to deal with all of the possible String variants and formatting options and so on.
Since that work CAN BE done on-the-fly using dot notation and anonymous implicit intermediate classes there isn't much need to reinvent that functionality in the new classes. If certain uses become standard new methods can always be added (e.g. to the Instant class) that will 'appear' to do things in one step.
And, being an early adopter release, you can always file a 'bug' or enhancement request from the 1.8 download page. That page has links for 'Report Bugs' and 'Feedback forum' that you can use.
In this current forum no one can give you an 'official' answer as to why something was implemented a particular way and/or whether that implementation is a 'bug' or was designed to work that way. Only Oracle can do that.

Trying to find Java release 1.6.0.1_45, any ideas

Trying to find Java release 1.6.0.1_45, any ideas

why this version ?
if you heard about security issues in later versions it will 90% be in the older one too
oracle is not adding new features to the java releases they are fixing security issues and bugs
most security issues
I keep the latests version but only have it enabled in a browser I otherwise don't use
in osx it's Safri in Windows8 it's IE
and then I only use those browsers when I have to do something which require java like my netbank and everything in relation to state and govenment

New Java Release

Similar Messages

Maybe you are looking for