2 Replies Latest reply on Feb 6, 2017 5:33 AM by ctomc

    Is standalone-preview.xml obsolet and is docs.jboss.org vague here?

    kaspatoo
    kaspatoo Feb 6, 2017 5:03 AM

      Hi,

       

      I am getting started with JBOSS, thats why I am reading this article:

      Getting Started Guide - JBoss AS 7.0 - Project Documentation Editor

       

      About the standalone configuration there is said:

      Standalone Server Configurations
      • standalone.xml (default)
        • Java Enterprise Edition 6 certified web profile configuration which includes the technologies required by the Web Profile specification plus Java Connector 1.6 Architecture, Java XML API for RESTFul Web Services, and OSGi
      • standalone-preview.xml
        • referred to as our Java Enterprise Edition 6 full profile preview, this configuration contains all the technologies in the default configuration with additional technology previews of Java API for XML-Based Web Services (JAX-WS) 2.2 and Java Message Service 1.1.
      • standalone-ha.xml
        • default profile with Clustering capabilities
      • standalone-preview-ha.xml
        • EE 6 full profile preview with Clustering capabilities

       

      I tried searching for further information about this standalone-preview.xml and was wondering why my installation og JBOSS EAP 7.0.0 do not have such an standalone-preview.xml but a standalone-full.xml.

      Output of version.txt is: "Red Hat JBoss Enterprise Application Platform - Version 7.0.0.GA"

      My searches also most times are about standalone-full.xml but never about standalone-preview.xml.

       

      This leads to my first question:

      Is standalone-preview.xml obsolet and replaced by standalone-full.xml?

       

      I found this second article about EAP 7.1:

      Getting Started Guide - JBoss AS 7.1 - Project Documentation Editor

       

      There its said:

      Standalone Server Configurations
      • standalone.xml (default)
        • Java Enterprise Edition 6 full profile certified configuration which includes the technologies required by the Full Profile specification plus others including OSGi
      • standalone-ha.xml
        • Java Enterprise Edition 6 certified full profile configuration with high availability
      • standalone-osgi-only.xml
        • OSGi only standalone server. No JEE6  capabilities
      • standalone-xts.xml
        • Standalone JEE6 full certified profile with support for transactional web services.

       

       

      Here no standalone-full.xml appears at all.

      This leads to my second question:

      Are my sources here for getting started a little bit vague or maybe wrong?

       

       

      Thanks for further information.