Shawn Dahlen wrote:
I've spent the weekend perusing the source for prototype 2. I have
written down a number of thoughts and questions and look forward to
your feedback:
Shawn,
very good comments. see my replies below.
1) Could someone clarify the concept of a Phase and phase rules in
relation to a Handler chain? I looked at some server deployment
descriptors within test-resources, but found it rather vague. From my
understanding so far, at the global, transport, and service scope a
set of handlers may be defined for the in, out, and fault flows. Is
this correct?
i think phases are meant to be generalization of scopes
2) Modules. Do they represent a means to package a reusable handler
chain to be used by multiple services?
i think so.
Am I correct in understandingyes but that is yet to be seen how effective "handler modules" are for packaging purposes.
that implementations of WS-RM and WS-Security would use this mechanism
for packaging and deployment?
3) I've read through a few of the comments in this thread regardingi agree especially that i think AXIS2 should be flexible in choice of XML-Java data binding.
JAX-RPC. I for one am glad of the seperation the Axis team will be
pursuing. However, may I ask why the team members have negative
feelings against JAX-RPC (especially the early draft of 2.0)? I
personally would like the choice between a low-level messaging model
and a higher-level service abstraction. This is driven by my need to
access the XML payload for direct transformation to the end user. JAX-RPC 2 adds this capability, although I question the timeframe for
its release and its dependence on JAXB.
for example i would like to see to have first class support for XmlBeans.
4) It is of my opinion that the success of the service-orientedthere was an early decision that AXIS should be JDK 1.4 compatible however i think that as there are now available
concept will depend greatly on the the simiplicity of creating service
contracts (WSDL/XSD/Policy). There has been a great deal of promotion
of the "contract-first" design principle to ensure interoperability
between web service stacks. This approach allows the designer to
define extensible documents and messages and focus on the set of MEPs
a service may provide. However, writing the service contract is not a
simple feat when dealing directly with XML. Our team has used
XMLSpy's visual tools to generate the contract. What is the Axis2
team's thoughts on the use of metadata within code to represent a
contract, as an alternative means of contract creation? Also, what of
using metadata to define particular aspects (RM, Security) a service
may use? I understand that JSR-181 exists to address part of this
issue (although requiring J2SE 5). I guess I view this question in
light of the blog entry by Don Box on Service Contracts in Indigo.
bytecode weaver tools that can add and annotations and read them even in JDK 1.4 maybe we should
try to use such metadata.
for sure it makes programming much easier and code (almost) self describing when thoughtful
declarations are used.
5) I mentioned earlier that I had an interest in a low-level messaging
API. It certainly is not my place to question the naming conventions
of the classes, but I found the name 'Call' a bit akward as the
central class surrounding the low level API. I was picturing
something like SOAPClient or SOAPAgent. I apologize if I do offend
anyone on this matter, but I thought I should offer my two cents.
i think API issues need to be revisited.
thanks,
alek
Shawn Dahlen
On Thu, 10 Feb 2005 18:15:44 -0500, Shawn Dahlen <[EMAIL PROTECTED]> wrote:
Eran -
Thanks for the the quick tips. I was able to setup the Axis2 project with Eclipse in no time. I have been lurking for a few weeks now on the dev mailing list and wiki site to check out the progress you have all been making.
I have a great interest in a low-level SOAP-based messaging model, and will dive into your client API and have a look at its async capabilities. Time permitting, I will try to reply within a few days with some constructive feedback.
Shawn Dahlen
On Thu, 10 Feb 2005 16:22:33 +0600, Eran Chinthaka
<[EMAIL PROTECTED]> wrote:
Hi,
Some of you might be interesting in looking at Axis 2, and since the M1 release is coming, we really appreciate if you all can have a look at that.
So to do that, I thought of giving you some quick tips as how to set up the project.
1. Get a latest copy from https://svn.apache.org/repos/asf/webservices/axis/trunk/java/dev/scratch/pro totype2 (if you are a committer, there is a quite a bit of setting up SVN, if you have never accessed SVN before. Look at http://wiki.apache.org/ws/FrontPage/Axis2, section 1.11.1 for more details) This location of prototype two may change soon to main src tree at https://svn.apache.org/repos/asf/webservices/axis/trunk/java
2. Install Maven (you can download that from http://maven.apache.org/)
3. Go to the prototype2 folder in the command prompt and type "maven". This will automatically download all the jars, compile, test and build the system.
4. If you want to set up this in your favorite IDE: - for IntellijIDEA type "maven idea" (without quotes). This will generate IDEA .ipr, .iml and .iws project files
- for eclipse type "maven eclipse" (without quotes). This will generate project files for eclipse.
To see a list of goals in maven or to find other IDE support type "maven -g".
So you are done.
Have a nice time with Axis 2 code. ;)
Regards, Eran Chinthaka Lanka Software Foundation
-- The best way to predict the future is to invent it - Alan Kay
