Re: AW: AW: AW: AW: [JBoss-user] JBoss.NET error

2003-03-26 Thread Nathan Hoover
Ursprüngliche Nachricht- Von: Nathan Hoover [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 25. März 2003 20:40 An: [EMAIL PROTECTED] Betreff: Re: AW: AW: AW: [JBoss-user] JBoss.NET error This worked for me (of course) and my problem with the JNDI name went away. Hopefully this jar will b

Re: AW: AW: AW: AW: [JBoss-user] JBoss.NET error

2003-03-26 Thread Nathan Hoover
Ursprüngliche Nachricht- Von: Nathan Hoover [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 25. März 2003 20:40 An: [EMAIL PROTECTED] Betreff: Re: AW: AW: AW: [JBoss-user] JBoss.NET error This worked for me (of course) and my problem with the JNDI name went away. Hopefully this jar will be in

Re: AW: AW: AW: AW: [JBoss-user] JBoss.NET error

2003-03-26 Thread Nathan Hoover
PROTECTED] Betreff: Re: AW: AW: AW: [JBoss-user] JBoss.NET error This worked for me (of course) and my problem with the JNDI name went away. Hopefully this jar will be included as part of the 3.2 release. I am now having a new problem: An unhandled exception of type 'System.Web.Service

AW: AW: AW: AW: [JBoss-user] JBoss.NET error

2003-03-26 Thread Jung , Dr. Christoph
OTECTED] Betreff: Re: AW: [JBoss-user] JBoss.NET error You're totally right, the bean is not being hit at all, and it's due to the web-service.xml. I had updated the bean to have both remote and local interfaces since the last time it was working. The pr

Re: AW: AW: AW: [JBoss-user] JBoss.NET error

2003-03-25 Thread Nathan Hoover
Gesendet: Dienstag, 25. März 2003 16:04 An: [EMAIL PROTECTED] Betreff: Re: AW: AW: [JBoss-user] JBoss.NET error I have 3.2RC4, which was released on Sunday. Shouldn't I have the right code? How can I get just the XDoclet module without rebuilding JBoss in its entirety? N At 03:33 PM 3/25/

AW: AW: AW: [JBoss-user] JBoss.NET error

2003-03-25 Thread Jung , Dr. Christoph
März 2003 14:33 An: [EMAIL PROTECTED] Betreff: Re: AW: [JBoss-user] JBoss.NET error You're totally right, the bean is not being hit at all, and it's due to the web-service.xml. I had updated the bean to have both remote and local interfaces since the last time

Re: AW: AW: [JBoss-user] JBoss.NET error

2003-03-25 Thread Nathan Hoover
s, it should not occur anymore. -Ursprüngliche Nachricht- Von: Nathan Hoover [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 25. März 2003 14:33 An: [EMAIL PROTECTED] Betreff: Re: AW: [JBoss-user] JBoss.NET error You're totally right, the bean is not being hit at all, and it's

AW: AW: [JBoss-user] JBoss.NET error

2003-03-25 Thread Jung , Dr. Christoph
Title: Nachricht this bug has been resolved in the 3.2 branch last week. If you get the latest sources, it should not occur anymore. -Ursprüngliche Nachricht-Von: Nathan Hoover [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 25. März 2003 14:33An: [EMAIL PROTECTED]Betreff: Re

Re: AW: [JBoss-user] JBoss.NET error

2003-03-25 Thread Nathan Hoover
You're totally right, the bean is not being hit at all, and it's due to the web-service.xml. I had updated the bean to have both remote and local interfaces since the last time it was working. The problem seems to be a bug in the XDoclet code that generates the web-service.xml - this is what's ge

AW: [JBoss-user] JBoss.NET error

2003-03-25 Thread Jung , Dr. Christoph
Title: Nachricht It does not look like your session bean is called at all. What is your global JNDI name of your session bean and how does your  web-service.xml look like? Looks like there is a name "Facadecomp" in your web-service.xml referenced?   CGJ     -Ursprüngliche Nachricht-

AW: [JBoss-user] jboss.net error messages

2003-02-05 Thread Jung , Dr. Christoph
The web-service.xml of jboss.net is a tiny extension to the axis wsdd that additionally allows to - deploy references to external web services - include some extended options into the service tags We once had the idea that web-service.xml should be designed quite along web-applica

Re: AW: AW: [JBoss-user] JBoss.net: error on wsr UNdeployment

2002-07-23 Thread David Ward
t; CGJ > > > -Ursprüngliche Nachricht- > Von: David Ward [mailto:[EMAIL PROTECTED]] > Gesendet: Montag, 22. Juli 2002 16:01 > An: [EMAIL PROTECTED] > Betreff: Re: AW: [JBoss-user] JBoss.net: error on wsr UNdeployment > > > Dr. Jung, > > I do have some

AW: AW: [JBoss-user] JBoss.net: error on wsr UNdeployment

2002-07-22 Thread Jung , Dr. Christoph
Nachricht- Von: David Ward [mailto:[EMAIL PROTECTED]] Gesendet: Montag, 22. Juli 2002 16:01 An: [EMAIL PROTECTED] Betreff: Re: AW: [JBoss-user] JBoss.net: error on wsr UNdeployment Dr. Jung, I do have some unnamed handler elements, but I do that because I was following example. In the

Re: AW: [JBoss-user] JBoss.net: error on wsr UNdeployment

2002-07-22 Thread David Ward
Dr. Jung, I do have some unnamed handler elements, but I do that because I was following example. In the jboss.net module, there is testsuite/src/resources/store/wsr/META-INF/web-service.xml that has in the requestflow: and in the responseFlow, a similar SerialisationResponseHandler and T

AW: [JBoss-user] JBoss.net: error on wsr UNdeployment

2002-07-21 Thread Jung , Dr. Christoph
David, AxisService will turn your deployment element automatically into a corresponding undeploy element when tearing down your app. Guess it is complaining about an element inside the undeploy which could be most likely an unnamed handler, a chain, or something like that? CGJ -Ursprünglich