well, I was refering to the "trivial little auto-deploy feature of Axis".
Its a shame they didnt make it able to support collections, because there is absolutely (as far as I can tell) no technical reason not to. I am sure there are reasons to use all of the features of wsdl, but the learning curve is steep and when you can offer a simpler solution there seems like no reason not to. I dont need all the features of wsdl and I just can afford the weeks it will take (on my present course, and based on the available docs) to learn how to do it the non- "trivial little" way. But perhaps I am over estimating the complexity of this. Is there any kind of quick start that is easy to understand and doesnt require a hundred pages of reading? I find the Axis website fairly unhelpful. Hank On 6/19/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
By "jws", are you referring to "Java Web Services", BEA's metadata-driven system that forms the foundation of JAX-WS, or the trivial little auto-deploy feature of Axis? If the latter, then bear in mind that jws is useful for only the most trivial RPC-oriented invocations, in which all parameters are simple types. Anne On 6/18/06, hank williams <[EMAIL PROTECTED]> wrote: > I am developing an application for which I was intending to use a different RPC strategy for use with a flash application. Unfortunately the company (adobe/macromedia) has abandoned their "remoting" technology for allowing flash to access java pojos. Now if you want a decent solution you have to spend 6k or 20k for their "new technology". So now I need to use something else. Flash supports web services, so this seems like a choice, but it is 150 times harder than their old solution and I am overwhelmed. All of the documentation seems circular, where in order to understand A you must understand B and to understand B you must understand C and D etc. - couldnt they make this easier :). Anyway, I love the idea of jws, but it seems like the designers didnt think it was a good idea to make things too simple because when you read about it they immediately discourage its use. But I am stubborn and would at least like to try to use jws, but I cant seem to find any detailed documentation on what it will or wont do - (great way to discourage use but I am persistent!). That calculator example in the docs for jws is great, but, for example how would I send a table of information for populating a dataGrid? For example, will it convert an Array, or an ArrayList of objects? And I would love a more detailed explanation of what jws *wont* do that I will really need. I am hoping that the designers visions of what is necessary is just much grander than what I need and that it would actually be fine. Because the learning curve for this stuff, particularly for a project that is at the end of its development cycle - not the beginning - is steep. This is seeming super painful. Regards Hank --------------------------------------------------------------------- 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]
