[ 
https://issues.apache.org/jira/browse/AXIS2C-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Lazarski resolved AXIS2C-1479.
-------------------------------------
    Resolution: Won't Fix

Closing as "Won't Fix" with the following rationale:                            
              
                                                                                
              
  1. Limited benefit with only 2 parsers: With only Guththila and libxml2 as 
options (and a   
  3rd unlikely), dynamic loading provides minimal value. A compile-time choice 
between 2      
  options is straightforward and well-documented.                               
              
  2. Issue age and inactivity: Nearly 16 years old with no assignee or 
implementation attempts
   suggests no real demand.                                                     
              
  3. Abstraction already exists: The ops-based interface pattern means 
application code is    
  already parser-agnostic. The only compile-time dependency is the parser 
wrapper selection.  
  4. Complexity vs. benefit: Dynamic loading would require:                     
              
    - Plugin discovery and loading infrastructure                               
              
    - Configuration file parsing (needs a parser to load a parser - bootstrap 
problem)        
    - Platform-specific dlopen/LoadLibrary code                                 
              
    - Error handling for missing/incompatible plugins                           
              
  5. Similar to AXIS2C-1481: This is the same reporter requesting the same 
pattern (runtime vs
   compile-time) for XML parsers as they did for SSL. The rationale for 
rejecting that applies
   here too.                                                                    
              
  6. Current approach works well: Users who need libxml2 simply rebuild with 
--enable-libxml2.
   This is a one-time configuration decision, not something that changes 
frequently.          
                 

> Should dynamically resolve to XML parser
> ----------------------------------------
>
>                 Key: AXIS2C-1479
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1479
>             Project: Axis2-C
>          Issue Type: Improvement
>          Components: xml/parser
>            Reporter: Nadir K. Amra
>            Priority: Major
>
> Axis2/C has an interface it expects to invoke when dealing with the XML 
> parser.  But adding a parser requires rebuild Axis2/C with the new parser. 
> We need to be able to specify the XML parser in axis2.xml file and Axis2/C 
> should dynamically load the parser.  This way, new parsers can be added 
> without having to recompile or rebuilt Axis2/C.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to