Hi,
Is there a way to generate the WSDL file during build time with xfire?
The only possible way I have noticed is after deploying the war and
calling http:// .../service name?wsdl
I need to create the WSDL during build time in order to create the
client classes with the help of the WSDL
You can use AbstractInvoker.getContext only from within your service
implementation, not from client.
On 4/26/07, craig w [EMAIL PROTECTED] wrote:
I see that the latest snapshot is out, is the change that I need:
XFIRE-964Support for accessing MessageContext from within service
No, eclipse plugin use 1.2.5 version.
On 4/26/07, craig w [EMAIL PROTECTED] wrote:
yea i use the eclipse plugin but does it support the latest snapshot from
April 25?
On 4/25/07, craig w [EMAIL PROTECTED] wrote:
thanks, somehow I forgot about that.
On 4/25/07, Tomek Sztelak [EMAIL
Its not only way :) Take a look at WsdlGenTask task.
On 4/26/07, Liav Elias [EMAIL PROTECTED] wrote:
Hi,
Is there a way to generate the WSDL file during build time with xfire?
The only possible way I have noticed is after deploying the war and
calling http:// …/service name?wsdl
I need
When I try, AbstractInvoker.getContext() it is always returning NULL.
Example:
HelloServiceClient service = *new* HelloServiceClient();
HelloServiceSoap client = service.getHelloServiceSoap();
HolderUserInfo holder = new HolderUserInfo();
SayHelloResult result = client.sayHello(bob, holder);
Thanks, your answer helped mi a lot! But here comes another question: If
we're able to get client's certificate as an effect of signing the message
by the client, is there an ability to use this certificate to encrypt the
response without impoting it to server's store?
On 26/04/07, Tomek Sztelak
you can use AbstractInvoker ONLY inside methods of your service
implementations on server side.
On 4/26/07, craig w [EMAIL PROTECTED] wrote:
When I try, AbstractInvoker.getContext() it is always returning NULL.
Example:
HelloServiceClient service = new HelloServiceClient();
Hi Ashok and list,
Thanks for the help. I have a further problem in that the bean that returns
the list is an object from a jar file which I do not have authorization to
change. I know that I need to create the aegis.xml file in the same
directory as the bean, besides unjaring and then rejaring
You can add in handler do your client which will get headers from response.
On 4/26/07, craig w [EMAIL PROTECTED] wrote:
So from the code I am doing in my last message (i.e. using a client), I can
not get access to the headers returned in the servers SOAP response???
On 4/26/07, Tomek
Can you explain a bit more, I am not sure what you mean by add in handler
do your client? So are you saying in HelloServiceClient I should add code
such as...
public MessageContext getContext() {
return AbstractInvoker.getContext();
}
On 4/26/07, Tomek Sztelak [EMAIL PROTECTED] wrote:
Hi all,
I have managed to map all the remaining objects that are returned by a
legacy component except for the java.security.cert.CertPath getCertficates
method. ( I am pretty sure that this components login method returns every
know object in its domain :( ) I have setup the folder structure
Hi,
We use Xfire on our server and client side, but we ran into a problem
after turning validation on. We have an operation witch takes the
folloing element as a payload:
xs:element name=getUserProfileRequest
xs:complexType
xs:sequence
Hi there,
You could add nillable=true to your userId element. The generated
payload would then match the contract.
Dan
From: Ivo van Dongen [mailto:[EMAIL PROTECTED]
Sent: 26 April 2007 14:03
To: user@xfire.codehaus.org
Subject: [xfire-user] Xfire generates
Or is there some sort of addHandler method I need to use?
Thanks in advance for the help.
On 4/26/07, craig w [EMAIL PROTECTED] wrote:
Can you explain a bit more, I am not sure what you mean by add in handler
do your client? So are you saying in HelloServiceClient I should add code
such
Ivo van Dongen wrote:
Hi,
Thanks for the quick reply. If I remember correctly putting
nillable=true and minOccurs=0 together results in some strange
behaviour in Xfire. Instead of generating Strings you get
JAXBElementString or something or is this fixed in the current release?
It seems to
Hi,
Further to this, is there any way to force the service to actually
return the WSDL file that was used to generate the stub code instead of
XFire generating it?
Cheers,
Matthew
Matthew Graham wrote:
Hi,
I'm using XFire 1.2.2 with XmlBeans binding from a WSDL defined with:
Hi,
I was trying the example with code first contract instead of wsdl first
contract.
I am able to deploy the war(weblogic 9.1) but when tried to access the wsdl
using
http://15.246.23.197:7001/wsgen-jaxws-spring-1.2.5/services/HelloService?wsdl
returns the same page
when clicked again on wsdl
Our current issues revolves around calling a service method that takes in
an abstract class as a parameter. e.g.
public void loadGelcoCCAddendum(GelcoCCAddendum gelcoCCAddendum) throws
GeneralWebServiceException;
Class Hierachy:
GelcoCCAddendum - Abstract Class
GelcoLodgingCCAddendum -
Hi,
I have the following WSDL2Java generated client code:
public static void main(String[] args) {
HelloServiceClient service = new HelloServiceClient();
HelloServiceSoap client = service.getHelloServiceSoap();
HolderUserInfo holder = new HolderUserInfo();
SayHelloResult result =
19 matches
Mail list logo
