October 2006 - jbossws-users - Jboss List Archives

[JBossWS] - Re: Clarify WSDL generation from Object parameters

by heiko.braun＠jboss.com

JAXWS is only available as a 2.0.beta version. The easiest would to be to checkout trunk and build it on your own: http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQSourceRepository The test suite contains examples on how to build and deploy jaxws services and clients. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980967#3980967 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980967

17 years, 8 months

1
0
0 / 0

[JBossWS] - Re: web services client

by heiko.braun＠jboss.com

The JSR-181 preview under JAX-RPC doesn't have a client programming model. In order to consume your service you'd need to use one the jax-rpc client models: http://labs.jboss.com/portal/jbossws/user-guide/en/html/clients.html View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980966#3980966 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980966

17 years, 8 months

1
0
0 / 0

[JBossWS] - Re: WS-Eventing - sending notification

by heiko.braun＠jboss.com

I think artems suggestion is perfectly valid. The SubscriptionManager knows about the schema and could actually validate the event messages. At least this was my original intention. But as palin already realized, there's two things to be done: The MetaDataBuilder needs to extract the schema (there might be a better format than String) and populate the deployment info. This would make the schema available to the event source instance. In a second step, the message could be validated in SubscriptionManager.dispatch() before handiong off to the background task. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980964#3980964 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980964

17 years, 8 months

1
0
0 / 0

[JBossWS] - Re: WS-Eventing - sending notification

by maeste

Hi artem, I can't understand what you mean? Specification of ws-eventing doesn't constrain notifications because (specification said) any message MAY be a notification. But in real world producer and receiver have to constrain the message accepted. And it is an application level know how. Of course should be convenient if the application engine does it for you, but I can't understand where is the value of that: immagine you (event producer) define a schema for notification and a subscriber implement a different schema. When you will send notifications you will construct the xml according to your schema (the only one you are supposed to know). You are asking the engine to validate notifications according to the receiver schema, but in that case (schema defined by the ws-eventing source != schema implemented by the event sink) it wold (always) fail and throws an exption. You can check the exception, but anyway you can't recover it. Isn't it? Instead the validation of the producer defined schema could be conveniently made by the engine, but it can be done also at application level as Alessio already said. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980948#3980948 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980948

17 years, 8 months

1
0
0 / 0

[JBossWS] - Re: WS-Eventing - sending notification

by artem_spector

Yes, I know the notification schema, but aparently it might be different from the instance loaded by the subscription manager. Therefore the "real" validation can be done only by the engine - or by the application if the engine provides an access to that schema (by URI) thank you, Artem View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980923#3980923 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980923

17 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Endpoint address / server not running at port 8080

by artem_spector

It just shows you the port 8080, actually it runs (the http listener port is) on 9080. For example, if you click on the wsdl link, you will get an error page, but if you change the port in the URL to 9080 - you will see the wsdl. Please note that the address listed in the wsdl is 8080 too, so if you are going to use it (for JSR-181 client for example) you will have to override the address. Artem View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980918#3980918 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980918

17 years, 8 months

1
0
0 / 0

[JBossWS] - How do I customize WSDL when using 181 EJB WS

by kimbaltrue

I'm using the lastest AS and WS. My Webservice uses a complex object as a paramter (i.e. java.util.List as attribute.) The webservice deploys, but the complex object in the generated WSDL is empty. How do I get JBossWS to generate a WSDL with the complete object model? Is there anyway to provide JBossXB XSD annotations when using 181 EBJ webservices? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980830#3980830 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980830

17 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Urgent Help requested ...support for enums..update jboss

by t_skowronek

Take a look at the following links. I think you will need to uses arrays. http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JAXRPC4.html#wp130550 http://www.w3.org/TR/wsdl http://schemas.xmlsoap.org/soap/encoding/ View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980827#3980827 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980827

17 years, 8 months

1
0
0 / 0

[JBossWS] - Endpoint address / server not running at port 8080

by MmarcoM

hi all, i am deploying EJB3 webservices on jboss4.0.4.. the problem i have is that, no matter the fact that my server is running on port 9080, the Endpoint address of my webservice is always at http://localhost:8080/....... here's what i have when i view services deployed in jboss | Registered Service Endpoints | ServiceEndpointID ServiceEndpointAddress | jboss.ws:context=ejbJ2me-app-1,endpoint=TestFacade http://WorldCorp:8080/ejbJ2me-app-1/TestFacade?wsdl | is there any way to override that?? can anyone tell me what to do? with best regards Marco View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980825#3980825 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980825

17 years, 8 months

1
0
0 / 0

[JBossWS] - Urgent Help requested ...support for enums..update jbossws g

by sursha

Hi, I want to use enumerations in wsdl. I've a ejb3 exposed web service deployed in jboss 4.0.4 GA. I tried defining a java class with static final constants , but it the constants wont show up in wsdl. I also tried using enums in a java class, that also wont show up as enumerations in wsdl. Is there a way for java enums to show up in the generated wsdl? Or can i edit the generated the wsdl to support enumerations and deploy to jboss? Please advise... Thanks Suresh View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980819#3980819 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980819

17 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-users October 2006