Cada vez esta mas facil esto de crear tu empresa oye,

• Ves al menú Tools >> Preferences
• Selecciona Accelerators en el Arbol de la izquierda
• Reimporta los settings pulsando el botón “Load Presets”

Espero que esto os ahorre algo de frustracion.

Mas recursos:

Aplicaciones existentes escritas en Java

http://developers.facebook.com/get_started.php

facebook-java-api

Os presento fbFund y los siguientes son los requisitos:

Selection Criteria

We consider our Guiding Principles and the following criteria:

1. Originality of Concept

   Do you introduce a great idea in a new and unexplored area?

2. Market

   Is your experience targeted to key cohorts or meet compelling market needs?

3. Social/Useful

   Does your experience enable people to interact with each other? Does it deliver real value to users (incl. entertainment)?

4. Expressive

   Does the experience allow people to share more information?

5. Intuitive

   Is your experience compelling and easy to use? Does it have a well thought out user experience?

6. Potential

   What are the monetization and growth opportunities?

7. Team

Do you believe this team can execute and is driven to succeed?

Espero que os guste:

An XA transaction, in the most general terms, is a “global transaction” that may span multiple resources. A non-XA transaction always involves just one resource.

An XA transaction involves a coordinating transaction manager, with one or more databases (or other resources, like JMS) all involved in a single global transaction. Non-XA transactions have no transaction coordinator, and a single resource is doing all its transaction work itself (this is sometimes called local transactions).

XA transactions come from the X/Open group specification on distributed, global transactions. JTA includes the X/Open XA spec, in modified form.

Most stuff in the world is non-XA – a Servlet or EJB or plain old JDBC in a Java application talking to a single database. XA gets involved when you want to work with multiple resources – 2 or more databases, a database and a JMS connection, all of those plus maybe a JCA resource – all in a single transaction. In this scenario, you’ll have an app server like Websphere or Weblogic or JBoss acting as the Transaction Manager, and your various resources (Oracle, Sybase, IBM MQ JMS, SAP, whatever) acting as transaction resources. Your code can then update/delete/publish/whatever across the many resources. When you say “commit”, the results are commited across all of the resources. When you say “rollback”, _everything_ is rolled back across all resources.

The Transaction Manager coordinates all of this through a protocol called Two Phase Commit (2PC). This protocol also has to be supported by the individual resources.

In terms of datasources, an XA datasource is a data source that can participate in an XA global transaction. A non-XA datasource generally can’t participate in a global transaction (sort of – some people implement what’s called a “last participant” optimization that can let you do this for exactly one non-XA item).

For more details – see the JTA pages on java.sun.com. Look at the XAResource and Xid interfaces in JTA. See the X/Open XA Distributed Transaction specification. Do a google source on “Java JTA XA transaction”.

Pero… que es Jobsket?

Bueno, dejare que descubrais vosotros mismos los detalles pero os adelanto que si teneis un CV en el disco duro, conexion a internet y 5 minutos, descubrireis cuanto vale el CV en el mercado laboral.

Disfrutad!

Gracias Velijko!!

http://olex.openlogic.com/wazi/2009/how-to-fix-memory-leaks-in-java