1 2 Previous Next 17 Replies Latest reply on Jul 11, 2012 1:11 AM by Logan McGrath Go to original post
      • 15. Re: Nexus access to http://jesperpedersen.github.com/fungal/maven2
        Murray Todd Williams Newbie

        I'm sure we all experience the "dilema of choice" from all these tools and standards like Maven, Ivy, Eclipse, etc. It took me a couple years of constant pressure to finally bite the bullet and start using Maven. (And their documentation really does suck!)


        But, like so many JBoss initiatives, IronJacamar is a really wonderful contributiont to the Java EE space—hell, are there any more difficult and opaque technologies than JCA out there!!?! As I said before, your code generation template and your embeddable testing platform are like manna from heaven for the poor engineer wandering into this space!


        I just don't want these Maven issues to be blockers that ward-away an engineer from IronJacamar during the initial discovery/evaluation phase. I'm pretty underwater at the moment, but if I can put a few hours into this (sometime over the next 2-3 weeks), maybe there are a couple simple tweaks we can figure out that smooth these things out.

        • 16. Re: Nexus access to http://jesperpedersen.github.com/fungal/maven2
          Jesper Pedersen Master

          Trust me, we take all reported issues seriously - bugs, feature requests, usability, ... - but we may take some things for granted which other people doesn't. We need feedback for us to improve the project - the more detailed the better. Logan is now working on helping us improve the Maven support, which is great !


          As you said JCA isn't the most easy tech out there - so usability is a key focus for us. And we will continue to push in order to be the de-facto JCA implementation

          • 17. Re: Nexus access to http://jesperpedersen.github.com/fungal/maven2
            Logan McGrath Newbie

            I've updated Murray's ticket: https://issues.jboss.org/browse/JBJCA-847


            Incidentally, I've never been able to get any tests to run against IronJacamar, either directly using the embedded version or using Arquillian. They always fail with stack traces like the following:


            org.jboss.arquillian.container.spi.client.container.DeploymentException: Could not deploy the application: Deployment file:/C:/Users/LOGANM~1/AppData/Local/Temp/ConnectorTestCase.rar failed
            Caused by: com.github.fungal.spi.deployers.DeployException: Deployment file:/C:/Users/LOGANM~1/AppData/Local/Temp/ConnectorTestCase.rar failed
            Caused by: org.jboss.jca.common.metadata.ParserException: IJ010065: Missing mandatory jndi-name attribute: connection-definition
            java.lang.RuntimeException: Could not run @AfterSuite
            Caused by: org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not stop the EmbeddedJCA container: Could not delete C:\Users\LOGANM~1\AppData\Local\Temp\iron.jacamar\tmp\ConnectorTestCase.rar\61e3f7f3-fb18-407f-abe5-8a8374a5cbf2.jar
            Caused by: java.io.IOException: Could not delete C:\Users\LOGANM~1\AppData\Local\Temp\iron.jacamar\tmp\ConnectorTestCase.rar\61e3f7f3-fb18-407f-abe5-8a8374a5cbf2.jar


            Until Arquillian was capable of doing integration tests in JBoss AS with resource adapters, I had no real way of performing a "real-world" integration test, and I almost ditched Java EE and JBoss AS for Spring and Jetty because of it.


            I'll be sure to put in a ticket regarding the issues I've had with the tests, but for now it's past my bedtime. I'm looking forward to working with a more friendly IronJacamar.

            1 2 Previous Next