avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vinay Chandran <vinay...@yahoo.com>
Subject Re: LifecycleHelper & Verifier
Date Sun, 19 May 2002 18:01:55 GMT
Paul,
> How are you using SAX? Via the factory built into
> the JDK ?  or via the 
> Cornerstone block?
>
No ,I as such am not using SAX,
Its the  phoenix call within 
o.a.a.p.tools.configuration.ConfigurationBuilder.
createXMLReader()  which is failing .

Regards,
Vinay

> - Paul
> 
> 
> >Hi,
> >( Excuse my ignorance here  if
> >this is the expected behaviour)
> >
> >I try to deploy two sars within the /apps 
> >folder (2 apps from avalon-apps )
> >and phoenix-runtime cribs about 
> >"Provider
> org.apache.xerces.jaxp.SAXParserFactoryImpl
> >not found", 
> >when it tries loading the SAxParserFactory for 
> >building the configuration of the  second SAR'ed 
> >application.
> >(I think this behaviour would occur when 2 or more
> >sar's are deployed in the /apps folder.
> >)
> >
> >The Culprit I feel is the  setting of the 
> >contextClassLoader to 'null' in the following place
> :
> >DefaultApplication.loadBlockListeners().
> >
> >So Is there a problem somewhere ?, 
> >or as my ignorance speaks, 
> >Have I intrepreted something wrong here ?
> >
> >Regards,
> >V i n a y
> >
> >--- Peter Donald <peter@apache.org> wrote:
> > On Sun, 19 May 2002 16:19, Robert wrote:
> >  
> >
> >>>A couple of simple questions:
> >>>
> >>>In ResourceAccessor, you mention that the
> argument
> >>>      
> >>>
> >>would be some meta
> >>    
> >>
> >>>data, so would this equate to say, a
> Configuration
> >>>      
> >>>
> >>object,
> >>
> >>Both are possible. It basically depends on what
> the
> >>container implementers 
> >>prefer. I tend to prefer a typesafe metadata
> object
> >>but other people prefer 
> >>free-form Configuration trees. 
> >>
> >>    
> >>
> >>>or are/is
> >>>there going to be a MetaData structure that
> >>>      
> >>>
> >>abstracts out these things?
> >>
> >>I hope that we can achieve a standard set of
> >>metadata between containers. I am 
> >>am hopeful that we can achieve this. I am not sure
> >>whether there will be a 
> >>standard MetaData structure, xml descriptor or
> >>whatever in future (there 
> >>maybe or there may not). It basically comes down
> to
> >>how successful we are at 
> >>abstracting things away ;)
> >>
> >>So I guess the answer is hopefully but it will
> only
> >>occur if we can do it 
> >>properly.
> >>
> >>    
> >>
> >>>I really like the idea of the LifecycleHelper.
> >>>      
> >>>
> >>Would this potentially
> >>    
> >>
> >>>move up from Phoenix?
> >>>      
> >>>
> >>Eventually. Just needs to mature and we need to
> make
> >>sure it works for all the 
> >>containers we currently have.
> >>
> >>-- 
> >>Cheers,
> >>
> >>Peter Donald
> >>
> >>
> >>--
> >>To unsubscribe, e-mail:  
> >><mailto:avalon-dev-unsubscribe@jakarta.apache.org>
> >>For additional commands, e-mail:
> >><mailto:avalon-dev-help@jakarta.apache.org>
> >>
> >>    
> >>
> >
> >
> >__________________________________________________
> >Do You Yahoo!?
> >LAUNCH - Your Yahoo! Music Experience
> >http://launch.yahoo.com
> >
> >--
> >To unsubscribe, e-mail:  
> <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
> >For additional commands, e-mail:
> <mailto:avalon-dev-help@jakarta.apache.org>
> >
> >
> >
> >  
> >
> 
> 
> 
> 
> --
> To unsubscribe, e-mail:  
> <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
> <mailto:avalon-dev-help@jakarta.apache.org>
> 


__________________________________________________
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
http://launch.yahoo.com

--
To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@jakarta.apache.org>


Mime
View raw message