[ http://issues.apache.org/jira/browse/AXIS2-1609?page=all ]
Ulf Heyder updated AXIS2-1609:
--
Attachment: KeinFehlerWsdl2Java.zip
Thanks to Carlos Riberiro answering my mail in axis-user list:
He wrote:
You probably need to do: "-ns2p
http://www.foo-bar.de/
[
http://issues.apache.org/jira/browse/AXIS2-1746?page=comments#action_12455963 ]
Sajith Salim commented on AXIS2-1746:
-
Hello
The same issue occured for me also. We converted our java class into WSDL.,
generated the client stub using that
[ http://issues.apache.org/jira/browse/AXIS2-1746?page=all ]
Sajith Salim updated AXIS2-1746:
Attachment: Src.zip
ShipmentStatusService.aar
Attached is the aar and source files for the shipment status web service
> POJO client call faile
Hi all,
It is very hard for me to understand the semantics of
OMElement.setFirstChild().
Let's see,,,
-
OMElement parent = .
OMElement a = .
OMElement b = .
OMElement c = .
parent.addChild(a);
parent.addChild(b);
parent.addChild(c);
parent.setFirstChild(b);
-
Then, what h
[
http://issues.apache.org/jira/browse/AXIS2-1746?page=comments#action_12455969 ]
Santhosh Kumar Nullipady commented on AXIS2-1746:
-
Hi,
I also get the same error while running the client.I have tried with
axis2 latest nightl
Hello,
I posted this question on the user list but it couldn't be solved there so I
post it again here since the docs clearly state question on this subject can
be posted here as well.
http://ws.apache.org/axis2/1_1/http-transport.html.
Here's what I'm trying to do:
We run apache httpd partial
Http session is always created, even if transport session management is disable.
Key: AXIS2-1833
URL: http://issues.apache.org/jira/browse/AXIS2-1833
Project: Apache Axis
[ http://issues.apache.org/jira/browse/AXIS2-1833?page=all ]
Davanum Srinivas resolved AXIS2-1833.
-
Resolution: Fixed
already fixed both in 1.1 branch and trunk.
thanks,
dims
> Http session is always created, even if transport session management is
Hi
I've been working with a consortium who want to be able to use smtp
mail for SOAP1.2. The current SOAP 1.2 binding for email has a concern
that the message is the main body of the email, and might be corrupted
by spam or anti-virus filters that add text into the message.
So the proposal that
Oh I forgot to mention. I'd like us to implement this in Axis2. I
guess we need a property to define whether we use the SOAP1.2 email
binding or this binding.
Paul
On 12/6/06, Paul Fremantle <[EMAIL PROTECTED]> wrote:
Hi
I've been working with a consortium who want to be able to use smtp
mail
did you try setting socket_keepalive and other timeout related
properties in the tomcat worker.properties?
http://tomcat.apache.org/connectors-doc/config/workers.html
-- dims
On 12/6/06, Peter Neu <[EMAIL PROTECTED]> wrote:
Hello,
I posted this question on the user list but it couldn't be sol
Hi,
I already got these settings in my worker.properties:
worker.worker2.cache_timeout=600
worker.worker2.socket_keepalive=1
worker.worker2.reclycle_timeout=300
despite this I get the java.net.SocketTimeoutException. :o(
Cheers,
Pete
> -Ursprüngliche Nachricht-
> Von: Davanum Sr
AddressingBasedDispatcher doesn't dispatch according to the wsa:Action
--
Key: AXIS2-1834
URL: http://issues.apache.org/jira/browse/AXIS2-1834
Project: Apache Axis 2.0 (Axis2)
[ http://issues.apache.org/jira/browse/AXIS2-1834?page=all ]
Ali Sadik Kumlali updated AXIS2-1834:
-
Attachment: patch.txt
Patch has been added.
> AddressingBasedDispatcher doesn't dispatch according to the wsa:Action
> --
Sorry, I have to ask... why not ws-addressing?
You could embed an EPR with a refparam identifying the service in the
WSDL which should then be copied to the SOAP Header. Or even just use
the fact that the ?X-Service-Path would be automatically copied into a
wsa:To element.
Per Basic Profile 1.1
[
http://issues.apache.org/jira/browse/AXIS2-1834?page=comments#action_12456045 ]
David Illsley commented on AXIS2-1834:
--
Hi,
Thanks for the patch. I've had a quick look and have a couple of thoughts:
1. Why is service dispatch based on wsa:
Hi Eran,
My response is below.
Cheers
Brian DePradine
Web Services Development
IBM Hursley
External +44 (0) 1962 816319 Internal 246319
If you can't find the time to do it right the first time, where will you
find the time to do it again?
Eran Chinthaka <[EMAIL PROTECTED]> wrote on
Hi,
I want to create a service which return an object containing a List:
The object to return:
public class Container {
private List myList = new ArrayList();
public List getList() {
return myList;
}
}
The service (pojo) :
public class MyService {
private Container container = new
Hi Benoit ;
Seems like bug in the code rather missing part :) , so please create a
JIRA I will fix that before next release:
Thanks
Deepal
> Hi,
>
> I want to create a service which return an object containing a List:
>
> The object to return:
> public class Container {
> private List myList =
[
http://issues.apache.org/jira/browse/AXIS2-1609?page=comments#action_12456095 ]
Craig S. Bosma commented on AXIS2-1609:
---
I think this remains an issue yet for namespaces that do not follow the
'http://example.com/some/path' convention. T
[ http://issues.apache.org/jira/browse/AXIS2-1826?page=all ]
Jeff Barrett resolved AXIS2-1826.
-
Resolution: Fixed
Patch applied; Committed revision 483117. Thanks, Roy!
> Several bug fixes for Description Builder Composite
> ---
[ http://issues.apache.org/jira/browse/AXIS2-1609?page=all ]
Craig S. Bosma updated AXIS2-1609:
--
Attachment: saw-local.wsdl
SAWServices.xsd
expression.xsd
Here are the WSDL and referenced schemas.
> namespace to package
[
http://issues.apache.org/jira/browse/AXIS2-1834?page=comments#action_12456101 ]
Ali Sadik Kumlali commented on AXIS2-1834:
--
Hi David,
You are totally right. But, for the JMS case, for example, wsa:To doesn't have
service name[1]. The
[
http://issues.apache.org/jira/browse/AXIS2-1834?page=comments#action_12456107 ]
David Illsley commented on AXIS2-1834:
--
OK. I'm totally in favour of a fix for AXIS2-1665 but totally against the
approach put forward in this issue which I t
return a java.lang.List return a java.lang.IllegalArgumentException: null rcl
-
Key: AXIS2-1835
URL: http://issues.apache.org/jira/browse/AXIS2-1835
Project: Apache Axis 2.0 (
JAX-WS JAXBContext cannot be shared across ClassLoaders
---
Key: AXIS2-1836
URL: http://issues.apache.org/jira/browse/AXIS2-1836
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
C
[ http://issues.apache.org/jira/browse/AXIS2-1832?page=all ]
Jeff Barrett resolved AXIS2-1832.
-
Resolution: Fixed
Patch applied; Committed revision 483143. Thanks, Mike!
> fix and enable the test added in jira AXIS2-1830
> -
[ http://issues.apache.org/jira/browse/AXIS2-1836?page=all ]
Rich Scheuerle updated AXIS2-1836:
--
Attachment: patch.txt
Committed to SVN. Revision = 483147
> JAX-WS JAXBContext cannot be shared across ClassLoaders
> ---
[ http://issues.apache.org/jira/browse/AXIS2-1836?page=all ]
Rich Scheuerle resolved AXIS2-1836.
---
Resolution: Fixed
> JAX-WS JAXBContext cannot be shared across ClassLoaders
> ---
>
>
Hi all
Hope this is the right place to talk about this:
I found that generating the wsdl from a java class with a method
returning a 'java.util.Date' object has the same behaviour as using a '
java.util.Calendar'. In both generated wsdl files the type is translated to
'dateTime'. I expected the
[
http://issues.apache.org/jira/browse/AXIS2-1402?page=comments#action_12456147 ]
Ulf Heyder commented on AXIS2-1402:
---
With all generated XML, XSD, WSDL, ... character encoding as well as xml
version an encoding specification should be preserv
jaxws client processing exceptions are absorbed
---
Key: AXIS2-1837
URL: http://issues.apache.org/jira/browse/AXIS2-1837
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Reporter: Mike
[
http://issues.apache.org/jira/browse/AXIS2-1837?page=comments#action_12456154 ]
Mike Rheinheimer commented on AXIS2-1837:
-
Crud. I forgot to select JAXWS component.
> jaxws client processing exceptions are absorbed
> -
[ http://issues.apache.org/jira/browse/AXIS2-1837?page=all ]
Mike Rheinheimer updated AXIS2-1837:
Attachment: patch.txt
> jaxws client processing exceptions are absorbed
> ---
>
> Key: AXIS2
Jacob,
The generation is based on java to xml mapping as defined in the
specification JAX-RPC 1.1. I have not
looked at JAX-WS, but I suspect it has the same mapping.
Have you tested the runtime behavior. I would expect the runtime to do the
necessary conversion based
on what the target service
[
http://issues.apache.org/jira/browse/AXIS2-1810?page=comments#action_12456162 ]
Glen Daniels commented on AXIS2-1810:
-
Hi Gul:
Deepal and I are sitting here at XML2006 discussing this issue, and we're
having trouble seeing what the benefi
[
http://issues.apache.org/jira/browse/AXIS2-1837?page=comments#action_12456166 ]
Rich Scheuerle commented on AXIS2-1837:
---
I am reviewing the patch and will commit it this afternoon.
> jaxws client processing exceptions are absorbed
>
[
http://issues.apache.org/jira/browse/AXIS2-1831?page=comments#action_12456167 ]
Glen Daniels commented on AXIS2-1831:
-
Hi Na:
Unfortunately, this bug report really doesn't help us much. :( Is this a
problem with *every* generated stub, o
[ http://issues.apache.org/jira/browse/AXIS2-1799?page=all ]
Rich Scheuerle updated AXIS2-1799:
--
Attachment: patch3.txt
Enabled and fixed the SimpleFault test.
The schema for the simpleFault is
Which means the @WebFault faultBean="int".
Special
[
http://issues.apache.org/jira/browse/AXIS2-1810?page=comments#action_12456170 ]
Gul Onural commented on AXIS2-1810:
---
If you design the service upgrade strategy around the assumption of
every change in a service interface makes a new servic
[
http://issues.apache.org/jira/browse/AXIS-2594?page=comments#action_12456172 ]
Henri Yandell commented on AXIS-2594:
-
Nope, sorry Joon. I'm guessing that there hasn't been a resolution to AXIS-1343
and I've got very little Resin experience
[
http://issues.apache.org/jira/browse/AXIS2-1823?page=comments#action_12456178 ]
Deepal Jayasinghe commented on AXIS2-1823:
--
How about adding a method to service client to get current operation context
from that , something like
Servi
[ http://issues.apache.org/jira/browse/AXIS2-1837?page=all ]
Rich Scheuerle resolved AXIS2-1837.
---
Resolution: Fixed
Committed to SVN. Revision=483193
> jaxws client processing exceptions are absorbed
> ---
[
http://issues.apache.org/jira/browse/AXIS2-1817?page=comments#action_12456182 ]
Deepal Jayasinghe commented on AXIS2-1817:
--
The main idea of ServiceClient is to provide a way to invoke a service using
very XML centric manner , that is
[
http://issues.apache.org/jira/browse/AXIS2-1819?page=comments#action_12456184 ]
Deepal Jayasinghe commented on AXIS2-1819:
--
Is there any possibility of attaching your service aar file , that will help us
to regenerate the issue.
> ja
[
http://issues.apache.org/jira/browse/AXIS2-1810?page=comments#action_12456185 ]
Glen Daniels commented on AXIS2-1810:
-
OK, here's an example. You've got:
class Service {
public String getWeather(int zipcode) { ... }
}
And you deploy th
[ http://issues.apache.org/jira/browse/AXIS2-1823?page=all ]
Glen Daniels reassigned AXIS2-1823:
---
Assignee: Glen Daniels
> Client API needs a method to access Current Message Context
> ---
>
>
Thanks for the reply,
You are right, the mapping follows the specification and i was wrong
about the correct behavior. In my previous experiences with axis 1.x I
played with wsdl2java and the mapping of 'date' in java is a
'java.util.Date' object so i made a mistake assuming the mapping was
'date
[
http://issues.apache.org/jira/browse/AXIS2-1708?page=comments#action_12456203 ]
Deepal Jayasinghe commented on AXIS2-1708:
--
fixed in 1.1 branch not in trunk
483221
> NullPointerException while accessing WSDL in a HTTPS way
> -
On Tue, 2006-12-05 at 01:25 +0900, Takahide Nogayama wrote:
>
> Hi Sanjiva,
>
> I am hoping to resume this discussion with you.
> Please give us comment about these alternative solution's pros and
> cons or let me know what is your concrete worry.
Sorry for dropping the ball on this; will rev
On Tue, 2006-10-31 at 08:19 -0600, R J Scheuerle Jr wrote:
> >But we can not filter SOAP header part by the handler solution,
> because
> >SOAP header part is already build in transport layer before handler
> layer
> >by invoking envelope.getBody(). For example, envelope.getBody() is
> called
>
On Wed, 2006-11-22 at 13:59 +0530, Shyam Shukla wrote:
> Hi All,
>
>
>
> Is there any way to set the value of elements for example ,
> , in axis2.xml at run-time
> programmatically?
You shouldn't need to be even aware of the presence of an axis2.xml file
at runtime- you can change anything at
On Tue, 2006-10-31 at 17:12 +0900, Takahide Nogayama wrote:
>
> Yes, That is right. If we wrote handler which get parser and insert
> filter,
> at the top of handler chain, then we could avoid to change transport
> layer to
> insert filter.
>
> But we can not filter SOAP header part by the ha
[
http://issues.apache.org/jira/browse/AXIS2-1810?page=comments#action_12456204 ]
Gul Onural commented on AXIS2-1810:
---
Based on your example :
- The existing system will have an weather.aar file under let say
"http://localhost/services/v1.0.
[
http://issues.apache.org/jira/browse/AXIS2-1662?page=comments#action_12456205 ]
Deepal Jayasinghe commented on AXIS2-1662:
--
Hi Rajith ;
do you still have the problem , if not pls close the issue.
Thanks
Deepal
> Classloading issues w
Hi Ruchith ;
I dont know its a problem in my machine , but following security test
case is failing for me.
[ERROR] TEST org.apache.axis2.security.Scenario7Test FAILED
I have attached the error report for your consideration.
Thanks
Deepal
Testsuite: org.apache.axis2.security.Scenario7Test
Tests ru
[ http://issues.apache.org/jira/browse/AXIS2-1608?page=all ]
Deepal Jayasinghe reassigned AXIS2-1608:
Assignee: Deepal Jayasinghe
> SimpleAxis2 server does not call ListerManager.stop();
> --
>
[ http://issues.apache.org/jira/browse/AXIS2-1564?page=all ]
Deepal Jayasinghe reassigned AXIS2-1564:
Assignee: Deepal Jayasinghe
> Incoming SOAPFault on client side flows though InFlow *and* InFaultFlow
>
[ http://issues.apache.org/jira/browse/AXIS2-1564?page=all ]
Deepal Jayasinghe updated AXIS2-1564:
-
Priority: Blocker (was: Critical)
> Incoming SOAPFault on client side flows though InFlow *and* InFaultFlow
> ---
[
http://issues.apache.org/jira/browse/AXIS2-1393?page=comments#action_12456217 ]
Deepal Jayasinghe commented on AXIS2-1393:
--
are we there yet:D
> Both Eclipse or IDEA plugins need to show the same behaviour
> --
Hi,
I checked both the axis2 1.1 tag and the trunk. This file:
org.apache.axis2.deployment.FileSystemConfigurator.FileSystemConfigurator(String,
String)
has a bug in it right there where the repoLocation is determined if it is valid
or not (lines 57-69):
try {
if (repo
Hi George ;
Thanks you for finding this , can you do one more step :) , please
create a JIRA.
Thanks
Deepal
> Hi,
>
> I checked both the axis2 1.1 tag and the trunk. This file:
>
> org.apache.axis2.deployment.FileSystemConfigurator.FileSystemConfigurator(String,
> String)
>
> has a bug in
[ http://issues.apache.org/jira/browse/AXIS2-1835?page=all ]
Deepal Jayasinghe reassigned AXIS2-1835:
Assignee: Deepal Jayasinghe
> return a java.lang.List return a java.lang.IllegalArgumentException: null rcl
> --
JAX-WS Dispatch Payload mode should handle a String that represents no
content
--
Key: AXIS2-1838
URL: http://issues.apache.org/jira/browse/AXIS2-1838
Project: Apache
[ http://issues.apache.org/jira/browse/AXIS2-1838?page=all ]
Rich Scheuerle updated AXIS2-1838:
--
Attachment: patch.txt
Committed to SVN: 483250
> JAX-WS Dispatch Payload mode should handle a String that represents
> no content
> --
[ http://issues.apache.org/jira/browse/AXIS2-1838?page=all ]
Rich Scheuerle resolved AXIS2-1838.
---
Resolution: Fixed
> JAX-WS Dispatch Payload mode should handle a String that represents
> no content
> --
http://issues.apache.org/jira/browse/AXIS2-1839
George Stanchev
From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED]
Sent: Wed 12/6/2006 2:33 PM
To: axis-dev@ws.apache.org
Subject: Re: small problem with FileSystemConfigurator
Hi George ;
Thanks you for finding thi
FileSystemConfigurator doesn't throw AxisFault when failed to find a user
supplied repo or axis2xml location
Key: AXIS2-1839
URL: http://issues.apache.org
[
http://issues.apache.org/jira/browse/AXIS2-1823?page=comments#action_12456237 ]
Glen Daniels commented on AXIS2-1823:
-
This has been fixed on the trunk. The way this would work is as follows:
stub._getServiceClient().setCachingOperationCo
[ http://issues.apache.org/jira/browse/AXIS2-1839?page=all ]
Deepal Jayasinghe reassigned AXIS2-1839:
Assignee: Deepal Jayasinghe
> FileSystemConfigurator doesn't throw AxisFault when failed to find a user
> supplied repo or axis2xml location
>
JAX-WS Need doPriv calls in FactoryFinder
-
Key: AXIS2-1840
URL: http://issues.apache.org/jira/browse/AXIS2-1840
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Reporter: Rich Scheuerle
[ http://issues.apache.org/jira/browse/AXIS2-1840?page=all ]
Rich Scheuerle updated AXIS2-1840:
--
Attachment: patch.txt
Committed to SVN: 483268
> JAX-WS Need doPriv calls in FactoryFinder
> -
>
>
So in taking a look at https://issues.apache.org/jira/browse/AXIS2-653
and also the threads relating to
http://marc.theaimsgroup.com/?l=axis-dev&m=114505970102143&w=2, I'm in
search of a little clarification... can we just remove cleanup() now
that we have flowComplete()? And close 653?
Als
Hi,
I have put down Axis2 1.1 and have found that some things have changed that I
relied on.
AxisService.getFileName use to return a URL to the service. I was able to
acquire resources from my aar or exploded directory bundled with my service.
This method call now returns null. Why?
When y
Duplicate code in OperationClient
--
Key: AXIS2-1841
URL: http://issues.apache.org/jira/browse/AXIS2-1841
Project: Apache Axis 2.0 (Axis2)
Issue Type: Improvement
Components: client-api
Affects
[
http://issues.apache.org/jira/browse/AXIS2-1831?page=comments#action_12456266 ]
Na Wang commented on AXIS2-1831:
Every generated stub and every operation.
Here is the code:
---
try{
org.apa
[
http://issues.apache.org/jira/browse/AXIS2-1402?page=comments#action_12456289 ]
Ajith Harshana Ranabahu commented on AXIS2-1402:
As for the formatting of WSDL and other xml files, I've wrote and included a
XML pretty printer pl
"setenv.sh" can't work well in Cygwin environment
-
Key: AXIS2-1842
URL: http://issues.apache.org/jira/browse/AXIS2-1842
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Components: T
[ http://issues.apache.org/jira/browse/AXIS2-1842?page=all ]
Paladin R. Liu updated AXIS2-1842:
--
Attachment: setenv.sh.diff.gz
diff file for patch.
> "setenv.sh" can't work well in Cygwin environment
> -
Should be fixed now [1]
Thanks,
Ruchith
[1] http://svn.apache.org/viewvc?view=rev&rev=483351
On 12/7/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
Hi Ruchith ;
I dont know its a problem in my machine , but following security test
case is failing for me.
[ERROR] TEST org.apache.axis2.securit
+1
Saminda
On 12/6/06, Paul Fremantle <[EMAIL PROTECTED]> wrote:
Oh I forgot to mention. I'd like us to implement this in Axis2. I
guess we need a property to define whether we use the SOAP1.2 email
binding or this binding.
Paul
On 12/6/06, Paul Fremantle <[EMAIL PROTECTED]> wrote:
> Hi
>
>
[
http://issues.apache.org/jira/browse/AXIS2-1823?page=comments#action_12456307 ]
Sanjiva Weerawarana commented on AXIS2-1823:
Do we really need setCachcingOperationContext()?? When I looked at it I didn't
think there would be any co
Hello,
I'm still stuck with my problem. I suppose the
java.net.SocketTimeoutException is not the real reason that the web
Service fails. But the problem is I don't see any way to find the real
reason.
Is it possible that this is a bug in my axis version or in mod_jk or is
it rather port relate
[
http://issues.apache.org/jira/browse/AXIS2-1834?page=comments#action_12456313 ]
Ali Sadik Kumlali commented on AXIS2-1834:
--
Yes, I would rather look into the real problem. But, AFAIK, SOAP/JMS
implementation is not standardized yet[1]
84 matches
Mail list logo
