[
https://issues.apache.org/jira/browse/AXIS2-4650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843447#action_12843447
]
Amila Chinthaka Suriarachchi commented on AXIS2-4650:
-
can you attach a
On Wed, Mar 10, 2010 at 11:05 AM, Demetris wrote:
>
> Hi all,
>
> I am not sure if this was asked before but can Axis2 be queried for a
> list of the
> services (SOAP) that are currently deployed on it?
>
http://localhost:8080/axis2/services/listServices
Amila.
>
> Thanks
>
> ---
Hi all,
I am not sure if this was asked before but can Axis2 be queried for
a list of the
services (SOAP) that are currently deployed on it?
Thanks
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additi
On Tue, Mar 9, 2010 at 8:01 PM, Sagara Gunathunga <
sagara.gunathu...@gmail.com> wrote:
>
>
> On Tue, Mar 9, 2010 at 6:37 PM, Amila Suriarachchi <
> amilasuriarach...@gmail.com> wrote:
>
>>
>>
>> On Tue, Mar 9, 2010 at 3:45 PM, Sagara Gunathunga <
>> sagara.gunathu...@gmail.com> wrote:
>>
>>>
>>>
On Tue, Mar 9, 2010 at 7:40 PM, Deepal jayasinghe wrote:
> Amila,
>
> MessageContext.getCurrentMessageContext() only work at Server side and
> only after MessaeReceiver, so you cannot use this at the client side.
>
At client side any way ListnerManager.defaultConfigurationContext is null.
Pleas
The issue is still open and I can see the same leak with a snapshot
build. The scripting module allows you to deploy Web services
implemented using Javascript and other scripting languages. This
should actually be implemented as a custom deployer, but (for
presumably historical reasons) it was desi
WSDL20AxisServiceBuilder overwrites operations in bindingoperation property map.
Key: AXIS2-4651
URL: https://issues.apache.org/jira/browse/AXIS2-4651
Project: Axis2
[
https://issues.apache.org/jira/browse/AXIS2-4650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitor Manuel Alves Rodrigues updated AXIS2-4650:
Description:
Hello everyone,
I have this snippet from the WSDL:
.
BAD WSDL generation from Java class
---
Key: AXIS2-4650
URL: https://issues.apache.org/jira/browse/AXIS2-4650
Project: Axis2
Issue Type: Bug
Environment: OS: Debian GNU/Linux
WSO2 WSAS v3.1.3
Yes.. It happened last week.. You'll hear back soon.
thanks,
Thilina
On Mon, Mar 8, 2010 at 10:55 AM, Nadir Amra wrote:
> I am just wondering if the batch vote for previous committers ever
> happened?
>
> Nadir Amra
> Integrated Web Services for IBM i Operating System
> Internet: a...@us.ibm.co
On Tue, Mar 9, 2010 at 6:37 PM, Amila Suriarachchi <
amilasuriarach...@gmail.com> wrote:
>
>
> On Tue, Mar 9, 2010 at 3:45 PM, Sagara Gunathunga <
> sagara.gunathu...@gmail.com> wrote:
>
>>
>>
>> On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
>> amilasuriarach...@gmail.com> wrote:
>>
>>>
>>
hi,
The ListnerManager.defaultConfigurationContext is used as an easy way to
access the configuration context object within any place of the Axis2
container. But this would cause some security issues if we try to run
multiple Axis2 instances in a single JVM. (For an example using Axis2 in an
Mult
Andreas,
After removing scripting module, the error is gone. Is this bug is fixed in
Axis2 1.5.1? and what exactly we can do with scripting module?
Thanks a lot.
Chinmoy
On Tue, Mar 9, 2010 at 5:06 PM, Andreas Veithen
wrote:
> Chinmoy,
>
> This could be related to AXIS2-4263. Can you try the
Amila,
MessageContext.getCurrentMessageContext() only work at Server side and
only after MessaeReceiver, so you cannot use this at the client side.
And also we cannot assume that user is going to invoke with a
MessageContext when he use ServiceClient APIs (I agree in the case of
OperationClient it
Please ignore my previous mail...the error occurs with jdk 1.5 alsoI
guess it's Axis2 issue...
On Tue, Mar 9, 2010 at 3:28 PM, Chinmoy Chakraborty wrote:
> Andreas,
>
> One more observation : Currently I am running tomcat 6.0.24 with jdk 1.6
> but I do not get this error if I use jdk 1.5 wi
Amila,
At the client side when you create the ServiceClient inside a service
(let's say inside Tomcat) we use this approach to get the server's
configuration context. There are some other instances also, however I
cannot remember all of them now. I strongly suggest you to find an
alternative appro
On Tue, Mar 9, 2010 at 3:45 PM, Sagara Gunathunga <
sagara.gunathu...@gmail.com> wrote:
>
>
> On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
> amilasuriarach...@gmail.com> wrote:
>
>>
>>
>> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen <
>> andreas.veit...@gmail.com> wrote:
>>
>>> I also
Chinmoy,
This could be related to AXIS2-4263. Can you try the workaround(s)
proposed in that issue?
Andreas
On Tue, Mar 9, 2010 at 10:46, Chinmoy Chakraborty wrote:
> Andreas,
> Following is the report I got after stopping our app:
>
> /arit-war-0.1
>
> Thread, target=org.apache.tomcat.util.net
My proposal (to add an extension point to ServiceDeployer to allow
JAX-WS to inject AxisService descriptions built from JAX-WS
annotations) has the following advantages:
* The familiar services.xml syntax applies. No new descriptor formats
or annotations are necessary.
* No need for a new deployer;
On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
amilasuriarach...@gmail.com> wrote:
>
>
> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen > wrote:
>
>> I also created a proof-of-concept [1] that shows the feasibility of
>> the services.xml based approach that I suggested in AXIS2-4611. It
>
Andreas,
One more observation : Currently I am running tomcat 6.0.24 with jdk 1.6 but
I do not get this error if I use jdk 1.5 with the same version of tomcat. In
the previous report we saw there were two classes under DEFUNCT head and
both the classes extends TimerTask.
Could it be an issue with
Andreas,
Following is the report I got after stopping our app:
/arit-war-0.1
- Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
- Timer thread; tasks:
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
- Timer thread; tasks: labware.util.ResourceMonitor
Chinmoy,
The important test is actually to get the arit report after stopping
the Axis2 application. This will really show the leaked resources
(under ""). Can you do this and post the result?
Andreas
On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty wrote:
> Amila,
> Still I get the error afte
Amila,
Still I get the error after switching off following parameter:
false
false
Andreas,
I get following report when I tried *http://localhost:8080/arit-war-0.1/* :
/arit-war-0.1
Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
/web3_dev_1209 (this is our app)
Timer thread
24 matches
Mail list logo
