Here's How To Get iOS 6 Right Now

First make your way to Apple's developer center website. It's at developer.apple.com. Go to the iOS Dev Center.




 

Then you'll want to register a free account. Go through the process and put in all your information.



Once you have your account, log in on the iOS Dev Center.

Click on the iOS 6 button on the iOS developer center page.

 



If you aren't a registered developer, you'll have to spend $99 a year to sign up.

From there, jump to the downloads page...

...and download the appropriate version of iOS 6 for your device. We have an iPhone 4S, so we went with that.

Bang! Here we go.

 

This is the file you'll get. It's useless if you click on it, so go to iTunes.




Find your phone on the iTunes navigation bar.




With your phone plugged in, hold the option/alt key on the keyboard and press "restore." We advise that you back your phone up first.




Go to the file you unpacked for iOS 6, and select that one.




 

It'll give you one final warning before installing iOS 6 on your iPhone.

 

And you're done! It'll take a few minutes to install and update, and you'll be good to go



 

If you can't wait to try it out.

Here's What Really Happens To The 20,000 Bodies Donated To Science Each Year In The US

 

Mary Roach wanted to know what happened to bodies once they were donated to science. In her research, she found a 2,000 year history of cadavers and all they've accomplished for society.

The result is her book "Stiff: The Curious Lives of Human Cadavers," a non-fiction account of her research. She published it back in 2003, but the history and facts are still well worth reading.

About 20,000 U.S.bodies are donated to science every year, according to the Orange County Register.

Cadavers have flown in space and endured car crashes. They've been crucified to test the authenticity of the Shroud of Turin. One famous artist even spent his life savings so he could eat their flesh for two months.

The images are from videos of the Body Worlds exhibit, a display of cadavers.

 

Future iPhones May Have Interchangeable Camera Lenses

A patent filing uncovered by AppleInsider suggests that Apple is interested in making it possible to swap out different lenses for photography on your iPhone.

 

From the patent: "It would be desirable to provide a structure for a compact device that allows the end user to reconfigure the optical arrangement of the device while retaining the benefits of assembling the device using a pre-assembled digital imaging subsystem."

Steve Jobs had told Walter Isaacson before passing away that he wanted to reinvent the photography market.

These 6 Corporations Control 90% Of The Media In America

This infographic created by Jason at Frugal Dad shows that almost all media comes from the same six sources.

That's consolidated from 50 companies back in 1983.

NOTE: This infographic is from last year and is missing some key transactions. GE does not own NBC (or Comcast or any media) anymore. So that 6th company is now Comcast. And Time Warner doesn't own AOL, so Huffington Post isn't affiliated with them.

But the fact that a few companies own everything demonstrates "the illusion of choice," Frugal Dad says. While some big sites, like Digg and Reddit aren't owned by any of the corporations, Time Warner owns news sites read by millions of Americans every year.

Here's the graphic:

The New MacBook Pro: Unfixable, Unhackable, Untenable

iFixit removes the logic board from the new MacBook Pro with Retina Display during their teardown. Photo: iFixit

 

This week, Apple delivered the highly anticipated MacBook Pro with Retina Display — and the tech world is buzzing. I took one apart yesterday because I run iFixit, a team responsible for high-resolution teardowns of new products and DIY repair guides. We disassemble and analyze new electronic gizmos so you don’t have to — kind of like an internet version of Consumer Reports.

Kyle Wiens

The Retina MacBook is the least repairable laptop we’ve ever taken apart: Unlike the previous model, the display is fused to the glass, which means replacing the LCD requires buying an expensive display assembly. The RAM is now soldered to the logic board — making future memory upgrades impossible. And the battery is glued to the case, requiring customers to mail their laptop to Apple every so often for a $200 replacement. The design may well be comprised of “highly recyclable aluminum and glass” — but my friends in the electronics recycling industry tell me they have no way of recycling aluminum that has glass glued to it like Apple did with both this machine and the recent iPad.

The design pattern has serious consequences not only for consumers and the environment, but also for the tech industry as a whole.

The Retina MacBook is the least repairable laptop we’ve ever taken apart.

Four years ago, Apple performed a market experiment. They released the super thin, but non-upgradeable, MacBook Air in addition to their two existing, easily upgradeable notebooks: the MacBook and the MacBook Pro. Apple’s laptops had evolved over two decades of experience into impressively robust, rugged, and long-lasting computers. Apple learned a lot from the failings of the past: the exploding batteries of the PowerBook 5300, the flaky hinges of the PowerBook G4 Titanium, the difficult-to-access hard drive in the iBook.

Apple’s portable lineup was a triumph — for consumers and for Apple itself. IT professionals the world over love working on the MacBook. I’ve disassembled a few of them myself, and I can attest that they are almost as easy to repair as they are to use.

The 2008 Air went in a new direction entirely: It sacrificed performance and upgradeability in exchange for a thinner design. Its RAM is soldered to the logic board (as in the Retina MacBook Pro), so upgrading it means replacing the entire expensive logic board. And like all laptops, the Air has a built-in consumable. The MacBook Air’s battery was rated to last just 300 charges when it was introduced. But unlike laptops before it, replacing the Air’s battery required specialized tools and removing some 19 screws.

When Apple dropped the MacBook Air to $999 in 2010 to match the price point of the MacBook, they gave users a clear choice: the thin, light, and un-upgradeable MacBook Air or the heavier, longer lasting, more rugged, and more powerful MacBook. Same price, two very different products. At the time, I wasn’t very happy with the non-upgradeable RAM on the MacBook Air, but I respected that Apple had given their users a choice. It was up to us: Did we want a machine that would be stuck with 2GB of RAM forever? Would we support laptops that required replacement every year or two as applications required more memory and batteries atrophied?

Apple has presented the market with a choice. They have two professional laptops: one that is serviceable and upgradeable, and one that is not.

Consumers overwhelmingly voted yes, and the Air grew to take 40 percent of Apple’s notebook sales by the end of 2010.

The success of the non-upgradeable Air empowered Apple to release the even-less-serviceable iPad two years later: The battery was glued into the case. And again, we voted with our wallets and purchased the device despite its built-in death clock. In the next iteration of the iPad, the glass was fused to the frame.

Once again, with another product announcement, Apple has presented the market with a choice. They have two professional laptops: one that is serviceable and upgradeable, and one that is not. They’re not exactly equivalent products — one is less expensive and supports expandable storage, and the other has a cutting-edge display, fixed storage capacity, and a premium price tag — but they don’t have the same name just to cause confusion. Rather, Apple is asking users to define the future of the MacBook Pro.

Apple isn’t fundamentally against upgradeability and accessibility. The current Mac Mini has compelling finger slots that practically beg people to open it. When Steve Jobs released the “open-minded” Power Mac G3 with a door that opened from the side, the audience oohed and aahed. Apple products have historically retained their value quite well, in part due to third-party repair manuals, but also due to a number of very modular, very upgradeable designs.

Even the MacBook Pro was originally touted as an accessible, repairable machine — at Macworld in 2009, Steve Jobs said, “Our pro customers want accessibility: [...] to add memory, to add cards, to add drives.” That’s part of what I love about my MacBook Pro. I’ve upgraded my RAM, and I even replaced my optical drive with an 80GB SSD.

We have consistently voted for hardware that’s thinner rather than upgradeable. But we have to draw a line in the sand somewhere.

On the other hand, Apple has consistently introduced thinner, lighter products. They learn from experience. They react to their customers. They’re very adept at presenting us with what we want. And they give us options from time to time and allow product sales to determine their future designs.

We have consistently voted for hardware that’s thinner rather than upgradeable. But we have to draw a line in the sand somewhere. Our purchasing decisions are telling Apple that we’re happy to buy computers and watch them die on schedule. When we choose a short-lived laptop over a more robust model that’s a quarter of an inch thicker, what does that say about our values?

Every time we buy a locked down product containing a non-replaceable battery with a finite cycle count, we’re voicing our opinion on how long our things should last. But is it an informed decision? When you buy something, how often do you really step back and ask how long it should last? If we want long-lasting products that retain their value, we have to support products that do so.

Today, we choose. If we choose the Retina display over the existing MacBook Pro, the next generation of Mac laptops will likely be less repairable still. When that happens, we won’t be able to blame Apple. We’ll have to blame ourselves.

J2EE Tutorial-17(Common Problems and Their Solutions)

Cannot Start the J2EE Server

Naming and Directory Service Port Conflict

Symptom: When you start the J2EE server with the -verbose option, it displays these lines:

J2EE server listen port: 1050 RuntimeException: Could not initialize server... 

Solution: Another process is using port 1050. If the J2EE server is already running, you can stop it by typing j2ee -stop. If some other program is using the port, then you can change the default port number (1050) by editing the config/orb.properties file of your J2EE SDK installation.

For more information about default port numbers, see the Configuration Guide in the download bundle of the J2EE SDK.

Web Service Port Conflict

Symptom: When you start the J2EE server with the -verbose option, it displays these lines:

LifecycleException: HttpConnector[8000].open:
java.net.BindException: Address in use...

Solution: Another process is using port 8000. You can change the default port number (8000) by editing the config/web.properties file of your J2EE SDK installation.

Incorrect XML Parser

Symptom: When you start the J2EE server with the -verbose option, it displays these lines:

Exception in thread "main"
javax.xml.parsers.FactoryConfigurationError:
org.apache.xerces.jaxp.SAXParserFactoryImpl at ... 

Solution: Remove the jre/lib/jaxp.properties file from your J2SE installation.

Compilation Errors

ant Cannot Locate the Build File

Symptom: When you type ant converter, these messages appear:

Buildfile: build.xml does not exist!
Build failed.

Solution: Before running ant, go to the j2eetutorial/examples/src directory. If you want to run ant from your current directory, you must specify the build file on the command line. For example, on Windows you would type this command on a single line:

ant -buildfile C:\j2eetutorial\examples\src\build.xml
   converter

The Compiler Cannot Resolve Symbols

Symptom: When you type ant converter, the compiler reports many errors, including these:

cannot resolve symbol
...
BUILD FAILED
...
Compile failed, messages should have been provided

Solution: Make sure that you've set the J2EE_HOME environment variable correctly. See Checking the Environment Variables.

ant 1.4 Will Not Compile the Example after You Run the Client

Symptom: ant 1.4 displays this error:

The filename, directory name, or volume label syntax is 
incorrect.

Solution: Use version 1.3 of ant. The 1.4 version of the ant.bat script and the scripts of the J2EE SDK all use the JAVACMD environment variable. The SDK's runclient.bat script, for example, sets JAVACMD to a value that causes problems for ant.bat.

Deployment Errors

The Incorrect XML Parser Is in Your Classpath

Symptom: The error displayed has the following text:

...
[]java.rmi.RemoteException:Error saving/opening

Deployment Error:Bad mapping of key{0}  class{1}, 
not found: com.sum.enterprise.deployment.xml.ApplicationNode

Solution: Remove the jaxp.jar file from the jre/lib/ext directory of your J2SE installation. This JAR file contains XML parsing routines that are incompatible with the J2EE server. If you do not have a jaxp.jarfile, then perhaps your classpath refers to the XML routines of a Tomcat installation. In this case, you should remove that reference from your classpath.

The Remote Home Interface Was Specified as a Local Home Interface

Symptom: An error such as the following is displayed:

LocalHomeImpl must be declared abstract. 
It does not define javax.ejb.HomeHandle getHomeHandle() 
from interface javax.ejb.EJBHome.

Solution: Remove the enterprise bean from the EAR file (EditDelete) and create a new bean with the New Enterprise Bean wizard. In the General dialog box of the wizard, select values from the Remote Home Interface and Remote Interface combo boxes.

J2EE Application Client Runtime Errors

The Client Throws a NoClassDefFoundError

Symptom: The client reports this exception:

java.lang.NoClassDefFoundError:converter.ConverterHome

Solution: This error occurs if the client cannot find the classes in the ConverterAppClient.jar file. Make sure that you've correctly followed the steps outlined in Running the J2EE Application Client.

The Client Cannot Find ConverterApp.ear

Symptom: The client reports this exception:

IOException: ConverterApp.ear does not exist

Solution: Ensure that the ConverterApp.ear file exists and that you've specified it with the -client option:

runclient -client ConverterApp.ear -name ConverterClient

You created the ConverterApp.ear file in the section Creating the J2EE Application. See also the section Running the J2EE Application Client.

The Client Cannot Find the ConverterClient Component

Symptom: The client displays this line:

No application client descriptors defined for: ...

Solution: Verify that you've created the ConverterClient component and that you've specified it for the -name option of the runclient command. You created the ConverterClient component in the sectionPackaging the J2EE Application Client.

The Login Failed

Symptom: After you log in, the client displays this line:

Incorrect login and/or password

Solution: At the login prompts, enter guest as the user name and guest123 as the password.

The J2EE Application Has Not Been Deployed

Symptom: The client reports the following exception:

NameNotFoundException. Root exception is org.omg.CosNaming...

Solution: Deploy the application. For instructions, see Deploying the J2EE Application.

The JNDI Name Is Incorrect

Symptom: The client reports the following exception:

NameNotFoundException. Root exception is org.omg.CosNaming...

Solution: In the JNDI Names tabbed pane of the ConverterApp, make sure that the JNDI names for the ConverterBean and the ejb/SimpleConverter match. Edit the appropriate JNDI Name field and then redeploy the application.

Web Client Runtime Errors

The Web Context in the URL Is Incorrect

Symptom: The browser reports that the page cannot be found (HTTP 404).

Solution: Verify that the Web context (converter) in the URL matches the one you specified in the Component General Properties dialog box (see the section Packaging the Web Client). The case (upper or lower) of the Web context is significant.

The J2EE Application Has Not Been Deployed

Symptom: The browser reports that the page cannot be found (HTTP 404).

Solution: Deploy the application.

The JNDI Name Is Incorrect

Symptom: When you click Submit on the Web page, the browser reports

A Servlet Exception Has Occurred.

Solution: In the JNDI Names tabbed pane of the ConverterApp, make sure that the JNDI names for the ConverterBean and the ConverterWAR match. Edit the appropriate JNDI Name field and then redeploy the application.

Detecting Problems With the Verifier Tool

The verifier tool (verifier) can detect inconsistencies in deployment descriptors and method signatures. These inconsistencies often cause deployment or runtime errors. From deploytool, you can run the GUI version of verifier by selecting ToolsVerifier. You can also run a stand-alone GUI or command-line version of verifier. For more information, see Appendix B.

Comparing Your EAR Files with Ours

For most of the examples, the download bundle of the tutorial includes J2EE application EAR files, which are located in the j2eetutorial/examples/ears directory.

When All Else Fails

If none of these suggestions fixes the problem, you can uninstall the application and clean out the server's repository by running the cleanup script. You'll also need to shut down and restart the server:

j2ee -stop
cleanup
j2ee -verbose

J2EE Tutorial-16(Modifying the J2EE Application)

Since the J2EE SDK is intended for experimentation, it supports iterative development. Whenever you make a change to a J2EE application, you must redeploy the application.

Modifying a Class File

To modify a class file in an enterprise bean, you change the source code, recompile it, and redeploy the application. For example, if you want to change the exchange rate in the dollarToYen business method of theConverterBean class, you would follow these steps.

1. Edit ConverterBean.java.


2. Recompile ConverterBean.java by typing ant converter.


3. In deploytool, select ToolsUpdate Files.


4. The Update Files dialog box appears. If the modified files are listed at the top of the dialog, click OK and go to step 6. If the files are listed at the bottom, they have not been found. Select one of those files and click Edit Search Paths.


5. In the Edit Search Paths dialog, specify the directories where the Update Files dialog will search for modified files.
   
   
   
   1. In the Search Root field, enter the fully-qualified name of the directory from which the search will start.
   
   
   2. In the Path Directory list, add a row for each directory that you want searched. Unless fully-qualified, these directory names are relative to the Search Root field.
   
   
   3. Click OK.
   
   
   
   


6. Select ToolsDeploy. Make sure the checkbox labeled Save Object Before Deploying is checked. If you do not want to deploy at this time, select ToolsSave to save the search paths specified in step 5.

As a shortcut, you can select ToolsUpdate And Redeploy. With this shortcut, the Update Files dialog box does not appear unless the files are not found.

To modify the contents of a WAR file you follow the preceding steps. The Update Files operation checks to see if any files have changed, including HTML files and JSP pages. If you change the index.jsp file ofConverterApp, be sure to type ant converter. The converter task copies the index.jsp file from the src to the build directory.

Adding a File

To add a file to the EJB JAR or WAR of the application, perform these steps.

1. In deploytool, select the JAR or WAR in the tree.


2. Select the General tab.


3. Click Edit.


4. In the tree of the Available Files field, locate the file and click Add.


5. Click OK.


6. From the main toolbar, select ToolsUpdate And Redeploy.

Modifying a Deployment Setting

To modify a deployment setting of ConverterApp, you edit the appropriate field in a tabbed pane and redeploy the application. For example, to change the JNDI name of the ConverterBean from ATypo toMyConverter, you would follow these steps.

1. In deploytool, select ConverterApp in the tree.


2. Select the JNDI Names tab.


3. In the JNDI Name field, enter MyConverter.


4. From the main toolbar, select FileSave.


5. Select ToolsUpdate And Redeploy.