hmm , sometimes ago we set the module as the name specified in
module.xml , but we changed that recently (0.95) to have module name as
name of the archive file.So previously module.xml had name=logging
attribute and that become the name of the module even though actual
archive name
://www.nabble.com/-Axis2-1.0RC1-Problem-getting-MessageContext-in-ServiceImpl-class-t1423137.html#a3875656
Sent from the Axis - User forum at Nabble.com.
--
Thanks,
Deepal
~Future is Open~
not sure it will work without making some changes , I will update the
result.
Thanks
Gopal
--
View this message in context:
http://www.nabble.com/-Axis2-1.0RC1-Problem-getting-MessageContext-in-ServiceImpl-class-t1423137.html#a3946331
Sent from the Axis - User forum at Nabble.com.
Yeah that fixed it - thanks. I filed a jira on this:
http://issues.apache.org/jira/browse/AXIS2-570
Robert
http://www.braziloutsource.com/On 4/13/06, Ali Sadik Kumlali
[EMAIL PROTECTED] wrote:Hi Robert,I faced the same problem and posted messages about it yesterday. When
you rename
Hi there!
We installed the axis2 1.0 RC1 WAR file distribution in Tomcat 5.5.15. It loads
ok but whenever you click on Validation on the /axis2 homepage, it seems to have
problems with the latest refactoring of the AXIOM team. Is this a config problem
or a problem of this build?
Greetings,
--
Hi there,
we tried to port our (working) service from 0.95 to 1.0, but encountered some
problems. After calling WSDL2Java once for the service and once for the client
(in the same manner as for 0.95) we ended up with a non-working client.
We also get a warning from log4j, is this something to be
Sebastian,
JIRA bug please? :) (In Axis2)
thanks,
dims
On 4/12/06, Sebastian J. Schultheiss [EMAIL PROTECTED] wrote:
Hi there!
We installed the axis2 1.0 RC1 WAR file distribution in Tomcat 5.5.15. It
loads
ok but whenever you click on Validation on the /axis2 homepage, it seems to
have
Hi all,
I'm trying to port a module from around .94 to RC1 . I had some
engagement problems, so I decided to try deploying the LoggingModule
from the user guide - my module largely follows that example. The debug
logs show:
- Deploying module : LoggingModule
-
Hi Dims,
here's your JIRA:
http://issues.apache.org/jira/browse/AXIS2-569
I guess it's just a matter of refactoring the source of the validation code.
Hope to help,
-- Sebi
Davanum Srinivas wrote:
Sebastian,
JIRA bug please? :) (In Axis2)
thanks,
dims
On 4/12/06, Sebastian J.
Hi Robert,
I faced the same problem and posted messages about it yesterday. When
you rename LoggingModule.mar to logging.mar it should work. Could you
please give this a try?
Regards,
Ali Sadik Kumlali
--- robert lazarski [EMAIL PROTECTED] wrote:
Hi all,
I'm trying to port a module from
Yes, the change is incorporated in Axis2 1.0 RC1.
Add the method
public void setOperationContext(OperationContext opctx)
in your service class and from that you can get the message contexts.
To get In Message Context :
MessageContext inMsgCtxt =
Inoguchi, Kinichiro wrote:
Hi,
Let me answer the third question.
3. om import directive is changed.
I think this will be done by Axiom team, though.
0.95 org.apache.ws.commons.om.*;
1.0RC1 org.apache.axiom.om.*;
yes, this is due to latest refactorings in axiom and this
in context:
http://www.nabble.com/-Axis2-1.0RC1-Problem-getting-MessageContext-in-ServiceImpl-class-t1423137.html#a3874474
Sent from the Axis - User forum at Nabble.com.
Gopal Patwa wrote:
Thanks Chinthaka, It work now but I have some other problem.
I have wrote axis2 asynchronous service to work with BPEL. When I am trying
to call BPEL service while to engaging addressing module
ServiceClient sender = new ServiceClient();
addressing-version.mar in your
classpath.
-- Chinthaka
--
View this message in context:
http://www.nabble.com/-Axis2-1.0RC1-Problem-getting-MessageContext-in-ServiceImpl-class-t1423137.html#a3875656
Sent from the Axis - User forum at Nabble.com.
Hi,
I was checking Axis2 1.0RC1 a little bit.
I noticed 3 difference between with 0.95.
1. result of ?wsdl is changed.
Say, http://localhost:8080/axis2/services/version?wsdl,
In wsdl:types, getVersionRequest(0.95) is changed to
getVersion(1.0RC1).
In wsdl:message
to work in 0.95 but not anymore in
1.0RC1 (Tomcat 5.5 app server)
thanks
Gopal
--
View this message in context:
http://www.nabble.com/-Axis2-1.0RC1-Problem-getting-MessageContext-in-ServiceImpl-class-t1423137.html#a3853507
Sent from the Axis - User forum at Nabble.com.
17 matches
Mail list logo