Hi, well actually none are in the release ... the two last ones are in the source package, but they belong to the test resources and are not contained in the actual jars that make up blazeds.
I don't think it's a good idea to have default config files in there. Web applications are all different and you have to configure blazeds according to your usage. I would agree if we provided a tournkey-war-distribution this would contain the 4 files, but shipping default configs for blazeds would be sort of like shipping sample pom files for maven ... doesn't really make sense from my part. Chris -----Ursprüngliche Nachricht----- Von: Alex Harui [mailto:aha...@adobe.com] Gesendet: Freitag, 27. März 2015 17:02 An: dev@flex.apache.org Betreff: Re: Apache BlazeDS default configuration files [License] The four files you mentioned: - messaging-config.xml - proxy-config.xml - remoting-config.xml - services-config.xml Were donated by Adobe, so there are now Apache 2.0 licensed versions of them in the repos. I didn’t notice until just now that the first two are not in the official Apache release. I don’t know BlazeDS that well, so maybe the release manager can explain why that is. -Alex On 3/27/15, 8:27 AM, "Victor Turansky" <victor.turan...@gmail.com> wrote: >Default configuration files was not donated by Adobe? > >I want to use Apache BlazeDS. Could I create custom configuration for >Apache BlazeDS without license restrictions? > >Thanks. > > > >-- >View this message in context: >http://apache-flex-development.2333347.n4.nabble.com/Apache-BlazeDS-def >aul t-configuration-files-License-tp45832p45834.html >Sent from the Apache Flex Development mailing list archive at Nabble.com.
