Bug 980766 - Use standalone-full.xml instead of standalone.xml
Summary: Use standalone-full.xml instead of standalone.xml
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise WFK Platform 2
Classification: Retired
Component: doc-Snowdrop-Sportsclub-Example
Version: 2.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Sneha
QA Contact: Tomas Repel
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-03 08:14 UTC by Tomas Repel
Modified: 2014-11-09 23:02 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-07-16 11:33:34 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Tomas Repel 2013-07-03 08:14:30 UTC 
Document URL: 

http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.3/html-single/Snowdrop_Sportsclub_Example/index.html

Section Number and Name: 

1.3. Preparing your JBoss Enterprise Platform

Describe the issue: 

It is easier to use standalone-full.xml when running EAP because it already contains the messaging configuration. The guidance how to create JMS destination assumes that the default messaging configuration is already in place (which is true for standalone-full.xml and not for standalone.xml) and describes just modifications.

Suggestions for improvement: 

Just replace `$JBOSS_HOME/standalone/configuration/standalone.xml` by
`$JBOSS_HOME/standalone/configuration/standalone-full.xml`
Note You need to log in before you can comment on or make changes to this bug.