Where answers come from

Some pages can ask a language model questions. Set this up once; your choice is remembered in this browser for the whole site.

Model source
Use another source instead

Smallest-to-largest weight downloads. Qwen3.5 0.8B is our starting choice for page Q&A. GPU estimates are not total RAM: leave room for the browser, context and temporary buffers. Hardware changes speed and capacity; answers still need checking.

Session-only loading avoids saving model weights, uses extra RAM and downloads again after unloading. Turn it off to save downloads. Delete-data-on-exit or private browsing may impose a much smaller storage limit than the displayed estimate.

You sign in on OpenRouter; it gives this page a key for your account.

A free account does not make every model free. Choose a model with a listed :free variant; merely adding that suffix does not create one. Check free-model availability and pricing.

Chat

AI assistant, not Shawn Hartsock. It does not speak for him.

Inspect the page excerpt

Up to 4,800 characters, not the whole site. Recent conversation turns are retained within the model’s context limit.

Ask about this page, or just say hello.

Ready when you are.

Not saved or uploaded automatically. Closing keeps this conversation in this tab; changing pages starts a new one. Model replies can be wrong.

JBoss Portal 2.6.0 woe and the fix

Originally published .

I recently posted a problem in JBoss Forum and got an answer.

The problem was:


16:38:07,433 ERROR [StartupServletContextListener] Error initializing ServletContext

java.lang.IllegalArgumentException: Class org.jboss.portal.faces.portlet.JSFMetaBridgeViewHandlerImp

l is no javax.faces.application.ViewHandler

Which is consistent with deployment isolation issues. It turns out that you can’t isolate the right classes between a 2.6.0 install of JBoss Portal and certain legacy JSF servlets. The class cast problem will follow you around.

The fix is to head on over to:


http://anonsvn.jboss.org/repos/portal/trunk

checking that out and running build/build.sh deploy on that… (make sure your JBOSS_HOME is set and no old versions of jboss-portal.sar are lying around). From the trunk directory…


 $ export JBOSS_HOME=/usr/local/jboss

 $ ./build/build.sh

After that life in JSF land is good. Very vexing problem if you are doing anything in JSF not specific to JBoss Portal

Explore the map · Browse by topic and date