RE: [Springframework-developer] Import tag for XML bean definitions

[<jue...@we...>]

I'm not sure whether such a "transform-with" attribute would just apply =
to the import tag: This should be available for all XML bean definition =
files, not just for imported ones. The question is, how to specify the =
XSL file for a "contextConfigLocation" in web.xml, for example, or for a =
FileSystemXmlApplicationContext?

Juergen


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...]On Behalf
Of Andy Depue
Sent: Thursday, September 16, 2004 5:21 PM
To: spr...@li...
Subject: Re: [Springframework-developer] Import tag for XML bean
definitions


I like having this option.  One thought this triggered in my head is the =

possibility of having application oriented XML config files.  In other =
words,=20
config files that are oriented around your app so that they become =
easier to=20
work with for the masses.  ActiveMQ and Mule are two systems that allow =
you=20
to either configure via Spring or configure via a native XML that is=20
typically easier to work with.  ActiveMQ actually uses XSL internally to =

translate from the ActiveMQ oriented XML config to a Spring config.  So, =

having said all this, would it make sense to add an xsl (or =
transform-with)=20
attribute to the import tag?  I could then do something like this:
  <beans>
    <import resource=3D"app-config.xml" =
transform-with=3D"app-to-spring.xsl"/>
    ...
  </beans>

  Thoughts?

    - Andy

On Thursday 16 September 2004 01:22 am, j=FCrgen h=F6ller [werk3AT] =
wrote:
> Hi everybody,
>
> During an extra evening I had to spend at an airport hotel in Rome, =
I've
> implemented an "import" tag for XML bean definitions:
>
> http://opensource.atlassian.com/projects/spring/browse/SPR-137
>
> Basically, you can put any number of "import" tags at the beginning of =
bean
> definition files:
>
> <beans>
>
>   <import resource=3D"myImport1.xml"/>
>   <import resource=3D"myImport2.xml"/>
>
>   <bean ... />
>
> </beans>
>
> The resource locations are interpreted as relative to the file that
> contains the import tags. Effectively, this is delegated to the
> "createRelative" method on the Resource interface, invoked on the =
Resource
> object for the containing file. ("createRelative" has already been
> introduced in 1.1 final.)
>
> I'll commit this tonight, provided that there aren't any objections. =
While
> I'm not gonna recommend this feature too much, as I personally prefer =
a
> "contextConfigLocation" that refers to multiple files, I still believe =
that
> an import tag is a useful addition. In particular, some people are =
used to
> such a feature from Ant and XWork...
>
> Juergen
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
> Project Admins to receive an Apple iPod Mini FREE for your judgement =
on
> who ports your project to Linux PPC the best. Sponsored by IBM.
> Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer