anonymous wrote : | I have looked at all the logs I am aware of and have not located the problem. I've also attempted to install AXIS as a WAR and implement it that way after googling for about two days. Neither solution produced the WSDL. The part that is driving me nuts is that I got AXIS working with TOMCAT properly. |
Ok, so apparently I messed my classlibs up pretty good. Got them fixed and my WSDL is being properly generated. I do have another problem however... The WSDL that is generated will not work for remote endpoints... It is generating the Port info with the hostname, not FQDN which makes it impossible just to create a quick client based on the WSDL. The generated parts look like: | ... | <service name="FortuneService"> | <port binding="tns:FortuneBinding" name="FortunePort"> | <soap:address location="http://aku:8080/Fortune/Fortune"/> | </port> | </service> | ... | And should look like: | ... | <service name="FortuneService"> | <port binding="tns:FortuneBinding" name="FortunePort"> | <soap:address location="http://www.prestoncentral.com/Fortune/Fortune"/> | </port> | </service> | ... | How can I specify or force the use of the a different hostname and port? I'm using this under Apache, with the JK connector, which is working properly. Thanks! Joshua Preston. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3908042#3908042 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3908042 ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
