5 Replies Latest reply on Nov 29, 2007 1:22 PM by bsnyder

    Creating a Binding Component

    bnritte

      I have attempted to create a Binding Component using the FUSE tooling and each time I make the attempt I get an error from Maven telling me that the project does not exist...it reports the project name in the following way..... It appears to be looking for a project at a lower directory level with the same project name (which eclipse won't allow)...is my setup wrong or is this a bug???

        • 1. Re: Creating a Binding Component
          bsnyder

          Does the following procedure match what you're doing in Eclipse to create the BC?:

           

          1. File --> New --> Project --> Java Business Integration --> Binding Component

          2. Enter Project Name (manually enter a project name)

          3. Project Facets (the default should be good - make sure that the Java facet is 5.0)

          4. Archetype Version (manually enter the text 3.3.0.5-fuse (the latest version))

          5. Maven Group Id (use the default)

          6. Initial Version (use the default)

          7. Java Package (use the default)

           

          Please copy/paste the full error that you are seeing in the Eclipse console so I can see what you're seeing.

           

          Also, please be aware that for the process above to succeed, you must have access to a high-speed internet connection so that Maven can download the necessary artifacts. If you're required to use a proxy server to access the internet, then you need to configure Maven to use the same proxy server.

           

          Bruce

          • 2. Re: Creating a Binding Component
            bnritte

            Bruce,

             

            Unfortunately, I cannot cut-and-paste I am in a secure environment. This also means that we have our own Maven repository with (what we believe to be) all if the requisite jars.

             

            I do exactly what you surmised...I am using all of the defaults and creating a BindingComponent named "BindingTest"...here is the basic error message that I am getting...

             

            Unable to install Apache Maven fact

            Source directory does not exist(U:/development/BindingTest/BindingTest)

             

            Not sure why it is saying "BindingTest/BindingTest" it should be U:/development/BindingTest...

             

            Barry

            • 3. Re: Creating a Binding Component
              bsnyder

              Perhaps the issue below describes what you are seeing?:

               

              http://open.iona.com/issues/browse/ESB-40

               

              If so, this is due to the fact that the FUSE Eclipse Tooling requires access to the IONA Maven repository. If you are in a closed environment then you don't have access to this Maven repo, hence your problem.

               

              I've created a new JIRA issue for this problem (see the issue: Remove the requirement to access the IONA Maven repo from the FUSE Eclipse Tooling) so that it can be addressed in a future release.

               

              Bruce

              • 4. Re: Creating a Binding Component
                bnritte

                Bruce,

                 

                I went to my corporate office space (the customer space has limited access) and tried to use the FUSE tooling to generate a SE and BC...all worked as advertised. So, since I cannot access the IONA Maven repository is there a way to acquire the requisite artifacts so that we can update our internal repository?

                 

                Barry

                • 5. Re: Creating a Binding Component
                  bsnyder

                   

                  I went to my corporate office space (the customer space has limited access) and tried to use the FUSE tooling to generate a SE and BC...all worked as advertised. So, since I cannot access the IONA Maven repository is there a way to acquire the requisite artifacts so that we can update our internal repository?

                   

                   

                  It's just a matter of pulling the dependencies for the ServiceMix Maven archetypes (and their dependencies) for the version of ServiceMix that you're using. E.g., if you're using the servicemix-binding-component archetype from servicemix-3.3.0.5-fuse, then you'll need to pull all of the artifacts from here:

                   

                  http://repo.open.iona.com/maven2/org/apache/servicemix/tooling/servicemix-binding-component/3.3.0.5-fuse/

                   

                  Bruce