Guys, I've tried to hit the nightly build after two weeks and found some dreastic
changes in the deployment architecture. I've been using previous deployment facilities
to dynamically configure the axis pipeline at runtime.
It seems like we're getting away from DeploymentRegistry abstraction, and towards the
EngineConfiguration interfaces. It looks much better than before...
Could you possibly refresh me on
1. when the changes to the deployment architecture started happening?
2. what was the underlying intention?
Thanks.
-- Igor Sedukhin .. ([EMAIL PROTECTED])
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 31, 2002 4:11 PM
To: [EMAIL PROTECTED]
Subject: cvs commit: xml-axis/java/src/org/apache/axis/deployment/wsdd
WSDDDeployment.java
gdaniels 02/01/31 13:10:32
Modified: java/src/org/apache/axis/deployment/wsdd WSDDDeployment.java
Log:
Add getWSDDService() method (should add others, i.e. getWSDDHandler()
as well)
Revision Changes Path
1.20 +8 -0
xml-axis/java/src/org/apache/axis/deployment/wsdd/WSDDDeployment.java
Index: WSDDDeployment.java
===================================================================
RCS file:
/home/cvs/xml-axis/java/src/org/apache/axis/deployment/wsdd/WSDDDeployment.java,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- WSDDDeployment.java 30 Jan 2002 23:04:07 -0000 1.19
+++ WSDDDeployment.java 31 Jan 2002 21:10:32 -0000 1.20
@@ -382,6 +382,14 @@
}
/**
+ * Return the WSDD description for a given named service
+ */
+ public WSDDService getWSDDService(QName qname)
+ {
+ return (WSDDService)services.get(qname);
+ }
+
+ /**
*
* @param name XXX
* @return XXX
