[EMAIL PROTECTED] wrote:
Hi,
Could anyone help me?
Yup, probably google, every single result from
http://www.google.com/search?q=nillable is relevant. (I don't mean to
be totally obnoxious saying this, you might find an explanation you
prefer following the link)
Given the following example
AW are one of the publishers with books on Safari - any chance it will
appear there?
eg Elliotte's book is AW...
http://safari.informit.com/?XmlId=0-201-77186-1
or
http://safari.oreilly.com/JVXSL.asp?xmlid=0-201-77186-1
(links from the AW catalogue to safari appear on www.awprofessional.com
but
I took a look at the crimson code causing this, its a bit odd. The
exception being thrown is complaining about an illegal namespace
declaration, not an illegal use of a namespace. (in Parser2.java)
if (attQName.startsWith(xmlns)) {
// Could be a namespace declaration
if
This one is from your application. You're getting a null pointer
exception in the service, and the faultstring in the fault is being
reported back to you.
faultstring[B2BSERV.0088.9134] Exception occurred while processing the
body of the message/faultstring
becomes
[B2BSERV.0088.9134]
After some investigation...the problem seems to be distributed evenly
across crimson, SAX, and probably Axis too. If you look in the stack
trace you'll see there are two passes through crimson, separated by
org.apache.axis.message.SOAPFaultBuilder.onEndChild(SOAPFaultB In
the first pass,
You create DataHandlers from DataSources. You just need an appropriate
DataSource. i.e.:
ByteArrayDataSource ds = new ByteArrayDataSource();
ds.setContentType(image/jpeg);
ds.setBytes(bytes);
DataHandler dh = new DataHandler(ds);
Here's some sample code for a DataSource. I just typed this in
There have been quite a few problems reported relating to large
messages. The reply I give below is just quoting myself from:
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]msgId=653050
NB since that thread I've found out that there's no reason JAXRPC can't
use XMLPULL, this is a
Yes, several ways. You can stop and start just the axis webapp - try
looking at:
http://yourserver/manager/html
Via this page, or the services exposed by the manager webapp, you can
deploy, undeploy, stop and start individual webapps. More details here:
The limit is Win2k pro. You need Win2k server to support more connections.
http://support.microsoft.com/default.aspx?scid=kb;en-us;122920
The limit's been there in windows desktop editions for years, and is
purely a licensing thing. It doesn't make much sense to stress test on a
desktop
Steve Loughran wrote:
It would be a useful little exercise. You could perhaps strip out all the
wsdl-to-java generation for a run-time-only system, which should save space,
and some of the other stuff. You'll still need commons-logging, but bind it
to Java1.4 logging instead of log4j.
I look
Yes and no. I think the 'known issue' you're referring to may be my bug
report:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11296
The bugs are, I think, in the HttpSender code:
You don't need to edit the stub. When you get the stub back from the
locator you do
((org.apache.axis.client.Stub)stub).setProperty(org.apache.axis.client.Stub.SESSION_MAINTAIN_PROPERTY,
Boolean.TRUE)
If you look at the code that you edited in the stub you should find the
bit checking this
In code (using port 8080 as an example):
SimpleAxisServer sas=new SimpleAxisServer();
sas.setServerSocket(new ServerSocket(8080));
sas.start();
Or from the command line (using port 8080 as an example):
java org.apache.axis.transport.http.SimpleAxisServer -p 8080
see:
Going back (way back) into this thread -
Anne Thomas Manes wrote:
We had another discussion on this list [1] recently about performance.
The JAX-RPC spec forces the use of SAX, which isn't the most efficient
way to parse structured messages.
Ricky Ho wrote:
At the Parser side, in both XPP and SAX code case, the parser deliver
the same number of elements to the application sequentially
(regardless of whether the application ask for it or the parser callback
the application). So the Parser is doing same amount of work. Memory
Anecito, Anthony (HQP) wrote:
[...I am using applets, wireless...]
1. Only use stand-alone clients
2. Use perhaps Sun JAXP (very small jars 20K compared to 3MB for axis
jars)
3. Drop Axis all together (great concept if you can live with
stand-alone and non-light clients)
Any Ideas?
Use kSOAP.
It may well mean the soap response is not okay. A fairly common cause of
such problems is seeing html error pages (with a 200 Ok response code)
instead of being sent soap, due to bad service design[1].
Try contacting the soap service via a tunnel (eg the one supplied with
Axis, or Nettool from
See:
http://nagoya.apache.org/eyebrowse/ReadMsg?listId=49msgNo=8427
Thomason, Michael wrote:
I deployed a test web service and when running the client I receive an
org.xml.sax.SAXNotRecognizedException. Part of the fault string reads
Feature: http://xml.org/sax/properties/lexical-handler;.
Currently you have to use /both/ if you talk to a mix of Schema 2001 and
Schema 1999 services - see
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15581
However, if you only need 2001, Axis is better. Switch.
Oliver Hauger wrote:
Hi,
I've sourcecode written for ApacheSOAP and now I am
You need to add an entry in your web.xml for this servlet, because the
invoker servlet (the one that allows you to execute servlets without
mapping them to an URL) became disabled by default in Tomcat 4.1.12
(this is in the release notes).
The reason this was done was to fix a bug that let
This is an example WSDL file which specs a DIME attachment and is
supposed to be interoperable:
http://cvs.apache.org/viewcvs.cgi/xml-axis/java/test/wsdl/interop4/groupG/dime/rpc/dime-rpc.wsdl?rev=1.2content-type=text/vnd.viewcvs-markup
However, read the checkin comment:
Initial checkin for
If its a client error, you throw a fault with a fault code beginning
with the string Client - eg Client.AuthenticationFailure or
Client.SomeMadeUpMessage. If you want to send something more than a
simple code, you add 'detail' to your fault. You should /not/ put
something in the faultstring
Apostolopoulos Paris wrote:
Thank you very much brian!
To tell you the truth I was thinking of changing the Style of my web
service and move to a message driven one where there you have more
processing power to the logic of the request.What do you think!
The answer is just 'it depends'. RPC
handled correctly, but the
mechanism described in the SOAP, WSDL, and JAXRPC specs doesn't limit
you at all.
-Original Message-
From: Brian Ewins [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 17, 2003 4:11 PM
To: [EMAIL PROTECTED]
Subject: Re: Some help with the usage and notion
Several other people have reported this problem.
See this thread:
http://nagoya.apache.org/eyebrowse/ReadMsg?[EMAIL PROTECTED]msgNo=7998
This one is also relevant:
http://marc.theaimsgroup.com/?l=axis-userm=103825449231468w=2
...trash generated on the client side is about 18MB for each
round
See
http://www.saxproject.org/?selected=ext
The error you quote indicates that the XML parser you are using doesnt
support the SAX extension for lexical handlers.
In particular this quote off the page is relevant:
[Re: lexicalhandlers...]In practice, all distributions are already
including
Yang Zhonghua (Dr) wrote:
Hi,
I have recently installed Tomcat 4.1.18 and xml-axis.
The classpath I set is:
... completely ignored. Please read the tomcat documentation here:
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/class-loader-howto.html
System - This class loader is normally
This isn't such a good idea. A webapp acts as the scope for error-page
entries in its web.xml. This means that if you have an html webapp,
you inevitably end up returning html errors to an xml client.
This is then complicated by the fact that some servlet engines change
status codes on errors
exactly isn't there. If you run fingerprint.jsp as well, it
provides some useful info about your setup that helps people on the list
to diagnose setup problems. Neither of these depends on anything else in
axis to run.
Cheers,
Baz
Brian Ewins wrote:
This isn't such a good idea. A webapp acts
From the J2EE standpoint:
As JAXRPC is part of the J2EE stack, you're supposed to use JNDI for
configuring a service to know about the environment it is running in;
though there are other kinds of config.
Envrironment-specific configuration is something you shouldn't put in a
web.xml, or
Brian W. Young wrote:
I just recalled that Strings in a SOAP request are sent as element text
and not embedded in a CDATA section. Since my String is actually an
XML document, this means i've got around 50,000 tags with and that
are all being escaped into entities. My guess is that this
AAGH!!!
Does that answer your question? ;)
For my sins, I have to interface with a server[1] which does something
like this; in the previous version they had a semi-reasonable SOAP
interface which compressed and base64'd some fields. The latest release
of the
James Black wrote:
Hello,
We are finally ready to bring my web services into production, and I
have some concerns about what type of system to use it on.
I am hoping that some people here will be able to give me an idea
about performance issues. I have been developing on an Ultra10 with 128M
Its best not to construct XML documents by appending strings, but to use
one of the XML APIs to build the document instead.
If your documents will be small enough to fit in memory, then something
like this in JDOM would work:
Element firmName = new Element(Firmname).setText(Gmbh Co.KG);
A
A bunch of debugging later - I now know first of all that any attempt at
trying to turn off XSI types on the MessageContext will never work:
_call.getMessageContext().setProperty(_call.SEND_TYPE_ATTR,Boolean.FALSE);
...
java.lang.Object _resp = _call.invoke(new java.lang.Object[] {XMLRequest});
I am trying to get Axis to talk to a web service written by a third
party which uses the 1999 Schema. I seem unable to convince Axis to use
the 1999 schema, or to turn off sending the xsi:type info, which is
causing a validation error at the other end.
This whole PROP_SEND_XSI/SEND_TYPE_ATTR
://www.sosnoski.com
Redmond, WA 425.885.7197
Brian Ewins wrote:
I am trying to get Axis to talk to a web service written by a third
party which uses the 1999 Schema. I seem unable to convince Axis to
use the 1999 schema, or to turn off sending the xsi:type info, which
is causing a validation error
Ignatia sent me a question about classloaders (at the end of this), but
after writing a long response I thought it was worth mailing to the list
too so folk can comment/critique. The issue is the common one of not
getting log4j to initialise properly after creating your own
log4j.properties
Stocker, Walter wrote:
Hello *,
after two days of research i found a suitable solution. It seems,
there are several problems with the commons-logging and log4j integration.
The only way to solve my problem, was to replace the log4j.properties file
in axis.jar. All the other tips from the
Fred,
what method of that service were you calling, and with what parameters?
Out of curiosity I tried reproducing your problem using the test client
here: http://www.xmlbus.com:9010/WSDLClient/WSDLDynamicTestClient.html
and information about the service you mentioned here:
Its not a bug in axis or tomcat. You're not supposed to do this.
Normally you redistribute your web application as a .war file which
bundles all your jars, classes, and web resources and you don't need to
do things like this.
To take a parallel example, suppose I have a directory named
That mapping is supposed to be part of the JAX-RPC standard. Read
'Appendix: Mapping of XML Names' on page 141-143 of the spec - you're
not supposed to get control of the mapping.
However it looks like the mapping you've seen is a bug! It appears to
be treating '_' as a punctuation char when
Dittmann Werner wrote:
Hi all,
according to the SOAP specs
quote
The (SOAP Body) element MAY contain a set of SOAP body
blocks, each being an immediate child element of the
SOAP Body.
/quote
Axis (in RPC and/or doc/lit mode) processes (at least?)
one immediate child
Chris Haddad wrote:
Luoh - it might be. You need to post the type definition in the
WSDL for typens:address for us to validate your premise.
/Chris
-Original Message-
From: Luoh Ren-Shan [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 21, 2002 3:49 AM
To: [EMAIL
Sudhir wrote:
Olivier,
Thanks for the reply. Unfortunately, I dont have the luxury of using the
wsdl2java tool. My aim is to generate the clients and the required beans
automatically. And all I can use is the parsers and the axis apis. I cant
use that tool, wsdl2java.
My queston is, do I
45 matches
Mail list logo
