They did work for a nightly build a few weeks before beta3 was released.
Now I am using beta3 and I don't see the null pointer exception you see, but
I do get mapping not found.
java.lang.Exception: !! No Deserializer for
{http://grandcentral.com/schemas/delivery/v1}delivery
at
org.apache.
It is also possible that you your windows box is simply overloaded
processing your XML and simply can not get to service new requests in time.
If you can, try to put your service on a Solaris box, or even Linux. They
tend to have a little more responsive kernel and networking layer as Heitzso
poin
> Can Axis really be recommended for production use? Not in my
> opinion, and you have removed any condifence I may have had in your
software by
> suggesting that in the first place.
Axis provides a wide range of functionality.
Most of the people who use it will not use all of its functions.
Ba
To get text value, or any other object value for that matter, use
getObjectValue() function.
It will attempt to auto detect, and return to you the object of type this
node maps to.
If you do not have an "xsi:type" attribute in the element you can do 2
things.
1) Set the type of the element then ge
t; Till
>
> --
> Caught in our narrowminded believe...
> -
> Till Woerner
> Berlin, Germany
> EMail:[EMAIL PROTECTED]
> ICQ#: 7162410
>
> > -Ursprüngliche Nachricht-
> > Von: Taras Shkvarchuk [mailto:[EM
Axis provides most of the functionality you will need for attachment
management.
If you have large XML attachment, it should not be a problem.
You can write SAX handler for your attachment that will be as efficient as
you want it to be.
Attachment parse time is also good in axis, it has custom cod
-Original Message-
> From: Daniel F. Savarese [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, March 21, 2002 1:37 PM
> To: [EMAIL PROTECTED]
> Subject: Re: why Axis?
>
>
>
> In message <94F890AC98E9AF478F08FEFAC7467C7C095168@riker01>,
> Taras Shkvarchuk w
> ri
>Why Axis?
Because it is good implementation of JAXM and JAX-RPC APIs.
Not all the interfaces are implemented, but you will find APIs very close.
If you are doing Attachments, you will be pleased to know that Axis is not
using JavaMail for MIME parsing.
*** RE: JAXM ***
> after having used JAXM e
> 1). Does the latest Axis build support the attachement?
Yes.
> 2). If yes, does the attachement samples work with the latest build?
No. There seems to be a problem in RPCElement that does not pickup default
type serializer for the method call.
> 3). Is there any documentation for attachement in
Compelling reasons to NOT USE axis yet:
1) Its is still alpha. Very alpha in terms of error handling. You if you
expect always good SOAP, and don't mind AXIS dieing if someone is using
"myPrefix25:string" instead of "xsd:string" for type names.
2) API will be similar 6 months down the road, but do
This may not be the best example, but its something for you to look at. I
have an entry on my todo list to make something better looking, but somehow
things just appear in front of it.
This is a helloworld type service that takes requests with the body of:
http://myorg.com/hello";>
Taras
May the problem be here?
> serializer="com.eaaxis.chapter5.DataSer"
>deserializer="com.axis.DeserFactory"/>
-Taras
> -Original Message-
> From: Karna Harsha [mailto:[EMAIL PROTECTED]]
> Sent: Monday, March 04, 2002 11:06 AM
> To: [EMAIL PROTECTED]
> Subject: Problem with
Yes it is very possible.
There are 2 ways I can think of right away. Servlet one, and easy one.
(There maybe 10 other ways to do it though)
The easy way uses the shiny auto deployment, but has a little overhead with
creation of junk message.
1) Servlet way (Hello echo service)
Write a servlet tha
SDL Source. Isnt it completely integrated ?
>
> On Mon, 2002-02-18 at 11:28, Taras Shkvarchuk wrote:
> > Not that I know of yet. People are mostly working on
> getting wsdl<->java
> > working right now.
> > If you can add some code to make it work, it will be in
&g
cking call? in the alpha3 doc it says this
> functionality has not been implemented, do you know if has
> been done in
> more recent builds?
>
> thanks
>
> Jeff
>
> Taras Shkvarchuk wrote:
>
> >What you want are non blocking calls.
> >No. Currently Axis will
What you want are non blocking calls.
No. Currently Axis will block until response has arrived. It does however
suppose async messaging, as in you do not have to complete an RPC session.
You can submit a separate request to the server asking for your response, or
server can push response when its
Title: RE: how to log debug message in Axis
http://jakarta.apache.org/log4j/docs/documentation.html
In
your class you will need to have something like this:
import
org.apache.log4j.Category;
public
class Boo
{
private static Category
log=Category.getInstance(Boo.class.getName());
p
Tomcat has its parser.jar that does not have the method you (with axis) are
trying to call.
Solution: Put xerces-1_4_x.jar in front of parser.jar in your lib folder for
tomcat. problem will go away.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesda
Title: hi guys.
yes
-Original Message-From: Ashis Rout
[mailto:[EMAIL PROTECTED]]Sent: Thursday, February 07, 2002
3:05 PMTo: '[EMAIL PROTECTED]'Subject: hi
guys.
does axis support asynchronous messaging?
hought
> this was one of
> the reasons SAX is being used as opposed to DOM in Axis.
>
> -Original Message-
> From: Taras Shkvarchuk [mailto:[EMAIL PROTECTED]]
> Sent: Monday, February 04, 2002 4:56 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: High Volume
>
real
solution), sending dummy blocks (one char every second lets say) to keep
connection alive, or streaming the data as it becomes available.
All of these issues are transport level, and HTTP related. They will not go
away if you don't use SOAP.
> -Original Message-
> From: Taras
> You must know
> the Content-Length before you write the first byte of data.
Not true. Content-Length is not a required HTTP header. In fact many clients
don't use it.
You can still optionaly use Content-Length inside your MIME bocks to speed
up parsing, but even that is optional.
> -Origin
> That's probably not a good solution. It sounds to me SOAP is
> good for short messages.
Not true at all. There are no size limitations in the design of SOAP format.
Some of today's toolkits do not handle large messages well, but they also
don't handle SOAP itself well sometimes. :)
What he saw,
currently there is a DOM structure. What would be very nice, is if there was
an easy way to get RAW XML, that you could feed through a sax parser.
In the mean time your best bet I would say is to store XML you generate as
an attachment. That would eliminate expensive extra marshalling, and you
co
24 matches
Mail list logo
