Reputation
391
Next privilege 500 Rep.
Access review queues
Badges
1 7
Impact
~23k people reached

  • 0 posts edited
  • 3 helpful flags
  • 41 votes cast
Jun
10
comment handling external events in a cluster environment
RE:my trigger will be fired 4 times - I'm not entirely clear on the concern here: if you have 4 separate VMs, connected to the same DB, won't you want the notification to be available in all 4 VMs?
May
25
answered Designing Message class in Java
May
24
answered Would implementing a “Throwable Event System” be abusive?
Apr
15
comment How can I find what Resources a Java EE container provides?
The point I'm trying to communicate @marcus, is that @Resource is not a reserved category of components, like the TimerService is
Apr
13
answered How can I find what Resources a Java EE container provides?
Mar
29
comment Pattern for validating rules having different signatures
Just create a Context object that can be passed down the chain, regardless of the execution context (whether event handler or rule). This way, whatever component is currently handling the context object just need be aware of what it wants from the object. It's a fairly common pattern (don't know it's name) in web applications and DI containers
Nov
20
comment Passing by value multiple times vs. Creating a public class variable
en.wikipedia.org/wiki/Data_transfer_object
Nov
13
comment Designing a better performing total permissions setup for multiple permission levels
I don't see a problem here (or I don't understand the problem): Each client will have a group of available applications. Access to each application is supposed to be a permission. Group permissions into roles. This way, you can have multiple permutations of the same permissions. Some of your assertions don't add up (or aren't clear): "But, maybe for Application "Fruit" I grant the permission for Grape" - I don't get that. Fruit and Grape are two separate applications. Why are their permissions intersecting?
Oct
19
answered Design Question - System Integration
Oct
10
comment OOD: Java inheritance and access to child methods via casting
Looks like you're shoehorning inheritance into your use case. If the children cannot use inheritance to take advantage of a common parent, you're going to need to review your class design
Sep
26
comment which pattern is most intuitive for a calculator app?
I think the command pattern (that's what it looks like you're going for, but you just took a wrong left turn somewhere) is right for your use case. It might bulk up your code base, but you get cohesion and reusability also
Sep
24
awarded  Autobiographer
Aug
3
comment How to validate information on server without using database or session
It reads like you're trying to re-invent some variation of the "remember-me" functionality. All your options involve either hitting the database multiple times to verify info or storing info in the session - "Use a cache", cache where?
Jun
10
comment Pooling (Singleton) Objects Against Connection Pools
@MikePartridge - I mean it's outside of my reach from a domain perspective. It's not for a database, it's an ECM. Aside from the domain issue, I simply am not satisfied with the way the ECM responds to pool exhaustion - with catastrophic failure.
Jun
10
comment Pooling (Singleton) Objects Against Connection Pools
@MikePartridge - The same way any other pool handles it: queueing requests. Requests can wait within a specified timeout for a DAO to be available. The difference between that and actually pooling the resource in my case is that I don't have control over the timeout of the resource; hence why I'm trying to throttle it at the DAO level
Jun
9
comment Pooling (Singleton) Objects Against Connection Pools
@MikePartridge - My concern is not the object instantiation per se; it's the resource contention that results that worries me. On instantiation, each object will attempt to grab a connection from the pool. Uncurtailed instantiation will result in quick exhaustion of the pool. Pre-instantiating will ensure controlled access to pooled resources
Apr
11
comment Pooling (Singleton) Objects Against Connection Pools
An oversight on my part, sorry about that; It's a multithreaded webservice that connects to a popular ECM. Currently, each request to that service creates a new DAO, which in turn tries to get a new connection. My thinking is that a single DAO (or pool of DAOs), given the fact that there's no mutable state anywhere along the chain of command. What do you think?
Apr
10
awarded  Commentator
Apr
10
comment Pooling (Singleton) Objects Against Connection Pools
The way I read the linked material, these frameworks need to instantiate new context objects because by definition, they are context sensitive and consequently not reusable. The Linq resource also observes most other ORMs are stateless in their data connectivity and management object. The Linq-SQL pattern is not the norm. My example is far from hypothetical and there's no state being manipulated in the DAOs. In the same way a servlet container only ever creates a single instance of a servlet, it should be safe to reuse durable DAOs
Apr
10
revised Pooling (Singleton) Objects Against Connection Pools
added 126 characters in body