Hi
(B
(BEhh... Maybe this answer is too simple or I am misunderstanding you. Dunno.
(B
(BIn C# you would have to write a using declaration in top of you code file
(Bfor the namespace containing the generated proxy class.
(B
(BBetter of asking on the ms newsgroups for questions like these...
Ignore my previous post...Really way out answer from my side...You posted
what actually goes on the wire, not the WSDL...
Sorry, too fast on the trigger :-(
- Original Message -
From: "HG" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December 22
Hi there.
I can't actually remember, so this is a best shot, Ok?
IfcSpace
WS-I Basic Profile prohibits "soapenc", used the schema equivalent type
instead.
- Original Message -
From: "BLIS Webmaster (Patrick Houbaux)" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, Decembe
Hi Steve
As far as I remember WS-I Basic Profile suggest the .NET way of doing it,
meaning document-literal (wrapped) style.
I can't remember if rpc style web services is prohibited if you want to
support WS-I Basic Profile.. Anyone?
Regards
Henrik
- Original Message -
From: "Steve Ich
ations or adding additional data to a
> message payload. These types of changes are forward compatible with
caveats
> e.g. new elements are optional and not required. This change wouldn't
> necessarily require a new endpoint.
>
> If you make massive changes you essentially
Hi Ed
Is this *really* the only approach? Defining it at a new endpoint?
I mean that's what I do for know, because I can't think of any other
way...but..you know.. :-)
Maybe this would be a task for the UDDI registry? I dunno.? Do you? Anyone?
Regards
Henrik
- Original Message -
Fro
Hi again Tony...
I can see this thread evolved since
yesterday...fine discussion :-)
In this particular aspect, I prefer to work from
Java. The way I see it, I'm developing some business functionality, that might
be usable in many ways, not just as a web service. In developing the busine
In addition, you must
declare the namespace to reference any elements within the
namespace:
xmlns:foo=urn:foo
The same goes for
schema imports.
Anne
From: HG
[mailto:[EMAIL PROTECTED] Sent: Tuesday, November 16, 2004 8:57
AMTo: [EMAIL PROTECTED
efine
standalone fault message schema.
<xsd:import> the element
schema.
Define a schema
within the WSDL types section.
<xsd:import> the element
schema.
<xsd:import> the fault message
schema.
Define input/output message elements.
Regard
Hi Anne
Thanx for your fantastic reply/comments on this
post. They really makes sence.
Actually I used your suggestions already (maybe
without knowing it ??!) on a small-sized project where I only had one xsd file
for all types. The whole "domain model" in one file.
BTW, do you know th
Alright..I'll keep going :-)
You nearly answered your question
yourself.
The different between 1) and 2) is that it is
defined in two separate schemas (files).
That way SOAPscope doesn't "throw up" (guess not,
haven't tried it), because your are importing from a schema to a
schema
You
Hi Tony
I have a few...Some on this list might disagree,
but it is always nice with a discussion.
I have done this, on several projects, and it works
very well, especially for interop.
The main point is: Use Schemas
1.
Define a schema for each message you want your
webservice to process
Hi there
I have done this, although in C# and with no COM overhead, and I get about
the same results in the .NET as in your Axis client. That is, first call
takes longer than the two proceeding calls.
I don't know the exact reason for this, but I think it has to do with the
time it takes to estab
ï
Thanx James...
I thought so.. Not a pro either...better flick a test sample and test it on
both (J2EE and .NET) platforms..JUst to see how it actually behaves..
- Original Message -
From:
[EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, July 01, 2004 2:55
Hi Anne
Sorry for interferring in the discussion... hope it
is ok.
I am about to define a "schema model", a
collection of schemas with types that can be shared across web services, eg.
imported into WSDLs
Is it possible for WSDL2Java to generate the
proxy for the schema to one package,
t; won't attempt to expose Java collections through your WS interface.
>
> For best interoperability, your interface should consist of simple types,
> arrays (defined using minOccurs/maxOccurs), and complex types defined as
> sequence structures of simple types, arrays, and/or sequ
Hi all
I have developed some WebServices using Axis...nothing big...just a couple
of examples serializing beans and so between a java (Axis) server and a java
client...however...now a project is arising where web services is going to
be used in large scale...
and to add even more complexity..the
Hi there
From your stack trace it looks like the error is
happening here:
OpenDBLPClient.OpenDBLPBindingStub.searchPerson(OpenDBLPBindingStub.java:484)
Do you call your web service directly from your JSP
(through a service singleton)..
Check the stub and line number 484, to see if
there
18 matches
Mail list logo
