Sorry, I should have added that the version I am trying to build is 1.4
final.
-Original Message-
From: Tony Dodd [mailto:[EMAIL PROTECTED]
Sent: 11 March 2005 09:37
To: 'Apache AXIS C User List'
Subject: Compillation error
Building on debian Linux I get the compiler error:
In file
I was trying to implemennt X.509v3 Binary Security
Token.
I have encrypted an x.509 cerificate using
Bse64Encoding and also I have the encrypted value.
Now,
How do I decrypt that and get back the certificate?
Please help me out
__
i was implementing with wss4j only...the first
encoding part is done
but i am not able to do that the other round
please send me the code.
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
Hi,
This combination in the WSDL used as input to wsdl2java:
wsdlsoap:binding style=document ...
wsdlsoap:body use=literal .
Results in an empty namespace thus:
soapenv:Body
return xmlns=Hello World/return
/soapenv:Body
Following many
Hey Mike,
Give me your address and a good time to drop round. I
got that stuff you asked me to get for your burglar alarm, and I would
hate to drop by while you are at work or not at home!
Cheers buddy
PS - If (by chance) I get there and your not home, should I just get
on with the
Hello
All,
Sorry this is long
but I'm trying to provide all the detail someone might need to help me out! :)
If you'd like to
help me out and just want to get to the crux of my problem, skip down to
"Problem 3.)"... (thanks)
I'm at my wits end.
I've tried to get an attachment example
Dheeraj,
Can you try to change prefix for
type=contentimpl:CommercialContentImpl to
type=impl:CommercialContentImpl. It looks to me that your wsdl
defines CommercialContentImpl in http://ws.hrs.harris.com/; but not
in
http://impl.content.hrs.harris.com/;.
Timour
On Thu, 10 Mar 2005 18:30:41
Here is the whole doc.
For information I have tested this with all 4 possible combinations of
document/rpc literal/encoded and the work fine axis to axis. The
problem is that .net doesn't like xmlns= or encoded.
wsdl:definitions xmlns:impl=urn:LookupBorrower
xmlns:intf=urn:LookupBorrower
Richard,
This is not a valid doc/literal WSDL document. You need to define the
WSDL differently depending on whether you want rpc/encoded,
rpc/literal, of doc/literal.
Here's how you should define your WSDL if you'd like to create a
doc/literal service conforming to the wrapped programming
an empty namespace thus:
soapenv:Body
return xmlns=Hello World/return
/soapenv:Body
Following many threads on this list it is clear that this is a
problem.
If you are trying to consume an axis service in .net it appears to be
a 'show stopper'.
No.
xmlns=
2) There are a lot of namespace declarations in the document which
have no additional referents further down. Is this a good thing,
immaterial, or bad practice?
Code Clutter.
Bad practice.
-Original Message-
From: Elaine Nance [mailto:[EMAIL PROTECTED]
Sent: Friday, March 11,
Title: .NET and Axis
Hi
Dino,
thanks
for taking the time to reply in such detail..
I am
not sure whetherwe completely understand each other, so just to make sure
I will explain what approaches I have tried.
Ihave startedwith a Java class (field names in camelCase),
generated the WSDL
Elaine,
No need to apologize. XML Schema is a very complex subject, and lots
of people get confused. In fact, someone sent me a note off list
thanking me for answering your questions.
When learning schema, I suggest you start with the Primer:
http://www.w3.org/TR/xmlschema-0/.
Also, XML Schema
Hi Dino,
I don't like to live dangerously so I did start with the WSDL first,
then wsdl2java, then tested my solution axis - axis, finally used Visual
C#.net to pull in a Web reference to my service and let it build
everything.
The underlying code it built looks very similar to what you
Thanks again. I am studying the XML primer now.
My first forays into SOAP-land were using the MS SOAP toolkit 3
and VB 6. Some of the stuff works and some not. MS never
corrected some of the known bugs between 2 and 3. Fortunately
for me I am comfortable with sockets and the Win32 API in
Timour,
Thanks a lot for your reply. After changing to impl wsdl2java works without
error but all the classes (for complex types) are not getting generated. I
changed the namespaces after sending the mail. My target namespace is
services.hrs.harris.com. I plan to put other classes to be generated
Title: .NET and Axis
It seems likely that the name or namespace of the response
element does not agree between AXIS and .NET.
What you have sent shows the xml "on the wire", but does
not show the namespace or element name you have told AXIS to use (listed in
deploy.wsdd) and does not show
Any suggestions as to how I can do this?
If you start with WSDL, it should do what you want.
Does the Python webservices stack do WSDL ?
-Original Message-
From: C.C. Ang [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 09, 2005 6:17 PM
To: axis-user@ws.apache.org
Subject:
Yes ! Ack!
I have seen this before.
When the schema does not declare an elementFormDefault ,
.NET assumes it is one way,
And AXIS assumes it is the other.
This is a bug in one or the other.(I don't know what a schema parser is
expected to do with EFD is missing).
The workaround is to
Hi,
I have seen some examples where companies write a different set of objects and
expose them through wsdl. The service implementation can then convert those
objects into their internal counterparts. The advantages are:
--Every change in the internal structure doesn't break the API.
--Allows
Dino Chiesa wrote:
Ok, hold on.
Here's the issue. Suppose you have a schema, with no elementFormDefault
specified. The schema is embedded or imported into a WSDL, and you run
it all through .NET's wsdl.exe utility. .NET follows the W3C XML Schema
specification, which says if there's no
Dino,
My comment below. (Jongjin)
Thanks.
/Jongjin
- Original Message -
From: Dino Chiesa [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Saturday, March 12, 2005 11:57 AM
Subject: RE: Empty namespace - again
So I guess .NET and some other WS toolkit(JWSDP, WebLogic) makes
schema
22 matches
Mail list logo
