Hi Glen,

I'm sorry I forgot to replay the mail on the weekend. 

I totally agree with you that we could add a sentence to help people to search 
the simple front end  on the document if they want.

Now my question is will we rename the module name of the simple frontend in the 
code ?
If not, we still need to add a mapping between the code and docs. 
If so, we need to tell the people to change the poms if they are doing the 
upgrade.

It looks like we are introducing a troubles before we clean up the mass. The 
meaning of "simple" I think that is you don't need to configure any thing and 
it just runs, it is the KISS principle that we alway apply during our open 
source development process. But it could be dumb as CXF cannot know every thing 
he need to build up a right service module in the run time. That is why we need 
the JAXWS frontend. 

So I still opposite the proposal of rename the "Simple Frontend".

It could be more easier for users to realize that if they chose the simple 
frontend they may face lots of issues in the production world,  if we can list 
the issues in the wiki page instead of by guessing them from its name.

Any thought?

-- 
Willem Jiang

FuseSource
Web: http://www.fusesource.com (http://www.fusesource.com/)
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) 
(English)
          http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang 
Weibo: willemjiang





On Friday, September 7, 2012 at 12:35 AM, Glen Mazza wrote:

> Hi Willem, was my response sufficient for you to lift your veto or would you
> still like to prevent the proposed change?
> 
> Thanks,
> Glen
> 
> 
> 
> 
> --
> View this message in context: 
> http://cxf.547215.n5.nabble.com/PROPOSAL-Rename-Simple-Frontend-No-Annotation-Frontend-tp5713384p5713669.html
> Sent from the cxf-dev mailing list archive at Nabble.com (http://Nabble.com).



Reply via email to