[Building Sakai] Wicket Ajax Debug Console

[Steve Swinsburg]

When you load the web app, do you see this?
********************************************************************
*** WARNING: Wicket is running in DEVELOPMENT mode.              ***
***                               ^^^^^^^^^^^                    ***
*** Do NOT deploy to your live server(s) without changing this.  ***
*** See Application#getConfigurationType() for more information. ***
********************************************************************

?

cheers,
Steve


On 03/05/2013, at 12:05 AM, Brian Jones <bjones86 at uwo.ca> wrote:

> Ya, ScormTool.java is the 'Application' class (it extends
> SakaiWebApplication from sakai-wicket-for-scorm project which extends
> WebApplication), but the development flag is not set anywhere as far as I
> can tell.
> 
> Attached is the web.xml. OOTB it defines deployment mode inside the servlet
> definition. I've also tried setting it outside the servlet definitions in a
> context-param (like other wicket tools do).
> 
> Brian Jones
> Applications Development
> Information Technology Services
> Support Services Building, Room 4326
> Western University
> (519) 661-2111 x86969
> bjones86 at uwo.ca
> 
> 
> -----Original Message-----
> From: Steve Swinsburg [mailto:steve.swinsburg at gmail.com] 
> Sent: Wednesday, May 01, 2013 5:39 PM
> To: Brian Jones
> Cc: sakai-dev at collab.sakaiproject.org
> Subject: Re: [Building Sakai] Wicket Ajax Debug Console
> 
> Oops jut noticed you searched the code. When the webapp starts does it print
> a message in the log saying wicket is running in development mode and to not
> do this for production etc?
> 
> What is your deployed web.xml like?
> 
> Cheers
> Steve
> 
> Sent from my iPhone
> 
> On 02/05/2013, at 0:52, Brian Jones <bjones86 at uwo.ca> wrote:
> 
>> Hey Steve, thanks for your reply.
>> 
>> Not sure what you mean by 'Sakai Wicket', but I think not. It uses the
>> sakai-wicket-for-scorm-tool:
>> 
>> <dependency>
>> <groupId>org.sakaiproject</groupId>
>> <artifactId>sakai-wicket-for-scorm-tool</artifactId>
>> <type>jar</type>
>> <scope>compile</scope>
>> </dependency>
>> 
>> Which I have the source code for. However this project does not have a 
>> web.xml. I have searched both the SCORM source code and the 
>> sakai-wicket-for-scorm-tool source code for any occurrences of
> 'development'
>> in any file type, but nothing relevant is found.
>> 
>> Any other ideas?
>> 
>> Brian Jones
>> Applications Development
>> Information Technology Services
>> Support Services Building, Room 4326
>> Western University
>> (519) 661-2111 x86969
>> bjones86 at uwo.ca
>> 
>> 
>> -----Original Message-----
>> From: Steve Swinsburg [mailto:steve.swinsburg at gmail.com]
>> Sent: Wednesday, May 01, 2013 10:34 AM
>> To: Brian Jones
>> Cc: sakai-dev at collab.sakaiproject.org
>> Subject: Re: [Building Sakai] Wicket Ajax Debug Console
>> 
>> Does this use Sakai wicket? I think it does. Check that code to see if 
>> it's setting the development flag rather than deployment.
>> 
>> Cheers
>> Steve
>> 
>> Sent from my iPhone
>> 
>> On 02/05/2013, at 0:01, Brian Jones <bjones86 at uwo.ca> wrote:
>> 
>>> Hello,
>>> 
>>> I'm working on modifying some aspects of the SCORM player, adding in 
>>> some Ajax-y stuff here and there. My problem is that once I've added 
>>> an Ajax component to a page, I can never seem to get rid of the Ajax 
>>> Debug Console from the UI.
>>> 
>>> I've tried every avenue I know of to try to get rid of it. I've tried 
>>> the
>>> following:
>>> 
>>> 1) Define deployment mode in the servlet definition:
>>> <servlet>
>>>  <servlet-name>sakai.scorm.tool</servlet-name>
>>> 
>>> <servlet-class>org.apache.wicket.protocol.http.WicketServlet</servlet
>>> -
>>> class>
>>> 
>>>  <init-param>
>>>      <param-name>applicationFactoryClassName</param-name>
>>> 
>>> <param-value>org.apache.wicket.spring.SpringWebApplicationFactory</pa
>>> r
>>> am-val
>>> ue>
>>>  </init-param>
>>>  <init-param>
>>>      <param-name>configuration</param-name>
>>>      <param-value>deployment</param-value>
>>>  </init-param>
>>>  <init-param>
>>>      <param-name>applicationBean</param-name>
>>>      <param-value>toolWicketApplication</param-value>
>>>  </init-param>
>>> </servlet>
>>> 
>>> 2) Define deployment mode by itself above anything else in web.xml:
>>> <context-param>
>>>  <param-name>configuration</param-name>
>>>  <param-value>deployment</param-value>
>>> </context-param>
>>> 
>>> 3) Overriding getConfigurationType() in ScormTool.java:
>>> @Override
>>> public String getConfigurationType()
>>> {
>>>  return Application.DEPLOYMENT;
>>> }
>>> 
>>> 4) Overriding getConfigurationType() in SakaiWebApplication.java 
>>> (wicket-for-scorm project):
>>> @Override
>>> public String getConfigurationType()
>>> {
>>>  return Application.DEPLOYMENT;
>>> }
>>> 
>>> I made sure to clean out Tomcat's cache after each attempt, as well 
>>> as clean/build/deploy the project(s) after the modifications. But, to 
>>> my frustration, it never seems to respect any of these settings. I
>>> *always* get the Ajax Debug Console on the pages where I've added 
>>> Ajax-y components. I also tried changing the servlet definition to a 
>>> filter definition, as well as providing both a servlet and a filter 
>>> definition, but these two approaches blow up on Tomcat start-up.
>>> 
>>> Other Sakai tools that are using Wicket take approach #2, and it 
>>> works
>> fine.
>>> Can anyone give me any ideas as to why none of these are working for me?
>>> Thanks in advance.
>>> 
>>> Brian Jones
>>> Applications Development
>>> Information Technology Services
>>> Support Services Building, Room 4326
>>> Western University
>>> (519) 661-2111 x86969
>>> bjones86 at uwo.ca
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> sakai-dev mailing list
>>> sakai-dev at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>> 
>>> TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of 
>> "unsubscribe"
>> 
> <web.xml>