cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jiang, Ning \(Willem\)" <Ning.Ji...@iona.com>
Subject RE: META-INF versus inside packages
Date Fri, 26 Oct 2007 14:12:03 GMT

I'd like to put it in the package, just like the message file.
They are both being eventually accessed.

Willem.

-----Original Message-----
From: Benson Margulies [mailto:bim2007@basistech.com]
Sent: Fri 10/26/2007 22:05
To: cxf-dev@incubator.apache.org
Subject: RE: META-INF versus inside packages
 
How would you classify a JavaScript file that we will eventually return
as part of a ? URL? If 'META-INF' is for things we tell users how to
find, then the JavaScript doesn't go there. 

> -----Original Message-----
> From: Jiang, Ning (Willem) [mailto:Ning.Jiang@iona.com]
> Sent: Friday, October 26, 2007 10:00 AM
> To: cxf-dev@incubator.apache.org
> Subject: RE: META-INF versus inside packages
> 
> 
> ASFIK, we put the schemas and the spring configuration files for the
> modules into the META-INF directory.
> And put others in the package.
> 
> Willem.
> 
> 
> -----Original Message-----
> From: Benson Margulies [mailto:bim2007@basistech.com]
> Sent: Fri 10/26/2007 21:50
> To: cxf-dev@incubator.apache.org
> Subject: META-INF versus inside packages
> 
> Is there some principle that guides when to put resources into
META-INF
> versus inside a package?
> 


Mime
  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message