Re: [Abator] Unable to generate artifacts

mailing-list Sat, 18 Feb 2006 13:01:56 -0800

I'm using abator 0.6.1 and Eclipse 3.1.2 and still don't get the "generate artifiacts" pop up menu after editing my plugin.xml file. Anyone get it working correctly? Here is a snipped of what I updated my plugin.xml to:

<extension point="org.eclipse.ui.popupMenus">
      <objectContribution
            objectClass="org.eclipse.core.resources.IFile"
            nameFilter="*"
            id="org.apache.ibatis.abator.ui.contribution1">
         
         <action
               enablesFor="1"
               label="Generate iBATIS Artifacts"
               icon="icons/iBatisLogo.gif"
               class="org.apache.ibatis.abator.ui.actions.RunAbatorAction"
               menubarPath="additions"
               id="org.apache.ibatis.abator.ui.actions.RunAbatorAction">

               <selection class="org.eclipse.core.resources.IFile "
        name="abatorConfig.xml"/>
         </action>
      </objectContribution>
   </extension>

Jeff Butler
Tue, 07 Feb 2006 07:18:50 -0800

Eclipse 3.0 is somewhat limited in this area. What's supposed to happen is this:

1. The popup menu is enabled for any .xml file that has abatorConfiguration as the root element (good)

2. The Abator editor is associated with any file named abatorConfig.xml (not so good)

The second case is this way because the Eclipse folks did not get the more complex editor associations finished in time for release 3.0. With 3.1, I should be able to associate the editor with any XML file with abatorConfiguration as the root element.

Since there's a lot of movement in this area of Eclipse, it would not surprise me if something was amiss somewhere.  I have not done much investigation of Abator on Eclipse 3.1 yet - mainly because my team is stuck on 3.0 due to the Rational tooling being pegged there.

It's very interesting to me that their hack worked after all - I guess its time for me to dive into Eclipse 3.1 and see if I've made some bad assumptions.

Thanks for the update!

Jeff Butler

On 2/7/06, Bruyn Bill <[EMAIL PROTECTED]> wrote:
Thanks, Jeff. I'd appreciate that.  Their solution does seem like a bit of a hack, and rather limited in that you have to configure the name of the file, to your point - but IIRC doesn't the current release only recognize abatorConfig.xml anyway? In any case, I have it working per their suggestion for now. (Had to restart Eclipse with -clean to clear its cached version of the Abator plugin config). Looking forward to hearing more about anything you find.

Again, many thanks.

Bill

-----Original Message-----
From: Jeff Butler [mailto: [EMAIL PROTECTED]]
Sent: Monday, February 06, 2006 11:29 AM
To: [email protected]
Subject: Re: [Abator] Unable to generate artifacts

Well I'm not surprised it didn't work - that was a pretty silly (and awfully limiting) suggestion from them. Enabling selections by XML root element type is relatively new in Eclipse - perhaps they don't know how it works?

I suppose it could also be an Eclipse problem where Eclipse is getting confused about whether to enable the menu selection or not. But hard to tell.

I don't have an oXygen license to be able to test it myself. I might try to get a demo of oXygen to see if I can debug it further, but that will take me a few days.

Jeff Butler

On 2/6/06, Bruyn Bill <[EMAIL PROTECTED] > wrote:
I got the following response from oXygen support.  I tried the config as
suggested, but no change.  Any insight as to why this wouldn't work?

Thanks again.

Bill
----------------------------------------------------------------

After studying the plugin.xml file from the UI plugin of the "abator"
bundle the problem seems to be related with their mode of associating
the context menu actions.

So, on the "org.eclipse.ui.popupMenus" extension point you will see that
the <visibility> element claims that the current object must have a
certain conten type, i.e. the
"org.apache.ibatis.abator.ui.abatorConfigurationFileByElement" content
type.
But oXygen also has its own content type for xml documents with encoding
and BOM handling which seems to be more general than the one that
"abator" has, and Eclipse it taking the oXygen's one into account.

The solution for you is to edit by hand the "plugin.xml" file from the
"org.apache.ibatis.abator.ui_0.5.1" directory and comment the
<visibility> element, and then modify <action> as follows:

<action
enablesFor="1"
label="Generate iBATIS Artifacts"
icon="icons/iBatisLogo.gif"
class=" org.apache.ibatis.abator.ui.actions.RunAbatorAction"
menubarPath="additions"
id="org.apache.ibatis.abator.ui.actions.RunAbatorAction">

<selection class="org.eclipse.core.resources.IFile "
name="abatorConfig.xml"/>

</action>

> -----Original Message-----
> From: Bruyn Bill
> Sent: Thursday, February 02, 2006 1:41 PM
> To: ' [email protected]'
> Subject: RE: [Abator] Unable to generate artifacts
>
>
> Yeah, their plugin does add a few items to the context
> menu...  I don't know how that's handled internally, but now
> I can file a bug report and find out.  I'll post what I find,
> if anything.
>
> Thanks, Jeff.  (BTW, nice job.)
>
>
> Bill
>
> -----Original Message-----
> From: Jeff Butler [mailto: [EMAIL PROTECTED]]
> Sent: Thursday, February 02, 2006 12:23 PM
> To: [email protected]
> Subject: Re: [Abator] Unable to generate artifacts
>
>
> That's odd.  The menu option should enable for any file with
> xml as the extension, and with a root element of
> "abatorConfiguration".
>
> Question - does oXygen change the popup menu on an XML file
> significantly?  Abator assumes there is an insertion point on
> the popup menu called "additions" (which is an Eclipse
> convention).  If oXygen has significantly altered the popup
> menu for XML files, or they somehow removed the "additions"
> insertion point, then that could cause the problem.  This
> does point the finger at them I'm afraid, but I can't think
> of any other reason for the trouble you're having.
>
> Nevertheless, there should probably be more ways to run
> Abator than just through a pop-up menu.  I'll try to think of
> some for the next release.
>
> Jeff Butler
>
>
> On 2/2/06, Bruyn Bill < [EMAIL PROTECTED] > wrote:
> I have the Abator (0.5.1) plugin for Eclipse (3.1.2)
> installed here, and have a little trouble with it when I also
> have my oXygen XML Editor
> (7.0.0) plugin installed/enabled.
>
> I can set up my file association okay, create my config with
> the File/New wizard and edit it with the Abator editor (if I
> want to), but my "Generate iBATIS Artifcats" menu option
> disappears.  When I disable
> the oXygen plugin, everything works as advertised, so I'm not
> sure this is an Abator problem...  Still, I was hoping
> somebody might be able to explain what's going on?
>
>
> TIA,
>
> Bill Bruyn
>

Re: [Abator] Unable to generate artifacts

Reply via email to