I'll have to double check on this for sure when I get home, but a simple
JBOSS question. I can't just run mvn package jboss-as:deploy over and over
again? This has seemed to work for months up until this point. Obviously
I need to discontinue if it's not good practice; I just didn't know any
better. I'll try again when I get home. I'm on a different computer
that's out of sync with my code at home.
Here's the class:
package com.campingawaits;
import org.apache.wicket.Page;
import org.apache.wicket.Session;
import org.apache.wicket.authorization.IAuthorizationStrategy;
import
org.apache.wicket.authorization.strategies.page.SimplePageAuthorizationStrategy;
import org.apache.wicket.protocol.http.WebApplication;
import org.apache.wicket.request.Request;
import org.apache.wicket.request.Response;
import org.apache.wicket.settings.IRequestCycleSettings.RenderStrategy;
import com.campingawaits.auth.AuthenticatedWebPage;
import com.campingawaits.auth.CampingAwaitsSession;
import com.campingawaits.auth.SignIn;
import com.campingawaits.base.About;
import com.campingawaits.base.Blog;
import com.campingawaits.base.ContactUs;
import com.campingawaits.base.Index;
import com.campingawaits.blog.BlogDetails;
/**
* Application object for your web application. If you want to run this
application without deploying, run the Start class.
*
* @see com.campingawaits.Start#main(String[])
*/
public class CampingAwaitsApplication extends WebApplication
{
/**
* Contstruct
*/
public CampingAwaitsApplication()
{
}
/**
* @see org.apache.wicket.Application#getHomePage()
*/
@Override
public Class<? extends Page> getHomePage() {
return Index.class;
}
/**
* @see
org.apache.wicket.protocol.http.WebApplication#newSession(org.apache.wicket.request.Request,
* org.apache.wicket.request.Response)
*/
@Override
public Session newSession(Request request, Response response)
{
return new CampingAwaitsSession(request);
}
/**
* @see org.apache.wicket.Application#init()
*/
@Override
public void init() {
super.init();
getResourceSettings().setThrowExceptionOnMissingResource(false);
getRequestCycleSettings().setRenderStrategy(RenderStrategy.REDIRECT_TO_RENDER);
IAuthorizationStrategy authorizationStrategy = new
SimplePageAuthorizationStrategy(
AuthenticatedWebPage.class, SignIn.class) {
@Override
protected boolean isAuthorized() {
return (((CampingAwaitsSession)Session.get()).isSignedIn());
}
};
getSecuritySettings().setAuthorizationStrategy(authorizationStrategy);
/*mountPage("/", Index.class);*/
mountPage("/news", Blog.class);
mountPage("/news/${id}", BlogDetails.class);
mountPage("/contact", ContactUs.class);
mountPage("/about", About.class);
}
}
_______________________________________
Stephen Walsh | http://connectwithawalsh.com
On Sun, Jan 27, 2013 at 10:38 AM, procrastinative.developer <
[email protected]> wrote:
> I think that Sven has right about war duplication. Jboss maven plugin has 3
> goals to manage deployments: deploy, redeploy, undeploy. If you use only
> deploy goal, jboss could leave some trashes in deployment location.
>
> So if you reinstall JBoss, the old configuration files could still be on
> your disc. You should remove this folders (temp, works etc) - I don't know
> where this files are located on mac.
>
> Fast check: Download fresh zipped installation from JBoss site
> (http://www.jboss.org/jbossas/downloads) and unzip it, copy war into
> %JBOSS%/standalone/deployments and run it %JBOSS%/run/stanalone
>
>
> Can you publish also the com.campingawaits.CampingAwaitsApp class?
>
>
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Upgrade-to-6-5-0-tp4655782p4655802.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
