Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Message-ID: <2042624369.1125063506646.JavaMail.jira@ajax.apache.org>
Date: Fri, 26 Aug 2005 15:38:26 +0200 (CEST)
From: "Deepal Jayasinghe (JIRA)" <jira@apache.org>
To: axis-dev@ws.apache.org
Subject: [jira] Resolved: (AXIS2-175) Moving deployment descriptor parsing
 form stax to OM
In-Reply-To: <537523652.1124941871415.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/AXIS2-175?page=all ]
     
Deepal Jayasinghe resolved AXIS2-175:
-------------------------------------

    Resolution: Fixed

> Moving deployment descriptor parsing form stax to OM
> ----------------------------------------------------
>
>          Key: AXIS2-175
>          URL: http://issues.apache.org/jira/browse/AXIS2-175
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Improvement
>   Components: deployment
>     Reporter: Deepal Jayasinghe
>     Assignee: Deepal Jayasinghe

>
> In current implementation all the descriptor parsing in deployment section are done directly using Stax , I think this make difficulty in adding more and more configuration options into those descriptors , so my idea is to use StaxOMBuilder to read descriptors and using that populate all the deployment time descriptions like ServiceDescriptions , OperationsDescrptions etc...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira