You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Daniel Kulp <dk...@apache.org> on 2009/06/03 21:37:12 UTC
GSoC projects for CXF
Now that the "implementation/code" phase for the GSoC stuff has begun, it
would definitely be good to start getting some additional communications
flowing to see how progress is coming, resolve any roadblocks, answer
questions, etc....
Thus, here are some ideas I thought of...
1) File some JIRA tasks on our JIRA:
https://issues.apache.org/jira/browse/CXF
It would be good to get a "base" jira created for your project and then start
adding sub tasks to it. As things are implemented, the sub-projects can be
resolved so we can see progress and such. Also provides a good "checklist"
of what remains and such. (also, patches can be attached to the jiras so we
can apply them)
2) I'd also like to start seeing regular "status" updates to the dev list just
to keep tabs. Remember, part of your final evaluation with Google involves
how involved you got with the community. Thus, speaking up on the dev list
is a very good thing.
3) One "interesting" thought: I'd encourage you to get a github.com account
and "fork" the CXF project (http://github.com/apache/cxf) and start pushing
changes as you work in there. Thus, we can really see what you are doing,
how it all works together, etc.... Additionally, if the "patch" starts
getting complex, git does a MUCH better job of dealing with complex patches
than subversion.
Anyway, at this point, it's kind of important to get some information flowing.
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
Re: GSoC projects for CXF
Posted by Daniel Kulp <dk...@apache.org>.
Ah. Documentation. That's a good thing. However, to grant access to
edit the wiki, we need to have ICLA's on file. Thus, we should add to the
list:
4) Each of the GSoC students should sign and submit the "Individual
Contributor Agreement" from http://apache.org/licenses/#clas
so that we can grant access to the wiki's.
You can sign/scan/email if you don't have access to a fax.
Dan
On Sun June 7 2009 10:09:14 am Willem Jiang wrote:
> Hi Dan,
>
> LiuCong created a wiki page[1] of his project working status on apache
> wiki , he doesn't have the write right of cwiki.apache.org/CXF, neither
> to me (njiang) :(.
You definitely should. You are in all the correct groups. The main CXF
space (not the CXF20DOCS space) has a different theme setup. The "Page
Operations" (and thus the Edit button) is under the nav panel on the left.
> Could you grand the karma for us? So we can move the
> page into CXF.
>
> I just talked to LiuCong today on IRC , he will creates some JIRAs
> according his development plan shortly.
>
> [1] http://wiki.apache.org/general/soapjms4cxf
> Cheers,
>
> Willem
>
> Daniel Kulp wrote:
> > Now that the "implementation/code" phase for the GSoC stuff has begun, it
> > would definitely be good to start getting some additional communications
> > flowing to see how progress is coming, resolve any roadblocks, answer
> > questions, etc....
> >
> > Thus, here are some ideas I thought of...
> > 1) File some JIRA tasks on our JIRA:
> > https://issues.apache.org/jira/browse/CXF
> > It would be good to get a "base" jira created for your project and then
> > start adding sub tasks to it. As things are implemented, the
> > sub-projects can be resolved so we can see progress and such. Also
> > provides a good "checklist" of what remains and such. (also, patches can
> > be attached to the jiras so we can apply them)
> >
> > 2) I'd also like to start seeing regular "status" updates to the dev list
> > just to keep tabs. Remember, part of your final evaluation with Google
> > involves how involved you got with the community. Thus, speaking up on
> > the dev list is a very good thing.
> >
> > 3) One "interesting" thought: I'd encourage you to get a github.com
> > account and "fork" the CXF project (http://github.com/apache/cxf) and
> > start pushing changes as you work in there. Thus, we can really see
> > what you are doing, how it all works together, etc.... Additionally, if
> > the "patch" starts getting complex, git does a MUCH better job of dealing
> > with complex patches than subversion.
> >
> > Anyway, at this point, it's kind of important to get some information
> > flowing.
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
Re: GSoC projects for CXF
Posted by liucong <li...@gmail.com>.
Hi,
My cwiki.apache.org/CXF's User Name: liucong07@gmail.com, Full
Name: jason.
I have create a project for my project in gitHub.
(http://github.com/liucong/jms4cxf2/tree/master).
If it is needed, I'll do it following 3) One "interesting" thought:
Best regards,
Liu
Willem Jiang Writes:
> Hi Dan,
>
> LiuCong created a wiki page[1] of his project working status on apache
> wiki , he doesn't have the write right of cwiki.apache.org/CXF, neither
> to me (njiang) :(. Could you grand the karma for us? So we can move the
> page into CXF.
>
> I just talked to LiuCong today on IRC , he will creates some JIRAs
> according his development plan shortly.
>
> [1] http://wiki.apache.org/general/soapjms4cxf
> Cheers,
>
> Willem
>
> Daniel Kulp wrote:
>
>> Now that the "implementation/code" phase for the GSoC stuff has begun, it
>> would definitely be good to start getting some additional communications
>> flowing to see how progress is coming, resolve any roadblocks, answer
>> questions, etc....
>>
>> Thus, here are some ideas I thought of...
>> 1) File some JIRA tasks on our JIRA:
>> https://issues.apache.org/jira/browse/CXF
>> It would be good to get a "base" jira created for your project and then start
>> adding sub tasks to it. As things are implemented, the sub-projects can be
>> resolved so we can see progress and such. Also provides a good "checklist"
>> of what remains and such. (also, patches can be attached to the jiras so we
>> can apply them)
>>
>> 2) I'd also like to start seeing regular "status" updates to the dev list just
>> to keep tabs. Remember, part of your final evaluation with Google involves
>> how involved you got with the community. Thus, speaking up on the dev list
>> is a very good thing.
>>
>> 3) One "interesting" thought: I'd encourage you to get a github.com account
>> and "fork" the CXF project (http://github.com/apache/cxf) and start pushing
>> changes as you work in there. Thus, we can really see what you are doing,
>> how it all works together, etc.... Additionally, if the "patch" starts
>> getting complex, git does a MUCH better job of dealing with complex patches
>> than subversion.
>>
>> Anyway, at this point, it's kind of important to get some information flowing.
>>
>>
>
>
>
Re: GSoC projects for CXF
Posted by Willem Jiang <wi...@gmail.com>.
Hi Dan,
LiuCong created a wiki page[1] of his project working status on apache
wiki , he doesn't have the write right of cwiki.apache.org/CXF, neither
to me (njiang) :(. Could you grand the karma for us? So we can move the
page into CXF.
I just talked to LiuCong today on IRC , he will creates some JIRAs
according his development plan shortly.
[1] http://wiki.apache.org/general/soapjms4cxf
Cheers,
Willem
Daniel Kulp wrote:
> Now that the "implementation/code" phase for the GSoC stuff has begun, it
> would definitely be good to start getting some additional communications
> flowing to see how progress is coming, resolve any roadblocks, answer
> questions, etc....
>
> Thus, here are some ideas I thought of...
> 1) File some JIRA tasks on our JIRA:
> https://issues.apache.org/jira/browse/CXF
> It would be good to get a "base" jira created for your project and then start
> adding sub tasks to it. As things are implemented, the sub-projects can be
> resolved so we can see progress and such. Also provides a good "checklist"
> of what remains and such. (also, patches can be attached to the jiras so we
> can apply them)
>
> 2) I'd also like to start seeing regular "status" updates to the dev list just
> to keep tabs. Remember, part of your final evaluation with Google involves
> how involved you got with the community. Thus, speaking up on the dev list
> is a very good thing.
>
> 3) One "interesting" thought: I'd encourage you to get a github.com account
> and "fork" the CXF project (http://github.com/apache/cxf) and start pushing
> changes as you work in there. Thus, we can really see what you are doing,
> how it all works together, etc.... Additionally, if the "patch" starts
> getting complex, git does a MUCH better job of dealing with complex patches
> than subversion.
>
> Anyway, at this point, it's kind of important to get some information flowing.
>
Re: GSoC projects for CXF
Posted by Daniel Kulp <dk...@apache.org>.
On Wed June 17 2009 7:20:09 pm Krzysztof Wilkos wrote:
> I've got some busy days at university (exams etc.) but I'm close to
> get session initialization working. I should finish this before the
> end of this week. To initiate a session I have to call service method
> so there is short way from session initialization to complete conduit
> for soap over tcp protocol.
Thanks for the update. Definitely don't let work on this affect your
studying for exams. Keeping grades up is higher priority.
> BTW To send a message I have to know its length which I have to send
> in frame header. I'm planning to make buffer and ByteArrayOutputStream
> which I put into Message object and than in close method I'll send
> buffer content into real stream. With this solution I will not have to
> change existing cxf code which assumes that after prepare method call
> there is outputstream in Message object. For small messages this
> should be ok but with bigger one ByteArrayOutputStream can reallocate
> buffer few times. Can I do that this way?
Doesn't the SOAP/TCP protocol allow the message to be split across several
frames? Basically, send a "chunk" of the message at a time? If so, your
output stream would just need a fixed size buffer of some sort (like 4K or
something). When the buffer fills, write out a frame and reset the buffer
back to 0. That way, it would avoid having the whole message in a block.
The other option is to use our CachedOutputStream. It uses a
ByteArrayOutputStream for a while (64K by default), but then will change to
using a temporary file for storage to avoid having huge blocks in memory.
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
Re: GSoC projects for CXF
Posted by Krzysztof Wilkos <ka...@gmail.com>.
2009/6/16 Daniel Kulp <dk...@apache.org>:
>
> Just a reminder that July 13th (the date when Mid-term evaluations are due) is
> now less than a month away. We definitely should start seeing some visible
> progress sometime soon. More importantly, for mid-terms, we should be seeing
> more interaction with the communities.
>
> Anyway, I just wanted to remind everyone about that milestone in the GSoC
> timeline.
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>
I've got some busy days at university (exams etc.) but I'm close to
get session initialization working. I should finish this before the
end of this week. To initiate a session I have to call service method
so there is short way from session initialization to complete conduit
for soap over tcp protocol.
BTW To send a message I have to know its length which I have to send
in frame header. I'm planning to make buffer and ByteArrayOutputStream
which I put into Message object and than in close method I'll send
buffer content into real stream. With this solution I will not have to
change existing cxf code which assumes that after prepare method call
there is outputstream in Message object. For small messages this
should be ok but with bigger one ByteArrayOutputStream can reallocate
buffer few times. Can I do that this way?
--
Krzysztof Wilkos