Actually, I don't think everything should be escaped all the time, really I don't. :)
I think there should be dumpToString() and dumpToSafeString(), i.e. two different
methods for two different bits of functionality, rather than an overload with a flag.
When not in an HTML/browser context (i.e.
Just fixed this. Thanks for the catch, Wes!
--Glen
> -Original Message-
> From: Wes Devauld [mailto:[EMAIL PROTECTED]]
> Sent: Friday, January 31, 2003 8:59 PM
> To: [EMAIL PROTECTED]
> Subject: org.apache.axis.client.Call
>
>
> I've been having a problem with Java Client Calls.
>
>
I've forwarded a note about this to the apache members list - will post back here with
the results of the discussion there.
--Glen
> -Original Message-
> From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED]]
> Sent: Monday, January 27, 2003 11:23 PM
> To: [EMAIL PROTECTED]; [EMAIL PROTEC
Hi Tim!
Yup, I think this is a bug.
If the schema for the message indicates the "arrayness" of the "obj" parameter comes
from a minOccurs/maxOccurs constraint rather than from SOAP encoding, then an array of
one value might look like this:
[example 1]
insert myobject1 here
and a larger
+1 to the concept
-0 to the implementation
Wouldn't it be clearer to call it dumpToEncodedString() or somesuch and avoid the
boolean arg?
--Glen
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 15, 2003 6:31 PM
> To: [EMAIL PROTECTED
Thanks for the fix, James!
However, um, wouldn't just adding "else { param = null; }" to the final if in the
earlier version have been a little simpler?
--G
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 15, 2003 5:05 PM
> To: [EMAIL
Should this be xml-axis/java/addons?
--Glen
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 15, 2003 12:23 AM
> To: [EMAIL PROTECTED]
> Subject: cvs commit: xml-axis/addons - New directory
>
>
> jmsnell 2003/01/14 21:23:19
>
>
> > Is it the responsibility of the commiters/maintainers or
> the reporter of
> > the bug (i.e. me) to close the report in bugzilla?
>
> If you close it, it says 'this is really closed for me',
> which adds a better
> check than 'I've added some code which may fix it', which is
> what anyone
ocument.
> In either case, it's pissing me off. :-) I'm going to grab a
> snack and
> keep digging.
>
>
>
> - James Snell
> IBM Emerging Technologies
> [EMAIL PROTECTED]
> (559) 587-1233 (office)
> (700) 544-9035 (t/l)
> Progr
Discovered this while playing with James' WSDL - new Service("file.wsdl", qname)
wasn't working. I think this fix does about the right thing, but please feel free to
comment if I've missed something.
--G
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent:
The type mapping defines "NasdaqQuote" as the local part of the *type* QName.
The "getPriceReturn" element name has nothing to do with the type mapping, that's the
default (operationName + "Return") for operations with no "returnQName" specified in
the WSDD. You can change it by adding to the
ffice)
> (700) 544-9035 (t/l)
> Programming Web Services With SOAP
> O'Reilly & Associates, ISBN 0596000952
>
> Have I not commanded you? Be strong and courageous.
> Do not be terrified, do not be discouraged, for the Lord your
> God
James:
It would be great if you could open up a new Bugzilla issue for each one of these
things, so we can track them and mark them fixed when they're resolved.
Thanks!
--G
> -Original Message-
> From: James M Snell [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 07, 2003 3:13 PM
t; the classpath.
> Ideally, there would be 'stable builds' that would contain
> the classes I
> needed already compiled.
>
> Does that make sense?
>
>
>
>
>
>
>
>
>
> Gle
ild
> from the source distribution.
>
> Thanks,
> Jaime
>
> -Original Message-
> From: Glen Daniels [mailto:[EMAIL PROTECTED]]
> Sent: Monday, January 06, 2003 2:14 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: JMS transport not in 1.1 binary distribution
Actually, I did (JRun's), and have no idea why it wasn't in there.
I'll rebuild and repost, though, as beta2. We should get 1.1 up to speed and out soon!
--Glen
> -Original Message-
> From: Tom Jordahl [mailto:[EMAIL PROTECTED]]
> Sent: Monday, January 06, 2003 2:11 PM
> To: '[EMAIL PR
Keep reading, Tom... :)
(Joe-Bob says "catch up on *all* the mail before you reply")
--G
> -Original Message-
> From: Tom Jordahl [mailto:[EMAIL PROTECTED]]
> Sent: Monday, January 06, 2003 11:54 AM
> To: '[EMAIL PROTECTED]'
> Cc: 'Rich Scheuerle (E-mail)'
> Subject: RE: Q. about equals
*** rubys has quit IRC (Read error: 110 (Connection timed out))
Or not... :)
Incidentally, Sanjiva and I are there on openprojects.net, and dims and I are both on
#ApacheAxis on undernet.
--Glen
> -Original Message-
> From: Sam Ruby [mailto:[EMAIL PROTECTED]]
> Sent: Monday, January 0
Yup, will try to look at this today.
> -Original Message-
> From: Davanum Srinivas [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 02, 2003 9:37 AM
> To: Russell Butek
> Cc: [EMAIL PROTECTED]
> Subject: GroupG Interop EchoAttachments problem.
>
>
> Russell, Glen,
>
> Can you PLEAS
The "strong technical reason to do so" was the fact that the name was extremely
confusing, in that the class had/has nothing to do with SOAP 1.2. It was misnamed at
the start, and we just ddn't get around to fixing it before 1.0. You bring up a valid
concern, but I believe this case was justi
Hi Rich!
Hm - I'm trying to imagine an example for when this would actually get used, and
having trouble coming up with one. Could you elucidate? I guess what I'm really
asking is why doesn't "if (this == obj) return true" catch this?
--G
P.S. Nice to see you back!
> -Original Message
Dims:
1) Way cool
2) Could you please please put a README.txt file in the transport/mail directory?
Thanks!
--Glen
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Friday, December 13, 2002 3:46 PM
> To: [EMAIL PROTECTED]
> Subject: cvs commit: xml-axis
Because it's not something everyone wants to do with Axis, it's an example of an
extension to Axis.
There's likely to be a lot more of this (we hope!) as we move into the future - Axis
is an etensible engine which can be used as-is or built out to provide more complex
functionality. We'd like
gt; SerializationContextImpl to use
> the same approach you implemented in
> DeserializationContextImpl. To be
> honest, I think just changing pop() to match the required usage is
> simpler and cleaner. :-)
>
> - Dennis
>
> Glen Daniels wrote:
>
> >Oh, I
ightsraw}=ns27
> {http://schemas.xmlsoap.org/soap/encoding/}=soapenc
>
> clearFrame() only goes until it sees a null - which it does
> immediately.
> The null is then removed by the top--.
>
> I'll verify that the problem still occurs in tonight's drop,
> and
rator;
> >
> > /**
> >* The abstraction this class provides is a push down
> stack of variable
> > @@ -79,7 +76,7 @@
> >* Accordingly, this stack is implemented as a single
> array, will null
> >* values used to indicate frame b
+1
> -Original Message-
> From: Davanum Srinivas [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 11, 2002 2:42 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Web Services top-level project (was Re: [AXIS/WSIF]
> proposed new WSIF home page URL)
>
>
> I agree. One community would be be
Paul:
Just for future reference, you can look in java/test-reports under your Axis root dir,
and you'll find the outputs from the various tests in there. If you sort them
most-recent-first, you can open up the top one and see what went wrong.
The current CVS source works fine for me too, I'd
I think I just fixed this with the NSStack update, but it looks like this test is
still producing bad XML (even though it passes). Looking into it.
--G
> -Original Message-
> From: Sam Ruby [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 11, 2002 8:28 AM
> To: [EMAIL PROTECTED]
:
>
>
> java.
> javax.
>
> Like I said, though, consistency is most important, so +1
> from me, even if
> you put javax before java.
>
> Russell Butek
> [EMAIL PROTECTED]
>
>
>
>
I'd like to officially nominate Jaime Meritt from Sonic as an Axis committer.
He's been doing great work on the async stuff (despite my not agreeing with all the
APIs :)), and has submitted good bug fixes.
I say we make it official, and I'll start with:
+1
--Glen
Axis-dev'ers:
I agree with this being an issue. Here's my suggestion.
I'll volunteer to do a single commit cleaning up all the imports in the project, using
IDEA. After that we can just be careful about introducing / removing imports
appropriately. IDEA will order the imports as follows:
Thanks James for slicing out the FeatureEnabled thing for now, I appreciate it.
While we're on the topic, I'll squirt out this very brief version of how I envision
this stuff working. A full understanding / explanation of this entails grokking the
SOAP 1.2 extensibility model, including URI-na
52
>
> Have I not commanded you? Be strong and courageous.
> Do not be terrified, do not be discouraged, for the Lord your
> God will be with you whereever you go.- Joshua 1:9
>
>
>
> Glen Daniels <[EMAIL PROTECTED]>
> 12/04/2002 11:31 AM
>
James:
Not to be a pest, but I believe I mentioned before I didn't think this interface was
adequate, and we clearly had some more thinking to do on this topic, a good bit of
which I've already done and would like to discuss BEFORE we do anything. I thought
you'd agreed to simply remove it fo
That begs the question. Are we using the logger to output the results of
AdminClient's list command? If so, why?
--Glen
> -Original Message-
> From: Tom Jordahl [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, December 03, 2002 5:00 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: annoying hype
Web site updated, release posted.
Have at.
Note that this is really just a beta - we do expect to do some more work in between
now and the official 1.1 release, which we expect sometime around the end of the year.
It's being released now to give people who want the fixes in the current source
*/
> -public Object getLockObject() {
> +public synchronized Object getLockObject() {
>if (rep == null) {
>rep = new Hashtable();
>}
>
>
>
> 1.2 +9 -5 xml-axis/java/test/concurrency/TestService.ja
They are indeed two separate issues. Eventually, I want to move most of the tests
which currently access a service across the net to be local "XML playback" tests, to
avoid problems with down servers / remote version skew /etc. However we'll always
have a need for interop tests, and so we'll
Hi Steve:
I'm not sure the thing is any worse than any number of other things you can
do with admin access. For instance, you could deploy the System class as a service,
and then invoke System.exit()
That said, I'm fine with the *.wsdl idea too.
--Glen
> -Original Message-
> Fr
Hi Jeremy:
When Axis was born it was meant to be multi-protocol, and the "core" architecture
(handlers, messages) was designed that way. Unfortunately, since we didn't have a
strong set of user requirements to support other protocols, a lot of SOAP-specific
warts ended up being bolted in to A
Incidentally, a wire trace of what's being sent looks like this:
POST /axis/services/AttachmentPortRPC HTTP/1.0
Content-Type: multipart/related; type="text/xml";
start="";
boundary=6580840.1038882258149.JavaMail.Glen.AURORA
Accept: application/soap+xml, application/dime, multipart/related, tex
Hi folks!
I'm having problems with the wsdl.attachments test with the current CVS. It was
throwing a "no such method" error, but that was because the real error was being
masked inside the MimeMultipartDataHandlerDeserializer. It seems to be actually
throwing "Missing start boundary" when ca
What do people think about a system property switch we can use to activate/deactivate
tests which are "bleeding edge"? Right now, we have tests (like TestCircularRefs and
test/wsdl/gateway) which are in the tree but test things which are currently known to
be broken. The way we deal with this
I'm going to be incommunicado for the first part of tomorrow (doctor's appointment and
a run to the airport), but I'm still planning to build + release 1.1 beta tomorrow
afternoon/evening.
--Glen
aight to final, something will burn
> us. Actually
> something will burn us no matter what, but that's just a fact of life.
>
> once a timeline is agreed, we should communicate to axis-user.
>
> - Original Message -
> From: "Glen Daniels" <[EMAIL PROTECTE
Hi folks!
Here's the chat log for today.
--Glen
Session Start: Tue Nov 26 11:29:59 2002
[12:52] *** kameshwar has joined #ApacheAxis
[12:53] hi all
[12:54] Hi kamesh
[12:55] I had sent a mail to the list askign about the future of the Async
support
[12:55] in Axis
[12:55] I got a reply fr
speak? I
> also anticipate
> that my employer's security policy blocks out IRC, but that's another
> matter....
>
> Thanks,
> Eric Friedman
>
> -Original Message-
> From: Glen Daniels [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, November 26, 2002 7:06
Hi folks!
I'd like to suggest that we restart weekly IRC chats. I know a lot of our core dev
team have been swamped lately with non-Axis committments, but I think just getting
together even briefly to talk in realtime about what's coming down the Axis pipe would
be as beneficial to us now as
Dims, a few comments about this:
The dataset in the WSDL for your dataset test contains an followed by an
, so it looks to me like we're picking up on the any and therefore making a
MessageElement[] in the generated types. This "any" ends up picking up both the
and the in the returned resu
+1 to both.
--Glen
> -Original Message-
> From: Davanum Srinivas [mailto:dims@;yahoo.com]
> Sent: Wednesday, November 13, 2002 4:06 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [VOTE] Re: XML Schema support for Axis (Contrib from
> Infravio)
>
>
> James,
>
> The VOTE was to whether accep
Hi Vidyanand!
> 1. The QualifiedName is there because after you do a
> XmlSchema.compile(..) all the Types are supposed to be obtained form
> XmlSchema.getSchemaTypes(). This would include any types from
> the schema
> that is imported. In this a localname alone is not
> sufficient. But this
>
Hi Vidyanand!
A few comments about this library, first a couple related to the code in particular,
and then one about the process of integrating it with Axis.
In general, this looks great. Questions:
1) Why bother to keep all the objects in an XmlSchema referenced by QualifiedName?
For a gi
Thanks, Dims!
What the heck is the point of getNamespacePrefixes(), anyway? Doesn't seem very
useful to me, unless you're trying to figure out a new prefix so it doesn't collide
with an already-mapped one. *shrug*
--Glen
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:dims@;a
FYI, I can't get onto DALNet today, so I'm hanging out on undernet (irc.undernet.org)
for now.
Dims,
I'm a little concerned about unnecessary object creations here - why not just fix the
problem by checking for null accurately everywhere? I'm not quite sure about the
tradeoffs involved between creating an empty ArrayList for every MessageElement vs.
null-checking.
--Glen
> -O
We now support anonymous schema types when generating WSDL. No more ">" QNames in the
WSDL, etc.
I forgot to note that another effect of the change was to pull some of the logic that
was in Types out into the individual serializers, to be more architecturally accurate.
This means that the En
This reminds me of a suggestion I wanted to make...
I believe our functional tests should not require an internet connection. We should
have all the WSDLs we care about locally available, pointing to local services, and we
should use recorded XML playback to mimic the external sites. In most
OK, back to this one. :) I'm not seeing this. Anyone else? Is this a bleeding-edge
gumpism?
--Glen
> -Original Message-
> From: Sam Ruby [mailto:rubys@;us.ibm.com]
> Sent: Monday, October 21, 2002 8:04 AM
> To: [EMAIL PROTECTED]
> Subject: [GUMP] Build Failure - Axis
>
>
> -
In the interests of simplifying things, can we remove the "force" option from
Call.registerTypeMapping()?
I don't see anywhere in the code that actually uses force=false, which would seem to
defeat the purpose of registering a type mapping at all. If you're concerned about
overwriting some ex
Hit return too soon - also wanted to mention in the comments that I unwrapped all the
RemoteExceptions in the RoundtripTestServiceTestCase, to get more informative errors
bubbled up through junit if they occur.
--Glen
contains information specific to the fault in question, and sometimes the
package that created it. In this case, the stack trace is just a standard Java
printStackTrace() output, and anyone who cares to look for the element
can get at it. We've discussed putting in a switch to turn this on
-Original Message-
From: Ben Souther [mailto:bsouther@;fwdco.com]
Sent: Wednesday, October 16, 2002 11:33 AM
To: [EMAIL PROTECTED]
Subject: Re: Is there a 'thinner' client runtime?
It would be nice to see the client and server broken down into separate jar
files. I'm calling webservic
...and Steve's response. Just wanted to put this thread over here too in case anyone
else is as backed up on axis-user as I am. :(
--Glen
-Original Message-
From: Steve Loughran [mailto:steve_l@;iseran.com]
Sent: Wednesday, October 16, 2002 4:06 PM
To: [EMAIL PROTECTED]
Subject: Re: Is
I'm going through various bits of Call/MessageContext and I'm wondering why Call,
MessageContext, *and* OperationDesc all have use/style fields? Can we just coalesce
all of these to be the OperationDesc, since both the Call and the MC are going to have
an OperationDesc, and the info just gets
Doug:
Take a look over the code I just submitted - I believe it fixes the locking problem
you were having. Let me know what you think.
--Glen
> a playback server would be good, but since stage 2 of .net
> testing is to to
> do .net client, you still need install the framework.
We can also trivially make up any given message and send it to our server (i.e.
test.put).
> Complex tests are anything that test round tripping, or
> parti
Their tests were run back in May. We've had several multiples of performance
improvement since then. It would be interesting to run them again against the current
codebase.
--Glen
> -Original Message-
> From: Douglas Bitting [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 15, 20
Hi folks!
As discussed last week both on the list and in person with Sam & Tom, I'd like to
switch the stubs back to the way they used to be, namely each stub having a single
Call object which gets reused. So multiple threads can share a Service/Locator, but
each stub should only be used by
While it's certainly a great thing to be able to set up local .NET tests, I added a
"playback" handler today which can fill the role of the server for simple
"one-roundtrip" tests, simulating whatever response we desire. I'd like to filter the
tests into "simple" and "complex" ones, where the
> sync will sync on something that is local (or specific) to the service
> itself (the String object I created). I don't see what the
> problem is. I
> never sync the hashtable - I sync the session and then I sync the lock
> object. Man - I wish I could get on irc g
>
> Locking the String or Object that is placed in the hashtable
> will do it
> since that is presistent across all threads - and it doesn't
> really matter
> which kind of Object it is - we just need something/anything
> to sync on.
The problem is that you want only one thread to be the one th
Could you describe exactly what's happening when you have problems? I'm assuming it's
a deadlock situation, but I'm not sure I understand it - and in fact I think I see a
bug in the current code. The lock is on the Session object (i.e. the AxisHttpSession
for HTTP). It looks to me like ther
> It looks like (according to cvs) you added the sync blocks in
> JavaProvider and its cause use some problems.
> I'm trying to understand why those sync blocks were added.
> From what I can
> tell they don't prevent multiple threads from clobbering each others
> service object that's stored
Definitely. The key would be to make setProperty() work as expected - I'd deprecate
setScopedProperty() but leave it functional for now.
I'll see about doing this later today barring negative feedback.
--Glen
> -Original Message-
> From: Doug Davis [mailto:[EMAIL PROTECTED]]
> Sent:
Can we merge these two back together? I think the reason they were split out was
something to do with TCK compliance, but I can't see how that would be affected by
whether or not Call properties are available via the MessageContext.
Call.setProperty() should do what it used to, namely make pr
not.
>
> I also like the idea of a setHeader/getHeader API on the Call.
> I would think this would be a much more flexible design then
> adding the headers to the functional signature.
>
> Wouldn't the work be much simpler and more straightforward going this
> directio
Sorry I wasn't available earlier, there is no network connection available from the
interop - this means I also won't be around on Wednesday until late in the afternoon.
> This work contains:
> * Better rpc/literal support in the emitters and
> runtime...as described
> in previous notes.
I4 is now merged over to HEAD, ant clean all-tests passed multiple times.
The last problem was with the terra test - which I think is a bad test as it stands,
because it relies on broken behavior to "succeed". We get XML back with a value of an
type and try to deserialize it - the test was f
I think the type test failure is because there is some rpc/literal stuff
(elemWComplex) mixed in with the RPC/enc stuff, and we're being more sensitive to that
now. Rich's RPC/lit changes may well fix that.
I'm curious about the "helper class" comment too - could you explain in more detail,
My apologies, guys, but -1 for the moment.
I wrote up a big note on this last week and then Outlook crashed and ate it, and I
haven't yet had the time to redo it.
Here's the basics. I'm unconvinced that it is appropriate to change the generated API
for methods in the WSDL to include headers
We didn't want to get in anyone's way while we worked, especially in that we were more
concerened about passing the interop tests than keeping all-tests running.
At this point we're much more fault-functional on the interop4 branch, but there are
still a few of the functional-tests which we do
+1
I'd like to see the docs worked over a bit more, but I don't want to hold the release
for it.
Ship it, on to 1.1!
--G
> -Original Message-
> From: Sam Ruby [mailto:[EMAIL PROTECTED]]
> Sent: Monday, October 07, 2002 8:33 AM
> To: [EMAIL PROTECTED]
> Subject: [VOTE] axis 1.0 releas
:)
> - * This is a single threaded implementation of an HTTP
> server for processing
> + * This is a simple implementation of an HTTP server for processing
Hi Rich!
I haven't had a chance to review the code yet, but the description below sounds great.
My only concern is the connection between multirefs and encodingStyle - there might
be other encodingStyles which people come up with (Use.ENCODED?) which don't support
multi-ref. I'd been thi
+0,
I'm fine with it if others are.
-Original Message-From: Rick Rineholt
[mailto:[EMAIL PROTECTED]]Sent: Thursday, October 03, 2002 11:04
AMTo: [EMAIL PROTECTED]Subject: Re: [VOTE] Bug
13242 merged into 1.0Since this is not a main line feature the risk to the product
st
> -0. We only look like dorks NOW that we looked at some new
> WSDL. NOBODY
> complained to us about this in the past, so only folks who
> look at this new
> WSDL will think we're dorks (OK, so perhaps these are
> important people,
> that's why I didn't vote -1
All - this is a serious bug, and I think it merits the "we'll look like dorks if it's
not fixed" label. It changes nothing except that bindings which aren't explicitly
referenced (i.e. SOAP 1.1) are ignored when generating code. This means that we won't
mistakenly generate mismatched interfa
Note that Tom just forked an "interop4" branch, which we'll be using to do hot 'n
heavy interop work on this week and next. Once things settle down there and 1.0 goes
out, we plan to move all the fixes from interop4 over to HEAD. Anyone working on
interop stuff is more than welcome to check
+1
> -Original Message-
> From: Doug Davis [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 01, 2002 12:32 PM
> To: [EMAIL PROTECTED]
> Subject: [VOTE] bug 13149/client needs servlet.jar merged into 1.0
>
>
>
>
>
>
>
> I'd like to see this fix go into the v1.0 branch, w/o clien
+1
> -Original Message-
> From: Russell Butek [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 01, 2002 10:35 AM
> To: [EMAIL PROTECTED]
> Subject: [VOTE] merge terra service test case change into 1.0
>
>
>
>
>
>
> I suggest that we put this patch into the 1.0 branch. The
> te
Anyone else seeing this on their machines, or might this be a bleeding-edge gump
thing? I'm not seeing it myself...
--Glen
> -Original Message-
> From: Sam Ruby [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, September 29, 2002 6:53 AM
> To: [EMAIL PROTECTED]
> Subject: [GUMP] Build Failur
Check it out!
-Original Message-
From: SP [mailto:[EMAIL PROTECTED]]
Sent: Saturday, September 28, 2002 8:17 PM
To: [EMAIL PROTECTED]
Subject: Web services Management Tool for Axis
Hi,
I have developed a sort of Web services Management tool for Apache Axis. I
am releasing a beta1 vers
Unfortunately, most of the recent ones have, IMHO, been in that category. :/
--G
> -Original Message-
> From: Sam Ruby [mailto:[EMAIL PROTECTED]]
> Sent: Friday, September 27, 2002 5:27 PM
> To: [EMAIL PROTECTED]
> Subject: Re: rc2 status
>
>
> Richard Sitze wrote:
> > +1 to releasin
> As for static methods on the real object, as long as they
> don't have any
> state then that's fine, but proper programming style isn't
> something we can
> enforce anyway. All we have to do is hide the skeleton methods.
Right, and I've implemented that but I'm running into issues testing ri
>
>
>
> I thought we had agreed at one point that static methods SHOULD be
> excluded. They're certainly not part of traditional beans.
>
> Russell Butek
> [EMAIL PROTECTED]
>
>
> Glen Daniels <[EMAIL PROTECTED]> on 09/26/2002 05:10:39 PM
>
The plan is to continue rolling in changes that have been voted on into the 1.0
branch, so the 1.0 final release will likely still have a few more fixes/changes after
rc2.
--Glen
> -Original Message-
> From: David Chappell [mailto:[EMAIL PROTECTED]]
> Sent: Friday, September 27, 2002
> Glen> How could that possibly make any sense? If you have a type
> Glen> which you are never going to be able to receive, what good
> Glen> does it do to put an "anyType" placeholder there?
>
> We've registered a custom serializer for Locale. Although we don't
> pass it as a param
this behavior should be addressed post 1.0.
>
> Rich Scheuerle
> IBM WebSphere & Axis Web Services Development
> 512-838-5115 (IBM TL 678-5115)
>
>
>
>
WHOA!
Why do we WANT anyType appearing anywhere for this? IMO, we don't.
If you have myop(Object obj), THAT should generate anyType, because we have a mapping
for Object<->anyType in the registry. Then at runtime, we're free to do something
like:
if (obj instanceof SomeClassIHaveAMappi
1 - 100 of 444 matches
Mail list logo
