[jboss-svn-commits] JBL Code SVN: r20128 - labs/jbossesb/trunk/product/docs.

jboss-svn-commits at lists.jboss.org jboss-svn-commits at lists.jboss.org
Fri May 23 09:23:07 EDT 2008


Author: mark.little at jboss.com
Date: 2008-05-23 09:23:07 -0400 (Fri, 23 May 2008)
New Revision: 20128

Removed:
   labs/jbossesb/trunk/product/docs/FAQ.txt
Log:
http://jira.jboss.com/jira/browse/JBESB-1752

Deleted: labs/jbossesb/trunk/product/docs/FAQ.txt
===================================================================
--- labs/jbossesb/trunk/product/docs/FAQ.txt	2008-05-23 13:22:50 UTC (rev 20127)
+++ labs/jbossesb/trunk/product/docs/FAQ.txt	2008-05-23 13:23:07 UTC (rev 20128)
@@ -1,24 +0,0 @@
-Frequently Asked Questions (FAQs)
-
-Question 1:  I was used to using the old configuration model.  How do I transition to using the new XSD based model?
-
-Answer: See Transitioning From The Old Configuration Model.
-
-Question 2:  Can I put whatever markup I like, wherever I like, in the new XSD based configuration?
-
-Answer:  No!  The new XSD based configuration only supports free-form markup on <property> elements/types and even there, the XSD to  ConfigTree mapping that's currently in place, only supports mapping from <property> elements contained within an <action> i.e. the free form <property> child content is not mapped from <bus> or <listener> elements.
-See Transitioning From The Old Configuration Model.
-
-Question 3:  Why does the XSD based configuration specify <listeners> and <actions>, as well as an optional “service-class” attribute on the <service> type?
-
-Answer:  Sorry, but the answer to this question is quite convoluted.  The reason the “service-class” attribute is on the <service> element is down to 2 factors:
-1.A known issue in the ESB (http://jira.jboss.com/jira/browse/JBESB-280).
-2.The need to be able to override the default listener class for a Gateway or Message Aware Listener.
-
-In hindsight however, adding this attribute here may not have been the best workaround.  Hopefully the “service-class” attribute is only a short term feature of the XSD configuration.
-
-Question 4:  Why does the XSD based configuration specify “target-service-name” and “target-service-category” attributes on the <service> type?
-
-Answer:  As a workaround to a known issue in the ESB (http://jira.jboss.com/jira/browse/JBESB-280).
-
-




More information about the jboss-svn-commits mailing list