cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Mazza (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CXF-763) samples improvement
Date Thu, 05 Jul 2007 14:37:04 GMT

    [ https://issues.apache.org/jira/browse/CXF-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510374
] 

Glen Mazza commented on CXF-763:
--------------------------------

BTW, we now have a "samples" component in JIRA this can go to.

1.)  I think another "nice to have" is that close families of samples can reuse the same code.
 I.e., if the only difference between any two samples is a changed configuration file, I would
like us to consolidate the two samples and just mention the difference in the (single) README
file.  As a learner, I would rather have 10 rich samples than wade through 20 samples which
are nearly identical to others--I don't want to have to study the same class twice.

The Sun RI keeps every sample, even if just 2% different, standalone, which causes a lot of
duplicate classes and code, and from that you have the maintenance headaches as well as the
risks of code falling out of sync between samples.

2.)  For "ant server-tomcat", we already have that, its called "ant deploy" and "ant deploy-tomcat".
 There is currently a pesky requirement that the user has to enter "-Dtomcat='true'" property
in order to run either of these two tasks, that I would like us to remove.  (Probably remove
"ant deploy" would eliminate the need for that tomcat property, because if you're running
"deploy-tomcat" it's fairly obvious you want it sent to that container.)


> samples improvement
> -------------------
>
>                 Key: CXF-763
>                 URL: https://issues.apache.org/jira/browse/CXF-763
>             Project: CXF
>          Issue Type: Improvement
>          Components: Build system
>    Affects Versions: 2.0
>            Reporter: Bozhong Lin
>            Priority: Minor
>             Fix For: 2.1
>
>
> CXF samples can use some improvement along with following ideas:
> 1. rename/reorganize samples to be align with documentation, and from use case perspective.
Initial thinking of organizing/rename samples as following:
>  - wsdlfirst
>  - javafirst-annotations
>  - javafirst-pojo
>  - javafirst-spring-support
>  - other samples related to jax-ws features
>  - ws-*samples
>  - jbi-integration samples
>  - jca-integration samples
>  - jms samples
>  - secure-https sample
>  - in-jvm transport sample
>  - etc ...
> 2. each sample shall have ant target for running sample in standalone or servlet mode,
make things easier for users. for example:
>  - ant server-stanalone (or something similar)
>  - ant server-tomcat (or something similar)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message