History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: XFIRE-319
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Dan Diephouse
Reporter: Giampaolo Tranchida
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
XFire

Handler not invoked on client with XFireProxyFactory

Created: 27/Mar/06 11:25 PM   Updated: 08/Dec/06 03:28 PM
Component/s: Core
Affects Version/s: 1.1-beta-1, 1.0
Fix Version/s: 1.0

Time Tracking:
Not Specified

Environment: Sun JDK 1.4.2


 Description  « Hide
My Handler is not invoked, with this code

Service serviceModel = new ObjectServiceFactory().create(DemoService.class, "DemoService", "http://demo.tranchida.ch/DemoService", null);
serviceModel.addOutHandler(new WSSEClientHandler());

DemoService service = (DemoService)
new XFireProxyFactory().create(serviceModel, "http://localhost:8080/DemoService/services/DemoService");
System.out.println(service.echo("hello"));

Looking at XFireProxy in debug, outHandlers list contains only OutMessageSender

But Using Dynamic client, it is ok, my Handler is normaly invoked

Client client = new Client(new URL("http://localhost:9999/DemoService/services/DemoService?wsdl"));
client.setEndpointUri("http://localhost:9999/DemoService/services/DemoService");
client.addOutHandler(new WSSEClientHandler());
System.out.println(client.invoke("echo", new Object[] { "hello" })[0]);



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Dan Diephouse - 27/Mar/06 11:38 PM
Try this instead:

DemoService service = (DemoService)
new XFireProxyFactory().create(serviceModel, "http://localhost:8080/DemoService/services/DemoService");
Client client = ((XFireProxy) Proxy.getInvocationHandler(service)).getClient();
client.addOutHandler(handler);


Giampaolo Tranchida - 28/Mar/06 01:58 PM
Yes, it's work. Thank you

Matthew - 08/Dec/06 03:28 PM
Was this fixed? Or are you just suggesting the work-around? Because I'm using version 1.2 and I have the same problem. The service's handlers are not added to the pipeline in Invocation.Invoke. In my case the service is used over and over to create proxies and I would rather it be a service level configuration rather than proxy level.