[ http://issues.apache.org/jira/browse/AXIS2C-323?page=all ]
Damitha Kumarage updated AXIS2C-323:
It is discussed that this is not the right place to put this method. So now I'm
handling this from whithin wsclient code.
Added set_listen_port method
[
http://issues.apache.org/jira/browse/AXIS2C-324?page=comments#action_12441069 ]
Damitha Kumarage commented on AXIS2C-324:
-
I think this can be handled by setting a property in options called
AXIS2_TARGET_EPR instead of adding these
segfault when I try to create dynamic invocation
--
Key: AXIS2C-329
URL: http://issues.apache.org/jira/browse/AXIS2C-329
Project: Axis2-C
Issue Type: Bug
Components: woden
[
http://issues.apache.org/jira/browse/AXIS2C-321?page=comments#action_12441273 ]
Jean-Sebastien Delfino commented on AXIS2C-321:
---
I'd like to use handlers mainly to customize the dispatch algorithm.
For example, to invoke my REST
Hi,
I have done some changes and additions in some files in the core and
tested with existing samples. Please see the attached diffs. Please
also see comments in
https://issues.apache.org/jira/browse/AXIS2C-324
If there are no objections I'll commit the changes
thanks
Damitha
Index:
---BeginMessage---
Hi,
I have done some changes and additions in some files in the core and
tested with existing samples. Please see the attached diffs. Please
also see comments in
https://issues.apache.org/jira/browse/AXIS2C-324
If there are no objections I'll commit the changes
thanks
---BeginMessage---
Hi,
I have been working on a Savan implementation. The initial design is
as follows.
This is implemented as an Axis2 module, in the same level as rampart.
Folder structure
savan/
+--src/
| +--client/
| | savan_client.c
| +--core/
| |
I would not recommend you to try mixing the stuff between 1.0 and
1.1... You can try the snapshots together with 1.1-RC1...
http://people.apache.org/repository/org.apache.axis2/mars/rampart-1.1.mar
IMO this version number is wrong.. Should be 1.1-snapshots..
~Thilina
On 10/10/06, Ali Sadik
Hi,
Can we please re-visit the modules that should be included in Axis2
minimal distribution. Currently kernel, adb and java2wsdl modules are
included, but I saw even adb-codegen was added recently.
What do you think?
Thanks,
Chinthaka
signature.asc
Description: OpenPGP digital signature
Hi,How can I disable Transfer-Encoding: chunked in the response of my axis 1.4 webservice? Thanks in advance
William Ferguson wrote:
I can't find the Axis Fault sample in the release candidate.
http://issues.apache.org/jira/browse/AXIS2-917
Done !! Sorry I forgot to add it to the maven script.
-- Chinthaka
signature.asc
Description: OpenPGP digital signature
InvocationTargetException thrown when accessing 'Engage Module For a Service'
page in Axis2 admin console
-
Key: AXIS2-1333
URL:
Hi,
AFAIK ADB is there because we need the RPCMessageReceiver to work in
the minimal distro...
Just now I figured out that RPCMessageReceiver resides in the codegen
module..Which means we have to include codegen module to the minimal
distro..
I'm not sure why we are putting the adb-codegen in to
While we're looking into this, we should also check the war file
contents. It looks like the full set of jars are included, which is
certainly unnecessary. JiBX support only needs axis2-jibx-XXX.jar and
jibx-run-XXX.jar, not the much larger bcel-XXX.jar (.5 MB) and
jibx-bind-XXX.jar (.3 MB). I
[ http://issues.apache.org/jira/browse/AXIS2-729?page=all ]
Dennis Sosnoski resolved AXIS2-729.
---
Fix Version/s: nightly
Resolution: Fixed
Added more JiBX documentation, including details of wrapped and unwrapped
examples. All links should now
Hi Dennis,
http://svn.apache.org/viewvc/webservices/axis2/branches/java/1_1/maven.xml
This is it Have fun :)
Thanks,
~Thilina
On 10/10/06, Thilina Gunarathne [EMAIL PROTECTED] wrote:
Yes.. We need to figure out the unnecessary jars... Good to know that
we can get rid of bcel-xxx.jar and
Code Generation Exception occurred when Generating Clients
--
Key: AXIS2-1335
URL: http://issues.apache.org/jira/browse/AXIS2-1335
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
[ http://issues.apache.org/jira/browse/AXIS2-1335?page=all ]
Evanthika Amarasiri updated AXIS2-1335:
---
Attachment: Error 6.JPG
Code Generation Exception occurred when Generating Clients
--
Folks,
lets move rpc* out of coden. it does not belong there.
-- dims
On 10/10/06, Thilina Gunarathne [EMAIL PROTECTED] wrote:
Hi,
AFAIK ADB is there because we need the RPCMessageReceiver to work in
the minimal distro...
Just now I figured out that RPCMessageReceiver resides in the codegen
Thilina,
if i add snapshots to the name, the mar wont load :(
-- dims
On 10/10/06, Thilina Gunarathne [EMAIL PROTECTED] wrote:
I would not recommend you to try mixing the stuff between 1.0 and
1.1... You can try the snapshots together with 1.1-RC1...
+1 from me.
On 10/10/06, Srinath Perera [EMAIL PROTECTED] wrote:
+1
On 10/9/06, Bill Nagy [EMAIL PROTECTED] wrote:
There is currently a race condition between code that pauses the message
flow within a handler and resumes it on another thread (e.g. Sandesha)
and the message flow processing
Out of curiosity why gets an issue deleted without comment?
Greetings
Franz
Davanum Srinivas (JIRA) schrieb:
[ http://issues.apache.org/jira/browse/AXIS2-1335?page=all ]
Davanum Srinivas deleted AXIS2-1335:
Code Generation Exception
Wow ! Excellent - well done and thanks
!
I suggest you create a JIRA and attach
the files to that.
Haiping Zhao
[EMAIL PROTECTED]
09/10/2006 18:06
Please respond to
axis-dev@ws.apache.org
To
axis-dev@ws.apache.org
cc
Subject
RE: Apache
Code Generation Exception occurred when Generating stubs
Key: AXIS2-1336
URL: http://issues.apache.org/jira/browse/AXIS2-1336
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Null value is returned when accessing the 'List Single Service' page of an
available service group
--
Key: AXIS2-1337
URL:
Hi All,
I am trying to explore WS Addressing by creating a flow in which i call a WS
(INOUT-with NonBlockingDual client) and then i want the response to be
directed to another WS on a different port and server. I have explicitly set
the To/ReplyTo in my client. In the resluting SOAP request the
Code generation drops the element which holds an xsd:anyType element at both
client and server sides
Key: AXIS2-1338
URL:
[ http://issues.apache.org/jira/browse/AXIS2-1338?page=all ]
Asankha C. Perera updated AXIS2-1338:
-
Attachment: echo.wsdl
ComplexEchoServiceSkeleton.java
ComplexEchoServiceTest.java
Code generation drops the element
[ http://issues.apache.org/jira/browse/AXIS2-1338?page=all ]
Asankha C. Perera updated AXIS2-1338:
-
Attachment: AbstractTestCase.java
Code generation drops the element which holds an xsd:anyType element at both
client and server sides
Franz,
the delete button in JIRA does not allow us to add comments as the
comments are part of the issue that is to be deleted :)
-- dims
On 10/10/06, Franz Fehringer [EMAIL PROTECTED] wrote:
Out of curiosity why gets an issue deleted without comment?
Greetings
Franz
Davanum Srinivas
And what was wrong with this issue i.e. why got it deleted?
Franz
Davanum Srinivas schrieb:
Franz,
the delete button in JIRA does not allow us to add comments as the
comments are part of the issue that is to be deleted :)
-- dims
On 10/10/06, Franz Fehringer [EMAIL PROTECTED] wrote:
Out
On Tue, 2006-10-10 at 07:15 -0400, Davanum Srinivas wrote:
Thilina,
if i add snapshots to the name, the mar wont load :(
-- dims
On 10/10/06, Thilina Gunarathne [EMAIL PROTECTED] wrote:
I would not recommend you to try mixing the stuff between 1.0 and
1.1... You can try the
Franz,
I asked the reporter (a colleague) to open an issue using just the
WSDL2Java bat file and not using a product/gui. Here's the new issue:
http://issues.apache.org/jira/browse/AXIS2-1336
thanks,
dims
On 10/10/06, Franz Fehringer [EMAIL PROTECTED] wrote:
And what was wrong with this
On Mon, 2006-10-09 at 19:51 -0700, Bill Nagy wrote:
There is currently a race condition between code that pauses the message
flow within a handler and resumes it on another thread (e.g. Sandesha)
and the message flow processing chain (Phase.invoke(...),
AxisEngine.invoke(...), etc.)
Will that load when dropped as-is into a repo? I remember we nixed the
SNAPSHOT off the name of the mar to prevent such problems.
-- dims
On 10/10/06, Sanjiva Weerawarana [EMAIL PROTECTED] wrote:
On Tue, 2006-10-10 at 07:15 -0400, Davanum Srinivas wrote:
Thilina,
if i add snapshots to the
[ http://issues.apache.org/jira/browse/AXIS2-1334?page=all ]
Davanum Srinivas updated AXIS2-1334:
Priority: Critical (was: Blocker)
Not a blocker.
-- dims
Deployment of Sandesha2 causes exception in Axis2 Admin-Frontend
On Tue, 2006-10-10 at 08:57 -0400, Davanum Srinivas wrote:
Will that load when dropped as-is into a repo? I remember we nixed the
SNAPSHOT off the name of the mar to prevent such problems.
You'd have to engage as rampart-SNAPSHOT but otherwise should work
fine. Deepal??
Sanjiva.
[
http://issues.apache.org/jira/browse/AXIS2-1252?page=comments#action_12441139 ]
Davanum Srinivas commented on AXIS2-1252:
-
Venkat, Kinichiro, Deepal,
I think we need the ability to specify a namespace/pakage mapping to fully
control
I think I agree with you. How about we drop setOperationContext() and
introduce Axis1-style MessageContext.getCurrentContext() which returns
it for this thread? Have to be careful to put it in TLS and take it off!
We must be careful to tell users that instance variables are not
supported; you
Hi Thilo,
Yes. Sandesha2 1.0 release does not work with the Axis2 1.0 RC1
release. But we hope to do a Sandesha2 release compatible with Axis2
1.1 after it get release. For now you'll have to work with Sandesha2
SNAPSHOTs from
http://people.apache.org/repository/sandesha2/
BTW the Sandesha2
[
http://issues.apache.org/jira/browse/AXIS2-1252?page=comments#action_12441152 ]
Kinichiro Inoguchi commented on AXIS2-1252:
---
dims, Venkat, Deepal,
Thanks for your discussions.
I agree with algorithm of dims,
and I believe current
[
http://issues.apache.org/jira/browse/AXIS2-1252?page=comments#action_12441163 ]
Kinichiro Inoguchi commented on AXIS2-1252:
---
I see. I fully agreed with your algorithm.
java2wsdl generates unknown namespace
[
http://issues.apache.org/jira/browse/AXIS2-586?page=comments#action_12441165 ]
Davanum Srinivas commented on AXIS2-586:
Justin,
Could you please upload your java test code that you use to send the message? I
am assuming you ran w2j
[
http://issues.apache.org/jira/browse/AXIS2-586?page=comments#action_12441169 ]
Justin Schoeman commented on AXIS2-586:
---
The client code is on:
http://www.schoeman.org.za/axis2_test_client.tbz
It is hard coded to call either of the test
WSDL2Java client side stub code does not work with AXIS2 TCP Server
---
Key: AXIS2-1339
URL: http://issues.apache.org/jira/browse/AXIS2-1339
Project: Apache Axis 2.0 (Axis2)
[
http://issues.apache.org/jira/browse/AXIS2-749?page=comments#action_12441182 ]
Davanum Srinivas commented on AXIS2-749:
Problem shows up in user environments. we need to to this...
[
http://issues.apache.org/jira/browse/AXIS2-749?page=comments#action_12441185 ]
Davanum Srinivas commented on AXIS2-749:
Again, the idea is that you should be able to deploy rpc/pojo using just the
min distro.
-- dims
Mixing compile
Ok... Here's my suggestion.. Let's create new service objects per invocation..
AFAIK two things happen when we deploy a service in application scope.
One is that Axis2 will maintain a single service context throughout
the life of the service.. Other thing is Axis2 maintains one service
class
+1... Seeems like you have already migrated it to ADB :)..
~Thilina
On 10/10/06, Davanum Srinivas [EMAIL PROTECTED] wrote:
Folks,
lets move rpc* out of coden. it does not belong there.
-- dims
On 10/10/06, Thilina Gunarathne [EMAIL PROTECTED] wrote:
Hi,
AFAIK ADB is there because we need
Yes i did :)
-- dims
On 10/10/06, Thilina Gunarathne [EMAIL PROTECTED] wrote:
+1... Seeems like you have already migrated it to ADB :)..
~Thilina
On 10/10/06, Davanum Srinivas [EMAIL PROTECTED] wrote:
Folks,
lets move rpc* out of coden. it does not belong there.
-- dims
On 10/10/06,
Hi Thilina
Thilina Gunarathne wrote:
Ok... Here's my suggestion.. Let's create new service objects per
invocation..
I do not agree with this approach :) , with this if some one deploy a
service with application scope then there will be multiple instance of
same service impl class.
Deploying a
Thilina,Here is my concern. If you have application scope the expectation is that we have a single instance throught the life of the app.So I could be initializing very expensive stuff in my init() and thats ok bcos the expectation is that you do that only once.
Imagine if we have to do this for
Axis2Util.toOM() needs to work w/o XML-Security jar
---
Key: AXIS2-1340
URL: http://issues.apache.org/jira/browse/AXIS2-1340
Project: Apache Axis 2.0 (Axis2)
Issue Type: Improvement
Does this mean, now we can happily ship the minimal distro with kernel,
adb and java2wsdl in it?
Agreed?
-- Chinthaka
Davanum Srinivas wrote:
Yes i did :)
-- dims
On 10/10/06, Thilina Gunarathne [EMAIL PROTECTED] wrote:
+1... Seeems like you have already migrated it to ADB :)..
[
http://issues.apache.org/jira/browse/AXIS2-1247?page=comments#action_12441249 ]
Tom Jordahl commented on AXIS2-1247:
Note that an Axis 1.x, any integer type that is nillable has to become a Java
Integer. Otherwise you can not tell if 0
[
http://issues.apache.org/jira/browse/AXIS2-1272?page=comments#action_12441253 ]
Tom Jordahl commented on AXIS2-1272:
(Commented on AXIS2-1247 also) Note that an Axis 1.x, any integer type that is
nillable has to become a Java Integer.
[
http://issues.apache.org/jira/browse/AXIS2-1274?page=comments#action_12441255 ]
Tom Jordahl commented on AXIS2-1274:
Dims, Does this mean that by default wsdl2java does not emit code for all the
ports in a WSDL?
That seems bad to me.
[
http://issues.apache.org/jira/browse/AXIS2-1274?page=comments#action_12441258 ]
Davanum Srinivas commented on AXIS2-1274:
-
Yep :( I tried...
WSDL2Java does not create Stub class for PortType
+1 for Sanjiva's suggestions:
-c client side
-s server side
-t test case generation.
I think -a should be for all, but I assume it is in use already?
--
Tom Jordahl
Adobe ColdFusion Team
-Original Message-
From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED]
Sent: Monday, October
-0 from me.
While Jetty is super sweet, Axis2 has a serious jar file dependency
problem. I think its going to have to go in to a detox program soon!
--
Tom Jordahl
Adobe ColdFusion Team
-Original Message-
From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED]
Sent: Monday, October 09,
Hi Deepal,
Deploying a service in application scope , user want to have once
service impl instance (im I were a user , I want that )
Frankly I don't...
:)
Service impl class is a Axis2 bundled MR(eg:
RawXMLInOut..) specific notion... Service impl is meaning less if the
user has written
While we may have had to work around some bugs in Thread Local Storage
(TLS) on the whole I think the Axis 1.x
MessageContext.getCurrentContext() works exceptionally well.
Since JDK 1.4 is the minimum for Axis2, I believe we have all the TLS
bugs behind us, no?
--
Tom Jordahl
Adobe ColdFusion
Thilina,I understand your use case about having to create a new object for each invocation.But your use case is clearly in the minority. (meaning people will not do that often)So if you have a special requirment like that then why not use the concept of ServiceObjectSupplier.
So if u specify a
In terms of setting up TLS info, I'm interested by the comment that it
would be set in the AxisEngine. When we had the conversation about the
ThreadContextMigrator interface (which does now exist) I understood
that there wasn't any guarantee that there is a single thread in use
through the
[ http://issues.apache.org/jira/browse/AXIS2-1233?page=all ]
Bill Nagy closed AXIS2-1233.
Resolution: Fixed
Handlers do not get a chance to undo work if a fault occurs or complete work
when message processing finishes (this was split off from AXIS2-653)
Dennis Sosnoski wrote:
While we're looking into this, we should also check the war file
contents. It looks like the full set of jars are included, which is
certainly unnecessary. JiBX support only needs axis2-jibx-XXX.jar and
jibx-run-XXX.jar, not the much larger bcel-XXX.jar (.5 MB) and
[
http://issues.apache.org/jira/browse/AXIS2-1339?page=comments#action_12441283 ]
yogen commented on AXIS2-1339:
--
This is further information on this issue
One difference I debugged is ...
In TCP Server impl the MessageContext.Options.to value
[
http://issues.apache.org/jira/browse/AXIS2-1339?page=comments#action_12441284 ]
yogen commented on AXIS2-1339:
--
This is further information on this issue
One difference I debugged is ...
In TCP Server impl the MessageContext.Options.to
On Tue, 2006-10-10 at 20:21 +0100, David Illsley wrote:
In terms of setting up TLS info, I'm interested by the comment that it
would be set in the AxisEngine. When we had the conversation about the
ThreadContextMigrator interface (which does now exist) I understood
that there wasn't any
On 10/10/06, Sanjiva Weerawarana [EMAIL PROTECTED] wrote:
On Tue, 2006-10-10 at 20:21 +0100, David Illsley wrote:
In terms of setting up TLS info, I'm interested by the comment that it
would be set in the AxisEngine. When we had the conversation about the
ThreadContextMigrator interface
Hi
Sanjiva Weerawarana wrote:
On Tue, 2006-10-10 at 20:21 +0100, David Illsley wrote:
In terms of setting up TLS info, I'm interested by the comment that it
would be set in the AxisEngine. When we had the conversation about the
ThreadContextMigrator interface (which does now exist) I
Hi All;
Few note from todays Hackathon we had at ApacheCon US.
We are having very ugly name called finalizeInvoke() in service client
with restriction, so we (Glen and I agreed) to remove that method and
move the code into cleanup (well I am doing the changes in current
codebase).
Why do we
Deepal,
Please create JIRA issue(s) and let's work on them.
thanks,
dims
On 10/10/06, Deepal Jayasinghe [EMAIL PROTECTED] wrote:
Hi All;
Few note from todays Hackathon we had at ApacheCon US.
We are having very ugly name called finalizeInvoke() in service client
with restriction, so we
Hi,
I'm having a problem with the Axis2 1.1 RC on the client side. My services
still work as normal when I upgrade them to 1.1, but my non-Axis2 clients
fail when trying to parse the response message. I get the following error
message from the JAXP DocumentBuilder (Xerces):
[Fatal
Hi,
public MessageContext sendReceive(MessageContext req){}
public void sendReceiveNonBlocking(MessageContext req){}
public fireAndForget(MessageContext req){}
public sendRobust(MessageContext req){}
Huge +1.
Currently we provide SwA support only in the OperationClient level,
cause we need
Hi Sanjiva,
The problem isn't that both people are modifying MessageContext.paused,
so synchronizing that isn't going to work, the problem is that if the RM
handler, for instance, pauses the message and returns, but the RM thread
picks up the message and resumes it (thereby unpausing the message)
Hi All,The current spring support fails with the following exception possibly due to the new code change of obtaining the servlet config from the AxisConfiguration instead from the Message Context.Caused by:
org.apache.axis2.AxisFault: Axis2 Can't find ServletConfig; nested exception
Forwarding with the axis2 prefix.-- Forwarded message --From: Rajith Attapattu [EMAIL PROTECTED]
Date: Oct 10, 2006 10:17 PMSubject: Re: Spring support broken ?To: axis-dev@ws.apache.orgCc: [EMAIL PROTECTED]
Hi All,The current spring support fails with the following exception
On Tue, 2006-10-10 at 17:54 -0500, Deepal Jayasinghe wrote:
Why do we need operation client ?
??? You gotta be kidding.
We have it because that's the client API for a generic MEP.
As Dennis suggested , having annon name as public static seems not that
good , so we need to remove them
SanjivaI also agree on your comments regarding the operation client.Now about the whole session/clustering thing. You mention that outside of Axis2 the concept of Service Group does not exist !!!So a client would expect to interact with Services from two Service Groups in a single session.
Thats
Its late here so I'll take a look tomorrow. In the meantime, the
reason why this wasn't caught is because I'm not sure how to get a
ServletContext from our testing environment or if its even possible.
There are tests for the non-servlet container config. If someone knows
how to test the former
I dont' remember that. I do remember this:
http://marc.theaimsgroup.com/?l=axis-devm=115869598518264w=2
which was, that If mtom enabled is on, then we always use mime stuff
whether there is an attachment or not.
-- dims
On 10/10/06, Thilina Gunarathne [EMAIL PROTECTED] wrote:
Ahh... My bad..
[ http://issues.apache.org/jira/browse/AXIS2-1340?page=all ]
Davanum Srinivas resolved AXIS2-1340.
-
Resolution: Fixed
Looks like this is fixed:
http://marc.theaimsgroup.com/?l=axis-cvsm=116052397203244w=2
[ http://issues.apache.org/jira/browse/AXIS2-1163?page=all ]
Davanum Srinivas reassigned AXIS2-1163:
---
Assignee: Eran Chinthaka
replace service endpoint when serving original wsdl using useOriginalwsdl
param
[
http://issues.apache.org/jira/browse/AXIS-2541?page=comments#action_12441342 ]
Christian Phan-Trong commented on AXIS-2541:
I have exactly the same issue. I Took a look at similar issues in Jira, and it
seems like this one is a
[ http://issues.apache.org/jira/browse/AXIS2-1333?page=all ]
Davanum Srinivas resolved AXIS2-1333.
-
Resolution: Fixed
Charitha,
fixed in r462694 (branch 1.1).
Can u please try this?
thanks,
dims
PS: Make sure your completely remove the work
[ http://issues.apache.org/jira/browse/AXIS2-1336?page=all ]
Evanthika Amarasiri updated AXIS2-1336:
---
Attachment: CommodityQuote.wsdl
Wsdl File used to generate the stub
Code Generation Exception occurred when Generating stubs
Cannot disengage a globally engaged module
--
Key: AXIS2-1341
URL: http://issues.apache.org/jira/browse/AXIS2-1341
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Affects Versions: 1.1
Hi,
Thanks for the prompt reply Eran, this issue was resolved yesterday after a
suggestion by Brian, that in such a scenario we should use fireandforget
instead of sendrecievenonblocking and this worked for meand that
comes out to be the same tht you have suggested :-)
thanks
89 matches
Mail list logo
