RE: [JBoss-user] Remote Beans as Web Services

[Mark.Gargan]

Title: Nachricht

Hi Christoph,                I actually built jboss from a nightly snapshot I downloaded off the site. Originally I was using 3.2 though. The problem I think actually occurs when the java provider is trying to generate the wsdl. However I’m not 100% clear on the use of using breakpoints in eclipse with abstract classes so I’m gonna figure that out first and then have another look. If you do get it working and could let us know that’d be great.   Thanks, Mark.     -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jung , Dr. Christoph Sent: 17 March 2003 07:57 To: '[EMAIL PROTECTED]' Subject: AW: [JBoss-user] Remote Beans as Web Services   Marc,   as Kevin has noted, there seems to be a problem with WSDL generation for allowedMethods="*" even in the axis version we use in the JBoss 3.2 branch (which version did you use?).   I will fix this in the next days.   CGJ     -----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 14. März 2003 19:02 An: [EMAIL PROTECTED] Betreff: RE: [JBoss-user] Remote Beans as Web Services Christoph,           I finally managed to get a nightly build from the website. (Not too used to the open source idea yet) and anyway's I built that and my bean seemed to deploy grand. I could also make remote client calls thru the jndi and test them as exposed webservices. Initially I was unable to retrieve the WSDL file but then on Kevin's advice I only allowed for the one business method to be exposed and subsequently it all worked nicely.   I still have to try the remote debugging technique you mentioned earlier and basically get my head around all this new stuff I'm using, eclipse, jbosside etc. Could I ask you what the point in having the jbosside is if you can simply remotely debug jboss like a normal application like this?   Many thanks for your help and patience throughout this torrid installation. Mark.     -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jung , Dr. Christoph Sent: 14 March 2003 15:21 To: '[EMAIL PROTECTED]' Subject: AW: [JBoss-user] Remote Beans as Web Services     -----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 14. März 2003 12:33 An: [EMAIL PROTECTED] Betreff: RE: [JBoss-user] Remote Beans as Web Services Christoph, Kevin,                           I'd a look at the EJBProvider code myself and the strange thing was that the line pointed to in the stack trace where the NullPointerException occurred was blank? I figured it maybe somehow it was the superclass method i.e. the axis EJBProvider that was maybe throwing the error somehow but sure enough there was nothing at that line either? The jars I'm using were from the embedded catalina version I downloaded from Dr. Scharlau's site. Hence why I'm trying to get Jboss running within Eclipse so I can see exactly what's causing this NullPointerException.       so maybe the best is to recompile the 3.2 sources of jboss.net in order to get the line information consistent.        Christoph,          When you start jboss and connect to it remotely can you then step thru the code and insert the likes of break points etc? Also the JAVA_OPTS parameter, I couldn't find it in the build.bat file. Is it simply a case of inserting it yourself?     for example, set JAVA_OPTS=-classic -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n %JAVA_OPTS% Thanks a million for your help, Mark.   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jung , Dr. Christoph Sent: 14 March 2003 08:06 To: '[EMAIL PROTECTED]' Subject: AW: [JBoss-user] Remote Beans as Web Services   Mark, Kevin,   a) I looked through the JBoss.net EJBProvider code again. All we do there is to switch the classloading context and then delegate into the parent (Axis) EJBProvider. If there is a problem with "*" and wsdl generation, this should appear in plain Axis, too. I think I saw the right stop classes there. Kevin, have you any experience with that?   b) As for eclipse: If you look into the jboss.net module, there will be a ..classpath and .project ready for importing directly into eclipse (there are a few absolute paths in 3.2 which we have removed in 4.0 in favor of a global variable "JBOSS_ROOT". You can do a local build in jboss.net and move/extract the generated libs in the output/lib directory manually into your jboss distro. After that, I usually start jboss through the run script (but in debug mode - see the JAVA_OPTS parameter) and attach to it via remote debugging.   Thanks for having a look, CGJ   -----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 13. März 2003 22:47 An: [EMAIL PROTECTED] Betreff: Re: [JBoss-user] Remote Beans as Web Services Hi Christophe,       I deploy it within a wsr file that's located within an ear file. When this is deployed in the engine it seems to deploy fine, however if I attempt to look at the services through http://localhost:8080/jboss-net/services  I get the previous exception..   The actual version of Jboss that I use I downloaded from Dr Bruce Scharlau's site in Aberdeen as it was the only version that I could get to run a hello world been. http://www.csd.abdn.ac.uk/~bscharla/teaching/mtp_software/jboss/jboss-netGuide.shtml     I can't use the org.apache.axis.client.AdminClient class file as it kept throwing a strange error With 'FixME'  in it so I figured it was something that was underdevelopment.   I've downloaded the source for jboss-3.20RC2 and I'm attempting to get it running through Eclipse so I can have a better look at the problem, Unfortunately the only module that gives me any problems is the jboss.net module. Have you managed to integrate 3.2 with Eclipse or have you bothered?     Thanks, Mark.       ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/