Technical Beef - - Latest comments

In response to: Jdbc Jutsu Saves Heap Memory Against Wicket's Stateful Ajax

jazz [Visitor] — Thu, 20 May 2010 07:49:05 +0000

i use the way named JDBCStore.But i find nothing from the table tomcat_sessions.what's the reason ?

In response to: Tomcat, JSessionID, and subdomains...

Mahmoud Saleh [Visitor] — Wed, 05 May 2010 09:31:52 +0000

so jessionid cannot be used with https?

In response to: OSGI-fying the apache commons-logging API

nogunner [Member] — Thu, 08 Apr 2010 12:43:56 +0000

Hi Toni,

I hesitated somewhat to publish your comment, because it severely lacks arguments, and I think you're missing the big picture here. Anyway, it's not worth than some of the viagra-spam that sometimes pass the spam barrier, so I just let it.

First, the point you mention was already discussed there: http://blog.kornr.net/index.php/2008/12/18/osgi-logging-putting-it-all-together (read the comments please)

I'm not sure why you're aggressively defending Pax Logging, which is not a bad solution except it fragments _again_ the logging frameworks used by the java community, which by itself is enough to keep it at bay, but what really bothered me was all the FUD the PAX initiative seemed to use in order to justify their solution. From what I can see, bad habits are not lost.

Regarding your argument "it creates fat "self contained" bundles, sweeping out the entire service layer and replacing it with monotholic (I suppose you mean "monolithic", right?) uber bundles", it only shows you have not correctly understood what commons-logging is: it's not just a logging framework, it's also designed to be a _facade_ for a logging system that you can define at runtime. Let me put some emphasis on this: FACADE. I'm pretty sure you know how the facade pattern works, and why it makes sense to keep this facade because, well, it's widely used and can be considered a de facto standard.

It's straightforward to keep the commons-logging facade (that's 2 classes, Log and LogFactory), and just change the code behind to call the the OSGi Log Service instead of the normal commons-logging engine that is available by default. That's what the sample code I provide (2 classes, 6Kb in total, is that what you call fat?) do. Nothing more. The benefit of that is that only one logging API is used (read facade), and a common code base can be shared between OSGi and non-OSGi projects.

Now, please read the article I mentionned above, and if you have any suggestion for a better solution (and I'm sure there are), please do not hesitate to give a pointer. Pax Logging is not what _I_ call a better solution, but I'm not offended if it is for others. Just, please, stop the FUD, I'm sure you can make up better arguments than that to convince people to use your PAX stuff.

In response to: OSGI-fying the apache commons-logging API

Toni Menzel [Visitor] — Thu, 08 Apr 2010 10:03:15 +0000

Hi,

just found your blogs and complaints about Pax Logging.
Looking at your solution, i don't know if this is an april fool's joke or ment to be serious? Are you really saying that embedding the commons logging libs into each bundle is a solution?
What you showed here is counter-productive as it creates fat "self contained" bundles, sweeping out the entire service layer and replacing it with monotholic uber bundles.
I am not sure, maybe this article is too old (2008?) and does not reflect your current mindset anymore. (i hope so).
No offence, just blown away from spreading those code smells.
cheers,
Toni

In response to: Tomcat, JSessionID, and subdomains...

Karen [Visitor] — Fri, 05 Mar 2010 01:20:11 +0000

Heman,

No you can't use this solution with different domains. A JSESSIONID is just an HTTP cookie and HTTP cookies can't be shared with different domains (browser will not send cookies to different domains).

In response to: Someone out there is a total moron

L [Visitor] — Wed, 18 Nov 2009 22:06:41 +0000

It was done on purpose to confuse the issue from what I've understood.

In response to: Announcing Swit 0.9.0

Ýñòîíêà [Visitor] — Mon, 21 Sep 2009 07:41:51 +0000

Äàííàÿ ïóáëèêàöèÿ èìååò íåôîðìàëüíûé, èíôîðìàòèâíûé ñòèëü, áîëüøîå ñïàñèáî Âàì!

In response to: Announcing Swit 0.9.0

Nick [Visitor] — Sun, 20 Sep 2009 01:58:43 +0000

Very cool stuff.