You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cxf.apache.org by dk...@apache.org on 2006/08/25 15:17:37 UTC
svn commit: r436785 [10/18] - in /incubator/cxf/trunk: ./ api/
api/src/main/java/org/apache/cxf/buslifecycle/
api/src/main/java/org/apache/cxf/databinding/
api/src/main/java/org/apache/cxf/endpoint/
api/src/main/java/org/apache/cxf/interceptor/ api/src...
Modified: incubator/cxf/trunk/docs/src/faqs/general-faq.xml
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/docs/src/faqs/general-faq.xml?rev=436785&r1=436784&r2=436785&view=diff
==============================================================================
--- incubator/cxf/trunk/docs/src/faqs/general-faq.xml (original)
+++ incubator/cxf/trunk/docs/src/faqs/general-faq.xml Fri Aug 25 06:16:36 2006
@@ -1,124 +1,124 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
- Copyright 2002-2004 The Apache Software Foundation or its licensors,
- as applicable.
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
--->
-<!DOCTYPE faqs PUBLIC "-//APACHE//DTD FAQ V2.0//EN" "http://forrest.apache.org/dtd/faq-v20.dtd">
-
-<faqs>
- <title>General FAQ</title>
-
- <faqsection id="basic">
- <title>Basics</title>
- <faq>
- <question>
- What is CeltiXfire?
- </question>
- <answer>
- Cetlix is an open source Java Web services ESB implementation. It is based on JAX-WS 2.0.
- </answer>
- </faq>
- <faq>
- <question>
- What is an ESB?
- </question>
- <answer>
- ESB stands for Enterprise Service Bus. An ESB is the layer of technology that makes SOA possible.
- It enables the abstraction by translating the messages defining the services into data that can
- be manipulated by a physical process implementing a service. Essentially, an ESB is the yarn
- that weaves a SOA together.
- </answer>
- </faq>
- <faq>
- <question>
- What is SOA?
- </question>
- <answer>
- SOA stands for Service-Oriented Architecture. Service-Oriented Architecture is an approach
- to software architecture with the goal to decouple the agents of work in a software system
- from the functionality advertised by those agents. An agent offers a contract, representing
- a service, which can then be consumed by other software agents that require work to be done.
- In SOA terms, the contract-offering agent is the Service Provider, and the contract itself
- represents the Service. Using SOA, system designers can describe the core functions of the
- system as service elements that can be composed and reused to form business applications.
- </answer>
- </faq>
- </faqsection>
- <faqsection id="esbrelates">
- <title>Relationship to Other ESBs</title>
- <faq>
- <question>
- How does CeltiXfire compare to other open source ESBs like Mule and ServiceMix?
- </question>
- <answer>
- CeltiXfire is the only ESB that implements the JAX-WS specification. Also, CeltiXfire has the ability
- to send SOAP messages over HTTP built-in, and it does not require any external program for
- this functionality, like Apache Axis. Also, CeltiXfire is not based on a particular messaging
- technology. It supports JMS and comes with ActiveMQ, but it can work with any JMS implementation.
- CeltiXfire is extensible, so it is possible to write other messaging transports for CeltiXfire since
- the messaging bus is not tightly bound to how CeltiXfire works.
- </answer>
- </faq>
- <faq>
- <question>
- How does CeltiXfire compare to commercial ESBs?
- </question>
- <answer>
- Due to the rapid innovation capability of an open source community, CeltiXfire is comparable,
- and ahead in some ways, in capability to commercial Java-centric ESBs. For example, CeltiXfire is
- currently the only ESB with JAX-WS support. The non-Java-centric ESBs complement and interoperate
- with CeltiXfire to provide additional transports and bindings, i.e. IONA's Artix product provides
- additional capabilities to integrate with IBM MQ, CORBA, Tuxedo, etc.
- </answer>
- </faq>
- </faqsection>
- <faqsection id="osrelates">
- <title>Relationship to Other Open Source Projects</title>
- <faq>
- <question>
- Does CeltiXfire use other open source projects?
- </question>
- <answer>
- <p>Yes. CeltiXfire is built and packaged using Maven 2.0 from Apache. The Web site is built using Forrest
- from Apache. All of the documentation for the CeltiXfire project is written using OpenOffice 2.0.</p>
- <p>The CeltiXfire team is also working with the STP project at the Eclipse foundation to build a set of GUI tools for developing SOAs.</p>
- </answer>
- </faq>
- <faq>
- <question>
- What other open source projects does CeltiXfire work with?
- </question>
- <answer>
- Currently a number of open source projects are in discussions with the CeltiXfire project about taking shared dependencies.
- </answer>
- </faq>
- <faq>
- <question>
- Are members of the CeltiXfire community working with any open-source JBI projects?
- </question>
- <answer>
- Yes.
- </answer>
- </faq>
- <faq>
- <question>
- Are members of the CeltiXfire community working with any open-source SCA projects?
- </question>
- <answer>
- Yes.
- </answer>
- </faq>
- </faqsection>
-</faqs>
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Copyright 2002-2004 The Apache Software Foundation or its licensors,
+ as applicable.
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+<!DOCTYPE faqs PUBLIC "-//APACHE//DTD FAQ V2.0//EN" "http://forrest.apache.org/dtd/faq-v20.dtd">
+
+<faqs>
+ <title>General FAQ</title>
+
+ <faqsection id="basic">
+ <title>Basics</title>
+ <faq>
+ <question>
+ What is CeltiXfire?
+ </question>
+ <answer>
+ Cetlix is an open source Java Web services ESB implementation. It is based on JAX-WS 2.0.
+ </answer>
+ </faq>
+ <faq>
+ <question>
+ What is an ESB?
+ </question>
+ <answer>
+ ESB stands for Enterprise Service Bus. An ESB is the layer of technology that makes SOA possible.
+ It enables the abstraction by translating the messages defining the services into data that can
+ be manipulated by a physical process implementing a service. Essentially, an ESB is the yarn
+ that weaves a SOA together.
+ </answer>
+ </faq>
+ <faq>
+ <question>
+ What is SOA?
+ </question>
+ <answer>
+ SOA stands for Service-Oriented Architecture. Service-Oriented Architecture is an approach
+ to software architecture with the goal to decouple the agents of work in a software system
+ from the functionality advertised by those agents. An agent offers a contract, representing
+ a service, which can then be consumed by other software agents that require work to be done.
+ In SOA terms, the contract-offering agent is the Service Provider, and the contract itself
+ represents the Service. Using SOA, system designers can describe the core functions of the
+ system as service elements that can be composed and reused to form business applications.
+ </answer>
+ </faq>
+ </faqsection>
+ <faqsection id="esbrelates">
+ <title>Relationship to Other ESBs</title>
+ <faq>
+ <question>
+ How does CeltiXfire compare to other open source ESBs like Mule and ServiceMix?
+ </question>
+ <answer>
+ CeltiXfire is the only ESB that implements the JAX-WS specification. Also, CeltiXfire has the ability
+ to send SOAP messages over HTTP built-in, and it does not require any external program for
+ this functionality, like Apache Axis. Also, CeltiXfire is not based on a particular messaging
+ technology. It supports JMS and comes with ActiveMQ, but it can work with any JMS implementation.
+ CeltiXfire is extensible, so it is possible to write other messaging transports for CeltiXfire since
+ the messaging bus is not tightly bound to how CeltiXfire works.
+ </answer>
+ </faq>
+ <faq>
+ <question>
+ How does CeltiXfire compare to commercial ESBs?
+ </question>
+ <answer>
+ Due to the rapid innovation capability of an open source community, CeltiXfire is comparable,
+ and ahead in some ways, in capability to commercial Java-centric ESBs. For example, CeltiXfire is
+ currently the only ESB with JAX-WS support. The non-Java-centric ESBs complement and interoperate
+ with CeltiXfire to provide additional transports and bindings, i.e. IONA's Artix product provides
+ additional capabilities to integrate with IBM MQ, CORBA, Tuxedo, etc.
+ </answer>
+ </faq>
+ </faqsection>
+ <faqsection id="osrelates">
+ <title>Relationship to Other Open Source Projects</title>
+ <faq>
+ <question>
+ Does CeltiXfire use other open source projects?
+ </question>
+ <answer>
+ <p>Yes. CeltiXfire is built and packaged using Maven 2.0 from Apache. The Web site is built using Forrest
+ from Apache. All of the documentation for the CeltiXfire project is written using OpenOffice 2.0.</p>
+ <p>The CeltiXfire team is also working with the STP project at the Eclipse foundation to build a set of GUI tools for developing SOAs.</p>
+ </answer>
+ </faq>
+ <faq>
+ <question>
+ What other open source projects does CeltiXfire work with?
+ </question>
+ <answer>
+ Currently a number of open source projects are in discussions with the CeltiXfire project about taking shared dependencies.
+ </answer>
+ </faq>
+ <faq>
+ <question>
+ Are members of the CeltiXfire community working with any open-source JBI projects?
+ </question>
+ <answer>
+ Yes.
+ </answer>
+ </faq>
+ <faq>
+ <question>
+ Are members of the CeltiXfire community working with any open-source SCA projects?
+ </question>
+ <answer>
+ Yes.
+ </answer>
+ </faq>
+ </faqsection>
+</faqs>
Propchange: incubator/cxf/trunk/docs/src/faqs/general-faq.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: incubator/cxf/trunk/docs/src/faqs/general-faq.xml
------------------------------------------------------------------------------
svn:keywords = Rev Date
Propchange: incubator/cxf/trunk/docs/src/faqs/general-faq.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Modified: incubator/cxf/trunk/docs/src/faqs/license-faq.xml
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/docs/src/faqs/license-faq.xml?rev=436785&r1=436784&r2=436785&view=diff
==============================================================================
--- incubator/cxf/trunk/docs/src/faqs/license-faq.xml (original)
+++ incubator/cxf/trunk/docs/src/faqs/license-faq.xml Fri Aug 25 06:16:36 2006
@@ -1,86 +1,86 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
- Copyright 2002-2004 The Apache Software Foundation or its licensors,
- as applicable.
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
--->
-<!DOCTYPE faqs PUBLIC "-//APACHE//DTD FAQ V2.0//EN" "http://forrest.apache.org/dtd/faq-v20.dtd">
-
-<faqs>
- <title>License FAQ</title>
- <faq>
- <question>
- How many Celtix licensing options do I have to choose from?
- </question>
- <answer>
- Two. One option is primarily licensed under the LGPL; the other option is primarily licensed
- under the EPL. To ensure there is no confusion about which license a user is accepting,
- Celtix offers separate distributions: one primarily licensed under the LGPL and one primarily
- licensed under the EPL.
- </answer>
- </faq>
- <faq>
- <question>
- Why are there these two options? Why not just stick to one or the other?
- </question>
- <answer>
- The LGPL option allows compatibility with other free software projects, such as those
- licensed under the GPL and LGPL. The EPL option is more compatible with many other
- open source projects, specifically, with Apache and Eclipse projects. For example, the Eclipse
- SOA Tools Platform project will be including parts of Celtix in its distribution. Both the EPL
- and LGPL include a clause that requires that derivative works be distributed under the same
- license as the work from which it is derived.
- </answer>
- </faq>
- <faq>
- <question>
- What is meant above by "primarily licensed under"? What other licenses are relevant to the Celtix distributions?
- </question>
- <answer>
- All new code written for and contributed to the Celtix project is licensed under both the LGPL and
- the EPL. In addition, the same licenses apply to the collective work, known as a "Celtix distribution".
- However, Celtix uses and redistributes a few other open source components that are licensed
- differently. As of December 2005, the Celtix binary distribution includes third-party components
- licensed under the Apache License CDDL, and CPL (all approved by the Open Source Initiative).
- </answer>
- </faq>
- <faq>
- <question>
- How can I find out exactly what third-party components are included in Celtix and what licenses are applicable to them?
- </question>
- <answer>
- <p>There are several ways the Celtix team tries to make the licensing of Celtix and its components clear to users:</p>
- <ul>
- <li>Each Celtix distribution includes a file named <code>3party-licenses.txt</code> that identifies the name
- of each third-party component and its applicable license.</li>
- <li>The directory containing each third-party component will also include a copy of the applicable license.</li>
- </ul>
- <p>The Celtix committers do all this because we respect the intellectual property rights and licenses of others,
- and we want to make it easy for our users and redistributors to do the same.</p>
- </answer>
- </faq>
- <faq>
- <question>
- Could the Celtix source and binary distributions have different applicable licenses?
- </question>
- <answer>
- Yes. In addition to all the components included in the binary distribution, the source distribution includes
- some tools necessary for building and contributing to the project. These tools may be licensed differently
- than the other components that are also found in the binary distribution. The <code>3party-licenses.txt</code>
- file will list exactly what these components are and what the applicable license is for each one. However,
- aside from third-party components, the core Celtix code is still licensed under both the EPL or LGPL
- (your choice), for both source and binary form.
- </answer>
- </faq>
-</faqs>
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Copyright 2002-2004 The Apache Software Foundation or its licensors,
+ as applicable.
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+<!DOCTYPE faqs PUBLIC "-//APACHE//DTD FAQ V2.0//EN" "http://forrest.apache.org/dtd/faq-v20.dtd">
+
+<faqs>
+ <title>License FAQ</title>
+ <faq>
+ <question>
+ How many Celtix licensing options do I have to choose from?
+ </question>
+ <answer>
+ Two. One option is primarily licensed under the LGPL; the other option is primarily licensed
+ under the EPL. To ensure there is no confusion about which license a user is accepting,
+ Celtix offers separate distributions: one primarily licensed under the LGPL and one primarily
+ licensed under the EPL.
+ </answer>
+ </faq>
+ <faq>
+ <question>
+ Why are there these two options? Why not just stick to one or the other?
+ </question>
+ <answer>
+ The LGPL option allows compatibility with other free software projects, such as those
+ licensed under the GPL and LGPL. The EPL option is more compatible with many other
+ open source projects, specifically, with Apache and Eclipse projects. For example, the Eclipse
+ SOA Tools Platform project will be including parts of Celtix in its distribution. Both the EPL
+ and LGPL include a clause that requires that derivative works be distributed under the same
+ license as the work from which it is derived.
+ </answer>
+ </faq>
+ <faq>
+ <question>
+ What is meant above by "primarily licensed under"? What other licenses are relevant to the Celtix distributions?
+ </question>
+ <answer>
+ All new code written for and contributed to the Celtix project is licensed under both the LGPL and
+ the EPL. In addition, the same licenses apply to the collective work, known as a "Celtix distribution".
+ However, Celtix uses and redistributes a few other open source components that are licensed
+ differently. As of December 2005, the Celtix binary distribution includes third-party components
+ licensed under the Apache License CDDL, and CPL (all approved by the Open Source Initiative).
+ </answer>
+ </faq>
+ <faq>
+ <question>
+ How can I find out exactly what third-party components are included in Celtix and what licenses are applicable to them?
+ </question>
+ <answer>
+ <p>There are several ways the Celtix team tries to make the licensing of Celtix and its components clear to users:</p>
+ <ul>
+ <li>Each Celtix distribution includes a file named <code>3party-licenses.txt</code> that identifies the name
+ of each third-party component and its applicable license.</li>
+ <li>The directory containing each third-party component will also include a copy of the applicable license.</li>
+ </ul>
+ <p>The Celtix committers do all this because we respect the intellectual property rights and licenses of others,
+ and we want to make it easy for our users and redistributors to do the same.</p>
+ </answer>
+ </faq>
+ <faq>
+ <question>
+ Could the Celtix source and binary distributions have different applicable licenses?
+ </question>
+ <answer>
+ Yes. In addition to all the components included in the binary distribution, the source distribution includes
+ some tools necessary for building and contributing to the project. These tools may be licensed differently
+ than the other components that are also found in the binary distribution. The <code>3party-licenses.txt</code>
+ file will list exactly what these components are and what the applicable license is for each one. However,
+ aside from third-party components, the core Celtix code is still licensed under both the EPL or LGPL
+ (your choice), for both source and binary form.
+ </answer>
+ </faq>
+</faqs>
Propchange: incubator/cxf/trunk/docs/src/faqs/license-faq.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: incubator/cxf/trunk/docs/src/faqs/license-faq.xml
------------------------------------------------------------------------------
svn:keywords = Rev Date
Propchange: incubator/cxf/trunk/docs/src/faqs/license-faq.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Modified: incubator/cxf/trunk/docs/src/faqs/project-faq.xml
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/docs/src/faqs/project-faq.xml?rev=436785&r1=436784&r2=436785&view=diff
==============================================================================
--- incubator/cxf/trunk/docs/src/faqs/project-faq.xml (original)
+++ incubator/cxf/trunk/docs/src/faqs/project-faq.xml Fri Aug 25 06:16:36 2006
@@ -1,77 +1,77 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
- Copyright 2002-2004 The Apache Software Foundation or its licensors,
- as applicable.
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
--->
-<!DOCTYPE faqs PUBLIC "-//APACHE//DTD FAQ V2.0//EN" "http://forrest.apache.org/dtd/faq-v20.dtd">
-
-<faqs>
- <title>Project FAQ</title>
- <faq>
- <question>
- When did the Celtix project begin?
- </question>
- <answer>
- The Celtix project was formed in June 2005 and the first code was placed in the forge in
- July 2005. Since starting, the Celtix project has achieved five consecutive on-schedule
- milestone deliveries. In May of 2006, the Celtix project released its 1.0 build.
- </answer>
- </faq>
- <faq>
- <question>
- What is the road map for CeltiXfire?
- </question>
- <answer>
- As with all open source project road maps, the road map for CeltiXfire is dependent on the
- needs of the users and the willingness of contributors to work on those features. There
- is a list of proposed features on the mile stone page at
- https://wiki.objectweb.org/celtix/Wiki.jsp?page=Milestones. We welcome user feedback
- on the developer mailing list.
- </answer>
- </faq>
- <faq>
- <question>
- How do I contribute to the CeltiXfire project?
- </question>
- <answer>
- CeltiXfire is an open source project and accepts all contributions that are approved by the
- community. To find out more about contributing, visit the CeltiXfire project's getting started
- page at https://wiki.objectweb.org/celtix/Wiki.jsp?page=GettingStarted.
- </answer>
- </faq>
- <faq>
- <question>
- Are there any licensing restrictions that apply to using CeltiXfire?
- </question>
- <answer>
- CeltiXfire is licensed under both the LPGL and the EPL. The packages for distribution under each
- license is available from the download page. For more information, see the <a href="site:license">License FAQ</a>.
- </answer>
- </faq>
- <faq>
- <question>
- What is a milestone release?
- </question>
- <answer>
- <p>A milestone release is an interim release of CeltiXfire that occurs at regular intervals so that users can
- take advantage of new features without having to build CeltiXfire from the repository. Each milestone release
- contains new features and functionality (sometimes, partly implemented), but there is no guarantee that
- testing is complete. In general, milestone releases should be regarded as less stable and are not
- suitable for deployment.</p>
- <p>This contrasts with regular releases of CeltiXfire, where every effort is made to ensure that the release
- is stable and testing is complete.</p>
- </answer>
- </faq>
-</faqs>
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Copyright 2002-2004 The Apache Software Foundation or its licensors,
+ as applicable.
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+<!DOCTYPE faqs PUBLIC "-//APACHE//DTD FAQ V2.0//EN" "http://forrest.apache.org/dtd/faq-v20.dtd">
+
+<faqs>
+ <title>Project FAQ</title>
+ <faq>
+ <question>
+ When did the Celtix project begin?
+ </question>
+ <answer>
+ The Celtix project was formed in June 2005 and the first code was placed in the forge in
+ July 2005. Since starting, the Celtix project has achieved five consecutive on-schedule
+ milestone deliveries. In May of 2006, the Celtix project released its 1.0 build.
+ </answer>
+ </faq>
+ <faq>
+ <question>
+ What is the road map for CeltiXfire?
+ </question>
+ <answer>
+ As with all open source project road maps, the road map for CeltiXfire is dependent on the
+ needs of the users and the willingness of contributors to work on those features. There
+ is a list of proposed features on the mile stone page at
+ https://wiki.objectweb.org/celtix/Wiki.jsp?page=Milestones. We welcome user feedback
+ on the developer mailing list.
+ </answer>
+ </faq>
+ <faq>
+ <question>
+ How do I contribute to the CeltiXfire project?
+ </question>
+ <answer>
+ CeltiXfire is an open source project and accepts all contributions that are approved by the
+ community. To find out more about contributing, visit the CeltiXfire project's getting started
+ page at https://wiki.objectweb.org/celtix/Wiki.jsp?page=GettingStarted.
+ </answer>
+ </faq>
+ <faq>
+ <question>
+ Are there any licensing restrictions that apply to using CeltiXfire?
+ </question>
+ <answer>
+ CeltiXfire is licensed under both the LPGL and the EPL. The packages for distribution under each
+ license is available from the download page. For more information, see the <a href="site:license">License FAQ</a>.
+ </answer>
+ </faq>
+ <faq>
+ <question>
+ What is a milestone release?
+ </question>
+ <answer>
+ <p>A milestone release is an interim release of CeltiXfire that occurs at regular intervals so that users can
+ take advantage of new features without having to build CeltiXfire from the repository. Each milestone release
+ contains new features and functionality (sometimes, partly implemented), but there is no guarantee that
+ testing is complete. In general, milestone releases should be regarded as less stable and are not
+ suitable for deployment.</p>
+ <p>This contrasts with regular releases of CeltiXfire, where every effort is made to ensure that the release
+ is stable and testing is complete.</p>
+ </answer>
+ </faq>
+</faqs>
Propchange: incubator/cxf/trunk/docs/src/faqs/project-faq.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: incubator/cxf/trunk/docs/src/faqs/project-faq.xml
------------------------------------------------------------------------------
svn:keywords = Rev Date
Propchange: incubator/cxf/trunk/docs/src/faqs/project-faq.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Modified: incubator/cxf/trunk/docs/src/faqs/tech-faq.xml
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/docs/src/faqs/tech-faq.xml?rev=436785&r1=436784&r2=436785&view=diff
==============================================================================
--- incubator/cxf/trunk/docs/src/faqs/tech-faq.xml (original)
+++ incubator/cxf/trunk/docs/src/faqs/tech-faq.xml Fri Aug 25 06:16:36 2006
@@ -1,182 +1,182 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
- Copyright 2002-2004 The Apache Software Foundation or its licensors,
- as applicable.
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
--->
-<!DOCTYPE faqs PUBLIC "-//APACHE//DTD FAQ V2.0//EN" "http://forrest.apache.org/dtd/faq-v20.dtd">
-
-<faqs>
- <title>Technology FAQ</title>
-<faqsection>
-<title>Prerequisites</title>
- <faq>
- <question>
- What are the prerequisites for using CeltiXfire?
- </question>
- <answer>
- <p>For running CeltiXfire-enabled applications all you need to have is a Java 5 JVM.</p>
- <p>To develop services using CeltiXfire, you need Sun Microsystem's Java 5 JDK.</p>
- </answer>
- </faq>
- <faq>
- <question>
- Does the CeltiXfire runtime require a J2EE container?
- </question>
- <answer>
- No. CeltiXfire does not require either a J2EE container or a Web container.
- </answer>
- </faq>
-</faqsection>
-<faqsection>
-<title>Standards</title>
- <faq>
- <question>
- What Web service standards does CeltiXfire support?
- </question>
- <answer>
- <p>CeltiXfire implements the following Web service standards:</p>
- <ul>
- <li>JAX-WS 2.0</li>
- <li>WS-Addressing</li>
- <li>WS-ReliableMessaging(WS-RM)</li>
- <li>WSDL 1.1</li>
- <li>SOAP 1.1</li>
- </ul>
- </answer>
- </faq>
-</faqsection>
-<faqsection>
-<title>JAX-WS</title>
- <faq>
- <question>
- How does CeltiXfire allow you to service-enable your applications?
- </question>
- <answer>
- CeltiXfire implements the JAX-WS 2.0 specification. JAX-WS 2.0 provides a straightforward way
- to service-enable your applications using the Java 1.5 Annotation mechanism. It also
- provides a programming model that enables the creation of Web services-ready Java applications.
- </answer>
- </faq>
- <faq>
- <question>
- Has CeltiXfire extended JAX-WS in any way?
- </question>
- <answer>
- Yes. CeltiXfire has extended JAX-WS by adding the concept of system handlers. This allows
- developers to attach handlers at various points within the invocation chain, giving them more
- power to interact with the data as it flows in and out of CeltiXfire.
- </answer>
- </faq>
-</faqsection>
-<faqsection>
-<title>Messaging</title>
- <faq>
- <question>
- Does CeltiXfire provide messaging capabilities?
- </question>
- <answer>
- CeltiXfire supports a means to deliver messages to a JMS implementation.
- </answer>
- </faq>
-<faq>
- <question>
- Does CeltiXfire depend on any JMS implementation?
- </question>
- <answer>
- CeltiXfire is not based on a particular JMS implementation. It supports any JMS implementation and
- ships with the open source ActiveMQ JMS implementation.
- </answer>
-</faq>
-</faqsection>
-<faqsection>
-<title>J2EE</title>
- <faq>
- <question>
- Can CeltiXfire interoperate with a J2EE container?
- </question>
- <answer>
- While CeltiXfire does not require a J2EE application server, CeltiXfire artifacts can be deployed
- into a J2EE container.
- </answer>
- </faq>
-</faqsection>
-<faqsection>
-<title>JBI</title>
-<faq>
-<question>
-What is JBI?
-</question>
-<answer>
-<p>JBI stands for Java Bussines Integration. It is a standardized set of APIs, Service Provider
-Interfaces (SPIs) and technologies, maintained through the Java Community Process, for integration
-of business components.</p>
-<p>For more information see
-<a href="http://www.jcp.org/en/jsr/detail?id=208">http://www.jcp.org/en/jsr/detail?id=208</a></p>
-</answer>
-</faq>
-<faq>
-<question>
-How does CeltiXfire relate to JBI?
-</question>
-<answer>
-At a quick glance CeltiXfire and a JBI implementation may appear to be addressing the same set of
-problems. However, CeltiXfire is not a JBI implementation. Unlike JBI, CeltiXfire provides a much more
-extensible framework for building services. Its focus is to provide a rich framework for linking
-non-Java, non-Web Service artifacts as well as building feature rich Web services. CeltiXfire is
-intended to complement JBI. To this end, it is possible to deploy CeltiXfire runtime components and
-CeltiXfire developed services inside a compliant JBI container.
-</answer>
-</faq>
-</faqsection>
-<faqsection>
-<title>SCA</title>
-<faq>
-<question>
-What is SCA?
-</question>
-<answer>
-<p>SCA stands for Service Component Architecture. It is a set of specifications that describe a
-framework for building applications and systems using SOA concepts. One of the driving concepts
-behind SCA is that applications and systems are built up by linking services into assemblies.</p>
-<p>For more information see
-<a href="http://www-128.ibm.com/developerworks/library/specification/ws-scasdosumm/">http://www-128.ibm.com/developerworks/library/specification/ws-scasdosumm/</a>.</p>
-</answer>
-</faq>
-<faq>
-<question>
-How does CeltiXfire relate to SCA?
-</question>
-<answer>
-SCA focuses on assembling service implementations into complex business applications. CeltiXfire
-focuses on implementing individual services. CeltiXfire services can be consumed by SCA
-implementations. Currently, the CeltiXfire project is working with the Tuscany project to ensure
-robust integration between CeltiXfire services and SCA implementations.
-</answer>
-</faq>
-</faqsection>
-<faqsection>
-<title>Management</title>
-<faq>
-<question>
-What are CeltiXfire's management capabilities?
-</question>
-<answer>
-All of the internal components of CeltiXfire are instrumented using JMX. In addition, CeltiXfire supports
-adding custom JMX instrumentation to any services developed using CeltiXfire. Therefore, CeltiXfire
-artifacts can be managed by any JMX compliant management tool.
-</answer>
-</faq>
-</faqsection>
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Copyright 2002-2004 The Apache Software Foundation or its licensors,
+ as applicable.
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+<!DOCTYPE faqs PUBLIC "-//APACHE//DTD FAQ V2.0//EN" "http://forrest.apache.org/dtd/faq-v20.dtd">
+
+<faqs>
+ <title>Technology FAQ</title>
+<faqsection>
+<title>Prerequisites</title>
+ <faq>
+ <question>
+ What are the prerequisites for using CeltiXfire?
+ </question>
+ <answer>
+ <p>For running CeltiXfire-enabled applications all you need to have is a Java 5 JVM.</p>
+ <p>To develop services using CeltiXfire, you need Sun Microsystem's Java 5 JDK.</p>
+ </answer>
+ </faq>
+ <faq>
+ <question>
+ Does the CeltiXfire runtime require a J2EE container?
+ </question>
+ <answer>
+ No. CeltiXfire does not require either a J2EE container or a Web container.
+ </answer>
+ </faq>
+</faqsection>
+<faqsection>
+<title>Standards</title>
+ <faq>
+ <question>
+ What Web service standards does CeltiXfire support?
+ </question>
+ <answer>
+ <p>CeltiXfire implements the following Web service standards:</p>
+ <ul>
+ <li>JAX-WS 2.0</li>
+ <li>WS-Addressing</li>
+ <li>WS-ReliableMessaging(WS-RM)</li>
+ <li>WSDL 1.1</li>
+ <li>SOAP 1.1</li>
+ </ul>
+ </answer>
+ </faq>
+</faqsection>
+<faqsection>
+<title>JAX-WS</title>
+ <faq>
+ <question>
+ How does CeltiXfire allow you to service-enable your applications?
+ </question>
+ <answer>
+ CeltiXfire implements the JAX-WS 2.0 specification. JAX-WS 2.0 provides a straightforward way
+ to service-enable your applications using the Java 1.5 Annotation mechanism. It also
+ provides a programming model that enables the creation of Web services-ready Java applications.
+ </answer>
+ </faq>
+ <faq>
+ <question>
+ Has CeltiXfire extended JAX-WS in any way?
+ </question>
+ <answer>
+ Yes. CeltiXfire has extended JAX-WS by adding the concept of system handlers. This allows
+ developers to attach handlers at various points within the invocation chain, giving them more
+ power to interact with the data as it flows in and out of CeltiXfire.
+ </answer>
+ </faq>
+</faqsection>
+<faqsection>
+<title>Messaging</title>
+ <faq>
+ <question>
+ Does CeltiXfire provide messaging capabilities?
+ </question>
+ <answer>
+ CeltiXfire supports a means to deliver messages to a JMS implementation.
+ </answer>
+ </faq>
+<faq>
+ <question>
+ Does CeltiXfire depend on any JMS implementation?
+ </question>
+ <answer>
+ CeltiXfire is not based on a particular JMS implementation. It supports any JMS implementation and
+ ships with the open source ActiveMQ JMS implementation.
+ </answer>
+</faq>
+</faqsection>
+<faqsection>
+<title>J2EE</title>
+ <faq>
+ <question>
+ Can CeltiXfire interoperate with a J2EE container?
+ </question>
+ <answer>
+ While CeltiXfire does not require a J2EE application server, CeltiXfire artifacts can be deployed
+ into a J2EE container.
+ </answer>
+ </faq>
+</faqsection>
+<faqsection>
+<title>JBI</title>
+<faq>
+<question>
+What is JBI?
+</question>
+<answer>
+<p>JBI stands for Java Bussines Integration. It is a standardized set of APIs, Service Provider
+Interfaces (SPIs) and technologies, maintained through the Java Community Process, for integration
+of business components.</p>
+<p>For more information see
+<a href="http://www.jcp.org/en/jsr/detail?id=208">http://www.jcp.org/en/jsr/detail?id=208</a></p>
+</answer>
+</faq>
+<faq>
+<question>
+How does CeltiXfire relate to JBI?
+</question>
+<answer>
+At a quick glance CeltiXfire and a JBI implementation may appear to be addressing the same set of
+problems. However, CeltiXfire is not a JBI implementation. Unlike JBI, CeltiXfire provides a much more
+extensible framework for building services. Its focus is to provide a rich framework for linking
+non-Java, non-Web Service artifacts as well as building feature rich Web services. CeltiXfire is
+intended to complement JBI. To this end, it is possible to deploy CeltiXfire runtime components and
+CeltiXfire developed services inside a compliant JBI container.
+</answer>
+</faq>
+</faqsection>
+<faqsection>
+<title>SCA</title>
+<faq>
+<question>
+What is SCA?
+</question>
+<answer>
+<p>SCA stands for Service Component Architecture. It is a set of specifications that describe a
+framework for building applications and systems using SOA concepts. One of the driving concepts
+behind SCA is that applications and systems are built up by linking services into assemblies.</p>
+<p>For more information see
+<a href="http://www-128.ibm.com/developerworks/library/specification/ws-scasdosumm/">http://www-128.ibm.com/developerworks/library/specification/ws-scasdosumm/</a>.</p>
+</answer>
+</faq>
+<faq>
+<question>
+How does CeltiXfire relate to SCA?
+</question>
+<answer>
+SCA focuses on assembling service implementations into complex business applications. CeltiXfire
+focuses on implementing individual services. CeltiXfire services can be consumed by SCA
+implementations. Currently, the CeltiXfire project is working with the Tuscany project to ensure
+robust integration between CeltiXfire services and SCA implementations.
+</answer>
+</faq>
+</faqsection>
+<faqsection>
+<title>Management</title>
+<faq>
+<question>
+What are CeltiXfire's management capabilities?
+</question>
+<answer>
+All of the internal components of CeltiXfire are instrumented using JMX. In addition, CeltiXfire supports
+adding custom JMX instrumentation to any services developed using CeltiXfire. Therefore, CeltiXfire
+artifacts can be managed by any JMX compliant management tool.
+</answer>
+</faq>
+</faqsection>
</faqs>
Propchange: incubator/cxf/trunk/docs/src/faqs/tech-faq.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: incubator/cxf/trunk/docs/src/faqs/tech-faq.xml
------------------------------------------------------------------------------
svn:keywords = Rev Date
Propchange: incubator/cxf/trunk/docs/src/faqs/tech-faq.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Modified: incubator/cxf/trunk/docs/src/index.xml
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/docs/src/index.xml?rev=436785&r1=436784&r2=436785&view=diff
==============================================================================
--- incubator/cxf/trunk/docs/src/index.xml (original)
+++ incubator/cxf/trunk/docs/src/index.xml Fri Aug 25 06:16:36 2006
@@ -1,104 +1,104 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
-<document>
- <header>
- <title>CeltiXfire: The Open Source ESB</title>
- <abstract>CeltiXfire delivers a Java enterprise service bus (ESB) runtime and set of APIs that make it easy to add transports, message formats, and security features. The goal is to simplify the construction, integration and flexible reuse of technical and business components using a standards-based, service-oriented architecture.</abstract>
- </header>
- <body>
- <section id="updates">
- <title>Latest Updates</title>
- <section id="newest">
- <title>May 10, 2006</title>
- <p>Celtix 1.0 is released and available for download at <a href="http://forge.objectweb.org/project/showfiles.php?group_id=192">http://forge.objectweb.org/project/showfiles.php?group_id=192</a>. Celtix 1.0 is also available as a Maven distribution at, <a href="http://maven.objectweb.org/maven2">http://maven.objectweb.org/maven2</a>.</p>
- <p>Celtix 1.0 provides users with a feature-rich, open source ESB runtime that can support any organization's adoption of Service Oriented Architecture (SOA) in the enterprise.</p>
- <p>The Celtix project was initiated in June 2005 under the sponsorship of IONA. Celtix 1.0 is the result of the fifth consecutive on-schedule delivery of key project milestones and the acceptance of the current Celtix build by the ObjectWeb community. The availability of an open source ESB that offers comparable features and functionality to many commercially available ESB products provides users with an effective, standards-based foundation from which their SOA initiatives can be rapidly built and extended.</p>
- <p>The features contained in this release include:</p>
- <ul>
- <li>Persistence support for Reliable Messaging based on Apache Derby</li>
- <li>HTTPS based security support</li>
- <li>Support for Javascript based webservices.</li>
- <li>Support for changing configuration dynamically</li>
- <li>Management support for additional Celtix components</li>
- <li>Support for wsdlvalidator commandline tool</li>
- <li>Routing support for all Celtix bindings and transports</li>
- <li>Enhanced routing capabilities</li>
- <li>WS-Addressing support for JMS based services</li>
- <li>Interoperability with .NET.</li>
- <li>Support for Maven 2.0.4</li>
- <li>Support for running Celtix inside Apache Tuscany</li>
- <li>Support for Webservice callbacks</li>
- </ul>
- <p>Features completed in previous releases include:</p>
- <table>
- <tr>
- <td>
- <ul>
- <li>Support for JAX-WS Dispatch APIs</li>
- <li>Support for JAX-WS Provider APIs</li>
- <li>Support for non-wrapper Doc/Literal style</li>
- <li>Celtix based javatowsdl tool</li>
- <li>Celtix based wsdltojava tool</li>
- <li>First cut of transport APIs</li>
- <li>Enhanced binding API for better pluggability</li>
- <li>Support for Protocol Handlers</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>Support for Logical Handlers</li>
- <li>Support for Contexts</li>
- <li>SOAP 1.1 support for doc/rpc literal</li>
- <li>Support for SOAP 1.1 faults</li>
- <li>Support for SOAP 1.1 headers</li>
- <li>Support for JAX-WS Sync APIs</li>
- <li>Support for JAX-WS One-Way APIs</li>
- <li>Support for inout and out variables</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>HTTP 1.1 transport</li>
- <li>HTTP servlet transport</li>
- <li>JMS transport based on Active MQ</li>
- <li>Support for WS-Addressing</li>
- <li>Support for JAX-WS async client APIs</li>
- <li>Policy based configuration</li>
- <li>Support for StreamHandler APIs</li>
- <li>WS-RM based support for Webservices Reliability</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>Support for JMX based management</li>
- <li>XML Binding</li>
- <li>New commandline tools: xsd2wsdl, wsdl2xml, wsdl2soap, wsdl2service</li>
- <li>Native integration into Apache Geronimo J2EE appserver</li>
- <li>Support for validating application data against XMLSchema</li>
- <li>Enhanced support for deploying celtix services into a servlet container based on feedback from Jonas J2EE appserver project</li>
- </ul>
- </td>
- </tr>
- </table>
- </section>
- <section>
- <title>April 5, 2006</title>
- <p>The documentation team has added a <a href="site:jms">guide</a> for using the Celtix JMS transport. It includes information on:</p>
- <ul>
- <li>specifying JMS address information</li>
- <li>setting endpoint conneciton behavior</li>
- <li>using the internal contexts in JMS consumer endpoints</li>
- </ul>
- <p>In addition, the command line tools <a href="site:toolsref">guide</a> has been updated.</p>
- </section>
- </section>
- <section id="news">
- <title>Celtix in the News</title>
- <p><a href="http://www.tmcnet.com/usubmit/2005/dec/1234205.htm">ObjectWeb Celtix Project Achieves Third Key Milestone; Full JMS Transport Support and Multiple Licensing Strategy Mark Latest Accomplishments</a> - Internet Telephony</p>
- <p><a href="http://www.eweek.com/article2/0,1759,1904802,00.asp?kc=EWRSS03119TX1K0000594">IONA, ObjectWeb Announce Milestone 3 of Celtix</a> - eWeek Dec. 22, 2005</p>
- <p><a href="http://www.eweek.com/article2/0,1759,1900246,00.asp?kc=EWRSS03119TX1K0000594">Apache Tuscany Project to Simplify SOA Development</a> - eWeek Dec. 12, 2005</p>
- <p><a href="http://searchwebservices.techtarget.com/originalContent/0,289142,sid26_gci1141304,00.html">Proponents say JBI helps define ESBs</a> - SearchWebservices.com Nov. 08, 2005</p>
- <p><a href="http://newsvac.newsforge.com/article.pl?sid=05/11/04/1624233">ObjectWeb Celtix Project Achieves 2nd Key Milestone</a> - NewsForge Nov. 04, 2005</p>
- </section>
- </body>
-</document>
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
+<document>
+ <header>
+ <title>CeltiXfire: The Open Source ESB</title>
+ <abstract>CeltiXfire delivers a Java enterprise service bus (ESB) runtime and set of APIs that make it easy to add transports, message formats, and security features. The goal is to simplify the construction, integration and flexible reuse of technical and business components using a standards-based, service-oriented architecture.</abstract>
+ </header>
+ <body>
+ <section id="updates">
+ <title>Latest Updates</title>
+ <section id="newest">
+ <title>May 10, 2006</title>
+ <p>Celtix 1.0 is released and available for download at <a href="http://forge.objectweb.org/project/showfiles.php?group_id=192">http://forge.objectweb.org/project/showfiles.php?group_id=192</a>. Celtix 1.0 is also available as a Maven distribution at, <a href="http://maven.objectweb.org/maven2">http://maven.objectweb.org/maven2</a>.</p>
+ <p>Celtix 1.0 provides users with a feature-rich, open source ESB runtime that can support any organization's adoption of Service Oriented Architecture (SOA) in the enterprise.</p>
+ <p>The Celtix project was initiated in June 2005 under the sponsorship of IONA. Celtix 1.0 is the result of the fifth consecutive on-schedule delivery of key project milestones and the acceptance of the current Celtix build by the ObjectWeb community. The availability of an open source ESB that offers comparable features and functionality to many commercially available ESB products provides users with an effective, standards-based foundation from which their SOA initiatives can be rapidly built and extended.</p>
+ <p>The features contained in this release include:</p>
+ <ul>
+ <li>Persistence support for Reliable Messaging based on Apache Derby</li>
+ <li>HTTPS based security support</li>
+ <li>Support for Javascript based webservices.</li>
+ <li>Support for changing configuration dynamically</li>
+ <li>Management support for additional Celtix components</li>
+ <li>Support for wsdlvalidator commandline tool</li>
+ <li>Routing support for all Celtix bindings and transports</li>
+ <li>Enhanced routing capabilities</li>
+ <li>WS-Addressing support for JMS based services</li>
+ <li>Interoperability with .NET.</li>
+ <li>Support for Maven 2.0.4</li>
+ <li>Support for running Celtix inside Apache Tuscany</li>
+ <li>Support for Webservice callbacks</li>
+ </ul>
+ <p>Features completed in previous releases include:</p>
+ <table>
+ <tr>
+ <td>
+ <ul>
+ <li>Support for JAX-WS Dispatch APIs</li>
+ <li>Support for JAX-WS Provider APIs</li>
+ <li>Support for non-wrapper Doc/Literal style</li>
+ <li>Celtix based javatowsdl tool</li>
+ <li>Celtix based wsdltojava tool</li>
+ <li>First cut of transport APIs</li>
+ <li>Enhanced binding API for better pluggability</li>
+ <li>Support for Protocol Handlers</li>
+ </ul>
+ </td>
+ <td>
+ <ul>
+ <li>Support for Logical Handlers</li>
+ <li>Support for Contexts</li>
+ <li>SOAP 1.1 support for doc/rpc literal</li>
+ <li>Support for SOAP 1.1 faults</li>
+ <li>Support for SOAP 1.1 headers</li>
+ <li>Support for JAX-WS Sync APIs</li>
+ <li>Support for JAX-WS One-Way APIs</li>
+ <li>Support for inout and out variables</li>
+ </ul>
+ </td>
+ <td>
+ <ul>
+ <li>HTTP 1.1 transport</li>
+ <li>HTTP servlet transport</li>
+ <li>JMS transport based on Active MQ</li>
+ <li>Support for WS-Addressing</li>
+ <li>Support for JAX-WS async client APIs</li>
+ <li>Policy based configuration</li>
+ <li>Support for StreamHandler APIs</li>
+ <li>WS-RM based support for Webservices Reliability</li>
+ </ul>
+ </td>
+ <td>
+ <ul>
+ <li>Support for JMX based management</li>
+ <li>XML Binding</li>
+ <li>New commandline tools: xsd2wsdl, wsdl2xml, wsdl2soap, wsdl2service</li>
+ <li>Native integration into Apache Geronimo J2EE appserver</li>
+ <li>Support for validating application data against XMLSchema</li>
+ <li>Enhanced support for deploying celtix services into a servlet container based on feedback from Jonas J2EE appserver project</li>
+ </ul>
+ </td>
+ </tr>
+ </table>
+ </section>
+ <section>
+ <title>April 5, 2006</title>
+ <p>The documentation team has added a <a href="site:jms">guide</a> for using the Celtix JMS transport. It includes information on:</p>
+ <ul>
+ <li>specifying JMS address information</li>
+ <li>setting endpoint conneciton behavior</li>
+ <li>using the internal contexts in JMS consumer endpoints</li>
+ </ul>
+ <p>In addition, the command line tools <a href="site:toolsref">guide</a> has been updated.</p>
+ </section>
+ </section>
+ <section id="news">
+ <title>Celtix in the News</title>
+ <p><a href="http://www.tmcnet.com/usubmit/2005/dec/1234205.htm">ObjectWeb Celtix Project Achieves Third Key Milestone; Full JMS Transport Support and Multiple Licensing Strategy Mark Latest Accomplishments</a> - Internet Telephony</p>
+ <p><a href="http://www.eweek.com/article2/0,1759,1904802,00.asp?kc=EWRSS03119TX1K0000594">IONA, ObjectWeb Announce Milestone 3 of Celtix</a> - eWeek Dec. 22, 2005</p>
+ <p><a href="http://www.eweek.com/article2/0,1759,1900246,00.asp?kc=EWRSS03119TX1K0000594">Apache Tuscany Project to Simplify SOA Development</a> - eWeek Dec. 12, 2005</p>
+ <p><a href="http://searchwebservices.techtarget.com/originalContent/0,289142,sid26_gci1141304,00.html">Proponents say JBI helps define ESBs</a> - SearchWebservices.com Nov. 08, 2005</p>
+ <p><a href="http://newsvac.newsforge.com/article.pl?sid=05/11/04/1624233">ObjectWeb Celtix Project Achieves 2nd Key Milestone</a> - NewsForge Nov. 04, 2005</p>
+ </section>
+ </body>
+</document>
Propchange: incubator/cxf/trunk/docs/src/index.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: incubator/cxf/trunk/docs/src/index.xml
------------------------------------------------------------------------------
svn:keywords = Rev Date
Propchange: incubator/cxf/trunk/docs/src/index.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Modified: incubator/cxf/trunk/docs/src/site.xml
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/docs/src/site.xml?rev=436785&r1=436784&r2=436785&view=diff
==============================================================================
--- incubator/cxf/trunk/docs/src/site.xml (original)
+++ incubator/cxf/trunk/docs/src/site.xml Fri Aug 25 06:16:36 2006
@@ -1,103 +1,103 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
- Copyright 2002-2004 The Apache Software Foundation or its licensors,
- as applicable.
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
--->
-
-<!--
-Forrest site.xml
-
-This file contains an outline of the site's information content. It is used to:
-- Generate the website menus (though these can be overridden - see docs)
-- Provide semantic, location-independent aliases for internal 'site:' URIs, eg
-<link href="site:changes"> links to changes.html (or ../changes.html if in
- subdir).
-- Provide aliases for external URLs in the external-refs section. Eg, <link
- href="ext:cocoon"> links to http://cocoon.apache.org/
-
-See http://forrest.apache.org/docs/linking.html for more info
--->
-
-<site label="CeltiXfire" href="" xmlns="http://apache.org/forrest/linkmap/1.0">
- <!-- Note: No matter what you configure here, Forrest will always try to load
- index.html when you request http://yourHost/.
- 'How can I use a start-up-page other than index.html?' in the FAQs has more
- information tells you how to change that.
- -->
-
- <projLink label="Project Links">
- <dwnLoad label="Download" href="http://forge.objectweb.org/project/showfiles.php?group_id=192" description="Download the latest Celtix kits" />
- <training label="Training Materials" href="http://www.iona.com/info/services/oss/info_services_oss_train.html" description="Training materials offered by IONA technologies" />
- <milestone label="Milestones" href="https://wiki.objectweb.org/celtix/Wiki.jsp?page=Milestones" description="Roadmap of Celtix milestones" />
- <mailingList label="Mailing List" href="http://www.objectweb.org/wws/lists/projects/celtix" description="Project mailing lists" />
- <porjWiki label="Wiki" href="http://wiki.objectweb.org/celtix" description="Celtix team wiki" />
- </projLink>
- <licenses label="Licenses">
- <lpgl label="LPGL" href="http://forge.objectweb.org/softwaremap/trove_list.php?form_cat=16" description="Objectweb LPGL page"/>
- <epl label="EPL" href="http://forge.objectweb.org/softwaremap/trove_list.php?form_cat=271" description="Objectweb EPL page" />
- </licenses>
- <devcorner label="Developers' Corner">
- <repos label="SVN Repository" href="http://forge.objectweb.org/plugins/scmsvn/index.php?group_id=192" description="Celtix SVN repository" />
- <devplans label="Development Plans" description="Developers' plans for features" href="http://forge.objectweb.org/plugins/scmsvn/index.php?group_id=192" />
- <bugtracking label="Bug Tracking" description="Celtix bug database" href="http://forge.objectweb.org/tracker/?atid=350241&group_id=192&func=browse" />
- <forge label="Objectweb Forge Site" description="Objectweb forge for all of its projects" href="http://forge.objectweb.org/projects/celtix/" />
- </devcorner>
- <about label="About">
- <team label="Team" href="http://forge.objectweb.org/project/memberlist.php?group_id=192" description="Team member profiles." />
- </about>
-
- <top href="index.html" />
-
- <demos href="demos/">
- <home href="index.html" />
- </demos>
-
- <faqs href="faqs/">
- <general href="general-faq.html" />
- <license href="license-faq.html" />
- <project href="project-faq.html" />
- <features href="features-faq.html" />
- <tech href="tech-faq.html" />
- </faqs>
-
- <docco href="docs/">
- <home href="index.html" />
- <proj href="project.html" />
- <rel_notes href="release_notes.txt" />
- <jms href="guides/jms.html" />
- <config href="guides/configuration.html" />
- <dyn_lang href="guides/dynamic_lang.html" />
- <toolsref href="refs/tools.html" />
- <tomcat href="guides/tomcat_deploy.html" />
- <install href="guides/installation.html" />
- <get_started href="guides/getting_started.html" />
- <mgmt href="guides/management.html" />
- <consumer_dev href="guides/develop_consumer.html" />
- <style href="styleguide/styleguide.html" />
- </docco>
-
- <!--
- The href must be wholesite.html/pdf You can change the labels and node names
- <all label="All">
- <whole_site_html label="Whole Site HTML" href="wholesite.html"/>
- <whole_site_pdf label="Whole Site PDF" href="wholesite.pdf"/>
- </all>
- -->
-
- <external-refs>
- <iona href="http://www.iona.com/" />
- </external-refs>
-
-</site>
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Copyright 2002-2004 The Apache Software Foundation or its licensors,
+ as applicable.
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+<!--
+Forrest site.xml
+
+This file contains an outline of the site's information content. It is used to:
+- Generate the website menus (though these can be overridden - see docs)
+- Provide semantic, location-independent aliases for internal 'site:' URIs, eg
+<link href="site:changes"> links to changes.html (or ../changes.html if in
+ subdir).
+- Provide aliases for external URLs in the external-refs section. Eg, <link
+ href="ext:cocoon"> links to http://cocoon.apache.org/
+
+See http://forrest.apache.org/docs/linking.html for more info
+-->
+
+<site label="CeltiXfire" href="" xmlns="http://apache.org/forrest/linkmap/1.0">
+ <!-- Note: No matter what you configure here, Forrest will always try to load
+ index.html when you request http://yourHost/.
+ 'How can I use a start-up-page other than index.html?' in the FAQs has more
+ information tells you how to change that.
+ -->
+
+ <projLink label="Project Links">
+ <dwnLoad label="Download" href="http://forge.objectweb.org/project/showfiles.php?group_id=192" description="Download the latest Celtix kits" />
+ <training label="Training Materials" href="http://www.iona.com/info/services/oss/info_services_oss_train.html" description="Training materials offered by IONA technologies" />
+ <milestone label="Milestones" href="https://wiki.objectweb.org/celtix/Wiki.jsp?page=Milestones" description="Roadmap of Celtix milestones" />
+ <mailingList label="Mailing List" href="http://www.objectweb.org/wws/lists/projects/celtix" description="Project mailing lists" />
+ <porjWiki label="Wiki" href="http://wiki.objectweb.org/celtix" description="Celtix team wiki" />
+ </projLink>
+ <licenses label="Licenses">
+ <lpgl label="LPGL" href="http://forge.objectweb.org/softwaremap/trove_list.php?form_cat=16" description="Objectweb LPGL page"/>
+ <epl label="EPL" href="http://forge.objectweb.org/softwaremap/trove_list.php?form_cat=271" description="Objectweb EPL page" />
+ </licenses>
+ <devcorner label="Developers' Corner">
+ <repos label="SVN Repository" href="http://forge.objectweb.org/plugins/scmsvn/index.php?group_id=192" description="Celtix SVN repository" />
+ <devplans label="Development Plans" description="Developers' plans for features" href="http://forge.objectweb.org/plugins/scmsvn/index.php?group_id=192" />
+ <bugtracking label="Bug Tracking" description="Celtix bug database" href="http://forge.objectweb.org/tracker/?atid=350241&group_id=192&func=browse" />
+ <forge label="Objectweb Forge Site" description="Objectweb forge for all of its projects" href="http://forge.objectweb.org/projects/celtix/" />
+ </devcorner>
+ <about label="About">
+ <team label="Team" href="http://forge.objectweb.org/project/memberlist.php?group_id=192" description="Team member profiles." />
+ </about>
+
+ <top href="index.html" />
+
+ <demos href="demos/">
+ <home href="index.html" />
+ </demos>
+
+ <faqs href="faqs/">
+ <general href="general-faq.html" />
+ <license href="license-faq.html" />
+ <project href="project-faq.html" />
+ <features href="features-faq.html" />
+ <tech href="tech-faq.html" />
+ </faqs>
+
+ <docco href="docs/">
+ <home href="index.html" />
+ <proj href="project.html" />
+ <rel_notes href="release_notes.txt" />
+ <jms href="guides/jms.html" />
+ <config href="guides/configuration.html" />
+ <dyn_lang href="guides/dynamic_lang.html" />
+ <toolsref href="refs/tools.html" />
+ <tomcat href="guides/tomcat_deploy.html" />
+ <install href="guides/installation.html" />
+ <get_started href="guides/getting_started.html" />
+ <mgmt href="guides/management.html" />
+ <consumer_dev href="guides/develop_consumer.html" />
+ <style href="styleguide/styleguide.html" />
+ </docco>
+
+ <!--
+ The href must be wholesite.html/pdf You can change the labels and node names
+ <all label="All">
+ <whole_site_html label="Whole Site HTML" href="wholesite.html"/>
+ <whole_site_pdf label="Whole Site PDF" href="wholesite.pdf"/>
+ </all>
+ -->
+
+ <external-refs>
+ <iona href="http://www.iona.com/" />
+ </external-refs>
+
+</site>
Propchange: incubator/cxf/trunk/docs/src/site.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: incubator/cxf/trunk/docs/src/site.xml
------------------------------------------------------------------------------
svn:keywords = Rev Date
Propchange: incubator/cxf/trunk/docs/src/site.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Modified: incubator/cxf/trunk/docs/src/tabs.xml
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/docs/src/tabs.xml?rev=436785&r1=436784&r2=436785&view=diff
==============================================================================
--- incubator/cxf/trunk/docs/src/tabs.xml (original)
+++ incubator/cxf/trunk/docs/src/tabs.xml Fri Aug 25 06:16:36 2006
@@ -1,36 +1,36 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
- Copyright 2002-2004 The Apache Software Foundation or its licensors,
- as applicable.
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
--->
-<!DOCTYPE tabs PUBLIC "-//APACHE//DTD Cocoon Documentation Tab V1.1//EN" "http://forrest.apache.org/dtd/tab-cocoon-v11.dtd">
-
-<tabs software="Celtix" title="Celtix" copyright="2005" xmlns:xlink="http://www.w3.org/1999/xlink">
-
- <!-- The rules for tabs are:
- @dir will always have '/@indexfile' added.
- @indexfile gets appended to @dir if the tab is selected. Defaults to 'index.html'
- @href is not modified unless it is root-relative and obviously specifies a
- directory (ends in '/'), in which case /index.html will be added
- If @id's are present, site.xml entries with a matching @tab will be in that tab.
-
- Tabs can be embedded to a depth of two. The second level of tabs will only
- be displayed when their parent tab is selected.
- -->
-
- <tab id="home" label="Home" dir="" />
- <tab id="docs" label="Documentation" dir="docs" />
- <tab id="demos" label="Demos" dir="demos" />
-</tabs>
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Copyright 2002-2004 The Apache Software Foundation or its licensors,
+ as applicable.
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+<!DOCTYPE tabs PUBLIC "-//APACHE//DTD Cocoon Documentation Tab V1.1//EN" "http://forrest.apache.org/dtd/tab-cocoon-v11.dtd">
+
+<tabs software="Celtix" title="Celtix" copyright="2005" xmlns:xlink="http://www.w3.org/1999/xlink">
+
+ <!-- The rules for tabs are:
+ @dir will always have '/@indexfile' added.
+ @indexfile gets appended to @dir if the tab is selected. Defaults to 'index.html'
+ @href is not modified unless it is root-relative and obviously specifies a
+ directory (ends in '/'), in which case /index.html will be added
+ If @id's are present, site.xml entries with a matching @tab will be in that tab.
+
+ Tabs can be embedded to a depth of two. The second level of tabs will only
+ be displayed when their parent tab is selected.
+ -->
+
+ <tab id="home" label="Home" dir="" />
+ <tab id="docs" label="Documentation" dir="docs" />
+ <tab id="demos" label="Demos" dir="demos" />
+</tabs>
Propchange: incubator/cxf/trunk/docs/src/tabs.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: incubator/cxf/trunk/docs/src/tabs.xml
------------------------------------------------------------------------------
svn:keywords = Rev Date
Propchange: incubator/cxf/trunk/docs/src/tabs.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Propchange: incubator/cxf/trunk/etc/cruisecontrol_config.xml
------------------------------------------------------------------------------
svn:keywords = Rev Date
Propchange: incubator/cxf/trunk/etc/eclipse/CXFCodeFormatter.xml
------------------------------------------------------------------------------
svn:keywords = Rev Date
Propchange: incubator/cxf/trunk/etc/eclipse/codetemplates.xml
------------------------------------------------------------------------------
svn:keywords = Rev Date
Propchange: incubator/cxf/trunk/etc/eclipse/template.checkstyle-config.xml
------------------------------------------------------------------------------
svn:keywords = Rev Date
Propchange: incubator/cxf/trunk/maven/conf/settings.xml
------------------------------------------------------------------------------
svn:keywords = Rev Date
Propchange: incubator/cxf/trunk/pom.xml
------------------------------------------------------------------------------
svn:keywords = Rev Date
Modified: incubator/cxf/trunk/rt/bindings/soap/pom.xml
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/rt/bindings/soap/pom.xml?rev=436785&r1=436784&r2=436785&view=diff
==============================================================================
--- incubator/cxf/trunk/rt/bindings/soap/pom.xml (original)
+++ incubator/cxf/trunk/rt/bindings/soap/pom.xml Fri Aug 25 06:16:36 2006
@@ -1,65 +1,65 @@
-<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
- <modelVersion>4.0.0</modelVersion>
- <artifactId>cxf-rt-bindings-soap</artifactId>
- <packaging>jar</packaging>
- <name>CXF Runtime SOAP Binding</name>
- <url>http://cwiki.apache.org/confluence/display/CXF/CeltiXfire+space</url>
-
- <parent>
- <groupId>org.apache.cxf</groupId>
- <artifactId>cxf-rt-bindings</artifactId>
- <version>1.1-SNAPSHOT</version>
- </parent>
-
- <properties>
- <topDirectoryLocation>../../..</topDirectoryLocation>
- </properties>
-
- <dependencies>
-
- <dependency>
- <groupId>org.apache.cxf</groupId>
- <artifactId>cxf-api</artifactId>
- <version>${project.version}</version>
- </dependency>
- <dependency>
- <groupId>org.apache.cxf</groupId>
- <artifactId>cxf-rt-databinding-jaxb</artifactId>
- <version>${project.version}</version>
- </dependency>
- <dependency>
- <groupId>org.apache.cxf</groupId>
- <artifactId>cxf-testutils</artifactId>
- <version>${project.version}</version>
- <scope>test</scope>
- </dependency>
-
- <dependency>
- <groupId>junit</groupId>
- <artifactId>junit</artifactId>
- <scope>test</scope>
- </dependency>
-
- <dependency>
- <groupId>org.easymock</groupId>
- <artifactId>easymockclassextension</artifactId>
- <scope>test</scope>
- </dependency>
- <dependency>
- <groupId>javax.mail</groupId>
- <artifactId>mail</artifactId>
- <scope>test</scope>
- </dependency>
- <dependency>
- <groupId>javax.activation</groupId>
- <artifactId>activation</artifactId>
- <scope>test</scope>
- </dependency>
- <dependency>
- <groupId>javax.xml.bind</groupId>
- <artifactId>jaxb-api</artifactId>
- </dependency>
- </dependencies>
-
-</project>
+<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
+ <modelVersion>4.0.0</modelVersion>
+ <artifactId>cxf-rt-bindings-soap</artifactId>
+ <packaging>jar</packaging>
+ <name>CXF Runtime SOAP Binding</name>
+ <url>http://cwiki.apache.org/confluence/display/CXF/CeltiXfire+space</url>
+
+ <parent>
+ <groupId>org.apache.cxf</groupId>
+ <artifactId>cxf-rt-bindings</artifactId>
+ <version>1.1-SNAPSHOT</version>
+ </parent>
+
+ <properties>
+ <topDirectoryLocation>../../..</topDirectoryLocation>
+ </properties>
+
+ <dependencies>
+
+ <dependency>
+ <groupId>org.apache.cxf</groupId>
+ <artifactId>cxf-api</artifactId>
+ <version>${project.version}</version>
+ </dependency>
+ <dependency>
+ <groupId>org.apache.cxf</groupId>
+ <artifactId>cxf-rt-databinding-jaxb</artifactId>
+ <version>${project.version}</version>
+ </dependency>
+ <dependency>
+ <groupId>org.apache.cxf</groupId>
+ <artifactId>cxf-testutils</artifactId>
+ <version>${project.version}</version>
+ <scope>test</scope>
+ </dependency>
+
+ <dependency>
+ <groupId>junit</groupId>
+ <artifactId>junit</artifactId>
+ <scope>test</scope>
+ </dependency>
+
+ <dependency>
+ <groupId>org.easymock</groupId>
+ <artifactId>easymockclassextension</artifactId>
+ <scope>test</scope>
+ </dependency>
+ <dependency>
+ <groupId>javax.mail</groupId>
+ <artifactId>mail</artifactId>
+ <scope>test</scope>
+ </dependency>
+ <dependency>
+ <groupId>javax.activation</groupId>
+ <artifactId>activation</artifactId>
+ <scope>test</scope>
+ </dependency>
+ <dependency>
+ <groupId>javax.xml.bind</groupId>
+ <artifactId>jaxb-api</artifactId>
+ </dependency>
+ </dependencies>
+
+</project>
Propchange: incubator/cxf/trunk/rt/bindings/soap/pom.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: incubator/cxf/trunk/rt/bindings/soap/pom.xml
------------------------------------------------------------------------------
svn:keywords = Rev Date
Propchange: incubator/cxf/trunk/rt/bindings/soap/pom.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Modified: incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/AbstractSoapInterceptor.java
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/AbstractSoapInterceptor.java?rev=436785&r1=436784&r2=436785&view=diff
==============================================================================
--- incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/AbstractSoapInterceptor.java (original)
+++ incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/AbstractSoapInterceptor.java Fri Aug 25 06:16:36 2006
@@ -1,21 +1,21 @@
-package org.apache.cxf.binding.soap;
-
-import java.net.URI;
-import java.util.Collections;
-import java.util.Set;
-
-import javax.xml.namespace.QName;
-
-import org.apache.cxf.phase.AbstractPhaseInterceptor;
-
-public abstract class AbstractSoapInterceptor extends AbstractPhaseInterceptor<SoapMessage>
- implements SoapInterceptor {
-
- public Set<URI> getRoles() {
- return Collections.emptySet();
- }
-
- public Set<QName> getUnderstoodHeaders() {
- return Collections.emptySet();
- }
-}
+package org.apache.cxf.binding.soap;
+
+import java.net.URI;
+import java.util.Collections;
+import java.util.Set;
+
+import javax.xml.namespace.QName;
+
+import org.apache.cxf.phase.AbstractPhaseInterceptor;
+
+public abstract class AbstractSoapInterceptor extends AbstractPhaseInterceptor<SoapMessage>
+ implements SoapInterceptor {
+
+ public Set<URI> getRoles() {
+ return Collections.emptySet();
+ }
+
+ public Set<QName> getUnderstoodHeaders() {
+ return Collections.emptySet();
+ }
+}
Propchange: incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/AbstractSoapInterceptor.java
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/AbstractSoapInterceptor.java
------------------------------------------------------------------------------
svn:keywords = Rev Date
Propchange: incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/AttachmentOutInterceptor.java
------------------------------------------------------------------------------
svn:keywords = Rev Date
Modified: incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/HeaderUtil.java
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/HeaderUtil.java?rev=436785&r1=436784&r2=436785&view=diff
==============================================================================
--- incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/HeaderUtil.java (original)
+++ incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/HeaderUtil.java Fri Aug 25 06:16:36 2006
@@ -1,55 +1,55 @@
-package org.apache.cxf.binding.soap;
-
-import java.util.HashSet;
-import java.util.List;
-import java.util.Set;
-
-import javax.wsdl.extensions.soap.SOAPHeader;
-import javax.xml.namespace.QName;
-
-import org.apache.cxf.helpers.CastUtils;
-import org.apache.cxf.service.model.BindingMessageInfo;
-import org.apache.cxf.service.model.BindingOperationInfo;
-import org.apache.cxf.service.model.MessagePartInfo;
-
-public final class HeaderUtil {
- private static final String HEADERS_PROPERTY = HeaderUtil.class.getName() + ".HEADERS";
-
- private HeaderUtil() {
- }
-
- private static Set<QName> getHeaderParts(BindingMessageInfo bmi) {
- Object obj = bmi.getProperty(HEADERS_PROPERTY);
- if (obj == null) {
- Set<QName> set = new HashSet<QName>();
- List<MessagePartInfo> mps = bmi.getMessageInfo().getMessageParts();
- for (SOAPHeader head : bmi.getExtensors(SOAPHeader.class)) {
- String pn = head.getPart();
- for (MessagePartInfo mpi : mps) {
- if (pn.equals(mpi.getName().getLocalPart())) {
- if (mpi.isElement()) {
- set.add(mpi.getElementQName());
- } else {
- set.add(mpi.getTypeQName());
- }
- break;
- }
- }
- }
- bmi.setProperty(HEADERS_PROPERTY, set);
- return set;
- }
- return CastUtils.cast((Set<?>)obj);
- }
-
- public static Set<QName> getHeaderQNameInOperationParam(SoapMessage soapMessage) {
- Set<QName> headers = new HashSet<QName>();
- BindingOperationInfo bop = soapMessage.getExchange()
- .get(BindingOperationInfo.class);
- if (bop != null) {
- headers.addAll(getHeaderParts(bop.getInput()));
- headers.addAll(getHeaderParts(bop.getOutput()));
- }
- return headers;
- }
-}
+package org.apache.cxf.binding.soap;
+
+import java.util.HashSet;
+import java.util.List;
+import java.util.Set;
+
+import javax.wsdl.extensions.soap.SOAPHeader;
+import javax.xml.namespace.QName;
+
+import org.apache.cxf.helpers.CastUtils;
+import org.apache.cxf.service.model.BindingMessageInfo;
+import org.apache.cxf.service.model.BindingOperationInfo;
+import org.apache.cxf.service.model.MessagePartInfo;
+
+public final class HeaderUtil {
+ private static final String HEADERS_PROPERTY = HeaderUtil.class.getName() + ".HEADERS";
+
+ private HeaderUtil() {
+ }
+
+ private static Set<QName> getHeaderParts(BindingMessageInfo bmi) {
+ Object obj = bmi.getProperty(HEADERS_PROPERTY);
+ if (obj == null) {
+ Set<QName> set = new HashSet<QName>();
+ List<MessagePartInfo> mps = bmi.getMessageInfo().getMessageParts();
+ for (SOAPHeader head : bmi.getExtensors(SOAPHeader.class)) {
+ String pn = head.getPart();
+ for (MessagePartInfo mpi : mps) {
+ if (pn.equals(mpi.getName().getLocalPart())) {
+ if (mpi.isElement()) {
+ set.add(mpi.getElementQName());
+ } else {
+ set.add(mpi.getTypeQName());
+ }
+ break;
+ }
+ }
+ }
+ bmi.setProperty(HEADERS_PROPERTY, set);
+ return set;
+ }
+ return CastUtils.cast((Set<?>)obj);
+ }
+
+ public static Set<QName> getHeaderQNameInOperationParam(SoapMessage soapMessage) {
+ Set<QName> headers = new HashSet<QName>();
+ BindingOperationInfo bop = soapMessage.getExchange()
+ .get(BindingOperationInfo.class);
+ if (bop != null) {
+ headers.addAll(getHeaderParts(bop.getInput()));
+ headers.addAll(getHeaderParts(bop.getOutput()));
+ }
+ return headers;
+ }
+}
Propchange: incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/HeaderUtil.java
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/HeaderUtil.java
------------------------------------------------------------------------------
svn:keywords = Rev Date
Modified: incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/Messages.properties
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/Messages.properties?rev=436785&r1=436784&r2=436785&view=diff
==============================================================================
--- incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/Messages.properties (original)
+++ incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/Messages.properties Fri Aug 25 06:16:36 2006
@@ -1,5 +1,5 @@
-XML_STREAM_EXC=Error reading XMLStreamReader.
-MUST_UNDERSTAND=Can not understand QNames: {0}
-PARSER_EXC=Could not create DOM DocumentBuilder.
-NO_OPERATION=No such operation: {0}
+XML_STREAM_EXC=Error reading XMLStreamReader.
+MUST_UNDERSTAND=Can not understand QNames: {0}
+PARSER_EXC=Could not create DOM DocumentBuilder.
+NO_OPERATION=No such operation: {0}
ATTACHMENT_IO=Attachment IO Exception: {0}
Propchange: incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/Messages.properties
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/Messages.properties
------------------------------------------------------------------------------
svn:keywords = Rev Date
Propchange: incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/Messages.properties
------------------------------------------------------------------------------
svn:mime-type = text/plain
Propchange: incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/MultipartMessageInterceptor.java
------------------------------------------------------------------------------
svn:keywords = Rev Date
Propchange: incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/MustUnderstandInterceptor.java
------------------------------------------------------------------------------
svn:keywords = Rev Date
Propchange: incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/RPCInInterceptor.java
------------------------------------------------------------------------------
svn:keywords = Rev Date
Propchange: incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/RPCOutInterceptor.java
------------------------------------------------------------------------------
svn:keywords = Rev Date
Propchange: incubator/cxf/trunk/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/SoapConstants.java
------------------------------------------------------------------------------
svn:keywords = Rev Date