> So are you saying that Saxon9.2 would support this feature?  

I think it should be possible to make this work under Saxon 9.2, but it's
not something I have done and it would require some investigation or
experiment.

Regards,

Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay 


> 
> Kind regards,
> Robby
> 
> -----Original Message-----
> From: Michael Kay [mailto:mike@xxxxxxxxxxxx]
> Sent: Wednesday, March 10, 2010 12:04 PM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: RE:  xslt extensions accessing spring 
> application context
> 
> 
> Questions about Java extensibility are processor-specific 
> questions that are
> probably best asked on a processor-specific list.
> 
> One of the motivations behind the new "integrated extension function"
> mechanism in Saxon 9.2 was to give you better control on how 
> your extensions
> integrate into your particular application environment: but I 
> haven't worked
> out a Spring example as a specific use case.
> 
> Regards,
> 
> Michael Kay
> http://www.saxonica.com/
> http://twitter.com/michaelhkay  
> 
> > -----Original Message-----
> > From: Robby Pelssers [mailto:robby.pelssers@xxxxxxxxx] 
> > Sent: 10 March 2010 10:11
> > To: XSLT mailing list
> > Subject:  xslt extensions accessing spring application context
> > 
> > 
> > Hi all,
> > 
> > I know we can access java classes using extensions... but 
> > nowadays many developers use spring to configure beans where 
> > properties are configured in the applicationContext.
> > 
> > So instead of using the 'new' construct for instantiating a 
> > java object I would like to get access to a spring bean.  Are 
> > there solutions to accomplish this?
> > 
> > Kind regards,
> > Robby Pelssers