At the xml sexurity site it looks like there is a version 1.4 w/src, and a
version 2.0 as binary, but i can find absolutely no information about
v.2.0 on the site, or elsewhere. what is the story with this? can v.2.0
just be plugged into the lib directory of a web app an be used? it looks
like
I think I use 1.4 src/bin for xml security plug-in, and it works fine.
- Original Message -
From: pacow [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, March 25, 2004 12:06 AM
Subject: Re: Need help signing a SOAP Request with a Digital Signature
At the xml sexurity site it
Hi all,
I volunteer to be the release manager for the Axis C++ 1.1 release.
Following is the release plan.
Axis C++ 1.1 Release Plan
This is the release plan for Axis C++ version 1.1. This version will be a
snapshot of all the changes since 1.0, including critical bug fixes and
tests. The main
+1 from me.
--- [EMAIL PROTECTED] wrote:
Hi all,
I volunteer to be the release manager for the Axis C++ 1.1 release.
Following is the release plan.
Axis C++ 1.1 Release Plan
This is the release plan for Axis C++ version 1.1. This version will be a
snapshot of all the changes since 1.0,
Hi all again, (and thank you Chris for your help last night!!! :) )
We make a design for an integration system.
So we have the following Situation:
On the left side of the architecture (picture) are several WebClients.
Each Client will communicate with several Backend-Systems on the right side
Use the SAAJ API.
At 08:38 AM 3/25/2004, you wrote:
Hello Guys,
Can we develop doc-style web service clients?
When I say doc-style web service clients, I mean a client which calls a
web service directly without the involvement of Axis serialization wherein
marshalling of function calls to XML
How about passing the whole document as a single string parameter of a doc/literal web
service? Is there a better performance to expect when using SAAJ?
What i don't like about SAAJ: .NET requires the use of DIME format. I don't know all
platforms or toolkits used to develop the potential
I am trying to create a wrapped service which returns array,
which would work with MS Infopath.
Infopath expects message to look like:
?xml version=1.0
encoding=utf-8?
ArrayOfInt
xmlns:xsd=http://www.w3.org/2001/XMLSchema
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance
I am trying to create a wrapped service which returns array,
which would work with MS Infopath.
Infopath expects message to look like:
?xml version=1.0
encoding=utf-8?
ArrayOfInt
xmlns:xsd=http://www.w3.org/2001/XMLSchema
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance
Does anyone know whether axis support style=message
and provider=java:EJB?
The signature of my method is public SOAPBodyElement
[] method (SOAPBodyElement [] bodies).
With a java class (style=message),that works.
With an ejb,i have an exception Body not found.
If a specify in my wsdd
I heard grumblings awhile ago that Microsoft might be dropping support for
DIME in lieu of some WS-I discussions concerning attachments. Might wanna
try googling around for more information, but this probably won't occur
until the next .Net/Vis Studio release anyway.
-Jon
-Original
Not sure if Microsoft will drop support for DIME but
DIME does not appear to be part of the WS-I attachments
work.
Since Microsoft seems committed to WS-I, I would think
whatever ends up in that document will at least be
added to the next release.
Greg
-Original Message-
From:
Anne,
I think you misinterpreted my question. Currently, my client is NOT using
the attachments to pass my XmlDocuments of type Document. I wanted to know
how one can avoid the axis marshalling of calls to XML.
IIRC, doc style web services circumvent the (de)serialization of calls but
can we
I started with a WSDL file, ran WSDL2Java to generate both client
server sources. I successfully deployed the web service with
stubbed methods. I'm running the TCPMonitor and request response
look fine as far as I can tell. But the client blows up with an
exception from SimpleDeserializer.
Hi Fredo,
Maybe it is a problem with your JVM?
http://developer.java.sun.com/developer/bugParade/bugs/4724129.html
--Thunder
-Original Message-
From: Fredo Corleone [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 25, 2004 8:55 AM
To: [EMAIL PROTECTED]
Subject: need info about memory
On Thursday 25 March 2004 04:39 am, Dorner, Thomas wrote:
Your second solution is a bit like JCA, we used it in our integration, i.e.,
built generic connector to the backend system, however our main backpane is
JMS. We had problems with the explosion of metadata that the connectors
Im trying to deploy within a rar within an Ear. the resource adapter does
not though. I get the below exception when i try to run it. the Ear is
laid out in the following fashion.
/META-INF/application.xml (only one entry for the rar)
/Myconnector.rar (no jars in this, Manifest has
Fredo Corleone wrote:
I'm using axis as a ws client and I get a memory leak everytime I send
a request. The requests and responses are very small (less than 500
bytes), but the memory leak is significant. I'm using java 1.4.1 on
Solaris.
I was using axis 1.2 snapshot from Jan 6 2004 that I
I upgraded to jdk1.4.2_04 and am still getting the same results ~32K leak
per message.
The leak happens only when a request is made. If requests are not made , no
memory leak.
We don't cache anthing from the response to the request, so our code is not
the source of the leak.
Does anybody have
How are you tracing the leak? Can you post some sample code?
-Original Message-
From: Fredo Corleone [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 25, 2004 2:01 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: need info about memory leak in axis
I upgraded to
pls open a bug report WITH your sample server/client.
thanks,
dims
--- Fredo Corleone [EMAIL PROTECTED] wrote:
I upgraded to jdk1.4.2_04 and am still getting the same results ~32K leak
per message.
The leak happens only when a request is made. If requests are not made , no
memory leak.
We
Thanks very much Chirs.
:o)m
-Original Message-
From: Chris Haddad [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 24, 2004 10:43 AM
To: [EMAIL PROTECTED]
Subject: RE: basic questions before start using Axis...
Hi Om -
The Axis users guide is a good place to start for learning more
I am using Jbuilder to generate my WIDL. I am using document with literal. When I
use a bean that has a return type of void in receive a deserializer not found
exception. Is there an issue using the void return type with document in axis?
Tim McClure
[EMAIL PROTECTED]
Title: [newbie] how to get soap-envelope xml?
hello,
I'm writing a client, and I keep getting the error
(405)Method Not Allowed
How do I get the soap envelope xml that I'm sending to see what's wrong?
Thanks,
Jeff
CONFIDENTIAL NOTICE: This email including any attachments, contains
I saw a couple with this problem in earlier posts, but I haven't seen a
solution yet...
I'm installing a web service for the first time on a websphere 5 environment
over SSL. The service works fine over HTTP, but not HTTPS. The fault code
is this:
AxisFault
faultCode:
Title: [newbie] how to get soap-envelope xml?
Use
the tcpmonitor application provided with axis. Read about it in the
user-guide.
-Original Message-From: JEFF EMMINGER
[mailto:[EMAIL PROTECTED]Sent: Thursday, March 25, 2004 2:56
PMTo: '[EMAIL PROTECTED]'Subject: [newbie] how
Title: Message
Russell,
how
can i use that to monitor incoming requests on some machine outside of my
domain?
-Original Message-From: Pridemore,
Russell (MAN-Corporate) [mailto:[EMAIL PROTECTED] Sent:
Thursday, 25 Mar, 2004 3:08 PMTo:
'[EMAIL PROTECTED]'Subject: RE:
Title: [newbie] how to get soap-envelope xml?
You can use
the SoapMonitor instead.
There is a
good tutorial in http://www.sosnoski.com/presents/java-xml/axis/axis-monitor.html
Fabricio
-Mensagem original-De: Pridemore, Russell
(MAN-Corporate) [mailto:[EMAIL PROTECTED]Enviada
Title: Message
It
acts as a proxy for requests. So, if you have a service at http://host:8080/axis, launch
tcpmon
on
another port, for example , and point your client to http://host:/axis. tcpmon will
log
the
request response, forwarding to the real service.
This
may be a
Hello list:
I'm trying to write a wrapped- style service and client.
After fighting for days with unexplained things and missing
documentation, I decided that I need to
write my WSDL by hand.
In my deplyment I use style=wrapped use=literal and include my
wsdl with wsdlFile
What I've found
There is no such sample in my xmlsec package(v.1.4), what is the full path and
classname? can someone who has this sample forward me a copy? thanks.
-peter
Mei Wu wrote:
Hey, the sample.security package has a simple way although it is not a wsdl
generated client stubs, but I think you can
Peter,
Check-out WSS4J: http://ws.apache.org/ws-fx/wss4j/
Regards,
Yves
-Ursprüngliche Nachricht-
Von: pacow [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 25. März 2004 21:52
An: [EMAIL PROTECTED]
Betreff: Re: Need help signing a SOAP Request with a Digital Signature
There is no
I have a document / literal service with a single method, which has a void
return type. The call executes correctly however the server returns a
non-empty soap body. The element it creates is no where in the wsdl. The
client then throws this exception.
Hi all -
today, DIME is required for .NET interoperability when sending attachments. Axis
does support DIME.
and yes, MSFT is dropping support for DIME in the future. it is being superseded by
MTOM in their roadmap:
Hi
I developed a webservice client and was working fine
on tomcat5.0, i deployed this webserivce client on IBM
websphere 5.0 and when i try to get data from
webservice i get the following error
faultCode:
{http://websphere.ibm.com/webservices/}Server.generalException
faultString:
Hi,
I am using a command line Java client that is using Axis inside. How
can I replace the default XML parser with the Xerces parser? I am using
JDK1.4 on Linux.
Thanks
Souvik
In your stub code you should see a line like this:
oper.setReturnType(org.apache.axis.encoding.XMLType.AXIS_VOID);
Comment that line out and everything should work fine.
-Original Message-
From: Bajek, Aaron [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 25, 2004 4:31 PM
To: '[EMAIL
Are there any Axis developers that monitor this list that might be able
to answer these questions or should I post this on the developer list to
find an answer?
If I have a custom data type that is (de)serialized with the
BeanSerializer and one of the properties of the bean is an int, how can
I
1) Can I verify that the handler has actually been deployed? When I run the command
java
org.apache.axis.utils.Admin client samples/security/clientsecuritydeploy.wsdd, I get
no feedback,
though no Exceptions either.
2) When I run java org.apache.axis.client.AdminClient list to see what has been
looks to me like you have an mismatched xml security library, have you
checked which version Axis supports?
I believe I am use 1.4...
- Original Message -
From: pacow [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, March 25, 2004 10:06 PM
Subject: Questions Regarding Security
ah.. that may be it, as i'm using precompile class files from the AxisBinary
distribution.
though now i have to figure out how to undeploy the Handler, since the
undeploy.wsdd
is not working.
also, any ideas as to why it filters some clients but not others? it only
filters examples that
came
Hi there,
I am trying to use axis as client for image server writen in gSoap/c++.
Sending request is ok, but when parsing resulting dime response, it says:
org.xml.sax.SAXParseException: Character conversion error:
Unconvertible UTF-8 character beginning with 0x9d (line number may be
too low)
yeah, undeploy doesn't work for me either, I renamed the
clienthandlerdeploy(something like that).wsdd, and then, it no longer calls
that handler, but I still can't undeploy the global server side handler:
loghandler, anyone has any idea to undeploy that? -- I tried to undeploy, it
shows lots of
If there's a bug you wish to see fixed in Axis 1.2-Beta or final, read on...
- If there is no bug currently in JIRA (http://issues.apache.org/jira), please create
one.
- If there is a bug existing in JIRA, then Make sure there is enough information to
recreate the
bug
- Make sure you try latest
This question pertains to both WSIF and AXIS.
Using wrapped document literal style operations, the following XML Schema
fragment results in an error stating that the sequence element does not
have type information:
xsd:element name=zooService
45 matches
Mail list logo
