The front-end controls the xml mapping parameters and names of the functions in your interface.
The data binding controls the mapping of beans. There is, of course, some overlap. Aegis includes some XML controls that are specific to parameters, and I don't recommend using them if you use Aegis with JAX-WS. In other words, I don't recommend, indeed, the use of an Aegis XML file to control service interface methods and their parameters. Use JAX-WS annotations or customizations. On Mon, Apr 25, 2011 at 7:07 AM, Raj Floyd <[email protected]> wrote: > Hi Benson, > > What do we mean by JAX-WS parameters? You mean I should not try to use > external mapping file with JAX-WS based service with Aegis? > > Thx > > Raj > > > > On Mon, Apr 25, 2011 at 3:54 PM, Benson Margulies > <[email protected]>wrote: > >> No, it means that you shouldn't try to configure JAX-WS parameters >> with Aegis XML files. Aegis works fine with JAX-WS, but you should use >> JAX-WS @nnotations on the parameters. >> >> On Mon, Apr 25, 2011 at 12:32 AM, Raj Floyd <[email protected]> wrote: >> > Hi, >> > >> > The Aegis documentation states: Aegis service configuration is best used >> > with the Simple front end. >> > >> > Does it mean that it not advisable to use JAXWS with Aegis? Now as part >> of >> > my Aegis learning, I developed JAXWS based client and server and set the >> > databinding to Aegis and controlled the mapping through external mapping >> > file. It gave me the desired results. It effectively means JAXWS does >> > recognize external mapping. >> > >> > Why then simple front end? >> > >> > Thx >> > >> > Raj >> > >> >
