Re: ANNOUNCE : Axis 1.1 release

Re: "nillable" attribute inside of element

[EMAIL PROTECTED] wrote: Hi, Could anyone help me? Yup, probably google, every single result from 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 exampl

Re: Shameless plug

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

Re: Illegal Namespace prefix: "xml".

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,

Re: Illegal Namespace prefix: "xml"

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. [B2BSERV.0088.9134] Exception occurred while processing the body of the message becomes [B2BSERV.0088.9134] Exception occurred while proce

Re: Illegal Namespace prefix: "xml".

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 (!nsSu

Re: Illegal Namespace prefix: "xml".

The xml prefix doesnt need to be defined. http://www.w3.org/TR/REC-xml-names/#nsc-NSDeclared "The namespace prefix, unless it is xml or xmlns, must have been declared ..." the message isn't incorrect at all. Something is going wrong when it is being parsed by crimson. Jim Poulsen wrote: It ap

Re: Converting byte array to DataHandler for Soap attachment

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 wi

Re: Dynamically re-deploying AXIS server (class files )

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:

Re: Performance issue on big data

There have been quite a few problems reported relating to large messages. The reply I give below is just quoting myself from: NB since that thread I've found out that there's no reason JAXRPC can't use XMLPULL, this is a restrict

Re: Axis light for client

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 forw

Re: Connection limit

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 edition

Re: HTTP Connections Hanging

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:

Re: Maintain Session with .NET and AXIS

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 pro

Re: AW: Running AXIS standalone.

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: http://docs.pushtotest.com/axis

Re: Axis Client Performance issue explained

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 kSO

Re: Why Pull-Parser faster ?

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 u

Are JAXRPC, XMLPull incompatible? was Re: Why Pull-Parser faster?

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. http://marc.theaimsgroup.com/?l=axis-user&m=10442979

Re: SaxNotRecognizedException

See: 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";.

Re: how does a deserializer problem come from?

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

Re: using ApacheSOAP or Axis

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 thin

Re: Some help with the usage and notion of FAULT messages!

s a bug in Axis that may well prevent RPC faults being 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 PR

Re: Some help with the usage and notion of FAULT messages!

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 an

Re: Some help with the usage and notion of FAULT messages!

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 faultstri

Re: WSDL / attachments. Please help!

This is an example WSDL file which specs a DIME attachment and is supposed to be interoperable: However, read the checkin comment: "Initial checkin for d

Re: Accessibility of servlets within Axis webapp

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 peop

Re: Axis on Tomcat embeded in JOnAS Application Server

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 the

Re: XML Message Size (OutOFMemoryError)

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-user&m=103825449231468&w=2 "...trash generated on the client side is about 18MB for each round

Re: Problems in Installing and deploying web applications using xml-axis

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 init

Re: Axis integrated into existing web application?

spot what 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

Re: Axis integrated into existing web application?

This isn't such a good idea. A webapp acts as the scope for 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 when retur

Re: Data Transfer with XML between two DB's- a Real world Case

Anne - while I also probably wouldn't consider web services, Oracle's replication tech sucks really badly. Commercial alternatives or homegrown software is a better bet for many applications. Some good reasons why homegrown stuff can be faster: - if you already know exactly what data needs repli

Re: Out of Memory problem

Steve Loughran wrote: send it as an attachment. That works for files that size. base64 encoding is very slow as well as being inefficient; XML parsers dont like strings that size. Are we sure it's the XML parser thats at fault here? I'm a little interested in this one, as some of the stuff we d

Re: Web services configuration?

p-specific from there on. Cheers, Baz -Original Message----- From: Brian Ewins [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 8:39 AM To: [EMAIL PROTECTED] Subject: Re: Web services configuration? From the J2EE standpoint: As JAXRPC is part of the J2EE stack, you're supp

Re: Web services configuration?

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 anywh

Re: Axis client, OutOfMemoryException

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 thi

Re: gzip support

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 pr

Re: system specs needed

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 R

Re: & within a string / parser expects an entity reference

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");

SchemaVersion is broken was Re: Problems with PROP_SEND_XSI

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});

Re: Problems with PROP_SEND_XSI

what gets sent by Axis when you turn off PROP_SEND_XSI to show what's causing the problem (without your patching anything other than turning off the flag). Axis will still send types at times even with PROP_SEND_XSI false, because they're required by the SOAP spec. Think of it as controlling the se

Problems with PROP_SEND_XSI

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 is

Classloaders, jaxrpc, axis, log4j Re: log4j

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 an

Re: what the "wsdl" link is doing

This is just how the browsers react to seeing xml. It's nothing to do with axis. wsdl isnt really meant to be viewed this way by a human, its how other clients would grab the wsdl from your server. WRT the Opera crash, I notice from their build logs there were 'dom related crashes' in versions

Re: Integrating Axis with a web server

Jason D. Lee wrote: > I'd like to integrate Axis (or Tomcat, whichever is appropriate) with Apache > so that on my development system (Win2K), my web service is available as > long as my machine is on. I have Apache running as a service, and I'd like > to be able to avoid having the extra window

Re: UTFDataFormatException

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: http://soapclient.com/

Re: Solution: Problems logging with Log4j

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

Re: problem reading nested JAR files

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 'somedi

Re: WSDL2Java: FOO_Bar name is converted to FOOBar

Sure, I'll do it, I just thought you'd have wanted the thrill ;-) Ok, your bug is online here: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10375 -Baz [EMAIL PROTECTED] wrote: > Brian, > > I'm aware of the specification. The underscore character is mentioned there > explicit as the valid

Re: WSDL2Java: FOO_Bar name is converted to FOOBar

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 its

Re: How to get the returning message in plain XML?

Chris Haddad wrote: > Luoh - it might be. You need to post the 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 PRO

Re: Several SOAP body blocks - can Axis deal with it

Dittmann Werner wrote: > Hi all, > > according to the SOAP specs > > > The (SOAP Body) element MAY contain a set of SOAP body > blocks, each being an immediate child element of the > SOAP Body. > > > Axis (in RPC and/or doc/lit mode) processes (at least?) > one immediate child eleme

Re: complex types

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, d