[Chameleon] Chameleon 1.99 Beta 2 - CWC default context not r ecognized

[Paul Spencer]

Jacob,

it is possibly a bug, but the only way I can reproduce it right now is 
to have an invalid configuration.

I'll need some more details on this, including where everything is 
installed and your configuration files I think.

The directory structure should remain the same as in the zip file.  The 
cwc2 service instance is now just a simple application that 'include's 
the chameleon core, so it is much smaller and doesn't have any widgets 
of its own.

Cheers,

Paul

Delfos, Jacob wrote:

> Jeff
> 
> Yes, they are definitely set. I copied my configuration from my previous CWC
> setup (1.0.4). I copied it 1 parameter at a time, it should all be correct.
> However, I do not have any indication it is accessing the cwc2.xml file at
> all, because if I temporarily remove it, I get the same error. Should the
> directory structure remain as it is given in the beta2 zip file? This means
> that the config directory is at the same level as the CWC2 directory (as
> opposed to inside the htdocs directory). Also, should the htdocs directory
> be as empty as it is, or was I supposed to move all files around to make it
> similar to the old-style setup?
> 
> Regards,
> 
> Jacob
> 
> 
> -----Original Message-----
> From: Jeff McKenna [mailto:jmckenna at dmsolutions.ca] 
> Sent: Friday, 30 July 2004 10:47 PM
> To: Delfos, Jacob
> Cc: chameleon at lists.maptools.org
> Subject: Re: [Chameleon] Chameleon 1.99 Beta 2 - CWC default context not r
> ecognized
> 
> 
> Can u verify that in cwc2.xml that you have the following paths set 
> correctly?:
> 
>      <context-param>
>          <param-name>default_context</param-name>
>          <param-value>world_context.xml</param-value>
>          <description>Default map context to load when starting this 
> application</description>
>      </context-param>
> 
>      <context-param>
>          <param-name>context_root</param-name>
>          <param-value>/ms4w/apps/chameleon/cwc2/contexts/</param-value>
>          <description>Absolute root path to context files. All context 
> should be in that folder (or sub folder).</description>
>      </context-param>
> 
> 
> jeff
> 
> 
> 
> 
> Delfos, Jacob wrote:
> 
>>When I configure the CWC instance to use a default context and template, I
>>still get this error:
>>
>>request URI was http://auper1pc364/cwcepra/cwc2.php
>>query string was service=VCG&request=GetApplication&version=0.1.0
>>Invalid request. No CONTEXTS parameter was provided and the Service
> 
> Instance
> 
>>has no default context
>>
>>I'm using the same templates as for the normal chameleon, and my setup is
>>exactly similar to the one I use for CWC 1.0.4 (which works).
>>
>>Jacob
>>
>>
>>
>>-----Original Message-----
>>From: chameleon-bounces at lists.maptools.org
>>[mailto:chameleon-bounces at lists.maptools.org] On Behalf Of Paul Spencer
>>Sent: Thursday, 29 July 2004 3:15 AM
>>To: Ken Sanderson
>>Cc: chameleon at lists.maptools.org
>>Subject: Re: [Chameleon] Chameleon 1.99 Beta 2
>>
>>
>>Ken ...
>>
>>Ken Sanderson wrote:
>>
>>
>>
>>>Just installing the new version and had a couple general questions.
>>>
>>>The description of CWC2 says it allows for the creation of a chameleon
>>>application without a local install. Can someone give me an example of
>>>when you might use this? Are there limits on who can use CWC2 once you
>>>have it setup? I assume that my server would be doing the work of the
>>>other remote applications?
>>
>>
>>You would want to do this if you:
>>
>>* only want to set up only one server
>>* you want to allow other organizations to run apps without installing 
>>anything
>>* rapid application development
>>* centralized management
>>
>>... and probably other reasons too
>>
>>There are some limits you can place, either through the configuration 
>>files or through appropriate limitations in your web server.
>>
>>In the configuration files, you can choose to allow or deny access to 
>>remote contexts and templates.  If you deny access, you effectively 
>>limit them to only templates and contexts hosted on the server.  You 
>>should also limit the "root" of the context and template files.
>>
>>You can also restrict access with a .htaccess file (or IIS equivalent?)
>>
>>Your server would be doing all the work.
>>
>>
>>
>>>Do we need to install the CWC2, or is it optional? I know the folder is
>>>there, but if you don't want to use this feature do you need to go
>>>through the installation regardless? I noticed a few errors in the
>>>samples that I didn't have before, but I havent done the CWC2 install
>>>yet and wondering if that's the likely cause?
>>
>>
>>CWC2 is completely optional.  It is distributed with Chameleon but is 
>>only available if you actively configure it to be so.  Note that the 
>>MS4W version does come with it enabled.
>>
>>I highly doubt that CWC2 would break the samples.  They are broken all 
>>by themselves :)
>>
>>Paul
>>
>>
>>
>>
>>>Thanks,
>>>
>>>Ken
>>>Miistakis
>>>
>>>
>>>_______________________________________________
>>>Chameleon mailing list
>>>Chameleon at lists.maptools.org
>>>http://lists.maptools.org/mailman/listinfo/chameleon
>>>
>>
>>
> 
> 

-- 
  -----------------------------------------------------------------
|Paul Spencer                           pspencer at dmsolutions.ca   |
|-----------------------------------------------------------------|
|Applications & Software Development                              |
|DM Solutions Group Inc                 http://www.dmsolutions.ca/|
  -----------------------------------------------------------------