Re: deploy problem. would notwork.

I could imagine scenarios where each of the alternative behaviours is acceptable. Allowing existing sessions to continue while preventing new sessions from starting is less disruptive to clients and would allow a server to be 'quiesced' once the number of existing sessions had decreased to zero. O

Interceptor architecture?

Hi, I was wondering how easy it would be to incorporate an interceptor system into axis, or whether anyone else was already considering doing so? The problem I am trying to solve is as follows: We are a research institute, and as such consist of many different groups, these are almost totally

JAXM to-do

Tom, I noticed a to-do item with your name against it: "We do not emit SOAPElement arguments per JAX-RPC yet." I'm currently plumbing in some of the javax.xml.soap interfaces into the org.apache.axis.message package which includes making MessageElement implement SOAPElement. What else would you

RE: Question and a Suggestion

James, Currently you can get around this by specifying the system property "axis.EngineConfigFactory" and providing your own Configuration implementation. ServletEngineConfigurationFactory getServerEngineConfig(ServletContext ctx) checks for a EngineConfigurationFactory instance, if one is avail

RE: Bean Class/Bean Class Helper Generation

Yeah, the proliferation of files DOES worry me. Perhaps whatever solution we end up with should continue along the path you set? Right now the meta-data ONLY exists if we have attributes, so whether it's inline or outline, the meta data will only be generated when we need it (though I fear we'll

cvs commit: xml-axis/java/src/org/apache/axis/encoding/ser BeanDeserializer.java

dims02/03/12 05:47:54 Modified:java/src/org/apache/axis/encoding/ser BeanDeserializer.java Log: Need this fix to get our WSDL2Java generated code to work with Microsoft's "C# DataTypes.asmx" Web Service sample. Revision ChangesPath 1.12 +6 -4 xml-axis/jav

RE: Bean Class/Bean Class Helper Generation

Hi Russell! > Yeah, the proliferation of files DOES worry me. Perhaps > whatever solution > we end up with should continue along the path you set? Right now the > meta-data ONLY exists if we have attributes, so whether it's inline or > outline, the meta data will only be generated when we nee

Re: Interceptor architecture?

Tom, read the handlers section of the architecture guide. Your solution might be to implement a handler. Russell Butek [EMAIL PROTECTED] Tom Oinn <[EMAIL PROTECTED]> on 03/12/2002 03:09:58 AM Please respond to [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:Interceptor architectur

RE: cvs commit: xml-axis/java/src/org/apache/axis/encoding/ser BeanDeserializer.java

Hi dims! I think we can actually remove the get(localName) clause entirely, and just use the xmlNameToJava() version. --G > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, March 12, 2002 8:48 AM > To: [EMAIL PROTECTED] > Subject: cvs commit: xm

RE: cvs commit: xml-axis/java/src/org/apache/axis/encoding/ser Be anDeserializer.java

Ok by me. Thanks, dims --- Glen Daniels <[EMAIL PROTECTED]> wrote: > > Hi dims! > > I think we can actually remove the get(localName) clause entirely, and just use the > xmlNameToJava() version. > > --G > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] >

RE: Interceptor architecture?

Hi Tom! What you're proposing is precisely the point of the whole Axis Handler system. Axis allows you to specify per-service or global "request flows" which are Handlers that get access to the current message processing context (represented by a MessageContext object) and are free to read/ed

[GUMP] Build timed out - Axis

This email is autogenerated from the output from: Buildfile: build.xml setenv: [mkdir] Created dir: /home/rubys/jakarta/x

RE: Bean Class/Bean Class Helper Generation

> P.S. What do you mean the equals method "needs work"? > I think its pretty good for getting whipped off in 10 minutes at the interop. > :-) Then you can fix it up to make it work correctly for array components. I already fixed the potential NPE problems. Rich Scheuerle XML & Web Services Dev

RE: Bean Class/Bean Class Helper Generation

Glen, I think we're talking about 2 different types of developers, here: - the ones that know what they're doing and want to get their grubby paws in the dirt of ser/deser. - the ones that use axis just to get their real job done (I believe the greatest number of AXIS users will be in this group)

RE: Bean Class/Bean Class Helper Generation

The intent of the Helper class is to provide the necessary flexibility to use alternate meta data models and custom serialization. -- Let's use Doug's case as a scenario. I am not sure how one would populate the BeanInfo class wi

RE: Proposed change for RPCProvider.java for Beta 1

HI! Thanks for committing my change. There is one problem though: We need the "throws Exception" in the signature of the getMethod() method, as it was in my proposal. Could you change that? Thanks! Regards, Thomas > -Original Message- > From: Thomas Börkel > Sent: Freitag, 8. Mä

Re: Interceptor architecture?

Glen Daniels wrote: > > Hi Tom! > > What you're proposing is precisely the point of the whole Axis Handler system. > > Axis allows you to specify per-service or global "request flows" which are Handlers >that get access to the current message processing context (represented by a >MessageCon

RE: Bean Class/Bean Class Helper Generation

First off, I wouldn't in any way characterize this with phrases like "grubby paws" and "muck", especially if we do it cleanly. :) I also think there's a huge difference between the ease of writing a custom serializer/deserializer (two classes, deep understanding of SerializationContext/SAX ev

duplicate element name in different complexType elements.

This WSDL: http://services.xmltoday.com/vx_engine/wsdl.vep?flight.wsdl Gives this error: java.io.IOException: urn:vgx-flight:return already exists The error is correct, there are two instances of "return" in the same namespace, but they are in different complexType declarations. I

RE: Bean Class/Bean Class Helper Generation

The Helper class concept may be familiar to those who have used CORBA. The Helper class provides implementation specific type information and serialization assistance. Decoupling the Helper and Bean classes allows the code to migrate in a semi-independent fashion. This is important if additional

RE: Bean Class/Bean Class Helper Generation

Will attempt to respond to the rest of this later, but this comment stands out: >The use of a alternate meta models reduces the risk of Axis being >married to a particular model or implementation. I am not against >having default meta models, but the use of a particular > model in

RE: Bean Class/Bean Class Helper Generation

Please interpret the -1 in the same way you interpret a +1 for agreement. +1 are used with frequency, there is nothing bad about a -1 (at least the way I understand it). We do have a sharp disagreement about where the Metadata should go. Glen an I think it should stay where it is (mostly). I am

Re: duplicate element name in different complexType elements.

Tom, Ouch! The problem is that the embedded return elements both have anonymous types. The emitter needs to generate a name for the anonymous types, so it chooses the most reasonable name (return). This results in a collision. Brainstorming.. 1) I like the fact that we use the name "retu

cvs commit: xml-axis/java/test/wsdl/datatypes - New directory

dims02/03/12 08:08:04 xml-axis/java/test/wsdl/datatypes - New directory

RE: duplicate element name in different complexType elements.

+1 on number two. I like detecting the collision and munging the name. +1 on waiting to make them inner classes. :-) -- Tom Jordahl -Original Message- From: R J Scheuerle Jr [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 12, 2002 11:03 AM To: [EMAIL PROTECTED] Subject: Re: duplicate

cvs commit: xml-axis/java/test/wsdl/datatypes DataTypes.wsdl DataTypesTestCase.java DataTypes_BindingImpl.java

dims02/03/12 08:13:37 Modified:java/test/wsdl Wsdl2javaTestSuite.xml Added: java/test/wsdl/datatypes DataTypes.wsdl DataTypesTestCase.java DataTypes_BindingImpl.java Log: Equivalent for DataTypes Sample in .NET Framework SDK Revision Changes

RE: Bean Class/Bean Class Helper Generation

> Please interpret the -1 in the same way you interpret a +1 for agreement. > +1 are used with frequency, there is nothing bad about a -1 (at least the > way I understand it). Generally speaking, -1 in code discussions at Apache is to be interpreted as a solid veto. Generally, people are use "-

cvs commit: xml-axis/java/src/org/apache/axis/wsdl Java2WSDL.java

tomj02/03/12 08:22:40 Modified:java/src/org/apache/axis/wsdl Java2WSDL.java Log: Patch from Bob Cotton [[EMAIL PROTECTED]]: Java2WSDL ignoring -P/--portTypeName not used Revision ChangesPath 1.10 +4 -0 xml-axis/java/src/org/apache/axis/wsdl/Java2WSDL.j

RE: PATCH Java2WSDL ignoring -P/--portTypeName not used

Thanks Bob, I submitted this. -- Tom Jordahl Macromedia -Original Message- From: Bob Cotton [mailto:[EMAIL PROTECTED]] Sent: Friday, March 08, 2002 3:56 PM To: [EMAIL PROTECTED] Subject: PATCH Java2WSDL ignoring -P/--portTypeName not used cvs server: Diffing xml-axis/java/src/org/ap

cvs commit: xml-axis/java/src/org/apache/axis/wsdl/toJava JavaWriter.java

butek 02/03/12 08:34:54 Modified:java/src/org/apache/axis/wsdl/toJava JavaWriter.java Log: Change generated comments from //-style to javadoc-style. Revision ChangesPath 1.7 +3 -1 xml-axis/java/src/org/apache/axis/wsdl/toJava/JavaWriter.java Index: Java

RE: Bean Class/Bean Class Helper Generation

What does -1 mean in the context of design discussion? Same thing? -- Tom -Original Message- From: Sam Ruby [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 12, 2002 11:15 AM To: [EMAIL PROTECTED] Subject: RE: Bean Class/Bean Class Helper Generation > Please interpret the -1 in the sa

RE: JAXM to-do

Glyn, The JAX-RPC spec uses some of the JAXM data types (i.e. SOAPElement). See section 6.4.1, 6.4.2 and the example in section 6.4.3 of JAX-RPC version 0.7. In a nutshell, for literal use, if there is "no standard mapping for an XML schema type" a SOAPElement is used as the argument and retur

cvs commit: xml-axis/java/src/org/apache/axis/wsdl/fromJava ClassRep.java

gdaniels02/03/12 09:41:06 Modified:java/src/org/apache/axis/utils JavaUtils.java java/src/org/apache/axis/wsdl/fromJava ClassRep.java Log: Move getParameterNamesFromDebugInfo() into JavaUtils so it can be accessed by others, and make the cache a Hashtable for thread

cvs commit: xml-axis/java/lib excalibur-cli.LICENSE excalibur-cli.jar clutil.LICENSE clutil.jar

butek 02/03/12 09:44:16 Modified:java axis.properties build.xml java/docs developers-guide.html user-guide.html Added: java/lib excalibur-cli.LICENSE excalibur-cli.jar Removed: java/lib clutil.LICENSE clutil.jar Log: Excalibur changed their clutil.

RE: cvs commit: xml-axis/java/lib excalibur-cli.LICENSE excalibur-cli.jar clutil.LICENSE clutil.jar

ARGH! Can we leave this for the beta??? This is going to really screw things up for anyone who puts things in their classpaths, copies jars, etc. etc. I vote we make this change after the beta, please. --Glen > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]

cvs commit: xml-axis/java/src/org/apache/axis/providers/java RPCProvider.java

dims02/03/12 11:02:31 Modified:java/src/org/apache/axis/providers/java RPCProvider.java Log: Forgot one change needed by Thomas (http://marc.theaimsgroup.com/?l=axis-dev&m=101594652802276&w=2) Revision ChangesPath 1.47 +1 -0 xml-axis/java/src/org/apache/a

cvs commit: xml-axis/java/src/org/apache/axis SOAPPart.java

gdaniels02/03/12 11:04:21 Modified:java/samples/transport/tcp TCPListener.java java/src/org/apache/axis SOAPPart.java Log: Throw faults which occur during serialization, instead of making the SOAPPart's value equal to the serialized fault. Revision Changes

[PATCH] MessageElement value serialization, etc

This is the patch we were talking about in chat. set/getValue changed to set/getObjectValue() -Taras SOAPHeader.java Description: Binary data MessageElement.java Description: Binary data Constants.diff Description: Binary data

cvs commit: xml-axis/java TODO.txt

butek 02/03/12 11:20:01 Modified:java TODO.txt Log: Added a "MUST DO FOR BETA 1" section. Revision ChangesPath 1.18 +9 -0 xml-axis/java/TODO.txt Index: TODO.txt === RCS file: /home/c

Beta 1 status

During our weekly chat we came up with a number of issues for the beta. We added a "MUST DO FOR BETA1" section to our todo.TXT file. As of now, that list is (NOTE THE 3RD ITEM! That's something everyone can help with. Look at the published interfaces section of the User's Guide): ! Doug's is

cvs commit: xml-axis/java/test/wsdl/datatypes DataTypesTestCase.java

butek 02/03/12 12:45:05 Modified:java/test/wsdl/datatypes DataTypesTestCase.java Log: Fixed the test to work with the actual generated files. Revision ChangesPath 1.2 +12 -12xml-axis/java/test/wsdl/datatypes/DataTypesTestCase.java Index: DataTypesTestCas

cvs commit: xml-axis/java/samples/stock GetQuote.java

dug 02/03/12 13:00:34 Modified:java/samples/stock GetQuote.java Log: Make error message go to the screen instead of some mystery log file that newbies will never find. Revision ChangesPath 1.38 +1 -1 xml-axis/java/samples/stock/GetQuote.java Index: G

cvs commit: xml-axis/java build.xml axis.properties

butek 02/03/12 13:01:51 Modified:java build.xml axis.properties Log: Backing out the excalibur-cli changes. Revision ChangesPath 1.123 +5 -5 xml-axis/java/build.xml Index: build.xml ===

cvs commit: xml-axis/java/docs user-guide.html developers-guide.html

butek 02/03/12 13:03:16 Modified:java/docs user-guide.html developers-guide.html Log: Backing out the excalibur-cli changes (forgot to update the docs). Revision ChangesPath 1.43 +1 -1 xml-axis/java/docs/user-guide.html Index: user-guide.html =

Re: cvs commit: xml-axis/java/samples/stock GetQuote.java

I'd like to raise this as an issue - not sure whether or not its worth stopping the beta or not (probably not) but I do think that if this is not fixed a lot of newbies will be very very confused. Right now we seem to log almost everything. This change is an example of how something that should

Recent change to stock/GetQuote.java

I can understand your desire to see this for your immediate purposes, but this solution is counter productive when you integrate AXIS into a production environment or product. If you prefer, I would be happy to enable DEBUG output to an "axis.log" file, but not to the screen (Rich, who sits some

cvs commit: xml-axis/java/lib clutil.LICENSE clutil.jar excalibur-cli.LICENSE excalibur-cli.jar

butek 02/03/12 13:25:53 Added: java/lib clutil.LICENSE clutil.jar Removed: java/lib excalibur-cli.LICENSE excalibur-cli.jar Log: Sheesh! Backing out my changes, I forgot these! Time to hang it up for the day! Revision ChangesPath 1.3 +0 -0 xml-axis

cvs commit: xml-axis/java TODO.txt

butek 02/03/12 13:29:15 Modified:java TODO.txt Log: Doug's issue #2 is fixed. Revision ChangesPath 1.19 +0 -1 xml-axis/java/TODO.txt Index: TODO.txt === RCS file: /home/cvs/xml-axis/

Re: cvs commit: xml-axis/java/samples/stock GetQuote.java

I could be convinced that command-line tools should dump to stderr. However, by logging we CAN capture the problem for review without re-running a test. Regardless, the internal AXIS runtime should always log and/or throw an exception; it should NEVER write to stdout/stderr. I recognize that at

RE: Recent change to stock/GetQuote.java

While there are many places in the system where people integrating Axis will want to be using logging, there are also many places (esp the samples) where there are end users directly using Axis clients. I agree with Doug that it's kind of silly for those people to have to change their log4j c

RE: Recent change to stock/GetQuote.java

my comments below *** Richard A. Sitze[EMAIL PROTECTED] CORBA Interoperability & WebServices IBM WebSphere Development

RE: Recent change to stock/GetQuote.java

Richard, As Glen said there are plenty of places (like internal to axis) where logging makes the most sense. But I would claim that in things like the samples and AdminClient when we're in the "main" method people are 99% of the time going to be running it from the command line. So, running som

RE: Recent change to stock/GetQuote.java

+1 No logging for main()/command line code. -- Tom Jordahl -Original Message- From: Doug Davis [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 12, 2002 5:04 PM To: [EMAIL PROTECTED] Subject: RE: Recent change to stock/GetQuote.java Richard, As Glen said there are plenty of places

RE: Recent change to stock/GetQuote.java

Of course you realize that the default behavior is that a log file is NOT generated. I would be happy to adjust the properties file to (by default) to produce axis.log in the current directory. I'll make this change in the morning unless I hear descenting votes tonight... Regardless, I agree: m

RE: Recent change to stock/GetQuote.java

Changing the behavior so that it produces a file in the current directory is fine only as long as it logs only when its supposed to log. If for example, I run some of the samples it should *not* produce a log file by default. Unless I turn on some debug logging I would expect all output to go to

RE: duplicate element name in different complexType elements (I have a fix..shouldI commit for beta?)

I have a fix in my sandbox that fixes the problem presented by Tom. The fix also has improves the way root elements are handled, per chat dialogue with Glen last week. I feel confident in the fix, should I go ahead and commit it. (I will assume that no response means yes.)

Stress-testing the client

I have found a very peculiar behavior when heavily stressing the Axis client library.    After around 950 consecutive calls, I start to get a “java.net.ConnectException: Operation timed out: connect”    The strange thing is that the service side is fine.  If I stop the client and run it

Problem with WSDD Type Mapping

The following is a note from Thomas Sandholm. Looks like there may be a problem in wsdd type mapping ? -- Rich, I just tested the stuff, and it seems to work for me. The shared typemappings still have one problem, though. The problem I'm still seeing is that I can't add seri

cvs commit: xml-axis/java/src/org/apache/axis/utils resources.properties

gdaniels02/03/12 21:18:06 Modified:java/test/wsdl Wsdl2javaAntTask.java java/src/org/apache/axis/wsdl WSDL2Java.java java/src/org/apache/axis/utils resources.properties Log: Introduce a timeout (defaulted to 45 seconds) on the WSDL2Java emitter. This

cvs commit: xml-axis/java/src/org/apache/axis/client Call.java

gdaniels02/03/12 22:02:46 Modified:java/test/encoding TestArrayListConversions.java java/src/org/apache/axis/client Call.java Log: Add a convenience API to Call to allow specifying a desired return type (i.e. Java class) to which we will attempt to convert the resul