Hi Khaled,
what is very surprising is the fact that no one have the right answer at
least for the first use case
I think that we already have some material around this. Indeed, I have
ServiceMix deployed in production that use EJB via CXF-SE.
I'm very sorry, I haven't had any time for now to upgrade the SMX4 EJB
documentation. I try to do it as soon as possible.
We have discussed this morning (in the dev mailing list) with Guillaume
to add an EJB3 container embedded in SMX4. I think it's a killer
feature, so we need to going deeper in this way.
Back to the documentation part i think that the first things to do is
to restructure the documentation and to complete the missing parts
(especially the blank pages in SM website) as Gert said.
the PDF thing is just how to deliver this documentation which very useful
for off line usage and can be shipped with SM releases.BTW i think that
confluence can generate PDF files thanks to plugins:
http://confluence.atlassian.com/display/DOC/Confluence+to+PDF
Some folks talked about making an open source book for SM in the users
mailing list see :
http://cwiki.apache.org/SM/discussion-forums.html#nabble-td22374793|a22374793
i think that is a great idea too.
I'm agree. I have proposed to create a documentation project, build in
the continuous integration process. This documentation project will
publish DocBook in several output formats (such as PDF/HTML). I have a
positive feedback from Lars, I'm waiting for feedback from other team
members.
Regards
JB
Regards
Khaled
________________________________________________________
My blog = http://thepurplecows.blogspot.com/
On Wed, Apr 1, 2009 at 8:44 AM, Gert Vanthienen
<gert.vanthie...@gmail.com>wrote:
Khaled,
I'm not sure projects about documentation would really get a lot of
attention, but you're absolutely right about the problems with our
documentation. Actually, I think the problem is twofold:
- some areas are probably really underdocumented and you can hardly
find anything about it on the website
- most things do have some kind of documentation, but the organisation
of the documentation is really bad
Especially for ServiceMix 4, the documentation seems to be all
scattered around: you'll find bits in the ServiceMix Kernel wiki, the
NMR wiki and for the components and the Maven tools you'll have to go
into the main ServiceMix (3) wiki/website.
With all that being said, we're particularly open to any kind of
suggestion on how to improve things (or even a helping hand ;) ).
Could you give us an overview of the information you were looking for
so we can figure out a way to get that together to start with or
something?
Regards,
Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
2009/3/31 Khaled Essghaier <thoughts.loudspea...@gmail.com>:
Hi,
looks very interesting, i am a student actually and working actually in a
SOA project in which we are planning to use an ESB but i think that you
should consider projects related with the documentation and samples
because
i got a hard time those couple of weeks trying to get something working
with
SM4 which lead me to consider using open-ESB.
Regards,
*Khaled*
________________________________________________________
My blog = http://thepurplecows.blogspot.com/
