HiIm trying to use Axis2 to do an EJB invocation. My approach is to plug transport senders/receivers and introduce a Message Receiver for EJB invocation. In Axis2 MessageReceivers are triggered on engine.receive() at server side. My problem is, I cannot run Axis2 on server side (Its not a WebServer
[
http://issues.apache.org/jira/browse/AXIS2-919?page=comments#action_12422805 ]
Derek Foster commented on AXIS2-919:
The title of this one should be "bug in OMElement.serialize()", not "but in..."
Looks like my finger slipped.
> Unable to
Unable to print out entire SOAP message: but in OMElement.serialize()
-
Key: AXIS2-919
URL: http://issues.apache.org/jira/browse/AXIS2-919
Project: Apache Axis 2.0 (Axis2)
I
Hi,
I have a couple of easy questions for you. ;-)
(1) session scope
I know how to enable a service for scope=session, but how is the actual goal
achieved. In other words how does Axis2 keep session affinity among services
and their many clients? Are clients expected to participate (be aware
[ http://issues.apache.org/jira/browse/AXIS2-912?page=all ]
Rich Scheuerle resolved AXIS2-912.
--
Resolution: Fixed
> JAXWS: Unable to serialize DOMSource blocks
> ---
>
> Key: AXIS2-912
>
[ http://issues.apache.org/jira/browse/AXIS2-912?page=all ]
Rich Scheuerle updated AXIS2-912:
-
Attachment: patch2.txt
Here's the corrected test and code.
> JAXWS: Unable to serialize DOMSource blocks
> ---
>
>
[
http://issues.apache.org/jira/browse/AXIS2-912?page=comments#action_12422773 ]
Rich Scheuerle commented on AXIS2-912:
--
I debugged this and the problem is not the code but the test itself.
The DOM that is created is not namespace aware. I
[
http://issues.apache.org/jira/browse/AXIS2-917?page=comments#action_12422741 ]
Derek Foster commented on AXIS2-917:
Note also issue AXIS2-918, which affects fault handling.
> User guide should give explanation and examples of fault handlin
WSDL2Java/XMLBeans generated interfaces should not reference inner classes of
their own subclasses
--
Key: AXIS2-918
URL: http://issues.apache.org/jira/browse/AXIS2-91
[
http://issues.apache.org/jira/browse/AXIS2-917?page=comments#action_12422734 ]
Derek Foster commented on AXIS2-917:
In case it matters, I am using XMLBeans data binding. If fault handling differs
between data bindings, an example of each s
User guide should give explanation and examples of fault handling
-
Key: AXIS2-917
URL: http://issues.apache.org/jira/browse/AXIS2-917
Project: Apache Axis 2.0 (Axis2)
Issue Typ
On Fri, 2006-07-21 at 17:04 +0100, David Illsley wrote:
> > So why dont you set the required transport out into options , and you
> > can do that as follows;
> > option.setTransportOut(TransportOutDescription transportOut).
>
> These absolutely are the properties that matter and it is easy for
>
[ http://issues.apache.org/jira/browse/AXIS2-631?page=all ]
Deepal Jayasinghe resolved AXIS2-631.
-
Resolution: Fixed
Do we need to keep this open forever ?
> Making the integration itests work correctly
>
[ http://issues.apache.org/jira/browse/AXIS2-602?page=all ]
Deepal Jayasinghe reopened AXIS2-602:
-
problem dose not exist
> "wsdl" src module should be merged into the "core" (or "kernel"?) src module
>
[ http://issues.apache.org/jira/browse/AXIS2-687?page=all ]
Deepal Jayasinghe resolved AXIS2-687.
-
Resolution: Fixed
Dims has fixed the issue
> Exploded Configuration for services
> ---
>
> Key: AXIS2-
[
http://issues.apache.org/jira/browse/AXIS2-814?page=comments#action_12422700 ]
Davanum Srinivas commented on AXIS2-814:
Nope. Please check the code, there is ONLY one schema construct that unwrap
supports.
[
http://issues.apache.org/jira/browse/AXIS2-814?page=comments#action_12422697 ]
Deepal Jayasinghe commented on AXIS2-814:
-
As I know Ajith has fix this issue
can we reslove this ?
> unwrapping support in codegen
> --
Deepal Jayasinghe <[EMAIL PROTECTED]> wrote on 07/21/2006 04:30:10 PM:
> Hi David
> Please see my comments below;
>
> David Illsley wrote:
>
> >
> >
> So As I can understand you are trying to keep different handler chains
> for different transports ?
That is something which has been suggested
[ http://issues.apache.org/jira/browse/AXIS2-914?page=all ]
Rich Scheuerle resolved AXIS2-914.
--
Resolution: Fixed
> JAXWS Dynamic Proxy new Updates and test cases
> --
>
> Key: AXIS2-914
>
[
http://issues.apache.org/jira/browse/AXIS2-913?page=comments#action_12422682 ]
Rich Scheuerle commented on AXIS2-913:
--
This appears to be an AXIOM problem. I opened WSCOMMONS-64 and I have provided
a fix. Once that fix is applied I will
Hi David
Please see my comments below;
David Illsley wrote:
>I'm trying to embed Axis2 into a clustered environment and have found that
>the code doesn't neatly fit into the existing extensible handler chain.
>
>The scenario I'm trying to support is non-Axis2 code which can decide to
>override
Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote on 07/21/2006 03:44:54
PM:
> I must be missing something .. what's the diff between this and
> dispatchers?
>
> Sanjiva.
I shouldn't have said 'dispatched to', that was sloppy use of terminology.
The idea here is that the service may be hosted on m
I must be missing something .. what's the diff between this and
dispatchers?
Sanjiva.
On Fri, 2006-07-21 at 12:41 +0100, David Illsley wrote:
> I'm trying to embed Axis2 into a clustered environment and have found that
> the code doesn't neatly fit into the existing extensible handler chain.
>
[
http://issues.apache.org/jira/browse/AXIS2-805?page=comments#action_12422653 ]
Kinichiro Inoguchi commented on AXIS2-805:
--
I checked current SVN.
Problem pattern (3) and (4), still remain.
(3) schema namespace is defined in services.x
Dynamic Web Service Invocation RPC/encoded invocation failed with Element
parameter
---
Key: AXIS-2528
URL: http://issues.apache.org/jira/browse/AXIS-2528
Project: Apache
[
http://issues.apache.org/jira/browse/AXIS2-916?page=comments#action_12422634 ]
Davanum Srinivas commented on AXIS2-916:
I can spot a command line ui in their attic as well:
http://dev.eclipse.org/viewcvs/index.cgi/wst/components/wsdl/pl
Command line WSDL Validator tool
Key: AXIS2-916
URL: http://issues.apache.org/jira/browse/AXIS2-916
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Reporter: Davanum Srinivas
Looks like the WTP
Dear Apache enthusiast,
ApacheCon Asia is the first ever Asian offering of the popular ApacheCon
Conference of the Apache Software Foundation (ASF). ApacheCon Asia
provides an excellent opportunity to experience first-hand what ASF
technologies and development communities can do for you and your
[ http://issues.apache.org/jira/browse/AXIS2-690?page=all ]
Deepal Jayasinghe resolved AXIS2-690.
-
Resolution: Fixed
adding following parameter into services.xml will solve the problem for you
true
> WSDL served up by http://mmcan01-20044:8080/axis2
[ http://issues.apache.org/jira/browse/AXIS2-908?page=all ]
Deepal Jayasinghe resolved AXIS2-908.
-
Resolution: Fixed
fixed in current SVN
to have this feature pls add following parameter into servies.xml
true
> Need a flag for "?wsdl" to show the u
I'm trying to embed Axis2 into a clustered environment and have found that
the code doesn't neatly fit into the existing extensible handler chain.
The scenario I'm trying to support is non-Axis2 code which can decide to
override the target address which is dispatched to based on some
clustering
Thanks Eran. I'll go thru the JIRA and mark items as blockers if needed.
-- dims
On 7/21/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
Hi,
I think its the best time to plan for Axis2 next release, Axis2 1.1. I
know there are bunch of people who rely on nightlies since we fixed some
bugs after
[
http://issues.apache.org/jira/browse/AXIS2-802?page=comments#action_12422619 ]
Eran Chinthaka commented on AXIS2-802:
--
Seems the issue is fixed once user sets the correct content type
> Possible header formation bug
>
[ http://issues.apache.org/jira/browse/AXIS2-802?page=all ]
Eran Chinthaka updated AXIS2-802:
-
Comment: was deleted
> Possible header formation bug
> -
>
> Key: AXIS2-802
> URL: http://issues.ap
[
http://issues.apache.org/jira/browse/AXIS2-802?page=comments#action_12422618 ]
Eran Chinthaka commented on AXIS2-802:
--
Seems the issue is fixed once user sets the current content type
> Possible header formation bug
>
[ http://issues.apache.org/jira/browse/AXIS2-802?page=all ]
Eran Chinthaka updated AXIS2-802:
-
Comment: was deleted
> Possible header formation bug
> -
>
> Key: AXIS2-802
> URL: http://issues.ap
[ http://issues.apache.org/jira/browse/AXIS2-802?page=all ]
Eran Chinthaka updated AXIS2-802:
-
Comment: was deleted
> Possible header formation bug
> -
>
> Key: AXIS2-802
> URL: http://issues.ap
[
http://issues.apache.org/jira/browse/AXIS2-802?page=comments#action_12422615 ]
Eran Chinthaka commented on AXIS2-802:
--
s/current/correct
> Possible header formation bug
> -
>
> Key: AXIS2-802
>
[ http://issues.apache.org/jira/browse/AXIS2-802?page=all ]
Eran Chinthaka resolved AXIS2-802.
--
Resolution: Fixed
Seems the issue is fixed once user sets the current content type
> Possible header formation bug
> -
>
>
Hi,
I think its the best time to plan for Axis2 next release, Axis2 1.1. I
know there are bunch of people who rely on nightlies since we fixed some
bugs after 1.0 and we have done enough, since the last release, to go
for the next release.
I put up some identified tasks here [1] as the criteria f
[ http://issues.apache.org/jira/browse/AXIS2-772?page=all ]
Deepal Jayasinghe resolved AXIS2-772.
-
Resolution: Fixed
fixed in current SVN
> Buggy code sample in MTOM GUIDE
> ---
>
> Key: AXIS2-772
>
[ http://issues.apache.org/jira/browse/AXIS2-794?page=all ]
Deepal Jayasinghe resolved AXIS2-794.
-
Resolution: Fixed
Fixed in current SVN
> erviceContext.getMyEPR(); returns null
> --
>
> Key: AXIS
[ http://issues.apache.org/jira/browse/AXIS2-911?page=all ]
Deepal Jayasinghe resolved AXIS2-911.
-
Resolution: Fixed
fixed in current SVN
> Extra "[#text [#text" around description in generated WSDL
>
Hi,
I want to use Axis 1.4 within Tomcat 5.5.17:
Using CATALINA_BASE: D:\tmp\axis\axis-server
Using CATALINA_HOME: D:\tmp\axis\apache-tomcat-5.5.17
Using CATALINA_TMPDIR: D:\tmp\axis\axis-server\temp
Using JRE_HOME:D:\java\jdk1.5.0
In each Tomcat startup I get the message:
- Unable
[ http://issues.apache.org/jira/browse/AXIS2-915?page=all ]
Deepal Jayasinghe reassigned AXIS2-915:
---
Assignee: Ruchith Udayanga Fernando
> Documentation for Rampart
> -
>
> Key: AXIS2-915
> UR
Hi Ajith,
Thanks for sharing your thoughts,
regarding point 3:
I thought if the original element is an array and it still remains to be an array in the derived type, then I should change the validate method of the array and replace the apptoperiate counts in :
if (param.length > ){throw new
Hey,
I am using the osgi-axis bundle from
knopflerfish (http://www.knopflerfish.org/repo/index.html)
for offering web services out of an osgi environment. I monitored the SOAP
messages created by the axis bundle and unfortunately it puts an extra
“multiRef” tag into the SOAP response me
Hi,
Can you look at the test report and see if there is a stack trace or
some useful message ? Also you can try running the test in IDE.
Ajith
On 7/21/06, Maryam Moazeni <[EMAIL PROTECTED]> wrote:
Hi,
I am trying to build Axis2 after some modifications, but it fails because of
a test failure
Hi,
I am trying to build Axis2 after some modifications, but it fails because of a test failure in the core module.
-
[junit] [ERROR] TEST org.apache.axis2.deployment.ModuleDisEngage
49 matches
Mail list logo
