Apache XMLBeans 2.0 beta


News: Apache XMLBeans 2.0 beta

  1. Apache XMLBeans 2.0 beta (4 messages)

    The Apache XMLBeans project is pleased to announce new releases of XMLBeans. The 2.0.0-beta1 release is a significant improvement from previous release and has been in development for about 10 months. The 1.0.4 release is a maintenance release focused on stability and bug fixes. The 1.0.4-jdk1.3 release is the first release of XMLBeans compatible with JDK 1.3.

    Major goals of the 2.0.0-beta1 release:
      - source backwards compatible
      - improve usability of wildcards, substitution groups, error handling
      - a native DOM level 2 API
      - integration with Saxon xpath/xquery engine
      - performance improvements
      - instance to schema and schema to instance tools

    For a comprehensive list of improvements, see the CHANGES.txt file in the distribution.

    Goals for the next 2.0.0 release include fixing any remaining performance issues and bugs. Please take 2.0.0-beta1 for a spin and help us make the 2.0.0 GA rock solid.

    The source and binaries are available on mirror near you at:

    XMLBeans Home: http://xmlbeans.apache.org

    Threaded Messages (4)

  2. Apache XMLBeans 2.0 beta[ Go to top ]

    I used XMLBeans for our project: http://junitscenario.sf.net !
    and I must say it's Great !

    Stéphane TRAUMAT
    JOnAS Live author
  3. too many framewoks[ Go to top ]

    I know that choice is freedom (and appreciate this a lot), but why have 2 differents XML binding framework in the same community (XMLBeans and JaxMe) ?

    I know that they have different functionalities (and histories) but isn't possible to merge the two projects and join the forces to have the better product ? (there will still left a lot of alternatives). I'm one of the guys who think that there are two many differents open source projects in the same area and choices are difficults for me ;-)

    I recently have to make a choice for a XML binding framework and I think I spent more time to read the documentations of each ones than to develop with the framework of my choice.

    Don't see offense, I'm a big fan of open-source and use almost only open-source products.

  4. too many framewoks[ Go to top ]

    Come on, open up. I'm sure you can find specific features in both frameworks that distinguishes them from one another, and will make you choose one or the other depending on your personal preferences and current requirements. Everything looks the same from 30,000 feet, but the devil is in the details. It is when projects impose their own specific requirements that you are glad to be able to choose what fits best.

    We could apply your reasoning to everything in life; what would we end up with in the end?
  5. too many framewoks[ Go to top ]