date:20120613

Re: References not loading correctly. Wicket 1.5.7

2012-06-13 Thread Martin Grigorov

Hi,

Please create a quickstart and attach it to a ticket in Jira.

On Wed, Jun 13, 2012 at 4:12 AM, Sean Kendall - NASource Imports
s...@nasource.com wrote:
 I wish it as that easy.   :p

 I did add in the super.renderHead(response); call (and I already had it
 set in child classes).

 But still my styles are not showing up. The other weird thing is that if I
 shutdown my app, re-create the artifacts and basically redeploy; the first
 time I open my 'HomePage' I see all my styles again, but after doing a
 page refresh, all styles are removed again and the following WARNING shows:

 WARN  - ResourceReferenceRegistry  - Asked to auto-create a
 ResourceReference, but
 ResourceReferenceRegistry.createDefaultResourceReference() return null.
 [scope: com.company.web.WebDummy; name: jquery/js/jquery.myjavascript.js;
 locale: null; style: null; variation: null]

 Possibly is a caching problem?







 On 12-06-12 12:24 AM, Martin Grigorov mgrigo...@apache.org wrote:

Hi,

On Tue, Jun 12, 2012 at 4:46 AM, Sean Kendall - NASource Imports
s...@nasource.com wrote:
 I am not sure if this is something I am missing or a bug in wicket
(1.5.7)
 (Tomcat 6)

 Basically, I am trying to add CSS and JS references to my 'BasePage'
 (extends WebPage) and my references are not loading.
 The actual markup has a link to the JS and CSS files, yet they do not
link
 to the actual files.

 Here is the basic setup of my 'BasePage.class'

 code

 public abstract class BasePage extends WebPage implements
 IHeaderContributor{

No need to implement IHeaderContributor.
o.a.w.Component does this for you in 1.5.x.


 protected BasePage() {
        initPage();
    }

 private void initPage() {
 this.setStatelessHint(true);
 //add a bunch of componentsŠ
 Add(some new Component);
 //end of my adding component code
 }//end of initPage

 public void renderHead(IHeaderResponse response) {

I see you do not call: super.renderHead(response).
For the base page it is not really needed but if you skip this call in
the children pages' #renderHead() then the following code wont be
executed and this will lead to the problem you describe.


        response.renderCSSReference(new
CssResourceReference(WebDummy.class,
 css/wicketIsAwesome.css), screen);
        response.renderJavaScriptReference(new
 JavaScriptResourceReference(WebDummy.class, js/javascriptRocks.js));
        response.renderJavaScriptReference(new
 JavaScriptResourceReference(WebDummy.class, js/lightbox.js));
        response.renderCSSReference(new
CssResourceReference(WebDummy.class,
 css/commonCss.css));
 //add to some page
        if (this instanceof AwesomeWicketPage) {
            response.renderCSSReference(new
 CssResourceReference(WebDummy.class, css/jqu.jqz.css));
            response.renderJavaScriptReference(new
 JavaScriptResourceReference(WebDummy.class, js/libjs-1.6.js));
            response.renderJavaScriptReference(new
 JavaScriptResourceReference(WebDummy.class, js/mylibsJs-core.js));
        }
 }//end of renderHead
 }//end of class
 /code

 This is my Directory Structure (hopefully this makes sense):
 -src (directory)
 ---main (directory)
 --java (directory)
 com.company (directory)
 ---com.company.common (directory)
 ---BasePage.class
 ---BasePage.html
 ---com.company.web (directory)
 ---WebDummy.class
 ---com.company.web.js  (directory)
 ---javascriptRocks.js
 ---lightbox.js
 ---libjs-1.6.js
 ---mylibsJs-core.js
 ---com.company.web.css (directory)
 ---wicketIsAwesome.css
 ---commonCss.css
 ---jqu.jqz.css


 Anyone?










--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: References not loading correctly. Wicket 1.5.7

2012-06-13 Thread vineet semwal

it actually means can't find jquery.myjavascript.js at the path you
provided ie. the path relative to WebDummy
so do you have that file in  com/company/web/jquery/js directory?

On Wed, Jun 13, 2012 at 6:42 AM, Sean Kendall - NASource Imports
s...@nasource.com wrote:
 I wish it as that easy.   :p

 I did add in the super.renderHead(response); call (and I already had it
 set in child classes).

 But still my styles are not showing up. The other weird thing is that if I
 shutdown my app, re-create the artifacts and basically redeploy; the first
 time I open my 'HomePage' I see all my styles again, but after doing a
 page refresh, all styles are removed again and the following WARNING shows:

 WARN  - ResourceReferenceRegistry  - Asked to auto-create a
 ResourceReference, but
 ResourceReferenceRegistry.createDefaultResourceReference() return null.
 [scope: com.company.web.WebDummy; name: jquery/js/jquery.myjavascript.js;
 locale: null; style: null; variation: null]

 Possibly is a caching problem?







 On 12-06-12 12:24 AM, Martin Grigorov mgrigo...@apache.org wrote:

Hi,

On Tue, Jun 12, 2012 at 4:46 AM, Sean Kendall - NASource Imports
s...@nasource.com wrote:
 I am not sure if this is something I am missing or a bug in wicket
(1.5.7)
 (Tomcat 6)

 Basically, I am trying to add CSS and JS references to my 'BasePage'
 (extends WebPage) and my references are not loading.
 The actual markup has a link to the JS and CSS files, yet they do not
link
 to the actual files.

 Here is the basic setup of my 'BasePage.class'

 code

 public abstract class BasePage extends WebPage implements
 IHeaderContributor{

No need to implement IHeaderContributor.
o.a.w.Component does this for you in 1.5.x.


 protected BasePage() {
        initPage();
    }

 private void initPage() {
 this.setStatelessHint(true);
 //add a bunch of componentsŠ
 Add(some new Component);
 //end of my adding component code
 }//end of initPage

 public void renderHead(IHeaderResponse response) {

I see you do not call: super.renderHead(response).
For the base page it is not really needed but if you skip this call in
the children pages' #renderHead() then the following code wont be
executed and this will lead to the problem you describe.


        response.renderCSSReference(new
CssResourceReference(WebDummy.class,
 css/wicketIsAwesome.css), screen);
        response.renderJavaScriptReference(new
 JavaScriptResourceReference(WebDummy.class, js/javascriptRocks.js));
        response.renderJavaScriptReference(new
 JavaScriptResourceReference(WebDummy.class, js/lightbox.js));
        response.renderCSSReference(new
CssResourceReference(WebDummy.class,
 css/commonCss.css));
 //add to some page
        if (this instanceof AwesomeWicketPage) {
            response.renderCSSReference(new
 CssResourceReference(WebDummy.class, css/jqu.jqz.css));
            response.renderJavaScriptReference(new
 JavaScriptResourceReference(WebDummy.class, js/libjs-1.6.js));
            response.renderJavaScriptReference(new
 JavaScriptResourceReference(WebDummy.class, js/mylibsJs-core.js));
        }
 }//end of renderHead
 }//end of class
 /code

 This is my Directory Structure (hopefully this makes sense):
 -src (directory)
 ---main (directory)
 --java (directory)
 com.company (directory)
 ---com.company.common (directory)
 ---BasePage.class
 ---BasePage.html
 ---com.company.web (directory)
 ---WebDummy.class
 ---com.company.web.js  (directory)
 ---javascriptRocks.js
 ---lightbox.js
 ---libjs-1.6.js
 ---mylibsJs-core.js
 ---com.company.web.css (directory)
 ---wicketIsAwesome.css
 ---commonCss.css
 ---jqu.jqz.css


 Anyone?










--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




-- 
thanks,

Vineet Semwal

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Wicket as Jboss Modules

2012-06-13 Thread Martin Grigorov

Hi,

Wicket uses ThreadLocal for the Application, Session and RequestCycle.
There are no JVM singletons.

Some people are against putting jars in the shared lib folder. I
personally see the benefit and I'd do it if I need to
If you use shared jars then make sure that none of the applications
provide these jars or another version of them because in this case you
will see some ClassLoader related problems, e.g.: ClassCastException:
o.a.w.Session class is not o.a.w.Session.

On Tue, Jun 12, 2012 at 11:04 PM, Martin Sachs sachs.mar...@gmail.com wrote:
Hello,

i think that is in general not a good idea. If you deploy the wicket-lib
outside the war and run multiple Wicket-Applications, then you could not use
all applications, because wicket stores (as far as i know) e.g. the
application instance in a static field. There is one application per
WAR-deployment with wicket, but if you use the libs from ear/lib or modules
there will be only one application.

best
Martin

Илья Нарыжный schrieb:

Hello,

I have several projects which use wicket and various wicket sun-modules.
Every project (*.ear file) took about 10Mb and about 8Mb is for wicket
libraries.
Recently I have move my projects to Jboss AS 7 and now I'm thinking
about putting all wicket related jars to JBOSS_HOME/modules.

49 matches

Mail list logo