How come FastLaneReader is a pattern?

[Satya Narayan]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Do you think FFR should be treated as a pattern.

 

Here we are directly acessing the DB via JDBC apis in place of passing it to an entity bean. That is all.

 

If we consider it to be a pattern, then every code I write becomes a pattern in some way or other.

 

Any other use of FFR other than mentioned at Sun website which will truly validate that its claim to be a pattern.

 

Cheers,
Satya Narayan

---

Unlimited freedom, unlimited storage. Get it now ==================================================================== Companion Site: http://www.corej2eepatterns.com J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@...

[Shweta Kumari, Noida]

Hi Satya,

I think patterns are some common pattern to solve some problem.

It is easier for people to understand.

And talking in terms there are patterns and there are anti-patterns. :)

Best regards
Shweta



________________________________________
From: An interest list for Sun Java Center J2EE Pattern Catalog [mailto:J2EEPATTERNS-INTEREST@...] On Behalf Of Satya Narayan
Sent: Thursday, March 13, 2008 6:16 PM
To: J2EEPATTERNS-INTEREST@...
Subject: How come FastLaneReader is a pattern?

Do you think FFR should be treated as a pattern.
 
Here we are directly acessing the DB via JDBC apis in place of passing it to an entity bean. That is all.
 
If we consider it to be a pattern, then every code I write becomes a pattern in some way or other.
 
Any other use of FFR other than mentioned at Sun website which will truly validate that its claim to be a pattern.
 
Cheers,
Satya Narayan


________________________________________
Unlimited freedom, unlimited storage. Get it now

DISCLAIMER:
-----------------------------------------------------------------------------------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in
this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of
this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have
received this email in error please delete it and notify the sender immediately. Before opening any mail and
attachments please check them for viruses and defect.

-----------------------------------------------------------------------------------------------------------------------

====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@...

[Satya Narayan]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hi Shweta,

 

I am not getting you as such. Perhaps we are deviating.

 

And I do not think FFR is an anti-pattern. And yes, patterns are there to solve commonly recurring problems. But do we try to solve commonly recuuring problesm via programming. In that case, every bit of programming I use becomes a DP, like:

 

1. Switch statement: I can switch an int and char. I can come out of the loop by break --> another pattern?

2. I can have try, catch without finally or try-finally without catch --> another pattern?

3. I can have preCreate() like postCreate() just before and after ejbCreate() --> another pattern?

 

etc.

 

Shall I call them as patterns? Then it becoms weird.

 

Cheers,

Satya Narayan 

----- Original Message ----
From: "Shweta Kumari, Noida" <shwetak@...>
To: J2EEPATTERNS-INTEREST@...
Sent: Thursday, 13 March, 2008 6:29:05 PM
Subject: Re: How come FastLaneReader is a pattern?

Hi Satya,

I think patterns are some common pattern to solve some problem.

It is easier for people to understand.

And talking in terms there are patterns and there are anti-patterns. :)

Best regards
Shweta



________________________________________
From: An interest list for Sun Java Center J2EE Pattern Catalog [mailto:J2EEPATTERNS-INTEREST@...] On Behalf Of Satya Narayan
Sent: Thursday, March 13, 2008 6:16 PM
To: J2EEPATTERNS-INTEREST@...
Subject: How come FastLaneReader is a pattern?

Do you think FFR should be treated as a pattern.
 
Here we are directly acessing the DB via JDBC apis in place of passing it to an entity bean. That is all.
 
If we consider it to be a pattern, then every code I write becomes a pattern in some way or other.
 
Any other use of FFR other than mentioned at Sun website which will truly validate that its claim to be a pattern.
 
Cheers,
Satya Narayan


________________________________________
Unlimited freedom, unlimited storage. Get it now

DISCLAIMER:
-----------------------------------------------------------------------------------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in
this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of
this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have
received this email in error please delete it and notify the sender immediately. Before opening any mail and
attachments please check them for viruses and defect.

-----------------------------------------------------------------------------------------------------------------------

====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@...

---

Forgot the famous last words? Access your message archive online. Click here. ==================================================================== Companion Site: http://www.corej2eepatterns.com J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@...

[Sasan-2]

Some parts of this message have been removed. Learn more about Nabble's security policy.

you are mixing refactoring techniques by design pattern. what you're explaining there is the method of applying a DP while DP doesn't go into that level of detail. your explainations lean toward refactoring

going back to fastlane reader (FLR), its only trying to explain a good practice for accessing readonly data and how to access them. because entity patterns are an overhead for RO data so when you have tabular data with RO request this is where you use FLR, but how you implement it differs case by case

DPs are best practices; not the implementation

----- Original Message ----
From: Satya Narayan <ndsatya@...>
To: J2EEPATTERNS-INTEREST@...
Sent: Thursday, March 13, 2008 4:20:02 PM
Subject: Re: How come FastLaneReader is a pattern?

Hi Shweta,

 

I am not getting you as such. Perhaps we are deviating.

 

And I do not think FFR is an anti-pattern. And yes, patterns are there to solve commonly recurring problems. But do we try to solve commonly recuuring problesm via programming. In that case, every bit of programming I use becomes a DP, like:

 

1. Switch statement: I can switch an int and char. I can come out of the loop by break --> another pattern?

2. I can have try, catch without finally or try-finally without catch --> another pattern?

3. I can have preCreate() like postCreate() just before and after ejbCreate() --> another pattern?

 

etc.

 

Shall I call them as patterns? Then it becoms weird.

 

Cheers,

Satya Narayan 

----- Original Message ----
From: "Shweta Kumari, Noida" <shwetak@...>
To: J2EEPATTERNS-INTEREST@...
Sent: Thursday, 13 March, 2008 6:29:05 PM
Subject: Re: How come FastLaneReader is a pattern?

Hi Satya,

I think patterns are some common pattern to solve some problem.

It is easier for people to understand.

And talking in terms there are patterns and there are anti-patterns. :)

Best regards
Shweta



________________________________________
From: An interest list for Sun Java Center J2EE Pattern Catalog [mailto:J2EEPATTERNS-INTEREST@...] On Behalf Of Satya Narayan
Sent: Thursday, March 13, 2008 6:16 PM
To: J2EEPATTERNS-INTEREST@...
Subject: How come FastLaneReader is a pattern?

Do you think FFR should be treated as a pattern.
 
Here we are directly acessing the DB via JDBC apis in place of passing it to an entity bean. That is all.
 
If we consider it to be a pattern, then every code I write becomes a pattern in some way or other.
 
Any other use of FFR other than mentioned at Sun website which will truly validate that its claim to be a pattern.
 
Cheers,
Satya Narayan


________________________________________
Unlimited freedom, unlimited storage. Get it now

DISCLAIMER:
-----------------------------------------------------------------------------------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in
this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of
this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have
received this email in error please delete it and notify the sender immediately. Before opening any mail and
attachments please check them for viruses and defect.

-----------------------------------------------------------------------------------------------------------------------

====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@...

---

Forgot the famous last words? Access your message archive online. Click here.==================================================================== Companion Site: http://www.corej2eepatterns.com J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@...

---

Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. ==================================================================== Companion Site: http://www.corej2eepatterns.com J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@...