Bug 380148 - Component Context validation not checked in the find-method
Summary: Component Context validation not checked in the find-method
Status: CLOSED WONTFIX
Alias: None
Product: Jubula (Archived)
Classification: Technology
Component: RC (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2012-05-21 10:15 EDT by Patrick Gutorski CLA
Modified: 2014-05-27 08:11 EDT (History)
1 user (show)

See Also:


Attachments
Allows to load the context through the html locator (970 bytes, patch)
2012-05-21 10:35 EDT, Patrick Gutorski CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Gutorski CLA 2012-05-21 10:15:18 EDT
Build Identifier: 6.0.0

The findComponent method from the FindComponentBP class uses also the context of a component to find a similar component to the given componentIdentifier in the hierarchy, but the html getComponentContext method only delivers the context for concrete webcomponents and not for a string locator which is used in the html context here. As a result the contextlist will be empty and the part to compare the contextes is skipped in the findComponent method.

Reproducible: Always
Comment 1 Patrick Gutorski CLA 2012-05-21 10:35:57 EDT
Created attachment 215968 [details]
Allows to load the context through the html locator

Patch that allows to load the context with the html locator, therefore we using the string to find the right abstracthtmlcomponent and then to get the context.
Comment 2 Eclipse Genie CLA 2014-05-16 11:10:45 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 3 Alexandra Schladebeck CLA 2014-05-26 06:11:10 EDT
Since the Genie has reminded us that this hasn't been looked at in a long while and I doubt that we're going to get around to looking at it in the near future, I'm marking as wontfix.

This doesn't mean it can't be reopened if new information or arguments for fixing it / prioritising it higher come to light. If that's the case, please reopen.
Comment 4 Oliver Goetz CLA 2014-05-27 08:11:17 EDT
Closed due to comment 3