[jbossws-dev] Re: jax-ws client artifacts: wsimport or not?

Thu Nov 9 14:15:51 EST 2006

"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)."

MTOM is really simple. I think SOAP UI has support for it as well. 

It just needs an xsd:base64Binary declaration in your schema. The
drawback: Only supported in jaxrpc/JSR109

/Heiko

________________________________

From: Burr Sutter 
Sent: Thursday, November 09, 2006 4:47 PM
To: Heiko Braun; 'Thomas Diesler'
Cc: 'jbossws-dev at lists.jboss.org'
Subject: RE: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not?

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 at 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 at 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 at lists.jboss.org
[mailto:jbossws-dev-bounces at lists.jboss.org] On Behalf Of Thomas Diesler
Sent: Thursday, November 09, 2006 10:10 AM
To: Heiko Braun
Cc: jbossws-dev at 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 at redhat.com] 
Sent: Thursday, November 09, 2006 3:59 PM
To: Jason T. Greene
Cc: Heiko Braun; jbossws-dev at 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 at lists.jboss.org [mailto:jbossws-dev-
	bounces at lists.jboss.org] On Behalf Of Thomas Diesler
	Sent: Thursday, November 09, 2006 8:35 AM
	To: Heiko Braun
	Cc: jbossws-dev at 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 at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossws-dev/attachments/20061109/39fe0421/attachment.html 