Along with adding the package requirement condition, the warning message
suggesting to create the web service with a package will have to be changed to
an error message explaining to the user why he can't go on to the next step.

In the interest to preserver consistency across the wizards (possibly the IDE),
where else should should this requirement condition be added? Isn't this going
to make the wizards too restrictive?

*** Issue 55724 has been marked as a duplicate of this issue. ***

*** Issue 53899 has been marked as a duplicate of this issue. ***

so far, this has to be done for web services only.
Ejb migh be ok.
Please, we need a fix in 4.1 for this on Web Services wizard.

Fixed. This change was applied to web services only, as per the above comment.

Checking in Bundle.properties;
/cvs/java/project/src/org/netbeans/modules/java/project/Bundle.properties,v  <--
 Bundle.properties
new revision: 1.29; previous revision: 1.28
done

Checking in JavaTargetChooserPanel.java;
/cvs/java/project/src/org/netbeans/modules/java/project/JavaTargetChooserPanel.java,v
 <--  JavaTargetChooserPanel.java
new revision: 1.23; previous revision: 1.22
done

Checking in JavaTemplates.java;
/cvs/java/project/src/org/netbeans/spi/java/project/support/ui/templates/JavaTemplates.java,v
 <--  JavaTemplates.java
new revision: 1.12; previous revision: 1.11
done

Checking in WebServiceWizard.java;
/cvs/websvc/dev/src/org/netbeans/modules/websvc/dev/wizard/WebServiceWizard.java,v
 <--  WebServiceWizard.java
new revision: 1.12; previous revision: 1.11
done

Fix needs to be backed out; the API change was not reviewed and is undocumented.

The fix was rolled back.

This fix can't make it into this release since there is not an alternate
reasonable way to implement it other than modifying
org.netbeans.spi.java.project.support.ui.templates.JavaTemplets for which it is
too late in the game to get approval as this issue is not a show-stopper.

org.netbeans.modules.java.project.JavaTargetChooser validates the package name
and  we need to let it know from outside the module to do the validation
slightly different in our case (and possibly other cases such as EJBs). 

Changing Target milestone to 'future'

2 or 3 other bugs was depending on this one.
I propose we force the creation of a package either pckg, or the name of the
project, javatized.

We need to keep looking for a fix for 4.1

Ludo

Trung, please take a look at this one...
A solution was done, by denied because it needed a change int the project
support publsihed apis...
How would do a code developer to force a wizard to have a real package and not
the default package...
I am sure you can find a solution with Jesse G.
If we cannot fix this one, I need to reopne a few  bugs because, having ws in
default package cannot compile with wscompile , or cannot be refactored or deleted.

Thanks 

Ludo, please work directly with Jesse to resolve it.  You two can talk with each
other directly.  

If I understand correctly the change was rolled back because it's unreviewed api
change.  You need to request the api change first with proper description with
use case and justification.

I also raise priority to P2.  This looks like a bad user experience problem.  If
she accepts all the defaults from the IDE, she ends up with broken code

I think that the API addition in JavaTemplates is actually OK.
Can this be reviewed and applied as it is? API reviewers, please comment.

I am copying the previous change that was done without review:

Directory: /java/project/src/org/netbeans/spi/java/project/support/ui/templates/
================================================================================
File [changed]: JavaTemplates.java
public static WizardDescriptor.Panel createPackageChooser(Project project,
 SourceGroup[] folders, WizardDescriptor.Panel bottomPanel, boolean 
validPackageRequired) throws IllegalArgumentException {
if (folders.length == 0) {
  throw new IllegalArgumentException("No folders selected"); // NOI18N
 }
 return new JavaTargetChooserPanel(project, folders, bottomPanel, false,
validPackageRequired);
  } 

Petr Hrebejk owns project ui api.  Please file a separate api change request
issue and assign to him.  Attach the patch 

The change would be in projecs module not websvc.  Wrong component

Fixed.

Checking in src/org/netbeans/modules/websvc/dev/wizard/WebServiceWizard.java;
/cvs/websvc/dev/src/org/netbeans/modules/websvc/dev/wizard/WebServiceWizard.java,v
 <--  WebServiceWizard.java
new revision: 1.15; previous revision: 1.14
done

[Build 20050403]