Hi,

Next I will focus on NetConnectionReply, NetPackageReply and NetResultSetReply classes of the client.net package which have low code coverage. I will look into these classes to get a better understanding of them. I would like to know any suggestions regarding this.

Thanks,
Nufail.

On Sun, May 27, 2012 at 11:55 AM, Mohamed Nufail <nufail56@gmail.com> wrote:
I created a JIRA issue for this at https://issues.apache.org/jira/browse/DERBY-5786

Regards,
Nufail.


On Sat, May 26, 2012 at 10:03 PM, Mohamed Nufail <nufail56@gmail.com> wrote:
Will do that. Thanks.

Nufail.


On Sat, May 26, 2012 at 8:21 PM, Bryan Pendleton <bpendleton.derby@gmail.com> wrote:
So making it a stand alone class and using it instead of InputStreamUtil and DynamicByteArrayOutputStream classes should solve
the problem. Shall I continue with this solution?

Sure!

It sounds like the problem is well-enough defined at this point.

I think the next thing you should do is to open a new JIRA issue
in the Derby JIRA system to track this work. In your JIRA, you
can describe the problem, how you propose to fix it, and include
a reference to this email thread in the mailing list archives.

Then, once you have coded the solution and are satisfied that it
is working, you can attach your proposed changes to the JIRA as
a patch.

Here's some information that describes the overall process:
http://wiki.apache.org/db-derby/DerbyCommitProcess

thanks,

bryan



--

Mohamed Nufail
Undergraduate,
Department of Computer Science & Engineering,
University of Moratuwa.
Blog: http://www.nufailm.blogspot.com/





--

Mohamed Nufail
Undergraduate,
Department of Computer Science & Engineering,
University of Moratuwa.
Blog: http://www.nufailm.blogspot.com/





--

Mohamed Nufail
Undergraduate,
Department of Computer Science & Engineering,
University of Moratuwa.
Blog: http://www.nufailm.blogspot.com/