Re: jboss.xml: webservice-description
by Thomas Diesler
The <config-name> can be set per endpoint, not just per top level
deployment. The property on ApplicationMetaData is IMO incorrect. This
has has probably not showed up yet since nobody tried to use two
different configuaratins in the same deployment.
-thomas
Alexey Loubyansky wrote:
> By that I meant, webservice-description is repeatable while configName
> and configLocal are fields in the ApplicationMetaData. So, each
> appearance of the webservice-description can override them on the
> ApplicationMetaData level.
>
> Alexey Loubyansky wrote:
>> I am confused about its children config-name and config-file. Do they
>> belong to webservice-description (as in the DTD) or its parent
>> webservices (as in the ApplicationMetaData)?
>>
>> Alexey
>>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
18 years, 2 months
RE: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?
by Burr Sutter
Great point. I always throw some WS stuff into my various
presentations. The big win being I consume it in VB.NET and talk to
things like JBoss Rules or an EJB from .NET.
However, I have to fill at least 1 hour of "hands-on" with JBossWS in
the "laptop workshop" (I'm helping coordinate all of the workshop
materials since Daryl left the company). Here is what I'm thinking:
* Lab 1: 181 WS POJO using the "servlet" technique - I'm not sure if
this approach as an official name
Soapui as a consumer (I can't expect students to have VB.NET on their
laptops but will demo that concept)
* Lab 2: Same as above but using a Person object (or something more
complex) as a return type/input parameter. SoapUI as a consumer
* Lab 3: Take existing SLSB and throw an @WebService on it (from the
EJB3 workshop labs). The SLSB that I have has CRUD methods over an
entity bean. Soapui as a consumer.
Is that 60 minutes worth of student's setup laptops, instructor demo,
students try it, instructor walks around the room and helps students get
it working on their various laptops?
What would Lab 4 be? Wsdl2java? It would be cool to show WS-Security
or MTOM but that is just too hard to setup and get working in a short
timeframe (all exercises should be doable in 15 minutes or less with
easy to setup tools/utilities).
The Office integration demos are still on the back burner. MSFT
SOAPtookit doesn't work with our stack and I'm awaiting stuff from MSFT
(Office 2007 beta and whatever they end up calling VSTO).
I'll then break into ESB related labs for the remaining 45 to 60 minutes
of the workshop.
Burr
________________________________
From: Heiko Braun
Sent: Thursday, November 09, 2006 10:27 AM
To: Burr Sutter; 'Thomas Diesler'
Cc: 'jbossws-dev(a)lists.jboss.org'
Subject: RE: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?
You are right Burr.
That's why I am adding to the intro demo...
In this case, we would need to communicate the Sun RI tools (wsimport).
IMO it's no big deal, as long as all the presentations are consistent in
this regard.
/Heiko
________________________________
From: Burr Sutter
Sent: Thursday, November 09, 2006 4:22 PM
To: Thomas Diesler; Heiko Braun
Cc: jbossws-dev(a)lists.jboss.org
Subject: RE: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?
I'm not sure if you want my 2 cents but option #1 makes for the best
demo though many audience members would like to see the wsdl2java
(contract first) method as well. I normally don't show this but I do
need to add it.
Java2wsdl from the command is only for those folks wishing to integrate
the WS development into their automated build scripts/unit testing.
________________________________
From: jbossws-dev-bounces(a)lists.jboss.org
[mailto:jbossws-dev-bounces@lists.jboss.org] On Behalf Of Thomas Diesler
Sent: Thursday, November 09, 2006 10:10 AM
To: Heiko Braun
Cc: jbossws-dev(a)lists.jboss.org
Subject: Re: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?
ok, lets do #1
Heiko Braun wrote:
>From my point of view #1 is perfectly fine, at least for the JBW demos.
People wont realize it, since I start with an JSR181-EJB3 first and the
pickup the WSDL from there.
/Heiko
________________________________
From: Thomas Diesler [mailto:thomas.diesler@redhat.com]
Sent: Thursday, November 09, 2006 3:59 PM
To: Jason T. Greene
Cc: Heiko Braun; jbossws-dev(a)lists.jboss.org
Subject: Re: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?
This shows how badly broken the integration is. If we can do it in
container, why can this not be done offline?
So what should the message be for java2wsdl?
#1 deploy to server, pickup the wsdl from the browser
#2 use wsgen
I'd opt for #1 otherwise we have people generating conflicting
contracts.
cheers
-thomas
Jason T. Greene wrote:
We don't yet have an offline tool for java2wsdl.
http://jira.jboss.com/jira/browse/JBWS-1043
Last we discussed this task was delayed until the following were
completed:
- CTS compliance
- Backporting to jbossws-1.0
-Jason
-----Original Message-----
From: jbossws-dev-bounces(a)lists.jboss.org [mailto:jbossws-dev-
bounces(a)lists.jboss.org] On Behalf Of Thomas Diesler
Sent: Thursday, November 09, 2006 8:35 AM
To: Heiko Braun
Cc: jbossws-dev(a)lists.jboss.org
Subject: [jbossws-dev] Re: jax-ws client artifacts: wsimport or
not?
For java2wsdl use our tools.
For wsdl2java use wsimport and monitor
http://jira.jboss.org/jira/browse/JBWS-1042
-thomas
Heiko Braun wrote:
What's the (communication) strategy for jax-ws tools?
Are we going to point people to the RI tools until we
are ready?
What should be communicated at JBW?
I am currently hacking the demo and don't know if I
should hide the
RI
or not...
/Heiko
--
Heiko Braun
JBoss, a division of Red Hat
T: +49 89 52350383
M: +49 178 1496854
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
jbossws-dev mailing list
jbossws-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossws-dev
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
18 years, 2 months
RE: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?
by Heiko Braun
Wow. I didn't know that.
To me it was the most natural way to do things.
;)
________________________________
From: Jason T. Greene
Sent: Thursday, November 09, 2006 4:26 PM
To: Burr Sutter; Thomas Diesler; Heiko Braun
Cc: jbossws-dev(a)lists.jboss.org
Subject: RE: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?
With JAX-WS, the point you have about java2wsdl is only true on our
container ;)
All other containers require you to generate additional source code that
has to be bundled with the deployment. We generate the bytecode
dynamically at deploy time.
-Jason
________________________________
From: jbossws-dev-bounces(a)lists.jboss.org
[mailto:jbossws-dev-bounces@lists.jboss.org] On Behalf Of Burr Sutter
Sent: Thursday, November 09, 2006 9:22 AM
To: Thomas Diesler; Heiko Braun
Cc: jbossws-dev(a)lists.jboss.org
Subject: RE: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?
I'm not sure if you want my 2 cents but option #1 makes for the best
demo though many audience members would like to see the wsdl2java
(contract first) method as well. I normally don't show this but I do
need to add it.
Java2wsdl from the command is only for those folks wishing to integrate
the WS development into their automated build scripts/unit testing.
________________________________
From: jbossws-dev-bounces(a)lists.jboss.org
[mailto:jbossws-dev-bounces@lists.jboss.org] On Behalf Of Thomas Diesler
Sent: Thursday, November 09, 2006 10:10 AM
To: Heiko Braun
Cc: jbossws-dev(a)lists.jboss.org
Subject: Re: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?
ok, lets do #1
Heiko Braun wrote:
>From my point of view #1 is perfectly fine, at least for the JBW demos.
People wont realize it, since I start with an JSR181-EJB3 first and the
pickup the WSDL from there.
/Heiko
________________________________
From: Thomas Diesler [mailto:thomas.diesler@redhat.com]
Sent: Thursday, November 09, 2006 3:59 PM
To: Jason T. Greene
Cc: Heiko Braun; jbossws-dev(a)lists.jboss.org
Subject: Re: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?
This shows how badly broken the integration is. If we can do it in
container, why can this not be done offline?
So what should the message be for java2wsdl?
#1 deploy to server, pickup the wsdl from the browser
#2 use wsgen
I'd opt for #1 otherwise we have people generating conflicting
contracts.
cheers
-thomas
Jason T. Greene wrote:
We don't yet have an offline tool for java2wsdl.
http://jira.jboss.com/jira/browse/JBWS-1043
Last we discussed this task was delayed until the following were
completed:
- CTS compliance
- Backporting to jbossws-1.0
-Jason
-----Original Message-----
From: jbossws-dev-bounces(a)lists.jboss.org [mailto:jbossws-dev-
bounces(a)lists.jboss.org] On Behalf Of Thomas Diesler
Sent: Thursday, November 09, 2006 8:35 AM
To: Heiko Braun
Cc: jbossws-dev(a)lists.jboss.org
Subject: [jbossws-dev] Re: jax-ws client artifacts: wsimport or
not?
For java2wsdl use our tools.
For wsdl2java use wsimport and monitor
http://jira.jboss.org/jira/browse/JBWS-1042
-thomas
Heiko Braun wrote:
What's the (communication) strategy for jax-ws tools?
Are we going to point people to the RI tools until we
are ready?
What should be communicated at JBW?
I am currently hacking the demo and don't know if I
should hide the
RI
or not...
/Heiko
--
Heiko Braun
JBoss, a division of Red Hat
T: +49 89 52350383
M: +49 178 1496854
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
jbossws-dev mailing list
jbossws-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossws-dev
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.409 / Virus Database: 268.14.0/524 - Release Date:
11/8/2006
18 years, 2 months
RE: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?
by Burr Sutter
I'm not sure if you want my 2 cents but option #1 makes for the best
demo though many audience members would like to see the wsdl2java
(contract first) method as well. I normally don't show this but I do
need to add it.
Java2wsdl from the command is only for those folks wishing to integrate
the WS development into their automated build scripts/unit testing.
________________________________
From: jbossws-dev-bounces(a)lists.jboss.org
[mailto:jbossws-dev-bounces@lists.jboss.org] On Behalf Of Thomas Diesler
Sent: Thursday, November 09, 2006 10:10 AM
To: Heiko Braun
Cc: jbossws-dev(a)lists.jboss.org
Subject: Re: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?
ok, lets do #1
Heiko Braun wrote:
>From my point of view #1 is perfectly fine, at least for the JBW demos.
People wont realize it, since I start with an JSR181-EJB3 first and the
pickup the WSDL from there.
/Heiko
________________________________
From: Thomas Diesler [mailto:thomas.diesler@redhat.com]
Sent: Thursday, November 09, 2006 3:59 PM
To: Jason T. Greene
Cc: Heiko Braun; jbossws-dev(a)lists.jboss.org
Subject: Re: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?
This shows how badly broken the integration is. If we can do it in
container, why can this not be done offline?
So what should the message be for java2wsdl?
#1 deploy to server, pickup the wsdl from the browser
#2 use wsgen
I'd opt for #1 otherwise we have people generating conflicting
contracts.
cheers
-thomas
Jason T. Greene wrote:
We don't yet have an offline tool for java2wsdl.
http://jira.jboss.com/jira/browse/JBWS-1043
Last we discussed this task was delayed until the following were
completed:
- CTS compliance
- Backporting to jbossws-1.0
-Jason
-----Original Message-----
From: jbossws-dev-bounces(a)lists.jboss.org [mailto:jbossws-dev-
bounces(a)lists.jboss.org] On Behalf Of Thomas Diesler
Sent: Thursday, November 09, 2006 8:35 AM
To: Heiko Braun
Cc: jbossws-dev(a)lists.jboss.org
Subject: [jbossws-dev] Re: jax-ws client artifacts: wsimport or
not?
For java2wsdl use our tools.
For wsdl2java use wsimport and monitor
http://jira.jboss.org/jira/browse/JBWS-1042
-thomas
Heiko Braun wrote:
What's the (communication) strategy for jax-ws tools?
Are we going to point people to the RI tools until we
are ready?
What should be communicated at JBW?
I am currently hacking the demo and don't know if I
should hide the
RI
or not...
/Heiko
--
Heiko Braun
JBoss, a division of Red Hat
T: +49 89 52350383
M: +49 178 1496854
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
jbossws-dev mailing list
jbossws-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossws-dev
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
18 years, 2 months
RE: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?
by Heiko Braun
You are right Burr.
That's why I am adding to the intro demo...
In this case, we would need to communicate the Sun RI tools (wsimport).
IMO it's no big deal, as long as all the presentations are consistent in
this regard.
/Heiko
________________________________
From: Burr Sutter
Sent: Thursday, November 09, 2006 4:22 PM
To: Thomas Diesler; Heiko Braun
Cc: jbossws-dev(a)lists.jboss.org
Subject: RE: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?
I'm not sure if you want my 2 cents but option #1 makes for the best
demo though many audience members would like to see the wsdl2java
(contract first) method as well. I normally don't show this but I do
need to add it.
Java2wsdl from the command is only for those folks wishing to integrate
the WS development into their automated build scripts/unit testing.
________________________________
From: jbossws-dev-bounces(a)lists.jboss.org
[mailto:jbossws-dev-bounces@lists.jboss.org] On Behalf Of Thomas Diesler
Sent: Thursday, November 09, 2006 10:10 AM
To: Heiko Braun
Cc: jbossws-dev(a)lists.jboss.org
Subject: Re: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?
ok, lets do #1
Heiko Braun wrote:
>From my point of view #1 is perfectly fine, at least for the JBW demos.
People wont realize it, since I start with an JSR181-EJB3 first and the
pickup the WSDL from there.
/Heiko
________________________________
From: Thomas Diesler [mailto:thomas.diesler@redhat.com]
Sent: Thursday, November 09, 2006 3:59 PM
To: Jason T. Greene
Cc: Heiko Braun; jbossws-dev(a)lists.jboss.org
Subject: Re: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?
This shows how badly broken the integration is. If we can do it in
container, why can this not be done offline?
So what should the message be for java2wsdl?
#1 deploy to server, pickup the wsdl from the browser
#2 use wsgen
I'd opt for #1 otherwise we have people generating conflicting
contracts.
cheers
-thomas
Jason T. Greene wrote:
We don't yet have an offline tool for java2wsdl.
http://jira.jboss.com/jira/browse/JBWS-1043
Last we discussed this task was delayed until the following were
completed:
- CTS compliance
- Backporting to jbossws-1.0
-Jason
-----Original Message-----
From: jbossws-dev-bounces(a)lists.jboss.org [mailto:jbossws-dev-
bounces(a)lists.jboss.org] On Behalf Of Thomas Diesler
Sent: Thursday, November 09, 2006 8:35 AM
To: Heiko Braun
Cc: jbossws-dev(a)lists.jboss.org
Subject: [jbossws-dev] Re: jax-ws client artifacts: wsimport or
not?
For java2wsdl use our tools.
For wsdl2java use wsimport and monitor
http://jira.jboss.org/jira/browse/JBWS-1042
-thomas
Heiko Braun wrote:
What's the (communication) strategy for jax-ws tools?
Are we going to point people to the RI tools until we
are ready?
What should be communicated at JBW?
I am currently hacking the demo and don't know if I
should hide the
RI
or not...
/Heiko
--
Heiko Braun
JBoss, a division of Red Hat
T: +49 89 52350383
M: +49 178 1496854
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
jbossws-dev mailing list
jbossws-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossws-dev
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
18 years, 2 months
RE: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?
by Jason T. Greene
With JAX-WS, the point you have about java2wsdl is only true on our
container ;)
All other containers require you to generate additional source code that
has to be bundled with the deployment. We generate the bytecode
dynamically at deploy time.
-Jason
________________________________
From: jbossws-dev-bounces(a)lists.jboss.org
[mailto:jbossws-dev-bounces@lists.jboss.org] On Behalf Of Burr Sutter
Sent: Thursday, November 09, 2006 9:22 AM
To: Thomas Diesler; Heiko Braun
Cc: jbossws-dev(a)lists.jboss.org
Subject: RE: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?
I'm not sure if you want my 2 cents but option #1 makes for the best
demo though many audience members would like to see the wsdl2java
(contract first) method as well. I normally don't show this but I do
need to add it.
Java2wsdl from the command is only for those folks wishing to integrate
the WS development into their automated build scripts/unit testing.
________________________________
From: jbossws-dev-bounces(a)lists.jboss.org
[mailto:jbossws-dev-bounces@lists.jboss.org] On Behalf Of Thomas Diesler
Sent: Thursday, November 09, 2006 10:10 AM
To: Heiko Braun
Cc: jbossws-dev(a)lists.jboss.org
Subject: Re: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?
ok, lets do #1
Heiko Braun wrote:
>From my point of view #1 is perfectly fine, at least for the JBW demos.
People wont realize it, since I start with an JSR181-EJB3 first and the
pickup the WSDL from there.
/Heiko
________________________________
From: Thomas Diesler [mailto:thomas.diesler@redhat.com]
Sent: Thursday, November 09, 2006 3:59 PM
To: Jason T. Greene
Cc: Heiko Braun; jbossws-dev(a)lists.jboss.org
Subject: Re: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?
This shows how badly broken the integration is. If we can do it in
container, why can this not be done offline?
So what should the message be for java2wsdl?
#1 deploy to server, pickup the wsdl from the browser
#2 use wsgen
I'd opt for #1 otherwise we have people generating conflicting
contracts.
cheers
-thomas
Jason T. Greene wrote:
We don't yet have an offline tool for java2wsdl.
http://jira.jboss.com/jira/browse/JBWS-1043
Last we discussed this task was delayed until the following were
completed:
- CTS compliance
- Backporting to jbossws-1.0
-Jason
-----Original Message-----
From: jbossws-dev-bounces(a)lists.jboss.org [mailto:jbossws-dev-
bounces(a)lists.jboss.org] On Behalf Of Thomas Diesler
Sent: Thursday, November 09, 2006 8:35 AM
To: Heiko Braun
Cc: jbossws-dev(a)lists.jboss.org
Subject: [jbossws-dev] Re: jax-ws client artifacts: wsimport or
not?
For java2wsdl use our tools.
For wsdl2java use wsimport and monitor
http://jira.jboss.org/jira/browse/JBWS-1042
-thomas
Heiko Braun wrote:
What's the (communication) strategy for jax-ws tools?
Are we going to point people to the RI tools until we
are ready?
What should be communicated at JBW?
I am currently hacking the demo and don't know if I
should hide the
RI
or not...
/Heiko
--
Heiko Braun
JBoss, a division of Red Hat
T: +49 89 52350383
M: +49 178 1496854
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
jbossws-dev mailing list
jbossws-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossws-dev
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.409 / Virus Database: 268.14.0/524 - Release Date:
11/8/2006
18 years, 2 months
RE: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?
by Heiko Braun
>From my point of view #1 is perfectly fine, at least for the JBW demos.
People wont realize it, since I start with an JSR181-EJB3 first and the
pickup the WSDL from there.
/Heiko
________________________________
From: Thomas Diesler [mailto:thomas.diesler@redhat.com]
Sent: Thursday, November 09, 2006 3:59 PM
To: Jason T. Greene
Cc: Heiko Braun; jbossws-dev(a)lists.jboss.org
Subject: Re: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?
This shows how badly broken the integration is. If we can do it in
container, why can this not be done offline?
So what should the message be for java2wsdl?
#1 deploy to server, pickup the wsdl from the browser
#2 use wsgen
I'd opt for #1 otherwise we have people generating conflicting
contracts.
cheers
-thomas
Jason T. Greene wrote:
We don't yet have an offline tool for java2wsdl.
http://jira.jboss.com/jira/browse/JBWS-1043
Last we discussed this task was delayed until the following were
completed:
- CTS compliance
- Backporting to jbossws-1.0
-Jason
-----Original Message-----
From: jbossws-dev-bounces(a)lists.jboss.org [mailto:jbossws-dev-
bounces(a)lists.jboss.org] On Behalf Of Thomas Diesler
Sent: Thursday, November 09, 2006 8:35 AM
To: Heiko Braun
Cc: jbossws-dev(a)lists.jboss.org
Subject: [jbossws-dev] Re: jax-ws client artifacts: wsimport or
not?
For java2wsdl use our tools.
For wsdl2java use wsimport and monitor
http://jira.jboss.org/jira/browse/JBWS-1042
-thomas
Heiko Braun wrote:
What's the (communication) strategy for jax-ws tools?
Are we going to point people to the RI tools until we
are ready?
What should be communicated at JBW?
I am currently hacking the demo and don't know if I
should hide the
RI
or not...
/Heiko
--
Heiko Braun
JBoss, a division of Red Hat
T: +49 89 52350383
M: +49 178 1496854
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
jbossws-dev mailing list
jbossws-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossws-dev
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
18 years, 2 months
RE: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?
by Jason T. Greene
The issue has nothing to do with integration. It has to do with my
extremely overloaded workload. I can only work on so many things at
once.
________________________________
From: Thomas Diesler [mailto:thomas.diesler@redhat.com]
Sent: Thursday, November 09, 2006 8:59 AM
To: Jason T. Greene
Cc: Heiko Braun; jbossws-dev(a)lists.jboss.org
Subject: Re: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?
This shows how badly broken the integration is. If we can do it in
container, why can this not be done offline?
So what should the message be for java2wsdl?
#1 deploy to server, pickup the wsdl from the browser
#2 use wsgen
I'd opt for #1 otherwise we have people generating conflicting
contracts.
cheers
-thomas
Jason T. Greene wrote:
We don't yet have an offline tool for java2wsdl.
http://jira.jboss.com/jira/browse/JBWS-1043
Last we discussed this task was delayed until the following were
completed:
- CTS compliance
- Backporting to jbossws-1.0
-Jason
-----Original Message-----
From: jbossws-dev-bounces(a)lists.jboss.org [mailto:jbossws-dev-
bounces(a)lists.jboss.org] On Behalf Of Thomas Diesler
Sent: Thursday, November 09, 2006 8:35 AM
To: Heiko Braun
Cc: jbossws-dev(a)lists.jboss.org
Subject: [jbossws-dev] Re: jax-ws client artifacts: wsimport or
not?
For java2wsdl use our tools.
For wsdl2java use wsimport and monitor
http://jira.jboss.org/jira/browse/JBWS-1042
-thomas
Heiko Braun wrote:
What's the (communication) strategy for jax-ws tools?
Are we going to point people to the RI tools until we
are ready?
What should be communicated at JBW?
I am currently hacking the demo and don't know if I
should hide the
RI
or not...
/Heiko
--
Heiko Braun
JBoss, a division of Red Hat
T: +49 89 52350383
M: +49 178 1496854
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
jbossws-dev mailing list
jbossws-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossws-dev
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
18 years, 2 months
RE: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?
by Jason T. Greene
We don't yet have an offline tool for java2wsdl.
http://jira.jboss.com/jira/browse/JBWS-1043
Last we discussed this task was delayed until the following were
completed:
- CTS compliance
- Backporting to jbossws-1.0
-Jason
> -----Original Message-----
> From: jbossws-dev-bounces(a)lists.jboss.org [mailto:jbossws-dev-
> bounces(a)lists.jboss.org] On Behalf Of Thomas Diesler
> Sent: Thursday, November 09, 2006 8:35 AM
> To: Heiko Braun
> Cc: jbossws-dev(a)lists.jboss.org
> Subject: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?
>
> For java2wsdl use our tools.
> For wsdl2java use wsimport and monitor
> http://jira.jboss.org/jira/browse/JBWS-1042
>
> -thomas
>
> Heiko Braun wrote:
> > What's the (communication) strategy for jax-ws tools?
> > Are we going to point people to the RI tools until we are ready?
> > What should be communicated at JBW?
> >
> > I am currently hacking the demo and don't know if I should hide the
RI
> > or not...
> >
> > /Heiko
> >
> > --
> > Heiko Braun
> > JBoss, a division of Red Hat
> > T: +49 89 52350383
> > M: +49 178 1496854
> >
> >
>
> --
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Thomas Diesler
> Web Service Lead
> JBoss, a division of Red Hat
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
> _______________________________________________
> jbossws-dev mailing list
> jbossws-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossws-dev
18 years, 2 months
Re: jax-ws client artifacts: wsimport or not?
by Thomas Diesler
For java2wsdl use our tools.
For wsdl2java use wsimport and monitor
http://jira.jboss.org/jira/browse/JBWS-1042
-thomas
Heiko Braun wrote:
> What's the (communication) strategy for jax-ws tools?
> Are we going to point people to the RI tools until we are ready?
> What should be communicated at JBW?
>
> I am currently hacking the demo and don't know if I should hide the RI
> or not...
>
> /Heiko
>
> --
> Heiko Braun
> JBoss, a division of Red Hat
> T: +49 89 52350383
> M: +49 178 1496854
>
>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
18 years, 2 months
