Bug 89808 Wording on the acess rules pages
20050329 - we should use 'Forbidden' instead of 'Non-accessible' to be consistent with jdt.core and the compiler settings - the text on the 'new access rules' should give examples for patterns
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/TypeRestrictionEntryDialog.java
String pattern= fPatternDialog.getText().trim();
		if (pattern.length() == 0) {
			fPatternStatus.setError(NewWizardMessages.getString("TypeRestrictionEntryDialog.error.empty")); 
			return;
		}
		IPath path= new Path(pattern);
		if (path.isAbsolute() || path.getDevice() != null) {
			fPatternStatus.setError(NewWizardMessages.getString("TypeRestrictionEntryDialog.error.notrelative")); 
			return;
		}
		
		fPattern= pattern; 
		fPatternStatus.setOK();
	}
	
	public IAccessRule getRule() {
		IPath filePattern= new Path(fPattern);
		int kind= fRuleKinds[fRuleKindCombo.getSelectionIndex()];
		return JavaCore.newAccessRule(filePattern, kind);
	}
	
	/*
	 * @see org.eclipse.jface.window.Window#configureShell(Shell)
	 */
	protected void configureShell(Shell newShell) {
		super.configureShell(newShell);
		PlatformUI.getWorkbench().getHelpSystem().setHelp(newShell, IJavaHelpContextIds.ACCESS_RULES_DIALOG);
	}
}