Home >> All

Page 1   2   3  

•	sample.basic.* (5)	•	sample.example.* (4)	•	sample.more.* (15)
•	samples.addr.* (4)	•	samples.attachments.* (3)	•	samples.bidbuy.* (10)
•	samples.client.* (1)	•	samples.config.* (1)	•	samples.core.* (1)
•	samples.echo.* (4)	•	samples.ejb.* (7)	•	samples.encoding.* (8)
•	samples.faults.* (4)	•	samples.filefind.* (10)	•	samples.handler.* (1)

Package Samples:

• samples.addr
• samples.filefind
• samples.config
• samples.core
• samples.attachments
• samples.bidbuy
• samples.client
• samples.echo
• samples.ejb
• samples.encoding
• samples.faults
• samples.handler
• sample.basic
• sample.example.test
• sample.example
• sample.more

Classes:

• TestRef: An example of sending an attachment via messages. The main purpose is to validate the different types of attachment references by content Id, content location both absolute and relative. Creates 5 separate attachments referenced differently by a SOAP document. Each attachment contains a string that is assembled and tested to see if if the attachments are correctly sent and referenced. Each attachment also contains a mime header indicating its position and validated on the server to see if mime headers are correctly sent with attachments. Sends the same message again however the second attachments ...
• MyListPortsWriter: This is my example of a class that writes a list of a service's ports to a file named Lst.lst. Note: because of a name clash problem, I add the suffix "Lst". I hope to remove this in a future version of this example. Details of the JavaWriter bug: JavaWriter looks to make sure a class doesn't already exist before creating a file, but not all files that we generate are .class files! This works with deploy.wsdd and undeploy.wsdd because these files just happen to begin with lowercase letters, where Java classes begin with uppercase letters. But this example shows the problem quite well. I would LIKE ...
• ValidationModel: ValidationController uses one of these to supply data for its Views, and to keep session state in. It contains a number of properties, including a simple String, a Date that will involve a String conversion when the View repopulates its model, and a property that has a validation rule that may result in a thrown Exception. This model contains a list of String validation failures that are put in red at the top of the page. Scope's default ModelManager implementation builds on the JavaBeans API, so this model object is just a normal JavaBean.
• GetQuote1: This version of the ever so popular GetQuote shows how to use the Axis client APIs with and without WSDL. The first flavor (getQuote1) will use WSDL to prefill all of the data about the remote service. The second one (getQuote2) will do it all manually. Either way the service is invoked it should produce the exact same request XML and of course same results. This sample supports the use of the standard options too (-p ...)
• JMSTest: Tests the JMS transport. To run: java org.apache.axis.utils.Admin client client_deploy.xml java org.apache.axis.utils.Admin server deploy.xml java samples.transport.FileTest IBM java samples.transport.FileTest XXX JMSTest is a simple test driver for the JMS transport. It sets up a JMS listener, then calls a delayed quote service for each of the symbols specified on the command line.
• LoginModel: LoginController uses one of these to supply data for its Views, and to keep session state in. In this case there's two String properties: username and password, and a method to validate the user. Scope's default ModelManager implementation builds on the JavaBeans API, so this model object is just a normal JavaBean.
• Hello2Model: Hello2Controller uses one of these to supply data for its Views, and to keep session state in. In this case there's just a single String field that users populate with their name. Scope's default ModelManager implementation builds on the JavaBeans API, so this model object is just a normal JavaBean.
• Hello3Model: Hello3Controller uses one of these to supply data for its Views, and to keep session state in. In this case there's just a single String field that users populate with their name. Scope's default ModelManager implementation builds on the JavaBeans API, so this model object is just a normal JavaBean.
• HelloModel: HelloController uses one of these to supply data for its Views, and to keep session state in. In this case there's just a single String field that users populate with their name. Scope's default ModelManager implementation builds on the JavaBeans API, so this model object is just a normal JavaBean.
• MenuModel: HelloController uses one of these to supply data for its Views, and to keep session state in. In this case there's just a single String field that users populate with their name. Scope's default ModelManager implementation builds on the JavaBeans API, so this model object is just a normal JavaBean.
• JSPFormModel: FormController uses one of these to supply data for its Views, and to keep session state in. In this case there's just a single String field that users populate with their name. Scope's default ModelManager implementation builds on the JavaBeans API, so this model object is just a normal JavaBean.
• FormModel: FormController uses one of these to supply data for its Views, and to keep session state in. In this case there's just a single String field that users populate with their name. Scope's default ModelManager implementation builds on the JavaBeans API, so this model object is just a normal JavaBean.
• FormModel: FormController uses one of these to supply data for its Views, and to keep session state in. In this case there's just a single String field that users populate with their name. Scope's default ModelManager implementation builds on the JavaBeans API, so this model object is just a normal JavaBean.
• GetQuote1: This version of the ever so popular GetQuote is a near-duplicate of the GetQuote1 method in samples/stock which shows how to use the AXIS client APIs with and without WSDL. This version is strictly JAX-RPC compliant. It uses no AXIS enhancements. This sample supports the use of the standard options too (-p ...)
• DynamicInvoker: This sample shows how to use Axis for completely dynamic invocations as it is completely stubless execution. It supports both doc/lit and rpc/encoded services. But this sample does not support complex types (it could if there was defined a to encode complex values as command line arguments).
• EchoTestClient: A quick-and-dirty client for the Interop echo test services as defined at http://www.xmethods.net/ilab. Defaults to the Apache endpoint, but you can point it somewhere else via the command line: EchoTestClient http://some.other.place/ DOES NOT SUPPORT DIFFERENT SOAPACTION URIS YET.
• SampleFtp: this sample test class implements following FTP actions : Expected parameters in args[] are : 1) FTP server host's name 2) FTP userId to use 3) FTP password to use 4) Local work text file name to use for test. 4) Local existing work binary file name to use for test.
• GridBagHelper: Helper for creating GridBagConstraints with convenience short methods. Fill and anchor are specified with single string containing letters 'n' (north), 'e' (east), 's' (south), 'w' (west) specifying in which direction from center span the component
• FileTest: Tests the simple File transport. To run: java org.apache.axis.utils.Admin client client_deploy.xml java org.apache.axis.utils.Admin server deploy.xml java samples.transport.FileTest IBM java samples.transport.FileTest XXX
• LoginAppController: Top-most application Controller for the Login Sample, creates a child FormController, but handles the Login process itself so that any child Controller can do logins by passing a REQUEST_LOGIN Control up the chain of command.
• echoHeaderStringHandler: This handler processes the SOAP header "echoMeString" defined in the SOAPBuilder Round2C interop tests. Essentially, you install it on both the request and response chains of your service, on the server side.
• echoHeaderStructHandler: This handler processes the SOAP header "echoMeStruct" defined in the SOAPBuilder Round2C interop tests. Essentially, you install it on both the request and response chains of your service, on the server side.
• ActivemodelModel: A version of samples.helloworld2.Hello2Model that implements ModelChangeEventSource by subclassing BasicModel and calling fireModelChange() after setters that change the model's state.
• FileSender: Just write the XML to a file called xml#.req and wait for the result in a file called xml#.res Not thread-safe - just a dummy sample to show that we can indeed use something other than HTTP as the transport.
• EchoAttachment: An example of sending an attachment via RPC. This class has a main method that beside the standard arguments allows you to specify an attachment that will be sent to a service which will then send it back.

Home | Contact Us | Privacy Policy | Terms of Service