This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 139062 - [permui] SOA samples doesn't follow permanent ui spec
Summary: [permui] SOA samples doesn't follow permanent ui spec
Status: RESOLVED FIXED
Alias: None
Product: usersguide
Classification: Unclassified
Component: SOA (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Vladimir Yaroslavskiy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-04 19:48 UTC by Lukas Hasik
Modified: 2008-07-14 12:21 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lukas Hasik 2008-07-04 19:48:32 UTC 
According to the Permanent UI specification for NB IDE [1] there should not be 
*Samples | SOA | BPEL BluePrints* category in New Project wizard

Please follow the UI Review process [2] or remove it from IDE

[1] http://wiki.netbeans.org/NewProjectWizard#section-NewProjectWizard-Categories
[2] http://wiki.netbeans.org/UIReviewProcess
Comment 1 jrojcek 2008-07-08 09:07:33 UTC 
We're trying to keep the tree of categories flat if possible. In case of SOA, there's 3 templates in the SOA samples category. It would be perfectly okay to move 
the blueprints into the SOA category like this:

Samples | SOA:
    Asynchronous BPEL Process
    Synchronous BPEL Process
    Travel Reservation Service
    BPEL BluePrint 1
    BPEL BluePrint 2
    ...
Comment 2 Vitaly Bychkov 2008-07-08 09:38:45 UTC 
In a closest future we are going to add 
SOA XSLT samples
I believe another SOA-related projects(Data Integration Module, SQL Module, Intelligent Event Processing Module, e.c. )
going to do the same.

It is resulted into tens samples of different meanings.
IMO it is a place where it would be nice to have subcategories.
Comment 3 jrojcek 2008-07-08 09:48:20 UTC 
When you're ready to add new samples and you want to create a new category for it, you should follow the review process. Don't write a UI spec for this 
simple case, just file a review issue and describe what category you want to create and list all templates that would go inside. We will then discuss the best 
solution.

For the existing templates, there's no reason for the "BPEL BluePrints" category.
Comment 4 Vitaly Bychkov 2008-07-08 10:27:52 UTC 
BPEL Blue Prints samples and another 3 Bpel samples have different meanings. That is why they were putted into different
categories.
While there are just 8 samples and all of them are related to the bpel it could make sense to put them all in one list.
But on the next step we will have to back it again. 

Anyway I agree that current SOA samples structure is not well enough. 
It would be better to add categories for all SOA modules but so as there are now just BPEL Samples we didn't it.

More over as I see it is common practise to use 2 and 3 levels of samples categories, e.g: 
Mobility, Web... This approach looks more user friendly for me.
Comment 5 jrojcek 2008-07-08 11:44:35 UTC 
There's separate issues filed against the mobility and web categories.

Regarding the new samples for SOA, please provide the list of new samples we want to deliver for 6.5 so that we talk about concrete proposal and not about 
theoretical categorization. That would help us solve this issue.
Comment 6 Vladimir Yaroslavskiy 2008-07-14 12:21:02 UTC 
I moved blue prints samples to the upper SOA category:

fixed in soa-dev: b3f98b014cc0
fixed in main: 367cc94503fb