Bug 831712
| Summary: | Adding a BPEL process file to a BPEL project always warns that "the selected location is not a BPEL project" (non-fatal warning message) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Len DiMaggio <ldimaggi> | ||||||
| Component: | Tooling | Assignee: | Robert (Bob) Brodt <bbrodt> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 5.3.0 GA | CC: | dpalmer, kejohnso, sdorfiel, soa-p-jira | ||||||
| Target Milestone: | CR2 | ||||||||
| Target Release: | 5.3.0 GA | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: |
When a user attempted to add a BPEL process file to a BPEL project, an error would occur. A non-fatal warning message would be displayed reading "the selected location is not a BPEL project". This problem has now been patched. As a result, the error no longer occurs wen adding the process.
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-07-16 19:45:50 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Len DiMaggio
2012-06-13 16:00:31 UTC
Link to: JBDS-2209 Douglas Palmer <dpalmer> updated the status of jira JBDS-2209 to Resolved Douglas Palmer <dpalmer> made a comment on jira JBDS-2209 Fixed in org.eclipse.bpel and incorporated into the CR1 build. Still a bug here: http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.CR1.soa-tooling/ Version: 5.0.0.GA Build id: v20120615-1714-H213-GA Build date: 20120615-1714 Len DiMaggio <ldimaggi> updated the status of jira JBDS-2209 to Reopened Robert (Bob) Brodt <bbrodt> made a comment on jira JBDS-2209 Right. It looks like the most recent bpel bits haven't been pulled in to this build. The org.eclipse.bpel features are still from 5/18/2012. Robert (Bob) Brodt <bbrodt> made a comment on jira JBDS-2209 Sorry, my mistake - was looking at the wrong build. I'm able to repro this, but only the first time after the first BPEL project is created. If the project is closed and reopened, the problem goes away for that project. If the workbench is restarted, the problem goes away permanently. This may be a bug in the project facet plugins somewhere...investigating. It doesn't go away permanently. Creating a new workspace brings it back. Created attachment 593643 [details]
Screenshots
I was just able to (once) create a new workspace (after a clean install) and then create a new BPEL project and process file and not see the bug. See attached screenshots. This was after seeing the problem repeatedly earlier in the day.
The issue is caused by the bpel.facet.core code being duplicated in the org.eclipse.bpel.runtimes and org.jboss.tools.bpel.runtimes Robert (Bob) Brodt <bbrodt> made a comment on jira JBDS-2209 Looks like you're right Len :) The solution is to simply remove the bpel.facet.core definition from the org.jboss.tools.bpel.runtimes plugin - this facet is already defined in org.eclipse.bpel.runtimes. Fixed in trunk, patch for 3.3.x branch attached here for review. Robert (Bob) Brodt <bbrodt> made a comment on jira JBDS-2209 Patch for org.jboss.tools.bpel.runtimes/plugin.xml Douglas Palmer <dpalmer> made a comment on jira JBDS-2209 Patch looks good. Is it worth deleting the offending source code at the same time? -- Posted from Bugbox for iPhone Robert (Bob) Brodt <bbrodt> made a comment on jira JBDS-2209 Committed the patch.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
When a user attempted to add a BPEL process file to a BPEL project, an error would occur. A non-fatal warning message would be displayed reading "the selected location is not a BPEL project". This problem has now been patched. As a result, the error no longer occurs wen adding the process.
Douglas Palmer <dpalmer> updated the status of jira JBDS-2209 to Resolved The problem is not seen with the CR2 build. Created attachment 598518 [details]
Screenshot of the - no longer present - bug
|