Problem with Axis RC1&2: Validation fails due to NoClassDefFoundError: org/w3c/dom/DOMErrorHandler, eventhough xercesImpl.jar is in webapps/axis-rc1/WEB-INF/lib

See and (why do those messages have no thread/list navigation links?).

NumberFormatException

I am currently trying to build a server specifically for Axis, with a few extra features, in order to provide something of a complete Java web services solution (see www.lombok.org.uk for details). I am, however, stuck in that every time I try to access a service, including the AdminService at de

RE: Handling of server config from EngineConfigurationFactoryServlet

Title: RE: Handling of server config from EngineConfigurationFactoryServlet I am seeing another problem with Weblogic 6.1 and Axis 1.0 RC1. I wonder if it is related to the one described in this thread. When I invoke AdminClient to deploy a WSDD file, it prints the following error message:   

DO NOT REPLY [Bug 13160] New: - samples/userguide/**/*.java are not built

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

cvs commit: xml-axis/java/src/org/apache/axis/deployment/wsdd WSDDDeployableItem.java WSDDDeployment.java

rsitze 2002/09/30 14:38:49 Modified:java/src/org/apache/axis/deployment/wsdd WSDDDeployableItem.java WSDDDeployment.java Log: Make non-public methods visible to derived classes as protected methods. Revision ChangesPath 1.47 +5 -5 xml-

Re: j2ee.jar && cvs commit: xml-axis/java/src/org/apache/axis/configuration EngineConfigurationFactoryFinder.java

yes. compiled fine. Am running all-tests now. Will holler if something's broken. Thanks, dims --- Richard Sitze <[EMAIL PROTECTED]> wrote: > Does that mean it still works (without j2ee.jar in classpath) after I > dropped that code? > > > *** > Richard A

Re: j2ee.jar && cvs commit: xml-axis/java/src/org/apache/axis/configurationEngineConfigurationFactoryFinder.java

Does that mean it still works (without j2ee.jar in classpath) after I dropped that code? *** Richard A. Sitze IBM WebSphere WebServices Development Davanum Srinivas <[EMAIL PROTECTED]> 09/30/2002 03:46 PM Please respond to axis-dev To: [

Re: rc2

Sam will have to rule with an iron-fist :) -- dims --- James M Snell <[EMAIL PROTECTED]> wrote: > > So, what's the number of new features and build-breaking > "enhancements" targeted for this release candidate? > > > Seriously... after the whirlwind that occurred over the past few week

rc2

So, what's the number of new features and build-breaking "enhancements" targeted for this release candidate? Seriously... after the whirlwind that occurred over the past few weeks, is this code really going to remain stable until the 1.0 release? - James Snell IBM Emerging Technolo

Re: j2ee.jar && cvs commit: xml-axis/java/src/org/apache/axis/configuration EngineConfigurationFactoryFinder.java

:) Thanks Richard. --- Richard Sitze <[EMAIL PROTECTED]> wrote: > Darn it, you folks just keep making me 'do-it-right' !! :-) > And cleaner... > > Dims, I am going to submit a patch over yours, please let me know if it > works for you!! > > > *** > Ric

cvs commit: xml-axis/java/src/org/apache/axis/discovery DiscoverConstNames.java

rsitze 2002/09/30 13:45:18 Modified:java/src/org/apache/axis/configuration EngineConfigurationFactoryFinder.java Added: java/src/org/apache/axis/discovery DiscoverConstNames.java Log: Bugzilla #13149 : fix using discovery. Let discovery handle er

Re: j2ee.jar && cvs commit: xml-axis/java/src/org/apache/axis/configurationEngineConfigurationFactoryFinder.java

Darn it, you folks just keep making me 'do-it-right' !! :-) And cleaner... Dims, I am going to submit a patch over yours, please let me know if it works for you!! *** Richard A. Sitze IBM WebSphere WebServices Development [EMAIL PROTECTED] 09/30/200

soap:header support

There are a lot of nuances to supporting soap:header in AXIS. Some of the quirks that concern me are: - explicit headers are SEI parameters that are sent as headers, implicit headers are messages that aren't used by the portType. How are implicit headers implemented? Via handlers, presumabl

DO NOT REPLY [Bug 13115] - Serialization of Arraylist containing Object arrays broken.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

cvs commit: xml-axis/java/src/org/apache/axis/encoding/ser ArraySerializer.java

rineholt2002/09/30 13:05:24 Modified:java/src/org/apache/axis/encoding SerializationContext.java SerializationContextImpl.java java/src/org/apache/axis/encoding/ser ArraySerializer.java Log: Bug 13115 Revision ChangesPath 1.83

SOAP message not well formed.

With a lot of help from James Black, I can finally get server side code executed till the end of operation that returns an array of my own object Folder. However, on the client side, I got: faultString: org.xml.sax.SAXParseException: The root element is required in a we

Problem with Axis RC1&2: Validation fails due to NoClassDefFoundError: org/w3c/dom/DOMErrorHandler, eventhough xercesImpl.jar is in webapps/axis-rc1/WEB-INF/lib

See and (why do those messages have no thread/list navigation links?).

DO NOT REPLY [Bug 13154] - BeanDeser... and java.sql.Date

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

DO NOT REPLY [Bug 13154] - BeanDeser... and java.sql.Date

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

DO NOT REPLY [Bug 13154] New: - BeanDeser... and java.sql.Date

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

Announcing Axis 1.0 release candidate 2!

I'm pleased to announce release candidate 2 of Axis release 1. All unit and functional tests pass with this release. The SAAJ and JAX RPC TCK tests pass. All bugs reported as of this morning targetted for the 1.0 release are resolved in this drop. Pending feedback from people like yourselv

Re: TCPMon Audio Feedback Mod ("RPC-Synth") RFC

Audio debugging! Did you try just putting an old AM radio on top of your IMP first? :-) I use TCPMon all the time for all sorts of things. I think there's a strong case to be made to spin TCPMon out of Axis entirely, grow it into a general HTTP tool. Maybe there already is a product like this? I

RE: TCPMon Audio Feedback Mod ("RPC-Synth") RFC

Title: Message Thanks for the information. Do you want me to open and improvement in bugzilla for an immediate return when no applet is connected? -Original Message-From: Brian Price [mailto:[EMAIL PROTECTED]] Sent: Monday, September 30, 2002 2:32 PMTo: [EMAIL PROTECTED]Su

DO NOT REPLY [Bug 13149] - Client requires servlet.jar

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

cvs commit: xml-axis/java/src/org/apache/axis/configuration EngineConfigurationFactoryFinder.java

dims2002/09/30 11:33:04 Modified:java build.xml java/src/org/apache/axis/configuration EngineConfigurationFactoryFinder.java Log: - Possible Fix for Bug #13149 - Client requires servlet.jar Notes: - Richard, please feel free to o

RE: TCPMon Audio Feedback Mod ("RPC-Synth") RFC

The SOAP Monitor is not something you would probably want in a production environment (because it does have some performace impact).  The current (initial) implementation of the SOAP Monitor handler does two tasks for every message (regardless of whether an applet is connected).  First, it assigns

RE: TCPMon Audio Feedback Mod ("RPC-Synth") RFC

Just a little side question on the SOAPMonitor. Any ideas on the performance impact? What does it mean if I turn this on (enable the SOAPMonitor handlers), but I just check through the web interface occasionally? What I mean is, does it make sense to have the SOAPMonitor handlers always enabled

DO NOT REPLY [Bug 13149] - Client requires servlet.jar

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

Conference call notes - 30 Sept 2002

Axis committers had a conferences call today to discuss the current status of rc2 and the 1.0 release. These are the notes from that call. RC2 status - Final problem with security tests was resolved by Dims - Kits will be released and announced today by Sam Bugs status - No currently targeted

DO NOT REPLY [Bug 13149] New: - Client requires servlet.jar

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

Re: axis requires j2ee.jar?

I never have j2ee.jar on my cpath; servlet.jar is all that seems required. maybe the test should shortcut out on null: if(param!=null && param instanceof ServletContext) { return new EngineConfigurationFactoryServlet((ServletContext)param); } else { return null; } return (param insta

DO NOT REPLY [Bug 13146] New: - On-the-fly wsdl generation incorrect for some overloaded methods

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

DO NOT REPLY [Bug 13115] - Serialization of Arraylist containing Object arrays broken.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

DO NOT REPLY [Bug 13115] - Serialization of Arraylist containing Object arrays broken.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

Re: [axis] WSDL2Java enhancements for WSIF

- Original Message - From: "Tom Jordahl" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, September 30, 2002 6:46 AM Subject: RE: [axis] WSDL2Java enhancements for WSIF > Anthony, > > I would think that a different approach would be much better: > > 1. Fix WSDL2Java so that it

DO NOT REPLY [Bug 13115] - Serialization of Arraylist containing Object arrays broken.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

DO NOT REPLY [Bug 13041] - org.apache.xml.security.c14n.CanonicalizationException

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

Re: axis requires j2ee.jar?

Could any axis people comment on this? I've just tried and it does seem to be true that you need the javax.servlet.ServletContext class from j2ee.jar when using the wsif axis provider. I guess we never noticed as all our testcases run with all the jars for everything. The problem looks like the

Conference call today

A reminder that there is a conference call today at 12:00 EDT (moved from 11:00) per the minutes of the LAST conference call. The call is being hosted by Computer Associates (Dims) and you can get the dial-in numbers on the IRC chat (on undernet, not DAL net today). Agenda - RC2 status - bug

RE: [axis] WSDL2Java enhancements for WSIF

I don't like lots of extra options on WSDL2Java just for WSIF (particularly if you'll always use those options in WSIF), so I prefer a new tool. If we go the route of a new tool, it should be under the WSIF umbrella, not AXIS. Russell Butek [EMAIL PROTECTED] "Anthony Elder" <[EMAIL PROTECT

RE: rc2 status

+1 I would like to review everyones changes and discuss. IRC or teleconference. Everything I've worked on in the last week falls in the category of regressions problems, and I believe thats true for the majority of changes from others. *** Richard A

RE: [axis] WSDL2Java enhancements for WSIF

Absolutely, fixing WSDL2Java so it doesn't abend is probably what I really meant but just described badly. Ignoring the extra WSDL should work fine. I don't know about a new API and a WSDL2WSIF command, it seems a little over kill when all WSIF needs is to suppress writing out the stub classes.

cvs commit: xml-axis/java/xmls targets.xml

rubys 2002/09/30 07:51:01 Modified:java Tag: axis1_0 buildTest.xml java/xmls Tag: axis1_0 targets.xml Log: Another security fix Revision ChangesPath No revision No revision 1.40.4.2 +2 -2 xml-

cvs commit: xml-axis/java/xmls targets.xml

dims2002/09/30 07:44:54 Modified:java buildTest.xml java/xmls targets.xml Log: - Current test harness was running ALL tests with signature signing on (when xml-security is present). This is an overkill - Switch to old behavior of running just a few tests wi

RE: BeanDeser... and java.sql.Date

Joachim, I think this is a good change. We are in the middle of closing down for 1.0 right now, can you file a bug with your suggested fix so this issue doesn't get lost? Also, it would be very nice if you could include a patch to an existing tests case, or create a new one, that would verify

RE: rc2 status

+1 on your proposal, Tom. Russell Butek [EMAIL PROTECTED] Tom Jordahl <[EMAIL PROTECTED]> on 09/30/2002 09:00:53 AM Please respond to [EMAIL PROTECTED] To:"'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> cc: Subject:RE: rc2 status I am in agreement with Sam and Russell. I never vote

RE: [axis] WSDL2Java enhancements for WSIF

Seems to me that we need a new extension - WSDL2WSIF. This could either extend WSDL2Java or extend the base framework WSDL2. If I could get some more information from you folks about what you actually generate, I could help create this extension (next week - this week I'm rather strapped for

RE: rc2 status

+1 to Tom's proposal. Thanks, dims --- R J Scheuerle Jr <[EMAIL PROTECTED]> wrote: > > +1 to Tom's proposal. > > Rich Scheuerle > IBM WebSphere & Axis Web Services Development > 512-838-5115 (IBM TL 678-5115) > > >

RE: rc2 status

+1 to Tom's proposal. Rich Scheuerle IBM WebSphere & Axis Web Services Development 512-838-5115 (IBM TL 678-5115) Tom Jordahl

DO NOT REPLY [Bug 13134] - java.io.IOException in WSDL2Java for test.wsdl._import

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

cvs commit: xml-axis/java/test/wsdl/ram ram.wsdl

rubys 2002/09/30 07:04:56 Modified:java/test/wsdl/ram Tag: axis1_0 ram.wsdl Log: Last fix for rc2 (fixes reported xml-security failure - thanks Dims!) Revision ChangesPath No revision No revision 1.1.10.1 +1 -1

RE: rc2 status

I am in agreement with Sam and Russell. I never voted for putting *everything* in, nor did I agree with the message calling for such an action. While I did have defects that I requested be merged in to 1.0, there were for 1.0 targeted bugs ONLY. I am an automatic +1 to any and all documentat

DO NOT REPLY [Bug 13041] - org.apache.xml.security.c14n.CanonicalizationException

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

cvs commit: xml-axis/java/test/wsdl/ram ram.wsdl

dims2002/09/30 06:55:36 Modified:java/test/wsdl/ram ram.wsdl Log: Fix for Bug 13041 - xml-security is *VERY* picky about namespaces. (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13041) Revision ChangesPath 1.2 +1 -1 xml-axis/java/test/wsdl/ram/ram.

RE: [axis] WSDL2Java enhancements for WSIF

Anthony, I would think that a different approach would be much better: 1. Fix WSDL2Java so that it either ignores or correctly processes the WSDL you run it. Then 2. Enhance WSDL2Java with an API that gives more control over which artifacts you want/need generated. This MAY be reasonable to

RE: (Attn:Tom and others) EsrTest

I just updated my CVS and I don't get any errors on InoutService?wsdl. Russell Butek [EMAIL PROTECTED] Glen Daniels <[EMAIL PROTECTED]> on 09/27/2002 04:13:07 PM Please respond to [EMAIL PROTECTED] To:"'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> cc: Subject:RE: (Attn:Tom and others)

Re: rc2 status

I would really like to stop this Friday, so I agree with Sam. If you notice, I've been silent on a number of the votes because I don't think we need them for 1.0. I haven't gone so far as to veto anything, but I've also noticed that some things didn't get the minimum 3 votes, so maybe other

DO NOT REPLY [Bug 12358] - SOAP mime attachments: does not work

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

DO NOT REPLY [Bug 13135] - saxparse error in deserialzing mime file to soap message while getting envelope

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

DO NOT REPLY [Bug 13135] New: - saxparse error in deserialzing mime file to soap message while getting envelope

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

Re: TCPMon Audio Feedback Mod ("RPC-Synth") RFC

Check the latest axis - there's an applet called SOAPMonitor that acts very much like TCPMon. In order to run it you need to enable the SOAPMonitor handlers though. The developers-guide and user-guide both mention it. -Dug "Dan Kamins" <[EMAIL PROTECTED]> on 09/30/2002 08:27:5

Re: TCPMon Audio Feedback Mod ("RPC-Synth") RFC

Just to clarify one issue with the "RPC Call" column mod... There were no extra *code* dependencies brought in, if that's what you mean. I saw that TCPMon was standalone and had no XML parser even, so it does a somewhat simplistic String search to extract the RPC Call. But more importantly,

Re: TCPMon Audio Feedback Mod ("RPC-Synth") RFC

I like it being a stand-alone app - when the i18n stuff was added I specifically asked that TCPMon get its own file to keep it separate from the rest of Axis. So your "RPC Call" hook, while really interesting, would bring in a dependency that I would prefer not be there. To be honest the pro

[axis] WSDL2Java enhancements for WSIF

In WSIF we use the AXIS WSDL2Java tool to generate the interfaces and complex type classes that WSIF requires. Currently WSDL2Java will always also generate the stub classes that WSIF does not require, and also when using WSDL that includes some of the WSIF specific bindings WSDL2Java will abend.

Re: TCPMon Audio Feedback Mod ("RPC-Synth") RFC

Excellent point (Doug) on the simplicity of tcpmon. That is what made it so easy to make these modifications in the first place. I would hesitate to give anybody down the road a harder time working on tcpmon than I have had, nor would I wish to slow it down or over-complicate it. How famili

Re: TCPMon Audio Feedback Mod ("RPC-Synth") RFC

One of the things I like about TCPMon is all of the things it doesn't try to be. To me its just a simple tool for watching TCP/IP traffic. It doesn't even know anything about SOAP. I can't say whether the audio feedback would be a nice feature or not - I'm sure it will vary depending on who y

[GUMP] Build Failure - Axis Security

This email is autogenerated from the output from: Build results exceed maximum length. Please see URL above for detai

[GUMP] Build Failure - Axis

This email is autogenerated from the output from: Build results exceed maximum length. Please see URL above for details. Last

DO NOT REPLY [Bug 13134] - java.io.IOException in WSDL2Java for test.wsdl._import

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

DO NOT REPLY [Bug 13134] New: - java.io.IOException in WSDL2Java for test.wsdl._import

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

DO NOT REPLY [Bug 13133] New: - Xerces 2.2.0 incompatibility

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

cvs commit: xml-axis-wsif/java readme.htm

antelder2002/09/30 02:03:17 Modified:java readme.htm Log: Update WSIF home page Revision ChangesPath 1.4 +16 -1 xml-axis-wsif/java/readme.htm Index: readme.htm === RCS file: /home/cvs/

Re: [wsif] Bug 13038 - WSIF's dynamic port/operation creation confusionabout message names

I think I agree with Jeff. If there is only one binding operation that matches the portType operation then WSIF should use it regardless of the input/output message names. How about adding the something like the following code to WSIFUtils and changing the providers to use it instead of the WSDL