× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



If you need to change the Context Root, right-click your web module
project, select "Properties", then "Web" and change the context root.
It will apply the changes to the .websettings file in the project and
update the Application Deployment Descriptor in the associated EAR
project.

Spaces are not a good idea because the browser encodes the spaces to
%20.  It looks like WebSphere doesn't decode the URL before doing the
Virtual Host/Web Group match.

HTH,
Robert

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Joe Pluta
Sent: Tuesday, October 12, 2004 11:11 AM
To: 'Websphere Development Studio Client for iSeries'
Subject: RE: [WDSCI-L] PLGN0021E: Web group not has not been defined

Rick, there's no requirement for the context to be lower case, though
embedded spaces are probably not a good idea.  I'm not sure whether
logic has been added in 5.1.2 to "help" you by changing your context
name to something it thinks is appropriate, but I can at least tell you
how to find what that context name is.

Open up your EAR Deployment Descriptor (if you haven't created your own
EAR project, one called DefaultEAR will have been created for you).
Click on the Modules tab and you will see all your WAR files (there may
only be one if you only have one project).  If you click on the WAR
file, you should see the context root in the upper right portion of the
view.

Joe

> From: Rick.Chevalier@xxxxxxxxxxxxxxx
> 
> Hi Joe,
> 
> I'm using version 5.1.2.  All the updates have been applied even
though
> the version number doesn't reflect it.  Don't know why.  I believe it
was
> this way with 5.0 also.
> 
> Is there any requirement that the context be in a specific case or not
> have spaces?  It seems odd that changing to lower case and removing
spaces
> would correct the problem.  Maybe when the references were updated
> something got changed behind the scenes that corrected the problem not
the
> changes I made.

_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.