[Design of JBoss Web Services] - Re: Proposed JAX-WS Docs
by thomas.diesler@jboss.com
>From Axis
* Introduction
o What is SOAP?
o What is Axis?
o What's in this release?
o What's still to do?
* Installing Axis and Using this Guide
* Consuming Web Services with Axis
o Basics - Getting Started
o Naming Parameters
o Interoperating with "untyped" servers
* Publishing Web Services with Axis
o JWS (Java Web Service) Files - Instant Deployment
o Custom Deployment - Introducing WSDD
o Service Styles - RPC, Document, Wrapped, and Message
* XML <-> Java Data Mapping in Axis
o How your Java types map to SOAP/XML types
o Exceptions
o What Axis can send via SOAP with restricted Interoperability
o What Axis can not send via SOAP
o Encoding Your Beans - the BeanSerializer
o When Beans Are Not Enough - Custom Serialization
* Using WSDL with Axis
o ?WSDL: Obtaining WSDL for deployed services
o WSDL2Java: Building stubs, skeletons, and data types from WSDL
o Java2WSDL: Building WSDL from Java
* Published Axis Interfaces
* Newbie Tips: Finding Your Way Around
o Places to Look for Clues
o Classes to Know
* Appendix : Using the Axis TCP Monitor (tcpmon)
* Appendix: Using the SOAP Monitor
* Glossary
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993952#3993952
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993952
19 years, 3 months
[Design of JBoss Web Services] - Re: Proposed JAX-WS Docs
by thomas.diesler@jboss.com
>From XFire
* Overview (READ FIRST!)
* Guides
o Quick Start - Your first service with XFire using services.xml
o Dependency Guide - This is so confusing... What jars do I need and why?!?!
o Client and Server Stub Generation from WSDL - How to make a web service client
o Embedded XFire HTTP Service - How to use the XFire API to create a Service, Client, and embedded HTTP server.
o JSR 181 Service - How to write a service using annotations
o JAXB 2.0 - Writing a schema and service with JAXB 2.0
o JMS Transport - Impress your friends by doing SOAP over JMS
o Service Router - How to route messages to various Services with one endpoint
o Maven Guide - How do I set up Maven to use XFire Jars?
o Parsing a SOAP Message without Web Services - How to leverage all the power of XFire without using traditional Web Services
o Eclipse Plugin - Using the eclipse plugin to generate services and clients from WSDL.
* XML Configuration
o services.xml Reference
* Using the XFire API
o The ServiceFactory
o Servlet Setup
o Embedding XFire
o Invokers
o The MessageContext and Messages
o Processing Pipeline
o Writing Handlers
o Fault and Exception Handling
o Logging
* Bindings
o Aegis Binding: XFire's default POJO binding
+ Inheritance
+ Aegis Java 5 Annotations
+ Interfaces
+ Collections
+ Custom Types
+ Aegis Internals
o Castor
o XMLBeans Binding
o JAXB 2.0
o JAXB 1.1
o JiBX
o Message Binding
* JSR 181 Annotations
* Client API
o Dynamic Client
* Client and Server Stub Generation from WSDL
* Authentication
* Container Support
o Spring
+ Spring QuickStart Guide
+ Spring, XBean, Servlets and more
+ Spring Remoting
+ Advanced Configuration
o Plexus
o Loom
o PicoContainer
o Yan
* MTOM Support
* JAX-WS
* JBI Integration
* WS-Addressing
* WS-Security
* GZip Support
* Transports
o Transport and Channel API
o HTTP Transport
o JMS Transport
o Local Transport
o XMPP Transport
* Application Server Support
* Best Practices
o Web Service Design
o Versioning
o Testing Your XFire Services
* Developers
o Architecture
o Source Repository
o Building from sources
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993951#3993951
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993951
19 years, 3 months
[Design of JBoss Web Services] - Re: Proposed JAX-WS Docs
by thomas.diesler@jboss.com
>From the SunRI
# JAX-WS 2.0 User's Guide
1. Contents
2. 1. Introduction
1. 1.1 What's new in JAX-WS 2.0 ea3
1. 1.1.1 new JAXWS 2.0 API
2. 1.1.2 Fully Dynamic Runtime
3. 1.1.3 MTOM & Swaref
4. 1.1.4 SOAP 1.2
2. 2.1 Features introduced in this release
1. 2.1.1 JAXB 2.0
2. 2.1.2 Annotations
3. 2.1.3 Customizations
4. 2.1.4 Improved Handler Framework
5. 2.1.5 Provider
6. 2.1.6 Dispatch
7. 2.1.7 Asynchronous Client Operations
3. 3. Programming Model
1. 3.1 Server
1. 3.1.1 Starting from Java
2. 3.1.1.1 Generate Portable Artifacts
3. 3.1.1.2 Create a WAR file to deploy
4. 3.1.2 Starting from a WSDL File
5. 3.1.2.1 Generate a Service Endpoint Interface
6. 3.1.2.2 Implement the Service Endpoint Interface
7. 3.1.2.3 Create a WAR
8. 3.1.2.4 J2SE Endpoints
2. 3.2 Client
1. 3.2.1 Dynamic Proxy
2. 3.2.1.1 Generate Client Artifacts
3. 3.2.2 Dispatch
4. 4. Useful Information
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993948#3993948
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993948
19 years, 3 months
[Design of JBoss Portal] - Federated search
by thomas.heute@jboss.com
Working on the federated search, i am wondering how to present the result to the end user.
I was thinking of 2 ways to do a search
- a very simple input field with no other parameter that could sit on top of a portal like there is here on jboss.com
- a search portlet for more complex search (Filter on portlets, specify dates and so on).
To present the results, this is more tricky, what i was thinking is to dynamically add a "Search results" page on the personal dashboard if there is none. Then add a "search results portlet instance" for each search request with the abality for the user to kill a portlet instance and to kill the page.
Once the search results are presented, we need to provide some way to let the user go and see an element of the search result. Providing a link to something in the CMS is trivial but we don't really have a way to provide a link to a portlet.
One thing i can think of right now, is to let the federated search give a Portlet instance reference and render parameters on each result so that we can display that portlet instance on a new temporary page. (There are several problems to that, the portlet instance could be already destroyed for example and we don't have the notion of temporary page)
I could miss the obvious though or anything better, feedback is appreciated from everybody, but please stay on the topic or open another forum thread
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993945#3993945
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993945
19 years, 3 months