samarthya saurabh

Greenhorn
+ Follow
since May 03, 2010
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by samarthya saurabh

Tim Ottinger wrote:
Agile does not require us to have zero documentation about design, it only reminds us that it is not the best way to share information.

Development should not be leisurely, but it should not impoverish developers or writers or QA team members.



Indeed, I agree to it completely.

Tim Ottinger wrote:
Do you track velocity? If you measure how much is totally shippable in an iteration, and plan by "yesterday's
weather", underestimation smooths out quickly. When the iteration is a near thing, the team will have a tendency
to start rounding their estimates up a bit. They hit their stride in a few iterations.



Yes we do.

Tim Ottinger wrote:
Is there some tracking and reward system that punishes (or fails to reward) the individual if they help others?
Anything that pushes against teamwork is non-agile, since agile values teamwork (interactions) so highly.


Probably it is not just about the ONE - team working one project but when knowledge is the key and a resource expertise might prove valuable to some other projects, his time needs to be borrowed and that is when the resource is reluctant may be because he is thinking of the task and the sprint. This is not always the case but yes I have certainly seen that.


Thanks any ways! the discussion indeed was to my liking and I did get few pointers which I can certainly use moving forward.

Jeff Langr wrote:
I've developed in plenty of teams as "just a" developer, and I've always seen the rate of development degrade over time because there was no continual attention to quality. Quality, as Deming said in one way or another, more than pays for itself over time.



This is my concern as well. We can have user stories that defines security, quality, performance requirements but these stories are usually hold less priority initially in a hurry to get to market. And we usually end up with pseudo-quality-security and worst performance at times.

How do we deal with it?

Thanks.

Tim Ottinger wrote:
1) It sounds like your stories are too large. We have a card or two on breaking them down.



The story usually is cut down to almost a feature requirement, but with a defines set of tasks, sometime related and sometimes un-related or by-products. How to decide if the story is too large? We just put down T-Shirt sizes to it and yes we do have Large, Medium and small as the sizes. What should be an optimum sprint size? Is it decided before hand or should it be based on the stories we tend to include or number of spill overs we have?

Tim Ottinger wrote:
2) Typically tasks aren't assigned to developers, but to teams. I wonder if you're in a half-state or I misunderstood.


Tasks are assigned to teams? I am not sure I understood it correctly. As in practice we as a team take up stories and tasks are assigned to individuals on voluntary basis, is it not the proper way?

Tim Ottinger wrote:
3) I'm not sure what you mean when you say "a developers time will never be accounted for."



Assuming there are a set of tasks and they are not completely related but, eventually when the feature goes live these tasks will have to interact. So considering an individual developing a task with relative independence has to interact at times with peers just to ensure the requirement or expectations are laid out for the members who will interact with his coded module. He has to interact with Test teams to make sure information is well conveyed. This is all because of lack of documentation (Zero documentation about design) and parallel development. A developers shoulders a responsibility of completing a task on time and in all probability might be reluctant to give the time required. If he does he cannot account it in any specific task, because these discussions takes time, sometimes too much. (I hope I am able to clarify)

Tim Ottinger wrote:
I suspect that there is less team focus and collaboration with project owners than I would like to see. If I were coaching, I would investigate
that first. Since I'm not, I suggest you may need your scrum master or coach to look into it.


What should be the focus? Design, development? I am afraid I am not able to understand. A little help?

Thanks.
The way Agile methodology is laid out it just expected that repeated incremental versions of (acceptable and ready to work on) solution would be churned out. A developer has a defined timeline with a number of tasks of a story(ies) with an estimated T-Shirt size (as per guidelines), this actually rules out any miscalculation in terms of problem at hand and closure of a user story cannot be achieved till the time all the tasks has been marked done.

A developer is burdened not only with the defined timeline but with quality + all basic unit testing + integration verification. If a user story is not properly documented or if number of tasks are not laid out comprehensively a developers time will never be accounted for. Making it more of a burden. A owner of story is also a very vague as a usually it is the product owner who knows what MUST be in the product and that defines the priority of tasks and stories and within a story a developer only knows which sequence of tasks makes more sense.

Your comments?

Bear Bibeault wrote:What is the purpose of declaring the jsp mapping in the first place? The whole purpose of putting JSPs under WEB-INF is to not allow them to be directly addressed by URL. If that's not what you want (and it should be), don't put the JSPs there.

Why do you want the JSPs addressable? That's a pretty poor practice.



Probably it is a bad practice, I just was trying to resolve a request for page (JSP) to the default view. Under tomcat if I do not include the JSP servlet tag the page is bever resolved.

Probably just to make it more clear - what I am trying to achieve here is create a set of pages and when the request comes in return the appropriate view. Just to learn the mapping process in a cleaner way.

A default Index.html I want to route and return a WELCOME.JSP for that and for every other direct request for any other page I will show a not accessible page, without using the spring-security here or any other helper framework libs.
- Samarthya
9 years ago
When I remove the JSP declaration it works in Glasffish fine, but the request for the desired JSP file does not work under tomcat6.
9 years ago
I am using Spring 3.0 + with eclipse as my tool, I added a simple controller to respond to incoming requests and following is my Deployment descriptor file




Now when I deploy it in tomcat it runs fine, when I use GlassFish Open source v3 I get error while deploying,




I believe the JSP servlet I have defined is the problem, but what should I do to remove this issue?

- Samarthya
9 years ago
Thanks!
9 years ago
JSF
I have defined a message bean in the JSF example I use to simply store the Login name and password values to be displayed on the navigated next page. My problem is even though there is no complication error. Only NULL gets set and returned. I have tried to debug and check if the setfunction is called, and it does but with null values and not with the actual text box values.

See below - faces-config.xml


and the login page looks like


and the navigated page is simply


I know I am wrong somewhere, but just seem to oblivious to it. Any help?
9 years ago
JSF
Thanks! I would try and abstain from using the "ItDoesNotWorks".
- Samarthya
10 years ago
JSF
Sorry My apologies about not being clear about what I have been using.

I did figure out that there is some JAR that I am missing because it was throwing exception while deployment with the stated exception message.

1. I am using JSF 2.0.
2. Using MyFaces API.
3. Using GlassFishv3
4. Using eclipse.


Now the problem I face is the navigation is not working.

the config file I defined is as under.



The login.jsp looks like



Thanks,
Samarthya
10 years ago
JSF
Hi All,

I have just tried to work out first JSF example the sample login to welcome navigation. But when I try to deploy it on glassfish v3 from my devlopment environment eclipse I get the error.




I have googled for some help but not much is available. I think I am missing out on some library or something?

The ones I have included are
jsf-impl.jar
jsf-api.jar

and these files were in glassfishv3 server I downloaded.

- Samarthya
10 years ago
JSF

Christophe Verré wrote:This is not going to work. If Spring is not managing your bean, how is it going to apply AOP ? Declare your worker in your context file, and get your bean via the application context or via a bean factory.



Thanks! I will try to do it that way!!


A method returning a boolean must return something. Your code doesn't return anything.



Yep!! i agree i removed the logic of the function, just to avoid un-necessary bloating and forgot the return.

Thank you!
10 years ago

Christophe Verré wrote:
How are you creating the com.Worker bean ?



Using the new operator to create the object of Worker class and calling execute of the function.
10 years ago

Christophe Verré wrote:I don't know how Worker#execute even compiles...



Is there any syntactical issue here? My code compiles fine. I do include all the imports.... or am i missing something?
10 years ago