Axis2 integration with Weblogic admin console
I have a web application .war that includes an axis2 (1.3) web service and a GUI component. This application is deployed on a weblogic 9.2 server. The application is 100% functional: - The GUI is available at http://localhost:7001/appName/index.html - The web service is available at http://localhost:7001/appName/webservice - The axis2 admin console is available at http://localhost:7001/appName/axis2-web/index.jsp However, in the weblogic administration console (http://localhost:7001/console), there are no web services listed under the deployment for my application. Does anyone know how to integrate Axis2 web services into the weblogic administration console? Is this even possible? Thanks, Kevin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 integration with Weblogic admin console
I've deployed the axis2.war, the services and axis2 admin console are working correctly. http://localhost:7001/axis2/axis2-web/index.jsp axis2.war is deployed with the Version and listServices web services. However, these services do not appear in the weblogic admin console. Is this a weblogic configuration issue? Are there any weblogic experts who can help? Kevin On Wed, Nov 26, 2008 at 9:46 AM, Jain, Prateek <[EMAIL PROTECTED]> wrote: > > > Kevin, > > I have never worked on web logic but, I am sure it must be using some > servlet container for functioning. You need to copy axis2 war package in > that container as normal web application and the deploy your web > services under its services directory. I think this should be handy for > now. If it doesn't work (as I said I am not a weblogic expert :-]) > > Regards, > Prateek > > > -Original Message- > From: Kevin TierOne [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 26, 2008 9:39 AM > To: axis-user@ws.apache.org > Subject: Axis2 integration with Weblogic admin console > > I have a web application .war that includes an axis2 (1.3) web service > and a GUI component. This application is deployed on a weblogic 9.2 > server. > > The application is 100% functional: > - The GUI is available at http://localhost:7001/appName/index.html > - The web service is available at > http://localhost:7001/appName/webservice > - The axis2 admin console is available at > http://localhost:7001/appName/axis2-web/index.jsp > > However, in the weblogic administration console > (http://localhost:7001/console), there are no web services listed > under the deployment for my application. > > Does anyone know how to integrate Axis2 web services into the weblogic > administration console? Is this even possible? > > Thanks, > Kevin > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Accessing SOAP message from MessageContexts in Handlers
Hi Wayne,
We've talked about this but I thought I'd post to see if anyone else can
give us insight.
The original message context of the MySoapReceiverInOut.invokeBusinessLogic()
code stores the incoming soap envelope. If your skeleton throws an
exception, AxisFault.handleFault() will replace the messageContext's soap
envelope with faultContext.getEnvelope(). If there is no exception in your
code, the setEnvelope() call is not invoked.
The reason why you cannot use
msgContext.getOperationContext().getMessageContext("In")
to get the orignal envelope, is that the getMessage("In") refers to the
original message context (because the hashmap stores a reference to original
message context). Its envelope was overwritten with the fault envelope
during the fault handling. Not sure why there is also a getMessage("Fault")
that returns the same envelope. Perhaps it's a bug or maybe there is a
reason for this. I don't know enough about the Axis2 code.
Kevin
--
From: [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Subject: Accessing SOAP message from MessageContexts in Handlers
Date: Wed, 20 Jun 2007 16:09:20 -0400
Using Axis2 1.2. Is there a way to read the original SOAP message within a
PostDispatch Handler?
I'm invoking a custom handler in the PostDispatch phase. The handler reads
the uses the MessageContext to get the original soap request message.
Something like this:
String incomingMsg=msgContext.getOperationContext
().getMessageContext("In").getEnvelope().toString();
System.out.println("Original SOAPMessage: "+incomingMsg);
This works fine in the success case. The problem is if the Skeleton code
throws an exception, the above code prints the "Fault" soap message. For
example, the following code prints exactly the same output:
String incomingMsg=3DmsgContext.getOperationContext
().getMessageContext("In").getEnvelope().toString();
System.out.println("SOAPMessage: "+incomingMsg);=0A=
String faultMsg=3DmsgContext.getOperationContext
().getMessageContext("Fault").getEnvelope().toString();
System.out.println("SOAPMessage: "+faultMsg);
Am I doing something incorrectly? Is there another way to get the original
SOAP message in a Handler?
Thanks,
Wayne
Axis2 1.2, Rampart 1.2 passwordType question
In the axis2 client, it looks like it is possible to configure password authentication with clear text passwords or a password digest. Like this: PasswordText or PasswordDigest On the Axis2 server, my inflow security is similar to rampart's sample02: UsernameToken Timestamp myClass Is it possible to configure the server to require a Password Digest? It would be nice if I can configure the server to fail authentication if the password sent in clear text. Thanks, Kevin
