You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Bozhong Lin <bl...@iona.com> on 2006/10/17 12:08:36 UTC
outstanding distribution cleanup works [was: Re: M1 TODOs (again)]
Hi All,
I have almost finished distribution cleanup related to license/NOTICE
stuff, so it looks good now with ARAT tool. Following are some
outstanding distribution cleanup TODOs:
1. remove Rhino XMLBeans from distribution and include a note in readme
for JavaScript frontend feature
2. remove ActiveMQ from distribution and include a note for JMS
transport feature. (If there is no objection for removing it from
distribution)
3. Unpackaging CXF to an installation directory name with a version#
4. change distribution package format to be ZIP/Tgz instead of JAR. (If
there is no objection)
5. As part of cleanup, I am going to remove Maven installation from
trunk. I don't think it makes sense to include Maven installation in CXF
repository and removing it will reduce source code download for
developers also. If you are pointing your MVN_HOME directory
trunk/maven, they you need to move Maven installation to other directory
and point MVN_HOME to new installation directory.
6. As part of cleanup, I will restructure "trunk/systemtests" and
"trunk/test" modules. "trunk/systemtests" will contain following new
contents:
1) trunk/systemtests/features: including all system test cases under
current "trunk/systemtests" module. ONLY this part of system test cases
will be included in part of development build lifecycle.
2) trunk/systemtests/performance: including all performance test cases
3) trunk/systemtests/interop: inclduing all interop test cases, such as
Axis interop, .NET interop, and WSA interop.
7. The obsolete "trunk/src" directory will be remove. "mvn site" does
not requirement any information under that directory any more.
Please let me know if you have suggestions on above items, otherwise, I
will start working on it a couple days later.
Cheers,
Bo
Dan Diephouse wrote:
> Hiya,
>
> Some of us from CXF met up today and talked about things we need to do
> yet before we can do M1. Here are some of the things we came up with:
>
> - Rhino can't be included in distribution
> - Fault handling on client side
> - Licensing
> - NOTICE files
> - schemas should have appropriate license (w3c?)
> - performance test licenses (Bo)
> - Documentation
> - Interop testing with Axis and .NET
> - Content-Type
> - Faults need 500 status code
> - Basic authentication
> - Support ?wsdl
> - Session Management?
> - SAAJ Handlers?
> - Drop StreamHandler demos
> - WS-Addressing interop?
>
> Anyone else have additional issues for inclusion?
>
> - Dan
>
Re: outstanding distribution cleanup works [was: Re: M1 TODOs (again)]
Posted by Jiang Ning <ni...@iona.com>.
Hi Dan,
When CeltiXfire moved to apache, I had not updated the my shell script
to use new trunk's maven,
The old trunk maven version is also 2.0.4, but the ' mvn install '
could not work, some wacky stack trace printed.
When I changed to use the new trunk's mvn , the error went away.
Are there some relationships with the maven's plugin and maven's core?
Thanks,
Willem.
Daniel Kulp wrote:
>Willem
>
>
>
>>>5. As part of cleanup, I am going to remove Maven installation from
>>>trunk. I don't think it makes sense to include Maven installation in
>>>CXF repository and removing it will reduce source code download for
>>>developers also. If you are pointing your MVN_HOME directory
>>>trunk/maven, they you need to move Maven installation to other
>>>directory and point MVN_HOME to new installation directory.
>>>
>>>
>>The user need to make sure the maven version up to 2.0.4, or there
>>could be some strange problem of runing 'mvn install' :)
>>
>>
>
>It's not exactly a "strange" error. We have:
> <prerequisites>
> <maven>2.0.4</maven>
> </prerequisites>
>in the pom.xml. Thus, when maven runs, it will specifically say: you
>need 2.0.4 or newer. It won't fail with some unusual error or wacky
>stack trace or something.
>
>Enjoy!
>
>
--
Willem Jiang
Software Engineer
IONA Asia Pacific Software Development Center
2/F, Unit A, Information Center
Zhongguancun Software Park Haidian District,
Beijing, P.R.China (100094)
Tel: +86-10-82825151 - 523
Fax: +86-10-82825210
Email: ning.jiang@iona.com
Re: outstanding distribution cleanup works [was: Re: M1 TODOs (again)]
Posted by Daniel Kulp <da...@iona.com>.
Willem
> > 5. As part of cleanup, I am going to remove Maven installation from
> > trunk. I don't think it makes sense to include Maven installation in
> > CXF repository and removing it will reduce source code download for
> > developers also. If you are pointing your MVN_HOME directory
> > trunk/maven, they you need to move Maven installation to other
> > directory and point MVN_HOME to new installation directory.
>
> The user need to make sure the maven version up to 2.0.4, or there
> could be some strange problem of runing 'mvn install' :)
It's not exactly a "strange" error. We have:
<prerequisites>
<maven>2.0.4</maven>
</prerequisites>
in the pom.xml. Thus, when maven runs, it will specifically say: you
need 2.0.4 or newer. It won't fail with some unusual error or wacky
stack trace or something.
Enjoy!
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194 F:781-902-8001
daniel.kulp@iona.com
Re: outstanding distribution cleanup works [was: Re: M1 TODOs (again)]
Posted by Jiang Ning <ni...@iona.com>.
Hi Bo,
Comments are in the mail.
Bozhong Lin wrote:
> Hi All,
>
> I have almost finished distribution cleanup related to license/NOTICE
> stuff, so it looks good now with ARAT tool. Following are some
> outstanding distribution cleanup TODOs:
> 1. remove Rhino XMLBeans from distribution and include a note in
> readme for JavaScript frontend feature
> 2. remove ActiveMQ from distribution and include a note for JMS
> transport feature. (If there is no objection for removing it from
> distribution)
Current JMS samples need to start up JMS broker as the basic condition
to run them. So Current distribution of CXF add ActiveMQ's configuration
and ActiveMQ core jar in the lib so the JMS samples can work without
any ActiveMQ installation. And there is a ant task for start up the JMS
broker.
If we remove all the ActiveMQ stuff from distribution, user need to
definitely install the ActiveMQ, and make the JMS broker start to listen
at it default port. These had to be written in the samples README.
> 3. Unpackaging CXF to an installation directory name with a version#
> 4. change distribution package format to be ZIP/Tgz instead of JAR.
> (If there is no objection)
> 5. As part of cleanup, I am going to remove Maven installation from
> trunk. I don't think it makes sense to include Maven installation in
> CXF repository and removing it will reduce source code download for
> developers also. If you are pointing your MVN_HOME directory
> trunk/maven, they you need to move Maven installation to other
> directory and point MVN_HOME to new installation directory.
The user need to make sure the maven version up to 2.0.4, or there could
be some strange problem of runing 'mvn install' :)
> 6. As part of cleanup, I will restructure "trunk/systemtests" and
> "trunk/test" modules. "trunk/systemtests" will contain following new
> contents:
> 1) trunk/systemtests/features: including all system test cases under
> current "trunk/systemtests" module. ONLY this part of system test
> cases will be included in part of development build lifecycle.
> 2) trunk/systemtests/performance: including all performance test cases
> 3) trunk/systemtests/interop: inclduing all interop test cases, such
> as Axis interop, .NET interop, and WSA interop.
> 7. The obsolete "trunk/src" directory will be remove. "mvn site" does
> not requirement any information under that directory any more.
>
> Please let me know if you have suggestions on above items, otherwise,
> I will start working on it a couple days later.
>
> Cheers,
> Bo
>
> Dan Diephouse wrote:
>
>> Hiya,
>>
>> Some of us from CXF met up today and talked about things we need to
>> do yet before we can do M1. Here are some of the things we came up with:
>>
>> - Rhino can't be included in distribution
>> - Fault handling on client side
>> - Licensing
>> - NOTICE files
>> - schemas should have appropriate license (w3c?)
>> - performance test licenses (Bo)
>> - Documentation
>> - Interop testing with Axis and .NET
>> - Content-Type
>> - Faults need 500 status code
>> - Basic authentication
>> - Support ?wsdl
>> - Session Management?
>> - SAAJ Handlers?
>> - Drop StreamHandler demos
>> - WS-Addressing interop?
>>
>> Anyone else have additional issues for inclusion?
>>
>> - Dan
>>
>
Willem.
Re: outstanding distribution cleanup works [was: Re: M1 TODOs (again)]
Posted by James Mao <ja...@iona.com>.
I have created several tasks.
Cheers,
James.
Bozhong Lin 写道:
> I don't think we filed any JIRA task yet. Anyone is working on this?
> This probably needs to be addressed for M1 release.
>
> Cheers,
> Bo
>
> James Mao wrote:
>>
>>>>>> - Content-Type
>>>>>> - Faults need 500 status code
>>> in SOAP 1.1 and XML we need add 500 status code , seems in SOAP1.2
>>> the status code should remain 200.
>>> SOAP 1.1 should use text/xml Content-Type, in SOAP 1.2 we should use
>>> application/soap+xml
>>>
>>> Do we have jira task for this?
>>>
>> SOAP 1.2 should also return 500 to indicate when an error occurs
>> processing the request, actually it provide a find grained mapping
>> between soap erros and http status code than soap1.1
>>
>> Cheers,
>> James.
>>
>
Re: outstanding distribution cleanup works [was: Re: M1 TODOs (again)]
Posted by Bozhong Lin <bl...@iona.com>.
I don't think we filed any JIRA task yet. Anyone is working on this?
This probably needs to be addressed for M1 release.
Cheers,
Bo
James Mao wrote:
>
>>>>> - Content-Type
>>>>> - Faults need 500 status code
>> in SOAP 1.1 and XML we need add 500 status code , seems in SOAP1.2 the
>> status code should remain 200.
>> SOAP 1.1 should use text/xml Content-Type, in SOAP 1.2 we should use
>> application/soap+xml
>>
>> Do we have jira task for this?
>>
> SOAP 1.2 should also return 500 to indicate when an error occurs
> processing the request, actually it provide a find grained mapping
> between soap erros and http status code than soap1.1
>
> Cheers,
> James.
>
Re: outstanding distribution cleanup works [was: Re: M1 TODOs (again)]
Posted by James Mao <ja...@iona.com>.
>>>> - Content-Type
>>>> - Faults need 500 status code
> in SOAP 1.1 and XML we need add 500 status code , seems in SOAP1.2 the
> status code should remain 200.
> SOAP 1.1 should use text/xml Content-Type, in SOAP 1.2 we should use
> application/soap+xml
>
> Do we have jira task for this?
>
SOAP 1.2 should also return 500 to indicate when an error occurs
processing the request, actually it provide a find grained mapping
between soap erros and http status code than soap1.1
Cheers,
James.
Re: outstanding distribution cleanup works [was: Re: M1 TODOs (again)]
Posted by James Mao <ja...@iona.com>.
>>>
>>> - Content-Type
>>> - Faults need 500 status code
in SOAP 1.1 and XML we need add 500 status code , seems in SOAP1.2 the
status code should remain 200.
SOAP 1.1 should use text/xml Content-Type, in SOAP 1.2 we should use
application/soap+xml
Do we have jira task for this?
Cheers,
James.
Re: outstanding distribution cleanup works [was: Re: M1 TODOs (again)]
Posted by Dan Diephouse <da...@envoisolutions.com>.
This sounds good to me. I do like the shorter directory name of
trunk/systests instead of rtrunk/systests/features, but am willing to
live with anything.
- Dan
Bozhong Lin wrote:
> Hi All,
>
> I have almost finished distribution cleanup related to license/NOTICE
> stuff, so it looks good now with ARAT tool. Following are some
> outstanding distribution cleanup TODOs:
> 1. remove Rhino XMLBeans from distribution and include a note in
> readme for JavaScript frontend feature
> 2. remove ActiveMQ from distribution and include a note for JMS
> transport feature. (If there is no objection for removing it from
> distribution)
> 3. Unpackaging CXF to an installation directory name with a version#
> 4. change distribution package format to be ZIP/Tgz instead of JAR.
> (If there is no objection)
> 5. As part of cleanup, I am going to remove Maven installation from
> trunk. I don't think it makes sense to include Maven installation in
> CXF repository and removing it will reduce source code download for
> developers also. If you are pointing your MVN_HOME directory
> trunk/maven, they you need to move Maven installation to other
> directory and point MVN_HOME to new installation directory.
> 6. As part of cleanup, I will restructure "trunk/systemtests" and
> "trunk/test" modules. "trunk/systemtests" will contain following new
> contents:
> 1) trunk/systemtests/features: including all system test cases under
> current "trunk/systemtests" module. ONLY this part of system test
> cases will be included in part of development build lifecycle.
> 2) trunk/systemtests/performance: including all performance test cases
> 3) trunk/systemtests/interop: inclduing all interop test cases, such
> as Axis interop, .NET interop, and WSA interop.
> 7. The obsolete "trunk/src" directory will be remove. "mvn site" does
> not requirement any information under that directory any more.
>
> Please let me know if you have suggestions on above items, otherwise,
> I will start working on it a couple days later.
>
> Cheers,
> Bo
>
> Dan Diephouse wrote:
>> Hiya,
>>
>> Some of us from CXF met up today and talked about things we need to
>> do yet before we can do M1. Here are some of the things we came up with:
>>
>> - Rhino can't be included in distribution
>> - Fault handling on client side
>> - Licensing
>> - NOTICE files
>> - schemas should have appropriate license (w3c?)
>> - performance test licenses (Bo)
>> - Documentation
>> - Interop testing with Axis and .NET
>> - Content-Type
>> - Faults need 500 status code
>> - Basic authentication
>> - Support ?wsdl
>> - Session Management?
>> - SAAJ Handlers?
>> - Drop StreamHandler demos
>> - WS-Addressing interop?
>>
>> Anyone else have additional issues for inclusion?
>>
>> - Dan
>>
--
Dan Diephouse
Envoi Solutions
http://envoisolutions.com
http://netzooid.com/blog