most of the .net WSDL with complex structures cant accessed via remedy filter-set fields....Refer integration docs..
After many hours of analysis we have finally implemented with oracle procedures... John Baker-2 wrote: > > Hello, > > Although if we're all honest, the AR System webservice implementation > isn't a > terribly great solution to integration. it's super for simple proof of > concepts, but it's not the kind of true SOA messaging solution that most > companies are implementing. To give some clarification on this point, my > job > for Monday morning is to go and solve a problem where AR System 6.3 and > 7.0 > produce different SOAP messages for the same WSDL, and both are > unacceptable > to the .NET server that produced the WSDL. I currently can't decide who > to > blame :-) > > If you want to produce a quality integration, you use a messaging system. > RESTful is the way forward. > > David, if you want a webex demo sometime, let me know :-) > > > John > > -- > Java System Solutions > http://www.javasystemsolutions.com > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are" > > -- View this message in context: http://n2.nabble.com/Mid-tier-VS-Remedy-Web-services--both-are-same--tp3121386p3122184.html Sent from the ARS (Action Request System) mailing list archive at Nabble.com. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
