Work is the Curse of the Web Technologist

While it is very good to be busy in economic times such as these, it becomes easy to fall behind when keeping ahead. One obvious example is the fall off of my postings on this blog. The other is when a new spec right at the heart of my day-to-day livlihood is under construction for four months before it pops up on my radar.

In this case, I’m talking about HTML 5.

OTOH, web specifications seem to be totally outside of the whole “Internet speed” thing, because I’m still waiting for there to be more HTML 4 compliant pages on the web 🙂

If you found this interesting, please share.

© Scott S. Nelson

WebLogic Workshop 8.x Out Of Memory Fix

A clip from the release notes:

Large Applications May Require Additional Memory Allocation If you are building and testing a large application, WebLogic Workshop may run out of memory, which can cause it to run slowly or shut down. Workaround: You can increase your memory allocation by modifying the Workshop.cfg file, located in the BEA_HOMEweblogic81workshop directory. Add this flag to the command-line arguments: VM flag -Xmx512m

If you found this interesting, please share.

© Scott S. Nelson

WSRP over HTTPS in WLP

Ever run across a problem that sounds real familiar, but you don’t remember all the details of the solution? Recently someone was telling me an issue they were having with WSRP where the WSDL when accessed over the HTTPS port still showed the HTTP end point.  That is when I experience De Ja Vue (I’v seen this before).

When using HTTPS with WSRP in WLP you must edit the wsrp-producer-config.xml in the producer application:

<!– This element describes the capabilities of this producer. Set the secure attribute to “true” if you require this producer offer any port over SSL. –>
<service-config>
<registration required=”true” secure=”true“/>
<service-description secure=”true“/>
<!– Set accepts-mime to true to more efficiently process uploaded files when the consumer is a WebLogic Portal. –>
<markup secure=”false” rewrite-urls=”true” transport=”string” accepts-mime=”false”/>
<portlet-management required=”true” secure=”true“/>
</service-config>

The bold is where the default value has been changed to true. My conclusion from this is that with WLP your WSRP portlets are either available over HTTP or HTTPS, but not both. I haven’t tested this theroy, however, as I have not yet worked on a WSRP project that was not over HTTPS.

If you found this interesting, please share.

© Scott S. Nelson

Speed Up The WebLogic Portal Admin Tool

Large WLP applications usually have many desktops. For speed and convenience, these are often based on a .portal file. You may notice a long delay in the loading of the list of .portal files when creating a new desktop. If you do, you can greatly improve the speed of that list being created with one or two steps. The firs step is to store all of your .portal files in a single location. Many people do this already, which is why for them this will be a one step process. The final step is to add the path in web.xml like this:

<context-param>
 <param-name>portalFileDirectory</param-name>
 <param-value>/</param-value>
</context-param>

 

This can be found in the performance tuning manual that comes with WLP, but we all know how often we get to read the whole manual 🙂

If you found this interesting, please share.

© Scott S. Nelson

One AJAX XSS Solution

While there are definitly some cool aspects to AJAX, it also reminds me of the good old days of the browser wars (which seem to be back, albeit more of a Cold War).  While my personal preference is to stick to simple solutions that will cause less headaches in production, sometimes you just have to do something the hard way. So far, I’ve been lucky and have found a simpler solution to the AJAX needs of my clients, but I almost didn’t once, which is when I found an article at Solitex Networks on one solution. I’m sure there are other approaches, and would love to see some comments pointing them out.

If you found this interesting, please share.

© Scott S. Nelson