SAP Adaptor Deployment Exception

[albupp]

Greetings,

I'm new to JBoss, and using v3.0.3, following the instructions in the Quick Start doc to deploy a SAP adaptor that I've written and packaged into a RAR file.

I've modified the sapr3-service.xml descriptor to match the specifics of my adaptor. However, when JBoss attempts to deploy the adaptor I get the following exception:

org.jboss.deployment.DeploymentException: Exception getting document: nested throwable: (org.xml.sax.SAXParserException: Document root element is missing.)

This message makes no sense to me as I've made no change to the root element. I have compared my modified service xml file w/ others in the jca\examples dir, and noticed that they all seem to use a "server" rather than "service" root element which the sapr3-service.xml uses. I tried using the "service" element but still get the same exception.

I should mention that I have successfully deployed and run the test ejb-test.jar, as well as the mssql-service.xml files.

Attached is the sapr3-service.xml file I'm using. I'd appreciate any insight into this problem anyone can offer.

Thanks, Albert

[davidjencks]

I don't see the attachment.... the forums are often flaky about them.

Can you show the exact structure of your .rar file? I suspect the RARDeployer can't find META-INF/ra.xml

thanks

[albupp]

Greetings David,

Thanks for your reply. I figured the problem out, at least in part. Due to my misunderstanding the way JBoss's config deployment descriptors work, I had simply edited sapr3-service.xml w/ my adapter's specifics, then placed this into the deploy dir.

I'm still not entirely clear on the right way to do deploy a RAR, but trying different things, I eventually pasted the modified mbean element from sapr3-service.xml into jboss-service.xml right before the close of the server element. This approach apparently deploys successfully.

I don't think there's anything wrong w/ the RAR, but to answer your question, here's the output from jar -tf SAPAdapter.rar:

ra.jar
btalk_rt.jar
META-INF/ra.xml

I say the adapter's apparently deployed successfully because although it deploys w/o error, I have yet to actually invoke the adapter. I'm porting a little demo app which I originally created to run on another J2EE app server that makes the invocation from w/in a servlet via an EJB. So now I'm working on figuring out why I get the dreaded "javax.deployment.NamingException: no ejb-link match" when deploying the app.

My existing deployment descriptors put the ejb releated elements into the web.xml file, but from searching the forums on this error I gather that this information's supposed to go into either the ejb-jar.xml or jboss-web.xml files.

I just bought the Admin docs this morning, so I've got the example in Chapter 7 as a reference. I'll holler if I need more help.

Thanks again, Albert

[albupp]

Greetings David,

Thanks for your reply. I figured the problem out, at least in part. Due to my misunderstanding the way JBoss's config deployment descriptors work, I had simply edited sapr3-service.xml w/ my adapter's specifics, then placed this into the deploy dir.

I'm still not entirely clear on the right way to do deploy a RAR, but trying different things, I eventually pasted the modified mbean element from sapr3-service.xml into jboss-service.xml right before the close of the server element. This approach apparently deploys successfully.

I don't think there's anything wrong w/ the RAR, but to answer your question, here's the output from jar -tf SAPAdapter.rar:

ra.jar
btalk_rt.jar
META-INF/ra.xml

I say the adapter's apparently deployed successfully because although it deploys w/o error, I have yet to actually invoke the adapter. I'm porting a little demo app which I originally created to run on another J2EE app server that makes the invocation from w/in a servlet via an EJB. So now I'm working on figuring out why I get the dreaded "javax.deployment.NamingException: no ejb-link match" when deploying the app.

My existing deployment descriptors put the ejb releated elements into the web.xml file, but from searching the forums on this error I gather that this information's supposed to go into either the ejb-jar.xml or jboss-web.xml files.

I just bought the Admin docs this morning, so I've got the example in Chapter 7 as a reference. I'll holler if I need more help.

Thanks again, Albert

[albupp]

Greetings David,

Thanks for your reply. I figured the problem out, at least in part. Due to my misunderstanding the way JBoss's config deployment descriptors work, I had simply edited sapr3-service.xml w/ my adapter's specifics, then placed this into the deploy dir.

I'm still not entirely clear on the right way to do deploy a RAR, but trying different things, I eventually pasted the modified mbean element from sapr3-service.xml into jboss-service.xml right before the close of the server element. This approach apparently deploys successfully.

I don't think there's anything wrong w/ the RAR, but to answer your question, here's the output from jar -tf SAPAdapter.rar:

ra.jar
btalk_rt.jar
META-INF/ra.xml

I say the adapter's apparently deployed successfully because although it deploys w/o error, I have yet to actually invoke the adapter. I'm porting a little demo app which I originally created to run on another J2EE app server that makes the invocation from w/in a servlet via an EJB. So now I'm working on figuring out why I get the dreaded "javax.deployment.NamingException: no ejb-link match" when deploying the app.

My existing deployment descriptors put the ejb releated elements into the web.xml file, but from searching the forums on this error I gather that this information's supposed to go into either the ejb-jar.xml or jboss-web.xml files.

I just bought the Admin docs this morning, so I've got the example in Chapter 7 as a reference. I'll holler if I need more help.

Thanks again, Albert

[albupp]

Greetings David,

Thanks for your reply. I figured the problem out, at least in part. Due to my misunderstanding the way JBoss's config deployment descriptors work, I had simply edited sapr3-service.xml w/ my adapter's specifics, then placed this into the deploy dir.

I'm still not entirely clear on the right way to do deploy a RAR, but trying different things, I eventually pasted the modified mbean element from sapr3-service.xml into jboss-service.xml right before the close of the server element. This approach apparently deploys successfully.

I don't think there's anything wrong w/ the RAR, but to answer your question, here's the output from jar -tf SAPAdapter.rar:

ra.jar
btalk_rt.jar
META-INF/ra.xml

I say the adapter's apparently deployed successfully because although it deploys w/o error, I have yet to actually invoke the adapter. I'm porting a little demo app which I originally created to run on another J2EE app server that makes the invocation from w/in a servlet via an EJB. So now I'm working on figuring out why I get the dreaded "javax.deployment.NamingException: no ejb-link match" when deploying the app.

My existing deployment descriptors put the ejb releated elements into the web.xml file, but from searching the forums on this error I gather that this information's supposed to go into either the ejb-jar.xml or jboss-web.xml files.

I just bought the Admin docs this morning, so I've got the example in Chapter 7 as a reference. I'll holler if I need more help.

Thanks again, Albert

[albupp]

OK, now I know, there's a lag between posting a reply, and it actually showing up in the topic thread...