Attachment data stored in ManagedMemoryDataSource is deleted (or at least
marked deleted), as soon as message has been serialized.
While in most cases you will not want to access the data after you have sent
out the message, why force a delete possibly too early?
In case where a service is trying
I have been playing with Attachment code trying to improve it a little, and
fill in the missing parts/TODOs.
Doing that I am not understanding 2 basic things in the design.
1) Why would you want to compile Axis without attachment support? Doing so
creates, in my opinion, unneeded code complexity
Let's say that Object had the attribute "abstract=true", then clearly the
Folder class should be generated since that would be the only type that
could
be instantiated and passed over the wire.
---
-Original Message-
From: RAMRAJ,ANUPRIYA (HP-Roseville,ex1) [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 13, 2001 11:21 AM
To: '[EMAIL PROTECTED]'
Subject: specify fault handlers/listeners in the AXIS deployment
descripto r ??
Hi,
With Apache Soap 2.1 , it was possible to specif
Muhammad,
Please make sure that you have a recent copy of Axis.
Here is the help text of the current tool:
$ java org.apache.axis.wsdl.Java2WSDL
Java2WSDL emitter
Usage: java org.apache.axis.wsdl.Java2WSDL [options] class-of-portType
Options:
-h, --help
print this messag
gdaniels02/02/04 16:38:54
Modified:java/src/org/apache/axis/deployment/wsdd WSDDService.java
WSDDDeployment.java
java/samples/echo deploy.wsdd
Log:
Don't actually require type mapping classes to be present at WSDD
construction time. Instead,
gdaniels02/02/04 16:37:42
Modified:java/src/org/apache/axis/encoding/ser ArraySerializer.java
Log:
OK, removeAttribute() just does NOT seem to be happy - keeps breaking
for me every time I run the functional tests within ant, but not from the
normal command line or within IDEA.
Muhammed,
This code has been re-architected, and I fixed this problem a while ago.
You may want to try a new version of Axis.
Thanks for the catch!
Rich Scheuerle
XML & Web Services Development
512-838-5115 (IBM TL 678-5115)
Title: WSDL2Java and xsd:simpleTypes
We're currently having issues with the way that wsdl2java handles simple types that are not enumerations.
Currently, a complex type defined as this:
is translated into this:
public class Ro
gdaniels02/02/04 15:34:10
Modified:java/src/org/apache/axis Constants.java
java/src/org/apache/axis/handlers JWSProcessor.java
java/src/org/apache/axis/transport/http AxisServlet.java
SimpleAxisServer.java
Log:
Improve customized
Hi Daniel,
This is a snapshot of your code from
org.apache.axis.wsdlgen.Emitter class:
/** Create a
PortType
* * @param def
* @param
binding
* @throws Exception
*/ private void writePortType(Defin
scheu 02/02/04 14:34:53
Modified:java/src/org/apache/axis/encoding/ser
Base64Deserializer.java
Log:
The following code was requested by Paul Mietz Egli.
SAX can break up values into 5k chunks. The
base64Deserializer is changed to collect all the dat
Tom, I think Richard's swayed me. I don't think it's a good idea to make
the rules complex. It should simply be "the service implementation is
named ServiceImpl." Period. If we add "unless
ends in Service, in which case it is Impl" then we lose
clarity.
With that said, I still don't particul
Russel,
You say "...But perhaps it SHOULD be generated because it COULD be used as
an Object?"
I say: "It SHOULD be generated because it WILL be used."
--
Sylvain
-Original Message-
From: Russell Butek [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 04, 2002 1:47 PM
To: [EMAIL P
Tom,
IMO, your statement is true except in the context of method overloading.
I am trying to find a reason why someone would define types while not
referring to them. The only one I see is for method overloading.
This being said, I don't see any harm in generating extra classes.
Certainly no
Hi,
I am using Java2Wsdl command line interface class
for generating WSDL file from a give class file. Is there any way I can restrict
some of the overloaded methods from being published in WSDL file. I mean if I
have a method foo() and another one foo(int) is there any way I can
restrict
gdaniels02/02/04 13:08:56
Modified:java/src/org/apache/axis/encoding/ser ArraySerializer.java
Log:
*sigh*
Still seemed to be problems with the removeAttr() call, this seems to
clear it up... apparently people's implementations of this (xerces vs.
crimson, etc) are a bit tou
rineholt02/02/04 12:19:06
Modified:java/src/org/apache/axis AxisEngine.java MessageContext.java
java/src/org/apache/axis/attachments
ManagedMemoryDataSource.java
java/src/org/apache/axis/server
DefaultAxisServ
[Crickets chirp]
Looks to still be a ways off... Please let us know when some details emerge.
Chris
-Original Message-
From: Chris Eppstein [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 01, 2002 1:06 PM
To: '[EMAIL PROTECTED]'
Subject: Beta?
My team is trying to decide between Axi
tomj02/02/04 11:39:56
Modified:java/src/org/apache/axis/wsdl/fromJava ClassRep.java
Log:
Walk up the inheritance heirarchy for classes and interfaces
when looking for methods. This supports the Stop Classes; classes
which teminate the lookup when encountered on the chain.
I would think that Folder should not be generated unless it is explicitly referenced.
If you needed code for a Folder type, you could always break out the types in to their
own file and feed them in to WSDL2Java. It would then generate code for all the types
given, given our hierarchy of refe
Folks in axis-dev, there's a discussion going on in axis-user about what
WSDL2Java generates. Given:
> >
> >
> > [...]
> >
> >
> >
> >
> >
> >
> >
> > [...]
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
Glyn,
Will EngineConfigurationFactory be a parameter to AxisEngine constructor? I'd say it
should (I'm just asking :), instead of the EngineConfiguration...
For example
Server application:
new AxisServer(MyEngineConfigFactory(...))
AxisEngine constructor:
AxisEngine(EngineConfigurationFactory
Glyn,
That is right engine does not call getConfig, although it does config.getHandler() for
instance, so that can be easily replaced with getConfig(versionStamp).getHandler().
I was thinking to establish an EngineConfigurationProvider interface that would define
getConfig(), getConfig(version
butek 02/02/04 08:25:11
Modified:java/src/org/apache/axis/wsdl/toJava JavaTestCaseWriter.java
Log:
The generated test cases now have one operation per method. The old one put
all operations in a single method. So if one operation failed, the test stopped.
Now
all operation
It's generated code. We are use to seeing "stupid names" coming from
generated code :-).
Seriously, when trying to figure out what the code generators are doing,
minimizing the variences in generated names seems like the best choice. A
"stupid" artificial name, yet no question on the intent or
Igor,
I'm a bit concerned that the engine would be using an interfaces which
gives the impression of delivering a particular version of a configuration
when the current configuration providers would not support this behaviour
and would ignore the version stamp. Wouldn't it be better to build
vers
butek 02/02/04 07:34:09
Modified:java/test/wsdl/filegen FileGenTestCase.java
Added: java/test/wsdl/clash VerifyFilesTestCase.java
java/test/wsdl/filegen README
java/test/wsdl/multibinding VerifyFilesTestCase.java
Log:
FileGenTestCase verifies
Good enough for me. There's still the possibility of name clashes, but I'm
not going to fret over it.
Russell Butek
[EMAIL PROTECTED]
Tom Jordahl <[EMAIL PROTECTED]> on 02/04/2002 09:20:32 AM
Please respond to [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc:
Subject: RE
Russell,
Is JAX-RPC 0.7 public yet? URL?
Thanks,
dims
--- Russell Butek <[EMAIL PROTECTED]> wrote:
> JAX-RPC 0.6 discussed generating a service interface and a service
> implementation. The interface was optional. In the interests of
> minimizing generated files, AXIS opted to NOT generate th
Currently, there is no standard way to obtain an engine configuration in
Axis. The result is quite a bit of duplicated code and an inability to
predictably override the defaults.
I'm working on a change to introduce an EngineConfigurationFactory
interface with a DefaultEngineConfigurationFactory
Here is a suggestion: Check for "Service" at the end of the name, and don't append it
if it's already there. This prevents the stupid name. Still avoids name clashes.
--
Tom Jordahl
-Original Message-
From: Russell Butek [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 04, 2002 10:0
JAX-RPC 0.6 discussed generating a service interface and a service
implementation. The interface was optional. In the interests of
minimizing generated files, AXIS opted to NOT generate the interface.
In JAX-RPC 0.7 the service interface is no longer optional. If the service
is named X, the se
+1
- Original Message -
From: Glen Daniels <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, February 04, 2002 3:49 PM
Subject: RE: Auto-generated test case question
>
> +1
>
> > -Original Message-
> > From: Russell Butek [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, Fe
gdaniels02/02/04 06:51:58
Modified:java/src/org/apache/axis Constants.java
java/src/org/apache/axis/handlers JWSProcessor.java
java/src/org/apache/axis/transport/http AxisServlet.java
SimpleAxisServer.java
Log:
Allow the system p
+1
> -Original Message-
> From: Russell Butek [mailto:[EMAIL PROTECTED]]
> Sent: Monday, February 04, 2002 9:21 AM
> To: [EMAIL PROTECTED]
> Subject: Auto-generated test case question
>
>
> There's a change I'd like to make to the auto-generated test
> cases. Right
> now they call al
Glyn,
How about a variation of your "Engine Replacement" based on EngineConfiguration
*versioning*. This can make it easy on the resources (won't require another Engine
instance) and simple for config providers. Here is how it would work:
When request first comes in:
- Engine calls getConfig(
+1
--
Tom Jordahl
Macromedia
-Original Message-
From: Russell Butek [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 04, 2002 9:21 AM
To: [EMAIL PROTECTED]
Subject: Auto-generated test case question
There's a change I'd like to make to the auto-generated test cases. Right
now they ca
There's a change I'd like to make to the auto-generated test cases. Right
now they call all operations from one method. The reason I'd like to
change this is that if any operation fails, the test stops. I'd like to
place each operation call into its own method so that all operations are
called
I was not able to bind a client to a service. Proxy generator complained about unknown
encoding used in the description.
It actually looks like it was/is Axis problem and not WSDL4J at all. (My fault :).
I have started moving up the nigthly builds befrore I hit this problem. I could not go
bey
40 matches
Mail list logo
