Igor,
Let's be clear: as things currently stand, changing the configuration of an
engine while requests are being processed can give unpredictable results
(like the case in your second paragraph below). This is not good.
The current notification mechanism (AxisEngine.refreshGlobalOptions)
prompt
http://www.javaworld.com/javaworld/jw-01-2002/jw-0125-axis.html
- Sam Ruby
Title: Log4J date in JAR file name
C'mon guys. I'm betting there's some good reason
why log4j.jar in the interim drops includes a date in the name. I'd just like to
hear what it is. Can someone please tell me?
If there is a good reason, why aren't other JARs
like clutil and wsdl4j dated? If
Title: Log4J date in JAR file name
Sam? Is this because we don't want to force people to move to an
un-"official" log4j release like 1.2? (that rationale doesn't actually
seem to work since the 1.2 classes will shadow the 1.1.3 ones if the new jar is
on the classpath first anyway)
There is a lot of code turning up in the tree with lines significantly longer than 80
characters. We do have a coding convention which says to break lines at column 79
We now return you to your regularly scheduled development conversation. :)
--G
glyn02/02/01 06:20:30
Modified:java/docs architecture-guide.html
Added: java/docs serclasses.jpg serfactoryclasses.jpg
typemappingclasses.jpg
typemappingregistryclasses.jpg
Log:
Describe encoding subsystem.
Revision C
Glen Daniels writes:
>
> Sam? Is this because we don't want to force people to move to an un-"official"
> log4j release like 1.2? (that rationale doesn't actually seem to work since the
> 1.2 classes will shadow the 1.1.3 ones if the new jar is on the classpath first
> anyway)
>
> Ori
Personally, I'd like to see a "checkpoint" nightly build which is built with exactly
the jars in lib/, and then a separate "bleeding-edge" build There have been
several occasions where we've wanted to switch to a nightly but had to rebuild
ourselves because we're locked to log4j-1.1.3. I
Glyn,
If you haven't heard this enough already, it is VERY COOL that you are doing this
documentation and architecture work for Axis.
A big +1 for Glyn for taking this responsibility.
--
Tom Jordahl
Macromedia
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sen
+1
--
Tom Jordahl
-Original Message-
From: Glen Daniels [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 01, 2002 9:44 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Log4J date in JAR file name
Personally, I'd like to see a "checkpoint" nightly build which is built with exactly
the jars
Hi folks:
Currently when we have a service which uses HashMaps, like the interop echo tests, the
WSDL that gets generated looks like this:
http://xml.apache.org/xml-soap";
xmlns="http://www.w3.org/2001/XMLSchema";>
http://util.java"; xmlns="http://www.w3
It is my belief that in addition to the SOAP standard, we need to document
a set of best practices and a create classification of errors that identify
potential interoperability issues. I jotted down some of my thoughts on
the subject and posted them at:
http://radio.weblogs.com/0101679/stor
Hi all,
following a short report about some tests done with JBoss-2.4.4 and
xml-axis (snapshot from January, 20 2002). The first goal was to get a
WSDL generated from an EJB interface (the remote EJB interface). The
second goal was to call methods of the remote EJB interface using SOAP
(JAX-RPC)
Tom,
Thanks! Glad to be of service, but it's not all altruistic -- I'm learning
more about SOAP by doing this than I did by just reading standards
documents.
Glyn
+1
I asked many moons ago if anyone was documenting the points of consensus
that this group comes to and received no answer. A "best practices" document
would be extremely helpful to those of use who don't have the luxury of
being able to spend our time following 100+ message threads on serializi
butek 02/02/01 07:39:18
Modified:java TODO.txt
Log:
Some updates to our TODO list.
Revision ChangesPath
1.13 +4 -3 xml-axis/java/TODO.txt
Index: TODO.txt
===
RCS file: /home/cvs/xml-
Sam,
Nice article!
The issue of complying with other standards (in respect of trailing zeros)
reminds me of the kind of problems that CORBA interoperation gets into.
It's not too hard to get interoperation at the level of IIOP, but when you
add security (CSIv2 etc.), transactions (OTS), and inte
I like! Now all it needs is a 'best practices' table summarizing it all.
Something like:
Practice Do's/don't's details
-
infinity use "INF"
precision stay within 18 digits
etc...
Russell Butek
[EMAIL PROTECTED]
tomj02/02/01 08:48:12
Modified:java/test/wsdl Wsdl2javaTestSuite.xml
Log:
Get the SalesRankNPrice .NET service from the net,
not from local file.
Revision ChangesPath
1.64 +6 -3 xml-axis/java/test/wsdl/Wsdl2javaTestSuite.xml
Index: Wsdl2javaTestSuite
Thanks Glen.
I'll clean these up as I make changes.
Rich Scheuerle
XML & Web Services Development
512-838-5115 (IBM TL 678-5115)
Glen Danie
I got Glen's example running eventually with help from Glen(thanks again).
However now i want to make changes to the Order in the BeanService and send
the object back.
However when i do that i get
"Error here Method names do not match
Body name = processOrder
Service name = processOrderResult
butek 02/02/01 09:55:18
xml-axis/java/test/wsdl/multibinding - New directory
butek 02/02/01 10:04:09
Modified:java/src/org/apache/axis/wsdl/toJava BindingEntry.java
JavaImplWriter.java JavaInterfaceWriter.java
JavaServiceImplWriter.java JavaSkelWriter.java
JavaStubWriter.java JavaTestCaseW
butek 02/02/01 11:58:47
Modified:java/samples/addr AddressBookSOAPBindingImpl.java
Log:
Use the thread-safe Hashtable instead of the unsafe HashMap so that the
multithread test doesn't intermittently fail.
Revision ChangesPath
1.10 +2 -2 xml-axis/java/sampl
My team is trying to decide between Axis and Apache SOAP 2.2 for our next
project. We'd like to use Axis but its current alpha status is a deterrent.
Is there a target date for Beta (functionally complete, APIs frozen)? I'm
not looking for an exact date, but a ball park figure would be very helpfu
I just downloaded Sun's wspack, it's a pretty impressive chunk of
code! I was surprised to see a reference implementation of JAX-RPC
that wasn't Axis. Anyone know where it comes from, how well it works?
I don't see it on White Mesa's interop matrix.
tomj02/02/01 14:46:13
Modified:java/src/org/apache/axis/wsdl/fromJava Types.java
Emitter.java DefaultBuilderPortTypeClassRep.java
DefaultBuilderBeanClassRep.java ClassRep.java
BuilderPortTypeClassRep.java
tomj02/02/01 15:17:17
Modified:java/src/org/apache/axis/wsdl/fromJava ClassRep.java
Log:
Back off on method inheritance change for the weekend.
Revision ChangesPath
1.10 +24 -0 xml-axis/java/src/org/apache/axis/wsdl/fromJava/ClassRep.java
Index: ClassRe
It's Sun's implementation. I haven't worked with it, so I can't tell you how
it works. We plan to give it some exercise in the next week or so.
Anne
> -Original Message-
> From: Nelson Minar [mailto:[EMAIL PROTECTED]]
> Sent: Friday, February 01, 2002 2:46 PM
> To: [EMAIL PROTECTED]
> Su
Nelson Minar wrote:
>
> I just downloaded Sun's wspack, it's a pretty impressive chunk of
> code! I was surprised to see a reference implementation of JAX-RPC
> that wasn't Axis. Anyone know where it comes from, how well it works?
> I don't see it on White Mesa's interop matrix.
It comes from Sun
What if I already have a WSDL as an XML document or in a file. Why would I want to
javax.wsdl it?
Current interfaces are flexible enough to accommodate all ways of generating or
receiving WSDL.
I'd suggest that current logic stays, but in addition it can take the new definition
and so the endp
Title: Axis and .NET inetrop failure due to WSDL4J!!
I was trying to consume some of the WSs exposed by latest Axis builds with an RTM VS.NET and wasn't able to do it because of:
http://www.w3.org/2001/06/soap-encoding
and
SOAP-ENC:string
These are the things generated by WSDL4J for the sake
32 matches
Mail list logo
