don't know how the formating got screwed up in the previous email ...
From https://servername/axis2/services/FMDTSystemService?wsdl I get the deployed wsdl ... but I get
<service name="FMDTSystemService"> <port name="FMDTSystemPort" binding="tns:FMDTSystemService"><soap:address location="https://192.165.184.22:80/axis2/services/FMDTSystemService"/>
</port> </service> where the wsdl I built the service with has <service name="FMDTSystemService"> <port name="FMDTSystemPort" binding="tns:FMDTSystemService"><soap:address location="https://servername/axis2/services/FMDTSystem"/>
</port> </service> Jim Pickering Senior Software Engineer SRI International 4119 Broad Street, Suite 210 San Luis Obispo, CA 93401 Phone: (805) 542-9330 ext. 125 FAX: (805) 546-2444 Jim Pickering wrote:
Platform:Axis2 1.3 running under Tomcat 5.5.25 running under Apache 2.0.59 httpd ... Apache configured to handoff http/https (ports 80/443) service requests to Tomcat.From https://servername/axis2/axis2-admin/upload page I loaded my service (FMDTSystemService.aar). No problems there.From https://servername/axis2/axis2-admin/listService my service (FMDTSystemService) is listed. No problems there.From https://servername/axis2/services/FMDTSystemService?wsdl I get the deployed wsdl ... but I get<#><service name="FMDTSystemService">- <#> <port name="FMDTSystemPort" binding="tns:FMDTSystemService"> <soap:address location="https://192.165.184.22:80/axis2/services/FMDTSystemService"; /></port> </service> where the wsdl I built the service with has <#> <service name="FMDTSystemService"> <port name="FMDTSystemPort" binding="tns:FMDTSystemService"> <soap:address location="https://servername/soap/FMDTSystem"/> </port> </service> How can I prevent this from happening? Thanks. Jim Jim Pickering Senior Software Engineer SRI International 4119 Broad Street, Suite 210 San Luis Obispo, CA 93401 Phone: (805) 542-9330 ext. 125 FAX: (805) 546-2444
smime.p7s
Description: S/MIME Cryptographic Signature
