Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[wtp-pmc] Agenda for WTP PMC telecon for Tuesday, July 25th 2006

Call info:

  • Tollfree in the US: 866-214-3176
  • Alternate: 404-827-9098
  • Access code: 8870689#

Call Time: 7am PDT / 10am PDT

 

Agenda:

  • Community [Lawrence]  
  • Process issues [Tim]
  • Requirements and 2.0 Planning (Jochen)
    • Component-level process discussion recap from status call (see Arthur’s summary, attached)
    • SAP request (see attached) and adopter requirements solicitation
    • STP interaction – see notice below (#150905)
  • 1.0.3 Rampdown status (David)
  • 1.5.1 Status (David)
  • JSF [Gerry[
  • Dali/JPA [Neil]
  • ATF [Robert]

 

 

 

-----Original Message-----

From: stp-dev-bounces@xxxxxxxxxxx [mailto:stp-dev-bounces@xxxxxxxxxxx] On Behalf Of Adrian Skehill

Sent: Thursday, July 20, 2006 1:25 AM

To: STP Dev list

Subject: [stp-dev] Service Creation Initial Contribution

 

Hi All,

 

IONA has recently submitted it's first proposed contribution to the STP project to the EMO for consideration. It is broken down into two

contributions:

 

150905    IONA Initial Contribution - JAX WS Framework Code

150908        IONA Initial Contribution - Celtix Tooling Support

 

These represent the creation of some generic framework JAX WS code for support JAX WS based runtimes, and then a specific Celtix implementation using this.

 

It's planned to continue development activities on these immediately after the contribution so any comments / suggestions are welcome.

 

Both of these bugs are accessible together with source attachment from http://bugs.eclipse.org.

 

Regards,

Adrian Skehill.

 

UI Team Lead,

IONA Technologies.

_______________________________________________

stp-dev mailing list

stp-dev@xxxxxxxxxxx

https://dev.eclipse.org/mailman/listinfo/stp-dev

 

 

From: wtp-dev-bounces@xxxxxxxxxxx on behalf of Arthur Ryman [ryman@xxxxxxxxxx]
Sent: Thursday, July 20, 2006 12:24 PM
To: wtp-dev@xxxxxxxxxxx
Subject: [wtp-dev] Generating Nicely Grouped Milestone Plan Reports fromBugzilla

Attachments: ATT5943870.txt

On the telecon today we discussed the use of Bugzilla as the primary way to record plan items. One of the problems is that there will be a lot of items and we need a better way to group them, for example, into Themes. I suggest we use the URL field in Bugzilla for this purpose.

We should define Theme documents on the Wiki. These documents can point to more detailed specs in our Web site. We should use the Theme documents to classify the Bugzilla entries by entering the URL of the Theme document in the Bugzilla URL field. We can then develop reports that group Bugzilla entries by URL.

We can also use the Theme documents to provide some level of hierarchy, say by adopting a naming convention for the URLs or using fragment ids for subtopics on a Theme page.

In the past, we generated Milestone Plan reports from Bugzilla by running a script and committing the generated report to CVS (which then refreshes the Web site). This meant that the reports were always slightly out of date. We should convert these scripts to PHP so they are executed on demand and therefore always up to date.

Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@xxxxxxx
Title: Detailed planning regarding Web Service support
From: wtp-pmc-bounces@xxxxxxxxxxx on behalf of Barheine, Joachim [joachim.barheine@xxxxxxx]
Sent: Tuesday, July 25, 2006 1:04 AM
To: wtp-pmc@xxxxxxxxxxx
Cc: Jagusch, Andre
Subject: [wtp-pmc] Detailed planning regarding Web Service support

Attachments: ATT7061577.txt

Hello,

as you may know SAP is one of the adopters of the WTP platform. Of particular interest to us is the further development (for WTP 2.0) in the web services area.

Two questions are very important to us here
- Will you introduce some sort of WS metamodel that goes beyond WSDL editing (i.e. is not restricted to the WSDL editor but used thoughout the entire WS parts)?

- Will support for WS-Security and WS-RM be tied to Axis 2.0 or will it be officially pluggable?

We would be very thankful if you could provide us with some insights in your current planning as we still have to decide how to proceed with WTP adoption in the WS area.

Many thanks in advance for you help and

Best regards
Joachim

Back to the top