Hi,
In a little custom thing I have going, I need to be
able to modify SOAPHeaderElement->SOAPElement's after
I have already created them and added them to the
SOAPMessage. I am unable to do this however. I try to
detach the origional text node and re attach a new one
to the Element, but this does
Hi Asbell,
http://www.rpbourret.com/xmldbms/
http://www.rpbourret.com/xml/XMLDatabaseProds.htm
and choose 'XML Middleware'
--- "Asbell, Jonathan"
<[EMAIL PROTECTED]> wrote:
> Hello all. While using "Axis" I have been searching
> for a java package that
> extracts DB data into xml format. I fo
Anne,
Just a little addition to your comment on WS-I BP:
"WS-I has just published its Basic Profile
draft, which only supports document-style"
In the current published revision, the profile support both rpc
and document styles. It only restrict the use to literal.
eric
> -Original Message-
> From: Steve Loughran [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, November 21, 2002 7:11 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Document style web services
>
> Must be the 3.0 version of MSSTK that defaults to document,
> right, as it was
> rpc/enc before, I believ
> -Original Message-
> From: Steve Loughran [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, November 21, 2002 7:08 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Document style web services
>
> At the same time, I cant help treating WS-I mandates with some less
> seriousness than W3C. W3C are layin
- Original Message -
From: "Anne Thomas Manes" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 21, 2002 14:25
Subject: RE: Document style web services
>
> Microsoft started the "document style by default" trend. Both MS SOAP
> Toolkit and .NET Framework generate docum
No idea; ask on ant-dev
- Original Message -
From: "Vidyanand Murunikkara" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 21, 2002 15:06
Subject: RE: Document style web services
We have an implementation whereby we use java:RPC with style=document
and the operati
- Original Message -
From: "Dennis Sosnoski" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 21, 2002 15:41
Subject: Re: Document style web services
> I think WS-I has serious credibility problems, especially since it came
> out that Microsoft's participation was co
That's old news.
Sun is now a member of WS-I. WS-I has added two new seats to the board, and
there will be a vote in March to elect the new board members. Let's hope
that Sun gets elected.
http://www.aspnews.com/news/article/0,,4191_1488041,00.html
Anne
> -Original Message-
> From: Denn
Anne Thomas Manes wrote:
WS-I has just published its Basic Profile
draft, which only supports document-style. Pretty much every SOAP vendor is
involved with WS-I, so it won't be long before all SOAP implementations
generate document style by default.
I think WS-I has serious credibility problem
We have an implementation whereby we use java:RPC with style=document
and the operation is identified by soap action URI. And we hack the
RPCProvider to make sure marshalling is done.
Steve, do u think such a thing should make it to the axis code base.
Vidyanand.
-Original Message-
F
Try
the latest nightly build. I know dims has submitted a fix for a bug I
submitted which might also solve the problem you're
encountering.
Jason
-Original Message-From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Sent: Thursday, November 21,
2002 2:19 PMTo: [EMAIL PROTECT
Jon,
There is no HTTP call involved when using the Axis transport. The JMS
message contains the SOAP request. The AxisServer (or any other server
with JMS support) that is listening on the other end gets the request,
invokes a service and sends the response back over JMS. Since there is
no HTTP
Inline...
Thanks,
Jaime
-Original Message-
From: Kevin Wang [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 21, 2002 3:47 PM
To: [EMAIL PROTECTED]
Subject: RE: JMS sample
Hi Jaime,
Can I archieve this using AXIS API:
VM1 --(request)--> VM2 --(forward request)--> VM3 --(response)-
Dennis,
My experience is that Java2WSDL in Axis 1.0 has too many bugs to generate
document/literal style WSDL, but if you can generate it by some other means,
the WSDL2Java and bean marshalling seem to work fine.
The reason you can't have multireferencing in document style calls is
because the do
- Original Message -
From: "Dennis Sosnoski" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 21, 2002 1:03 PM
Subject: Re: Document style web services
>
> Does Axis support automatic marshalling of document-style messages? I
> was under the impression it does not, wh
As you said in a subsequent response, Axis provides rudimentary support for
automatic marshalling of document-style messages (simple beans). This
support is less than what you can find in some of the other Java SOAP
implementations. See, for example, WASP's serialization framework:
http://www.systi
You are right that allowedMethods is used in MSG as well as RPC, but its
use in MSG is limited to naming the single method that will handle your
messages - not naming all of the methods then you are allowed to call.
I seem to remember an earlier post on this list which suggested that Axis
was una
thanks for your reply,
>>You need to implement your message handling method with one of the 3 or 4 signatures
I already know this and do already have an example integrated with my app that uses the method (SOAPEnvelope, SOAPEnvelope) signature.
>>The allowedMethods is aimed at RPC style SOAP.
Hi all,
I am attempting to make HTTPS invocations from an Axis client to an Apache HTTP
Server. I am using the latest nightly build as suggested by members of the developer
list. The latest version seems to be vast improvement in terms of providing for
changing keystore locations and passwords.
Whoops, in looking at the user manual I see that Axis *does* support
automatic binding for simple bean-like structures. AFAIK the rest of
these comments still apply, though.
Sorry for providing wrong information earlier in this thread, Matt -
check the "Document / Wrapped services" section in t
Can I get a clarification on JMS and AXIS (or any webservice for that
matter). If you wrap a webservice call in a jms call, all that really does
is spin off a thread. However, the http call initiated inside the thread
itself is still synchronous. That is, the webservice call can timeout
within t
You need to implement your message handling method with one of the 3 or 4
signatures listed in the user guide. (RTFM!) ;-) The allowedMethods is
aimed at RPC style SOAP.
If you wish to have multiple services, but all of them need pre-processing
by some common code, you could try implementing a
Hi Anne,
Does Axis support automatic marshalling of document-style messages? I
was under the impression it does not, which was why I suggested a
DataBindingProvider might be useful to add this support. I agree that
document-style is a better approach for the future, though I'd hardly
call it a
Hi Jaime,
Can I archieve this using AXIS API:
VM1 --(request)--> VM2 --(forward request)--> VM3 --(response)--> VM1?
(do we need change the code to allow user set replyTo to a nontemporary
wellknown destination?)
or I have to use this way:
VM1 <--(request/response)--> VM2 <--(request/response)-
I want to use the service to capture incoming web services. However I want to process all incoming messages with a single class. I am integrating Axis with our EAI application and it already has sophisticated handlers for triggering data transfers based on XML content.
In the WSDD file I tried s
I must fundamentally fail to understand the server-side class structure of an app deployed on Axis. Suppose I have a Java interface I want to expose. It's in package foo.bar. It has methods like:public Something getSomething(SomeInput input) throws SomeException; What's critical about this interfa
Jonathan,
Look at the datadump functionality of the Torque persistence layer:
http://jakarta.apache.org/turbine/torque/index.html
I have never used Torque myself. If you looked at it I would be
interested in your comments.
Niko
Asbell, Jonathan writes:
> Hello all. While using "Axis" I have
- Original Message -
From: "Chris Forbis" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 21, 2002 11:14
Subject: 1.1 When?
> Does anyone know when we will see an official 1.1 (or 1.01 as the dev list
> was debating?)
> I ask because 1.0 has the MAJOR bug with Custom
Dennis,
This is a pretty antiquated view of document style. Document style is no
longer used just for XML messaging. Most SOAP implementations support
automatic marshalling of both RPC-style and document-style messages. As long
as you have a WSDL description of the message structure, there's no pr
Has
anyone used Axis for sending attachments (in Messaging mode, not RPC) across?
The
following chunk of code does not seem to work. When the message reaches the
server, there are no attachments with it. What am I doing wrong? Also a side
question. Does Axis fully support JAXM?
==
Dennis -
Thanks. I was under the impression (from the "Service Styles" section in the
user's guide) that Axis can do this now. Unfortunately, the
"When Beans Are Not Enough - Custom Serialization" section is not complete.
Matt Crawford
Enterprise Rent-A-Car
-Original Message-
From:
I would like to see an "official" release with the custom exception handling
as well.
-Original Message-
From: Chris Forbis [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 21, 2002 2:15 PM
To: '[EMAIL PROTECTED]'
Subject: 1.1 When?
Does anyone know when we will see an official 1.1 (
Does anyone know when we will see an official 1.1 (or 1.01
as the dev list was debating?)
I ask because 1.0 has the MAJOR bug with Custom Exceptions
not working. I know that I can use nightly
builds to get around this (and they work), but I would like to uses a version
blessed setup in
Hello all.
While using "Axis" I have been searching for a java package that extracts DB
data into xml format. I found a package called db2xml, but it was not
dependable, needed a cache set aside, and used a very old version of an xml
parser causing conflicts. Does anyone else know of any
Hi
Do u have axis running as a separate Web Application or is part of your
own Web Application. If it is the former, then make sure that you can access
:
http://<_web_application_root>/axis/services/AdminServices.
If you have running within your own Web Application,
then change the CalClient i
Hi Matt,
The whole point of document style is that your application gets passed
the XML message payload as XML document fragments. See the "message"
sample for an example of this. With a document style interface your
class would look like:
public class SomeXMLService {
public Element[] some
Hi
Check whether your Application Server (Tomcat/Weblogic etc) is running
and is running on the port 8080 that the examples expect them to be.
If it is running but the port is different, then change the example client
java classes and then compile them again.
Cheers
Thyaga
- Original Messa
- Original Message -
From: "dumdum 420" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 21, 2002 6:38 AM
Subject: Error deploying deploy.wsdd from Admin Client
> Hi All,
>
> I am trying to deploy my deploy.wsdd using the admin client. Following
error
> comes which I
- Original Message -
From: "Yates, Danny (ANTS)" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 21, 2002 3:44 AM
Subject: RE: UTF-16 with Axis
> Why did it "assume" this? If Google was returning UTF-16, then
> a) it should have said so in the XML declaration
> b) th
File defects whenever this occurs. Its the only way these problems get found
and fixed. The only outstanding i18n bugs known about relate to WSDL export
not stating its locale
- Original Message -
From: "easter" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 21, 2002
Hello,
Has anyone had experience with document style web services similar to the
one shown below? The users guide indicates that "Document services do not
use any encoding (so in particular, you won't see multiref object
serialization or SOAP-style arrays on the wire) but DO still do XML<->Java
da
We've been successful at doing this using the Axis Session object to store
'tokens' or other items that are commonly accessible by multiple published
SOAP services.
- Original Message -
From: "Alex Dovlecel" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 21, 2002 6:02
Hi All,
When I try to run the very basic example of Calculator.jws using
CalcClient.java passing parameters as -p8080 add 5 7
I get the following exception.
Kindly help I am really stuck.
AxisFault
faultCode: {http://xml.apache.org/axis/}Server.userException
faultString: org.xml.sax.SAXParse
Seems to me the samples.echo is missing some source
files? I notice that the TestClient.java is the Abstract class, where’s
the concrete class?
I also noted in the comments on the Abstract TestClient
* Modified to use WSDL2Java generated stubs and artifacts by
* @author Rich Scheuer
Hello everyone,
I trying to solve the following problem I have a class that looks something like this:
public class Security {
private int securityType;
private Object userData;
private String label;
[get/set methods deleted]
}
I want user data to be ty
Agreed it's probably a Google issue.
In fact they do mention it' s going to be an UTF-8 result, however they
return as part of this result data coming from outside, for example a
resume etc, and they don't encode these objects when they create the
message, so sometimes the Axis parser crashes whe
I don’t see a sample that uses WSDL2Java that
generates/includes the following from MyService.wsdl:
MyService.java Interface
MyServiceLocator.java
MyServiceSoap.java Interface
MyServiceImpl.java
MyServiceSkeleton.java
MyServiceStub.java
MyServiceTestClient.java
MyType1.java
MyTy
Hi All,
I am trying to deploy my deploy.wsdd using the admin client. Following error
comes which I am wonderstuck why?
AxisFault
faultCode: {http://xml.apache.org/axis/}HTTP
faultString: (404)Not Found
faultActor: null
faultDetail:
null: return code: 404
Virtual Host or Web Application Not
Great, let me know if you have any other issues.
Thanks,
Jaime
-Original Message-
From: Kevin Wang [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 20, 2002 4:51 PM
To: [EMAIL PROTECTED]
Subject: RE: JMS sample
Jaime,
Thank you for your reply.
I have modified SimpleJMSListener.ja
Hi,
I have been looking at the samples in the test/wsdl/extensibility
package. My confusions can be illustrated using any of the examples i
think, but this is the one i've been experimenting with. Basically I
want to look at the request in it's component form (and before it's
added to the SOAPEn
Hi Pedro,
Actually, I haven't used MS Proxy, just MS ISA. I would imagine that
there is a pretty good chance that it would work, though.
Jess
On Thu, 2002-11-21 at 05:45, Pedro Mendoza wrote:
> Hi Jess,
>
> Thanks a lot for your prompt answer, BTW, since MS Proxy Server does support
> ba
Hello all,
I have started to read the "big zip" and seems pretty usefull. But before
reading all that stuff, I want to know if I can achieve this behaviour:
The web service that I am going to implement will provide many methods. So I
decided to split it (2, 3 or 4 web services). One of them wil
Why did it "assume" this? If Google was returning UTF-16, then
a) it should have said so in the XML declaration
b) the XML parser you (or Axis) were using should understand this
If a) is not true, this is a bug at Google's end, and you should
contact them to fix it. If b) is not true, this is a bu
As an example, a problem we ran into was using the Google web service,
which returns results in UTF-16.
This caused untold problems in Axis because the parser failed when it
reached an "illegal" character
since it assumed the response was UTF-8.
Perhaps you could be a bit more specific about wh
Hi Jess,
Thanks a lot for your prompt answer, BTW, since MS Proxy Server does support
basic auth, Axis is supossed to do right if MS Proxy Server is configured
that way, did you have any problems with this configuration ?
Thanks in advace,
Pedro
- Original Message -
From: "Jess Sightler"
well, hi to everyone
i've a Simple WSDL in wich i describe a service that accepts a string in
input and give an ID in output.
My original WSDL was more complex, this is only an example...
--
http://localhost:8080/ws/services/SimpleService";
Title: Message
can
you post the part of your client code where you register the DeserializerFactory
( its Call.registerTypeMApping() )?
Russell
-Original Message-From: Vijetha Vadlakonda (vijetha)
[mailto:[EMAIL PROTECTED]]Sent: 20 November 2002
20:08To: [EMAIL PROTECTED]Su
58 matches
Mail list logo
