Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [stp-dev] STP Deployment Framework: JAX-WS Logical and Physicalpackages
Title: STP Deployment Framework: JAX-WS Logical and Physical packages
Hi Andrei
 
> Probably in this case more logically will be to associate "build 
> package" menu with whole JAX-WS project, not only with wsdl file?

You are right. We also feel the limitation for current logical package association.
For example, some runtime (such as Apache CXF) do support simple font-end POJO application.
In that case, there maybe no wsdl file at all. So it is good to associate to project node for now.
In the future, when the hybrid model is committed. Maybe we can create a abstract service node under project in the package explorer view, which will represent the service component in the model. Thus we will associate the logical package with the service node.
 
 
> Do you plan to support also "project based" deployment for WTP 
> Server Tools API with own JAX-WS and SCA project facets?
Yes, we plan to support the project-based deployment for wtp and will create jax-ws, sca facets.
Hopefully, I can finish this code by the end of this week.
In that case, if user wants to deploy/debug one component, they can use the wtp 'Run-On-Server' directly.
If they want to deploy multiple components to multiple servers, they will do this in stp deployment profile editor.
 
btw, looks like the facets framework in under refactor in wtp 3.0
 
 
Regards
 
Johnson
 
----- Original Message -----
Sent: Monday, September 24, 2007 7:37 PM
Subject: [stp-dev] STP Deployment Framework: JAX-WS Logical and Physicalpackages

Hi Johnson,

I just have tried stp-all-in-one-R-R200709200237-200709200237 release and already can use the new deployment features there. It is really great!

I have one understanding question and one question about future plans regarding this stuff:

1. I do not completely understand why "build package" menu is associated with wsdl file. I thought that logical package contains wsdl, implemented service business logic in generated code (custome stuff in xxxBindingImpl.java classes) and generated code itself. Business logic is later packaged into war file and seems to be the part of the logical package (it is indepent on Server) .

Probably in this case more logically will be to associate "build package" menu with whole JAX-WS project, not only with wsdl file?

What do you think?

2. At the moment deployment is based on war file, not on the project itself like in WTP Web-Services.
Therefore some WTP features:
- automatic synchronization of deployed module with changed sources;
- "Add and remove projects" in Server context menu;
- "Run As -> Run On Server"
are not completely supported.
Do you plan to support also "project based" deployment for WTP Server Tools API with own JAX-WS and SCA project facets?

Regards,
Andrei.


Andrei Shakirin
IC-Consult on behalf of
Deutsche Post AG
SOPSOLUTIONS®
D - 53250 Bonn
telefon: +49(0)228 182 19077
***************************************
S O A D a y s 2 0 0 7
Technology Conference
Join us! Bonn, Germany
12th & 13th September 2007
***************************************


_______________________________________________
stp-dev mailing list
stp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/stp-dev

Back to the top