Hi Glen,
I have opened the JIRA: https://issues.apache.org/jira/browse/AXIS2-3492
But I am not sure how do you think is the right way to associate a
WSDLSupplier implementation with a given AxisService?
Do you suggest me to use the AxisDescription addParameter(String name,
Object value) method? If
Hi Glen,
yes it sounds good. Anyway I was thinking of having more generic approach.
What about just to add a new attribute for parameter that will define the
type of the value (e.g. class, String, etc.) ?
Anyway if this is not possible at the moment I will expect the fix you are
suggesting.
Thank
Hi Glen,
Axis2 Data Retrieval[1] architecture allows you to write your own custom
WSDL Data Locator which will give you the freedom to control WSDL generation
as you wish. Doesn't it work for you in the following case[2]
Cheers,
--Sanka
[1]
https://svn.apache.org/repos/asf/webservices/axis2/tru
Hi Dobri:
The WSDLSupplier, at least up until now, is something that gets added to
the AxisService as a parameter programatically, not via configuration.
The value is an actual WSDLSupplier, not a class name. However this
could certainly be changed, and I kind of like your idea for doing so.
Hi Saminda,
I am not sure I get everything right. So let's clarify it.
1) My understanding is that I should create a JIRA about WSDLSupplier
parameter, right? But I think this is a more or less feature than a bug? I
mean, AFAIK when you add a parameter to services/axis2.xml it is supposed to
be re
Hi Dobri,
In deed, if the parameter is defined as prior, it would cause a class cast
exception. This should be fixed. The intended used case for WSDLSupplier is
IMHO not what you have identified. You'll be able to find a use case in [1].
Since you are using org.apache.axis2.rpc.receivers.RPCMess
Hi everybody,
There is one mail thread
http://marc.info/?l=axis-dev&m=118399944531093&w=2that talks about
using WSDLSupplier that gives you the possibility to hook
your own WSDL on the fly. This is done implementing an interface
org.apache.axis2.dataretrieval.WSDLSupplier.
What I am currently tryin
Hi Deepal:
Deepal Jayasinghe wrote:
Seems like a good proposal. However if you can populate your service
correctly with the schemas, message and soap actions then at the run
time when you do ?wsdl we do the right thing. And even you do not need
to worry about ?wsdl and ?wsdl2 , that's the pro
+1
Rich Scheuerle
IBM Web Services
Apache Axis2 ([EMAIL PROTECTED])
512-838-5115 (IBM TL 678-5115)
"Afkham Azeez" <[EMAIL PROTECTED]> wrote on 07/09/2007 12:23:00 PM:
> Sounds good. +1.
>
> -- Azeez
> On 7/9/07, Glen Daniels <[EMAIL PROTECTED]> wrote::
> [Resending with correct prefix. Ple
hi Glen,
Seems like a good proposal. However if you can populate your service
correctly with the schemas, message and soap actions then at the run
time when you do ?wsdl we do the right thing. And even you do not need
to worry about ?wsdl and ?wsdl2 , that's the procedure we are using for
POJO.
Sounds like a decent approach but I do have a concern: by returning
Definition you're forcing WSDL 1.1 only. The approach of "put whatever you
need into AxisService so that printWSDL() does the right thing" allows us
to support both WSDL 1.1 and 2.0 nicely.
Can we modify your proposal a bit:
Glen,
Have you looked at AxisDataLocatorImpl and AxisDataLocator?
thanks,
dims
On 7/9/07, Glen Daniels <[EMAIL PROTECTED]> wrote:
Hi folks!
So I've got a custom deployer which wants to be able to generate its own
WSDL (via "?wsdl") for the artifacts it deploys. Unfortunately there's
no reall
Sounds good. +1.
-- Azeez
On 7/9/07, Glen Daniels <[EMAIL PROTECTED]> wrote:
[Resending with correct prefix. Please reply on THIS thread]
Hi folks!
So I've got a custom deployer which wants to be able to generate its own
WSDL (via "?wsdl") for the artifacts it deploys. Unfortunately there's
+1
Saminda
On 7/9/07, Glen Daniels <[EMAIL PROTECTED]> wrote:
[Resending with correct prefix. Please reply on THIS thread]
Hi folks!
So I've got a custom deployer which wants to be able to generate its own
WSDL (via "?wsdl") for the artifacts it deploys. Unfortunately there's
no really good
[Resending with correct prefix. Please reply on THIS thread]
Hi folks!
So I've got a custom deployer which wants to be able to generate its own
WSDL (via "?wsdl") for the artifacts it deploys. Unfortunately there's
no really good way that I've found in the Axis2 architecture to do that. :(
In
Hi folks!
So I've got a custom deployer which wants to be able to generate its own
WSDL (via "?wsdl") for the artifacts it deploys. Unfortunately there's
no really good way that I've found in the Axis2 architecture to do that. :(
In Axis1, WSDL generation was the responsibility of the "Provider
16 matches
Mail list logo
