Also,
I am getting these errors:
java.io.FileNotFoundException: C:\dev\espace-ws\WEB-INF\log4j.properties
20 Mar 2007 09:31:37,297 [main] FATAL
org.regenstrief.database.InitializationServlet - (Thread[main,5,main])
Error in servlet init():
java.lang.Exception: Error reading properties file 'database.properties'
I think it might be best to maybe give me the whole war, I hope that it
will bypass these errors. Unless, I can still use the service without
the database properties set and a proper JDBC connection.
If all this is required, then can you try to get a simple case working
(or not working) with the MTOM stuff and send me that aar?
Roshan Punnoose
Phone: 301-497-6039
-----Original Message-----
From: Tammy Dugan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 20, 2007 9:43 AM
To: axis-user@ws.apache.org
Subject: Re: [Axi2] Can't get MTOM attachments by reference to work
Attached is the .aar file in a zip folder.
Tammy
Punnoose, Roshan wrote:
Tammy,
Yeah, I just tested with your axis2.xml and it works with my
implementation, though I am using a nightly version of Axis2. There is
something else going on. I would have to see your AAR file to be sure.
Roshan Punnoose
Phone: 301-497-6039
-----Original Message-----
From: Paul Fremantle [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 20, 2007 8:07 AM
To: axis-user@ws.apache.org
Subject: Re: [Axi2] Can't get MTOM attachments by reference to work
Tammy
The reason you are getting mime headers even when you don't have an
attachment is that once Axis2 is in MTOM mode then it does a MIME
header anyway. So that's a good sign. I'm really confused by what is
going on because you seem to be doing everything correctly. Is there
any chance you can post an AAR and a client?
By the way you shouldnt need to write a URLConnection client like that
- you can use your ordinary client and see what's happening with
TCPMON.
Paul
On 3/20/07, Tammy Dugan <[EMAIL PROTECTED]> wrote:
I really need to get this problem solved fairly quickly so I would
appreciate any help I can get.
Thanks,
Tammy
Tammy Dugan wrote:
I am running the axis2 1.1.1 release since I can't get the nightly
build to run. I am using Tomcat 4.1. Even without attachments, the
message I am getting is weird. I am getting the following message
back:
--MIMEBoundaryurn_uuid_695DC8E94169A52D5E1174330901578
content-type: application/xop+xml; charset=UTF-8; type="text/xml";
content-transfer-encoding: binary
content-id: <0.urn:uuid:[EMAIL PROTECTED]>
<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";><soapenv:Heade
r
/><soapenv:Body><returnStatistics
xmlns:tns="http://queryposer.regenstrief.org";
xmlns:r="http://spin.regenstrief.org/query";><breakdownVariable
name="cmore patient gender" ordinal="1"><variableComponent r:id="A"
r:name="Gender (value)">value</variableComponent><condition
name="cmore patient gender"><all><variable code="21840-4"
name="cmore
patient gender" r:displayName="cmore patient gender (21840-4)"
r:objectType="REGISTRATION" r:valueType="CE" system="LN"
/></all></condition><breakdown max="25"><cutpoint name="Missing
value"
ordinal="1" /><cutpoint name="female (F)" ordinal="2"><ccode
code="F"
name="female" r:displayName="female (F)" system="SEX"
/></cutpoint><cutpoint name="male (M)" ordinal="3"><ccode code="M"
name="male" r:displayName="male (M)" system="SEX"
/></cutpoint><cutpoint name="transgender (T)" ordinal="4"><ccode
code="T" name="transgender" r:displayName="transgender (T)"
system="SEX" /></cutpoint><cutpoint name="unknown (U)"
ordinal="5"><ccode code="U" name="unknown" r:displayName="unknown
(U)"
system="SEX"
/></cutpoint></breakdown></breakdownVariable><cells><count>548</count><r
:count_discarded>0</r:count_discarded><cell><count>1</count><breakdownVa
riable
cutpoint="2" ordinal="1"
/></cell><cell><count>543</count><breakdownVariable cutpoint="3"
ordinal="1" /></cell><cell><count>4</count><breakdownVariable
cutpoint="5" ordinal="1"
/></cell></cells></returnStatistics></soapenv:Body></soapenv:Envelope>
Why am I getting the MIMEBoundary junk at the top when I am not even
sending an attachment. There shouldn't be a mime boundary at all,
right?
Here is what the response looks like with an attachment added:
--MIMEBoundaryurn_uuid_D1DACC47209741A7451174331364650
content-type: application/xop+xml; charset=UTF-8; type="text/xml";
content-transfer-encoding: binary
content-id: <0.urn:uuid:[EMAIL PROTECTED]>
<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";><soapenv:Heade
r
/><soapenv:Body><Testing
xmlns:tns="http://queryposer.regenstrief.org";><returnStatistics
xmlns:r="http://spin.regenstrief.org/query";><breakdownVariable
name="cmore patient gender" ordinal="1"><variableComponent r:id="A"
r:name="Gender (value)">value</variableComponent><condition
name="cmore patient gender"><all><variable code="21840-4"
name="cmore
patient gender" r:displayName="cmore patient gender (21840-4)"
r:objectType="REGISTRATION" r:valueType="CE" system="LN"
/></all></condition><breakdown max="25"><cutpoint name="Missing
value"
ordinal="1" /><cutpoint name="female (F)" ordinal="2"><ccode
code="F"
name="female" r:displayName="female (F)" system="SEX"
/></cutpoint><cutpoint name="male (M)" ordinal="3"><ccode code="M"
name="male" r:displayName="male (M)" system="SEX"
/></cutpoint><cutpoint name="transgender (T)" ordinal="4"><ccode
code="T" name="transgender" r:displayName="transgender (T)"
system="SEX" /></cutpoint><cutpoint name="unknown (U)"
ordinal="5"><ccode code="U" name="unknown" r:displayName="unknown
(U)"
system="SEX"
/></cutpoint></breakdown></breakdownVariable><cells><count>548</count><r
:count_discarded>0</r:count_discarded><cell><count>1</count><breakdownVa
riable
cutpoint="2" ordinal="1"
/></cell><cell><count>543</count><breakdownVariable cutpoint="3"
ordinal="1" /></cell><cell><count>4</count><breakdownVariable
cutpoint="5" ordinal="1"
/></cell></cells></returnStatistics><pdf>JVBERi0xLjMKJcfsj6IKNiAwIG9iago
8PC9MZW5ndGggNyAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4</pdf></Testing></soapen
v:Body></soapenv:Envelope>
There isn't even a separate mime boundary for the attachment.
Tammy
Punnoose, Roshan wrote:
That is weird, because I have the same configuration and mine is
working
at the moment.
Can you send back your axis2.xml?
And, what server are you running again?
Thanks!
Roshan Punnoose
Phone: 301-497-6039
-----Original Message-----
From: Tammy Dugan [mailto:[EMAIL PROTECTED] Sent: Monday,
March
19, 2007 10:48 AM
To: axis-user@ws.apache.org
Subject: Re: [Axi2] Can't get MTOM attachments by reference to work
Yes, there are MIME boundaries but the message looks something like
this:
--MIMEBoundaryurn_uuid_72EC4B349174A8C3141174305830430
content-type: application/xop+xml; charset=UTF-8; type="text/xml";
content-transfer-encoding: binary
content-id: <0.urn:uuid:[EMAIL PROTECTED]>
<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";><soapenv:Heade
r /><soapenv:Body>
<Testing
xmlns:tns="http://queryposer.regenstrief.org";><returnStatistics
xmlns:r="http://spin.regenstrief.org/query";><breakdownVariable
name="cmore patient gender" ordinal="1"><variableComponent r:id="A"
r:name="Gender (value)">value</variableComponent><condition
name="cmore patient gender"><all><variable code="21840-4"
name="cmore
patient gender" r:displayName="cmore patient gender (21840-4)"
r:objectType="REGISTRATION" r:valueType="CE" system="LN"
/></all></condition><breakdown max="25"><cutpoint name="Missing
value" ordinal="1" /><cutpoint name="female (F)" ordinal="2"><ccode
code="F" name="female" r:displayName="female (F)" system="SEX"
/></cutpoint><cutpoint name="male (M)" ordinal="3"><ccode code="M"
name="male" r:displayName="male (M)" system="SEX"
/></cutpoint><cutpoint
name="transgender (T)" ordinal="4"><ccode code="T"
name="transgender"
r:displayName="transgender (T)" system="SEX" /></cutpoint><cutpoint
name="unknown (U)" ordinal="5"><ccode code="U" name="unknown"
r:displayName="unknown (U)" system="SEX"
/></cutpoint></breakdown></breakdownVariable><cells><count>548</count><r
:count_discarded>0</r:count_discarded><cell><count>1</count><breakdownVa
riable cutpoint="2" ordinal="1"
/></cell><cell><count>543</count><breakdownVariable cutpoint="3"
ordinal="1" /></cell><cell><count>4</count><breakdownVariable
cutpoint="5" ordinal="1" /></cell></cells></returnStatistics>
<pdf>JVBERi0xLjMKJcfsj6IKNiAwIG9iago8PC9MZW5ndGggNyAwIFIvRmlsdGVyIC9GbGF
0ZURlY29kZT4+CnN0cmVhbQp4nL1U61dTRxA3QiNcepQitKVCXa1atGaz7we0jYIioFRyvRb
FW
1oKQYEklgBFKvbhs/avdnY3N8Zy+qFfPDnJZl6/nZnfzG4igiki7tM8l2vRZlSMBbq/FW0i6
k3ZsVxD40lUvIwoSlajLKLg/lBp4Vcrji1KatHIocO5zo4Pckfy3V1pPdeT7/4wbXQcO/pR<
/pdf>
</Testing></soapenv:Body></soapenv:Envelope>
--MIMEBoundaryurn_uuid_72EC4B349174A8C3141174305830430--
The mime boundaries are in there but the binary data is being
base64
encoded and stored in the actually body of the xml instead of an
include
tag inside the xml pointing to the binary data stored outside.
Tammy
Punnoose, Roshan wrote:
Are the MIME boundaries present? That is one way of telling
whether or
not MTOM is being used.
Something like:
--MIME...---
all the data
----MIME...---
If not, then MTOM is not being used. Then you can up the root
logger
to DEBUG and see what it actually is, and where the axis conf is
coming
from. (I believe)
Roshan
________________________________
From: Tammy Dugan [mailto:[EMAIL PROTECTED]
Sent: Fri 3/16/2007 1:26 PM
To: axis-user@ws.apache.org
Subject: [Axi2] Can't get MTOM attachments by reference to work
I use the following code to add attachments to an outgoing soap
message:
//add an attachment if needed
if (this.attachmentContent != null)
{
for (int i = 0; i < this.attachmentContent.length;
i++)
{
DataSource ds = new
ByteArrayDataSource(this.attachmentContent[i].toByteArray(),
this.attachmentContentType[i]);
OMText data = fac.createOMText(new
DataHandler(ds),
true);
OMElement parent =
fac.createOMElement("pdf",null);
parent.addChild(data);
resp.addChild(parent); ;
}
}
I have the following test client that sends and receives a message
from
a URLConnection:
charCnt = 0;
in = new BufferedReader( new InputStreamReader(
conn.getInputStream() ) );
out = new BufferedWriter( new FileWriter( OUTPUT_FILE
) );
while ( (response = in.readLine()) != null)
{
out.write( response );
out.write( "\n" );
charCnt += response.length();
}
in.close();
out.flush();
out.close();
When I look at the response output, the attachments in base64
encoded
in
the body of the xml. I have <parameter name="enableMTOM"
locked="false">true</parameter> in axis2.xml and am not overriding
it
in
the services.xml file so why isn't the attachment being sent by
reference? Here is my services.xml file entry for the service I am
testing:
<service name="QueryStatisticsReturn" scope="soapsession">
<parameter
name="ServiceClass">org.regenstrief.queryposer.QueryStatisticsReturnServ
let</parameter>
<operation name="queryStatisticsReturn">
<messageReceiver
class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>
</operation>
</service>
Thanks,
Tammy Dugan
--
Tammy Dugan
Computer Programmer
Regenstrief Institute, Inc.
1050 Wishard Blvd., RG5
Indianapolis, IN 46202
(317) 630 - 7346
Confidentiality Notice: The contents of this message and any files
transmitted with it may contain confidential and/or privileged
information and are intended solely for the use of the named
addressee(s). Additionally, the information contained herein may
have
been disclosed to you from medical records with confidentiality
protected by federal and state laws. Federal regulations and State
laws
prohibit you from making further disclosure of such information
without
the specific written consent of the person to whom the information
pertains or as otherwise permitted by such regulations. A general
authorization for the release of medical or other information is
not
sufficient for this purpose.
If you have received this message in error, please notify the
sender
by return e-mail and delete the original message. Any retention,
disclosure, copying, distribution or use of this information by
anyone
other than the intended recipient is strictly prohibited.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
------------------------------------------------------------------------
<!--
/*
* Copyright 2001-2004 The Apache Software Foundation.
*
* 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.
*/
-->
<axisconfig name="AxisJava2.0">
<!-- ================================================= -->
<!-- Parameters -->
<!-- ================================================= -->
<parameter name="hotdeployment" locked="false">true</parameter>
<parameter name="hotupdate" locked="false">false</parameter>
<parameter name="enableMTOM" locked="false">true</parameter>
<parameter name="enableSwA" locked="false">false</parameter>
<!--Uncomment if you want to enable file caching for attachments
-->
<!--parameter name="cacheAttachments"
locked="false">true</parameter>
<parameter name="attachmentDIR" locked="false"></parameter>
<parameter name="sizeThreshold"
locked="false">4000</parameter-->
<!--This will give out the timout of the configuration contexts,
in seconds-->
<parameter name="ConfigContextTimeoutInterval"
locked="false">30</parameter>
<!--During a fault, stacktrace can be sent with the fault
message. The following flag will control -->
<!--that behaviour.-->
<parameter name="sendStacktraceDetailsWithFaults"
locked="false">false</parameter>
<!--If there aren't any information available to find out the
fault reason, we set the message of the expcetion-->
<!--as the faultreason/Reason. But when a fault is thrown from a
service or some where, it will be -->
<!--wrapped by different levels. Due to this the initial
exception message can be lost. If this flag-->
<!--is set then, Axis2 tries to get the first exception and set
its message as the faultreason/Reason.-->
<parameter name="DrillDownToRootCauseForFaultReason"
locked="false">false</parameter>
<parameter name="userName" locked="false">admin</parameter>
<parameter name="password" locked="false">axis2</parameter>
<!--To override repository/services you need to uncomment
following parameter and value SHOULD be absolute file path.-->
<!--<parameter name="ServicesDirectory"
locked="false">service</parameter>-->
<!--To override repository/modules you need to uncomment
following parameter and value SHOULD be absolute file path-->
<!--<parameter name="ModulesDirectory"
locked="false">modules</parameter>-->
<!--Following params will set the proper context paths for
invocations. All the endpoints will have a commons context-->
<!--root which can configured using the following contextRoot
parameter-->
<!--<parameter name="contextRoot"
locked="false">axis2</parameter>-->
<!--Our HTTP endpoints can handle both REST and SOAP. Following
parameters can be used to distingiush those endpoints-->
<!--In case of a servlet, if you change this you have to
manually change the settings of your servlet container to map this -->
<!--context path to proper Axis2 servlets-->
<!--<parameter name="servicePath"
locked="false">services</parameter>-->
<!--<parameter name="restPath"
locked="false">rest</parameter>-->
<!--Set the flag to true if you want to enable transport level
session mangment-->
<parameter name="manageTransportSession"
locked="false">false</parameter>
<!--Following two parameters will be used to handle REST in
Axis2. The default settings will make Axis2 to have two-->
<!--different endpoints, one for REST (AxisRESTServlet) one for
SOAP message handling (AxisServlet). But following-->
<!--parameters help to tweak the message handling of two main
servlets. -->
<!-- If the enableRESTInAxis2MainServlet is true, then
Axis2MainServlet will handle both SOAP and REST messages -->
<parameter name="enableRESTInAxis2MainServlet"
locked="true">false</parameter>
<!-- Following parameter will completely disable REST handling
in both the servlets-->
<parameter name="disableREST" locked="true">false</parameter>
<!-- This will disable the separate servlet we have for REST
handling. -->
<parameter name="disableSeparateEndpointForREST"
locked="true">false</parameter>
<!-- If you have a frontend host which exposes this webservice
using a different public URL -->
<!-- use this parameter to override autodetected url -->
<!--<parameter name="httpFrontendHostUrl"
locked="false">https://someotherhost/context</parameter>-->
<!-- The way of adding listener to the system-->
<!-- <listener class="org.apache.axis2.ObserverIMPL">-->
<!-- <parameter name="RSS_URL"
locked="false">http://127.0.0.1/rss</parameter>-->
<!-- </listener>-->
<!-- ================================================= -->
<!-- Message Receivers -->
<!-- ================================================= -->
<!--This is the Deafult Message Receiver for the system , if you
want to have MessageReceivers for -->
<!--all the other MEP implement it and add the correct entry to
here , so that you can refer from-->
<!--any operation -->
<!--Note : You can ovride this for particular service by adding
the same element with your requirement-->
<messageReceivers>
<messageReceiver
mep="http://www.w3.org/2004/08/wsdl/in-only";
class="org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver"/>
<messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-out";
class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>
</messageReceivers>
<!-- ================================================= -->
<!-- Transport Ins -->
<!-- ================================================= -->
<transportReceiver name="http"
class="org.apache.axis2.transport.http.SimpleHTTPServer">
<parameter name="port" locked="false">8080</parameter>
<!-- Here is the complete list of supported parameters (see
example settings further below):
port: the port to listen on (default 6060)
hostname: if non-null, url prefix used in reply-to
endpoint references (default null)
originServer: value of http Server header in outgoing
messages (default
"Simple-Server/1.1")
requestTimeout: value in millis of time that requests
can wait for data (default 20000)
requestTcpNoDelay: true to maximize performance and
minimize latency (default true)
false to minimize bandwidth
consumption by combining segments
requestCoreThreadPoolSize: number of threads available
for request processing (unless queue fills up) (default 25)
requestMaxThreadPoolSize: number of threads available
for request processing if queue fills us (default 150)
note that default queue never
fills up: see HttpFactory
threadKeepAliveTime: time to keep threads in excess of
core size alive while inactive (default 180)
note that no such threads can
exist with default unbounded request queue
threadKeepAliveTimeUnit: TimeUnit of value in
threadKeepAliveTime (default SECONDS) (default
SECONDS)
-->
<!-- <parameter name="hostname"
locked="false">http://www.myApp.com/ws</parameter> -->
<!-- <parameter name="originServer"
locked="false">My-Server/1.1</parameter> -->
<!-- <parameter name="requestTimeout"
locked="false">10000</parameter> -->
<!-- <parameter name="requestTcpNoDelay"
locked="false">false</parameter> -->
<!-- <parameter name="requestCoreThreadPoolSize"
locked="false">50</parameter> -->
<!-- <parameter name="RequestMaxThreadPoolSize"
locked="false">100</parameter> -->
<!-- <parameter name="threadKeepAliveTime"
locked="false">240000</parameter> -->
<!-- <parameter name="threadKeepAliveTimeUnit"
locked="false">MILLISECONDS</parameter> -->
</transportReceiver>
<!--Uncomment this and configure as appropriate for JMS
transport support, after setting up your JMS environment (e.g.
ActiveMQ)
<transportReceiver name="jms"
class="org.apache.axis2.transport.jms.JMSListener">
<parameter name="myTopicConnectionFactory" locked="false">
<parameter name="java.naming.factory.initial"
locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory</p
arameter>
<parameter name="java.naming.provider.url"
locked="false">tcp://localhost:61616</parameter>
<parameter
name="transport.jms.ConnectionFactoryJNDIName"
locked="false">TopicConnectionFactory</parameter>
</parameter>
<parameter name="myQueueConnectionFactory" locked="false">
<parameter name="java.naming.factory.initial"
locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory</p
arameter>
<parameter name="java.naming.provider.url"
locked="false">tcp://localhost:61616</parameter>
<parameter
name="transport.jms.ConnectionFactoryJNDIName"
locked="false">QueueConnectionFactory</parameter>
</parameter>
<parameter name="default" locked="false">
<parameter name="java.naming.factory.initial"
locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory</p
arameter>
<parameter name="java.naming.provider.url"
locked="false">tcp://localhost:61616</parameter>
<parameter
name="transport.jms.ConnectionFactoryJNDIName"
locked="false">QueueConnectionFactory</parameter>
</parameter>
</transportReceiver>-->
<!--Uncomment if you want to have SMTP transport support-->
<!--<transportReceiver name="mail"
class="org.apache.axis2.transport.mail.SimpleMailListener">-->
<!--<parameter name="transport.mail.pop3.host"
locked="false">127.0.0.1</parameter>-->
<!--<parameter name="transport.mail.pop3.user"
locked="false">axis2</parameter>-->
<!--<parameter name="transport.mail.pop3.password"
locked="false">axis2</parameter>-->
<!--<parameter name="transport.mail.pop3.port"
locked="false">110</parameter>-->
<!--<parameter name="transport.mail.replyToAddress"
locked="false">[EMAIL PROTECTED]</parameter>-->
<!--</transportReceiver>-->
<!--Uncomment if you want to have TCP transport support-->
<!--transportReceiver name="tcp"
class="org.apache.axis2.transport.tcp.TCPServer">
<parameter name="port" locked="false">6060</parameter-->>
<!--If you want to give your own host address for EPR
generation-->
<!--uncommet following paramter , and set as you
required.-->
<!--<parameter name="hostname"
locked="false">tcp://myApp.com/ws</parameter>-->
<!-- /transportReceiver -->
<!-- ================================================= -->
<!-- Transport Outs -->
<!-- ================================================= -->
<transportSender name="tcp"
class="org.apache.axis2.transport.tcp.TCPTransportSender"/>
<transportSender name="local"
class="org.apache.axis2.transport.local.LocalTransportSender"/>
<transportSender name="http"
class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
<parameter name="PROTOCOL"
locked="false">HTTP/1.1</parameter>
<parameter name="Transfer-Encoding"
locked="false">chunked</parameter>
</transportSender>
<transportSender name="https"
class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
<parameter name="PROTOCOL"
locked="false">HTTP/1.1</parameter>
<parameter name="Transfer-Encoding"
locked="false">chunked</parameter>
</transportSender>
<!--Uncomment this and configure as appropriate for JMS
transport support, after setting up your JMS environment (e.g.
ActiveMQ)
<transportSender name="jms"
class="org.apache.axis2.transport.jms.JMSSender"/>
-->
<!-- Uncomment this one with the appropriate papameters to
enable the SMTP transport Receiver
<transportSender name="mailto"
class="org.apache.axis2.transport.mail.MailTransportSender">
<parameter name="transport.mail.smtp.host"
locked="false">127.0.0.1</parameter>
<parameter name="transport.mail.smtp.user"
locked="false">axis2</parameter>
<parameter name="transport.mail.smtp.password"
locked="false">axis2</parameter>
<parameter name="transport.mail.smtp.port"
locked="false">25</parameter>
</transportSender>
-->
<!-- ================================================= -->
<!-- Global Modules -->
<!-- ================================================= -->
<!-- Comment this to disable Addressing -->
<module ref="addressing"/>
<!--Configuring module , providing parameters for modules
whether they refer or not-->
<!--<moduleConfig name="addressing">-->
<!--<parameter name="addressingPara"
locked="false">N/A</parameter>-->
<!--</moduleConfig>-->
<!-- ================================================= -->
<!-- Phases -->
<!-- ================================================= -->
<phaseOrder type="InFlow">
<!-- System pre defined phases -->
<phase name="Transport">
<handler name="RequestURIBasedDispatcher"
class="org.apache.axis2.engine.RequestURIBasedDispatcher">
<order phase="Transport"/>
</handler>
<handler name="SOAPActionBasedDispatcher"
class="org.apache.axis2.engine.SOAPActionBasedDispatcher">
<order phase="Transport"/>
</handler>
</phase>
<phase name="Security"/>
<phase name="PreDispatch"/>
<phase name="Dispatch"
class="org.apache.axis2.engine.DispatchPhase">
<handler name="AddressingBasedDispatcher"
class="org.apache.axis2.engine.AddressingBasedDispatcher">
<order phase="Dispatch"/>
</handler>
<handler name="SOAPMessageBodyBasedDispatcher"
class="org.apache.axis2.engine.SOAPMessageBodyBasedDispatcher">
<order phase="Dispatch"/>
</handler>
<handler name="InstanceDispatcher"
class="org.apache.axis2.engine.InstanceDispatcher">
<order phase="Dispatch"/>
</handler>
</phase>
<!-- System pre defined phases -->
<!-- After Postdispatch phase module author or or service
author can add any phase he want -->
<phase name="OperationInPhase"/>
<phase name="soapmonitorPhase"/>
</phaseOrder>
<phaseOrder type="OutFlow">
<!-- user can add his own phases to this area -->
<phase name="soapmonitorPhase"/>
<phase name="OperationOutPhase"/>
<!--system predefined phase-->
<!--these phase will run irrespective of the service-->
<phase name="PolicyDetermination"/>
<phase name="MessageOut"/>
<phase name="Security"/>
</phaseOrder>
<phaseOrder type="InFaultFlow">
<phase name="PreDispatch"/>
<phase name="Dispatch"
class="org.apache.axis2.engine.DispatchPhase">
<handler name="RequestURIBasedDispatcher"
class="org.apache.axis2.engine.RequestURIBasedDispatcher">
<order phase="Dispatch"/>
</handler>
<handler name="SOAPActionBasedDispatcher"
class="org.apache.axis2.engine.SOAPActionBasedDispatcher">
<order phase="Dispatch"/>
</handler>
<handler name="AddressingBasedDispatcher"
class="org.apache.axis2.engine.AddressingBasedDispatcher">
<order phase="Dispatch"/>
</handler>
<handler name="SOAPMessageBodyBasedDispatcher"
class="org.apache.axis2.engine.SOAPMessageBodyBasedDispatcher">
<order phase="Dispatch"/>
</handler>
<handler name="InstanceDispatcher"
class="org.apache.axis2.engine.InstanceDispatcher">
<order phase="PostDispatch"/>
</handler>
</phase>
<!-- user can add his own phases to this area -->
<phase name="OperationInFaultPhase"/>
<phase name="soapmonitorPhase"/>
</phaseOrder>
<phaseOrder type="OutFaultFlow">
<!-- user can add his own phases to this area -->
<phase name="soapmonitorPhase"/>
<phase name="OperationOutFaultPhase"/>
<phase name="PolicyDetermination"/>
<phase name="MessageOut"/>
</phaseOrder>
</axisconfig>
------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Tammy Dugan
Computer Programmer
Regenstrief Institute, Inc.
1050 Wishard Blvd., RG5
Indianapolis, IN 46202
(317) 630 - 7346
Confidentiality Notice: The contents of this message and any files
transmitted with it may contain confidential and/or privileged
information and are intended solely for the use of the named
addressee(s). Additionally, the information contained herein may have
been disclosed to you from medical records with confidentiality
protected by federal and state laws. Federal regulations and State
laws
prohibit you from making further disclosure of such information
without
the specific written consent of the person to whom the information
pertains or as otherwise permitted by such regulations. A general
authorization for the release of medical or other information is not
sufficient for this purpose.
If you have received this message in error, please notify the sender
by return e-mail and delete the original message. Any retention,
disclosure, copying, distribution or use of this information by anyone
other than the intended recipient is strictly prohibited.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
