Error AXIS fault message is coming when we test the web services first time
after starting the server.
--
Key: AXIS-2821
URL: https://issues.apache.org/jira
any known workaround? Any help will be highly appreciated.
Thanks
> Axis2 should populate for custom exceptions for POJO services
> ---
>
> Key: AXIS2-3443
> URL: https://issues.apa
hanks & regards.
> -Prabath
>
> shyam shukla wrote:
>
>> Thanks Prabath for your reply.
>> Are you aware of any other framework available to develop SPML based web
>> services?
>>
>> Thanks,
>> Shyam
>>
>> On Wed, Feb 10, 2010 at
There are java libraries that support SPML, you may use such a library
and can write an axis2 module for that...
Thanks & regards.
-Prabath
shyam shukla wrote:
Thanks Prabath for your reply.
Are you aware of any other framework available to develop SPML based
web services?
Thanks,
S
Thanks Prabath for your reply.
Are you aware of any other framework available to develop SPML based web
services?
Thanks,
Shyam
On Wed, Feb 10, 2010 at 12:40 PM, Prabath Siriwardena wrote:
> Hi Shyam;
>
> AFAIK - currently we don't have support for SPML in Axis2.
>
&
Hi Shyam;
AFAIK - currently we don't have support for SPML in Axis2.
Thanks & regards.
-Prabath
shyam shukla wrote:
Hello All,
Does Axis2 support SPML v2.0 (Service Provisioning Markup Language)
based web services?
If yes, then please provide the pointer for the same.
Thanks,
Shyam
Hello All,
Does Axis2 support SPML v2.0 (Service Provisioning Markup Language) based
web services?
If yes, then please provide the pointer for the same.
Thanks,
Shyam
Hi all,
I am not sure if this was asked before - it is pretty trivial but I
cannot find the appropriate thread.
Is there a way to query a remote Axis registry for the services that are
running on it at any given
time? I know you can do that with OSGi registries and of course you can
query
mechanisms for deploying JAX-WS services:
* The service may be packaged and deployed as an AAR, just like any other
service within Axis2. Like with all AARs, a services.xml file containing the
relevant metadata is required for the service to deploy correctly.
* The service may be packaged in a
JAX-WS services can no longer be deployed as AAR
Key: AXIS2-4611
URL: https://issues.apache.org/jira/browse/AXIS2-4611
Project: Axis2
Issue Type: Bug
Components: jaxws
Affects
Hi All,
I have deployed two Axis 2 web services in two different machines in two
different application servers.Service 1 should be served the Service 2 in
the other machine.
How do I resolve the service group issue here and invoke WS2 after WS2 the
other to get the final result?
My Method
Needing some help with HTTP sessions.
When sending a SOAP simple message to Axis2, it create a single HTTP session
to handle the client message, and to handle the client HTTP POST request.
When sending a WSA SOAP message (by Axis2 Java Client), it creates another
http session to handle the WSA so
Hi:
I am trying to test the HA features of Axis2 clustering. I am using Asix2
version 1.4.1.
I have deployed a simple stateless service on two nodes (two OC4J instances on
two machines) that are clustered.
Here is what I see:
If I deactivate a service on one of the nodes using axis2 admin co
Hi Friends,
I am using eclipse WSDL explorer to browser wsdl, till now my
services are without securities now i added securities, so kindly help to
send security infromation like usernametoken etc., using wsdl explorer in
eclipse ide.
Thanks in Advance
---
Siva
--
View
from axis2 to synapse. nhttp
transport has been developed by the synapse community and was in the synapse
code base from its inception.
Some transports were moved out from synapse to axis2-transports but not
vice-versa.
Thanks,
Ruwan
> Axis2 Asynchronouse web services o
tory
.createConfigurationContextFromFileSystem("repo path",
"axis2.xml path");
If you don't want to specify a repository, pass null for the first parameter.
Thanks,
~Isuru
> Axis2 Asynchronouse web services over TLS
> -
>
>
t an error to the effect that "Repository
could not be found". I am assuming that Axis2 was looking for Modules and
Services. Is there a way I can create a copy of the axis2.xml, register my
custom Transport Sender to fulfill my requirement but have axis2.xml point to
the default reposit
en create the
ServiceClient using this configuration context. Add all nhttp libraries into
your client classpath and run it. It should work for you.
Thanks,
~Isuru
[1] http://synapse.apache.org/
> Axis2 Asynchronouse web services over TLS
> -
>
>
Axis2 Asynchronouse web services over TLS
-
Key: AXIS2-4560
URL: https://issues.apache.org/jira/browse/AXIS2-4560
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: kernel
Some Apache Axis related objects are not getting released in our Client
Application which accesses Web Services developed in 1.3
Key: AXIS-2811
Hi Glen,
> 2) Add yourself to the list of project members on the wiki page if you are an
> existing PMC member and would like to be on the new Axis2 PMC
>
By looking at the current wiki, feel like your point was not clear.
Thanks,
Deepal
> Here is my +1 for this proposal.
>
> Thanks,
> --Glen
>
; necessary
>> > as we can still decide what to do about each sub-sub-project
>> > individually
>> > later), I'd like to bring the following proposal up for a VOTE of the
>> > Web
>> > Services PMC. If this passes, I plan to submit this resoluti
step (the promotion of
> > WS-Commons sub-sub-projects to WS subprojects - this isn't really
> necessary
> > as we can still decide what to do about each sub-sub-project individually
> > later), I'd like to bring the following proposal up for a VOTE of the Web
>
t; later), I'd like to bring the following proposal up for a VOTE of the Web
> Services PMC. If this passes, I plan to submit this resolution to the board
> as soon as possible.
>
> http://wiki.apache.org/ws/FrontPage/Proposals/Axis2TLPProposal
>
> Note that I added just the first
that we had proposed a year ago. :)
>> So,
>> > having only altered the page in order to remove a step (the promotion of
>> > WS-Commons sub-sub-projects to WS subprojects - this isn't really
>> necessary
>> > as we can still decide what to do about each sub-sub
+1
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?
From:
Glen Daniels
To:
"gene...@ws.apache.org" , Axis
rojects - this isn't really
> necessary
> > as we can still decide what to do about each sub-sub-project individually
> > later), I'd like to bring the following proposal up for a VOTE of the Web
> > Services PMC. If this passes, I plan to submit this resolut
I'd like to bring the following proposal up for a VOTE of the Web
> Services PMC. If this passes, I plan to submit this resolution to the board
> as soon as possible.
>
> http://wiki.apache.org/ws/FrontPage/Proposals/Axis2TLPProposal
>
> Note that I added just the first few
structure that we had proposed a year ago. :)
>>> So,
>>> having only altered the page in order to remove a step (the promotion of
>>> WS-Commons sub-sub-projects to WS subprojects - this isn't really
>>> necessary
>>> as we can still decide what to
to WS subprojects - this isn't really
>> necessary
>> as we can still decide what to do about each sub-sub-project individually
>> later), I'd like to bring the following proposal up for a VOTE of the Web
>> Services PMC. If this passes, I plan to subm
a VOTE of the Web
Services PMC. If this passes, I plan to submit this resolution to the board
as soon as possible.
http://wiki.apache.org/ws/FrontPage/Proposals/Axis2TLPProposal
Note that I added just the first few people in the current PMC roster as
examples. I also nominated myself as the Axis2
> later), I'd like to bring the following proposal up for a VOTE of the Web
> Services PMC. If this passes, I plan to submit this resolution to the
> board
> as soon as possible.
>
> http://wiki.apache.org/ws/FrontPage/Proposals/Axis2TLPProposal
>
> Note that I
27;t really necessary
> as we can still decide what to do about each sub-sub-project individually
> later), I'd like to bring the following proposal up for a VOTE of the Web
> Services PMC. If this passes, I plan to submit this resolution to the
> board
> as soon as possible.
dl, while the inherited operation guardaPersona is missing
> axis2 deployment failure for web services proxied by Spring
> ---
>
> Key: AXIS2-4538
> URL: https://issues.apache.or
you have to provide a java interface for
"ServiceClass" parameter then you will not get these exceptions. please see the
following post [1] and try for that.
[1] - http://ssagara.blogspot.com/2008/08/axis2-with-spring-aop.html
> axis2 deployment failure for web services
axis2 deployment failure for web services proxied by Spring
---
Key: AXIS2-4538
URL: https://issues.apache.org/jira/browse/AXIS2-4538
Project: Axis 2.0 (Axis2)
Issue Type: Bug
I would like to expose some of my web services under services/admin/ and some
under services/public/ Is there any way for me to do this? I want to do this
so that I can associate different Tomcat Security Constraints with each
directory so that I can have one set automatically forward the
[
https://issues.apache.org/jira/browse/AXIS2-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Thaker closed AXIS2-4507.
> Axis2 Modules and Services do not Shutd
[
https://issues.apache.org/jira/browse/AXIS2-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Thaker resolved AXIS2-4507.
--
Resolution: Fixed
Fixed with revision 818290.
> Axis2 Modules and Services do not Shutd
and Services do not Shutdown.
> ---
>
> Key: AXIS2-4507
> URL: https://issues.apache.org/jira/browse/AXIS2-4507
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
>
[
https://issues.apache.org/jira/browse/AXIS2-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on AXIS2-4507 started by Nikhil Thaker.
> Axis2 Modules and Services do not Shutdown.
> ---
>
>
Axis2 Modules and Services do not Shutdown.
---
Key: AXIS2-4507
URL: https://issues.apache.org/jira/browse/AXIS2-4507
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: jaxws
ing always with Axis2 1.5, even with the fix
for issue AXIS2-4209.
> catalog resolution doesn't work for schema references used by JAX-WS services
> -
>
> Key: AXIS2-4494
>
catalog resolution doesn't work for schema references used by JAX-WS services
-
Key: AXIS2-4494
URL: https://issues.apache.org/jira/browse/AXIS2-4494
Project: Axis 2.0 (
4 AM:
---
Attaching the patch I described in my previous comment.
was (Author: mauromol):
The patch I described in my previous comment.
> Allow for sharing XSD schemas between services
> --
>
> Key: AXIS2-3354
>
XSD schemas between services
> --
>
> Key: AXIS2-3354
> URL: https://issues.apache.org/jira/browse/AXIS2-3354
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
>Af
xis2 1.5 things work in the following way.
Suppose I have MyService1 and MyService2 deployed as such:
contextpath/WEB-INF/services/MyService1/META-INF/
contextpath/WEB-INF/services/MyService2/META-INF/
and suppose both MyService1.wsdl and MyService2.wsdl import a schema called
CommonSchema.xsd pl
vice, rows 1247-1249, requests with ".." in
the URL are filtered out: this is why the workaround I described and that we
were using is not working in Axis2 anymore.
Is there a particular reason for this change?
> Allow for sharing XSD schemas
is a dirty trick, because we can't know at
design/deployment time what will be the full URL where the webapp (containing
WSDLs and XSDs) will be located.
> Allow for sharing XSD schemas between services
> --
>
>
workaround of
putting the shared XSD schema in both WEB-INF and WEB-INF\services (so that it
is eventually found in one of the two places where the XSD is referred to as
../../MyXSD.xsd) does not work anymore. A 404 is always given when I query the
AxisServlet for MyService?xsd=../../MyXSD.xsd
> Allow for sharing XSD schemas between services
> --
>
> Key: AXIS2-3354
> URL: https://issues.apache.org/jira/browse/AXIS2-3354
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
red the changes made when improving Faulty Services handling.
>
>
> Key: AXIS2-4289
> URL: https://issues.apache.org/jira/browse/AXIS2-4289
> Project: Axis 2.0 (Axis2)
>
the transportReceiver from
axis2.xml (and letting AxisServlet add its own TransportInDescription) doesn't
work either because of AXIS2-4141.
> Axis2 1.5 not compatible with Eclipse JST Web Services
> --
>
>
xis2.transport.http.AxisServlet.init(AxisServlet.java:444)
at org.apache.axis2.webapp.AxisAdminServlet.init(AxisAdminServlet.java:60)
It seems that JST excludes geronimo-ws-metadata_2.0.spec from the JARs copied
to the Web app.
> Axis2 1.5 not compatible with Eclipse JST Web S
Axis2 1.5 not compatible with Eclipse JST Web Services
--
Key: AXIS2-4464
URL: https://issues.apache.org/jira/browse/AXIS2-4464
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Affects
the handler, it can check whether it is engaged to
that by using message context.
Second if you put your handlers after the dispatch phase then that module will
be engaged to the service that you are trying to engage
> A module in the module folder works on al s
odule folder works on al services
> --
>
> Key: AXIS2-3852
> URL: https://issues.apache.org/jira/browse/AXIS2-3852
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Componen
.
*
)
> A module in the module folder works on al services
> --
>
> Key: AXIS2-3852
> URL: https://issues.apache.org/jira/browse/AXIS2-3852
> Projec
onic transmission.
*
> A module in the module folder works on al services
> --
>
> Key: AXIS2-3852
> URL: https://issues.apache.org/jir
27;ve got set for just one
of my services in service.xml, but it's getting applied to all the services in
axis2 including the version service. There seems to be no way to engage a
module for just one service.
> A module in the module folder wor
Wrapped array schema generation is not supported for document literal bare
services
---
Key: AXIS2-4442
URL: https://issues.apache.org/jira/browse/AXIS2-4442
Project
I am using axis2-1.5, and I see this exception trace when tomcat starts up with
our application as a war file.
Note however that I don't see this problem when starting tomcat with the
exploded archive, so it is perhaps a problem with
WarBasedAxisConfigurator.loadServices() ?
Jul 17, 2009 2:21:5
axis sends soap messages on error in http binded services
-
Key: AXIS2-4427
URL: https://issues.apache.org/jira/browse/AXIS2-4427
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Affects
Hi all,
This is regarding the JIRA that I've filed at..
https://issues.apache.org/jira/browse/AXIS2-4417
In JAXWS services, body and header parts are kept as
org.apache.axis2.jaxws.message.impl.BlockImpl objects. These message blocks
are read before invoking the service and all are s
"Block already consumed" error in JAXWS services
Key: AXIS2-4417
URL: https://issues.apache.org/jira/browse/AXIS2-4417
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Compone
-sample.jar
> "Block already consumed" error in JAXWS services
>
>
> Key: AXIS2-4417
> URL: https://issues.apache.org/jira/browse/AXIS2-4417
> Project: Axis 2.0 (Axis2
[
https://issues.apache.org/jira/browse/AXIS2-4407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suchitha Koneru updated AXIS2-4407:
---
Description:
Configuration
Tomcat 5.5
Axis 2 Version 1.5
Java 1.6.10
Restful services were
[
https://issues.apache.org/jira/browse/AXIS2-4407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suchitha Koneru updated AXIS2-4407:
---
Attachment: services.zip
services folder(WEB-INF/services)
> Axis 2 does not pick
ude whttp:location
> and whttp:method for Restful services
>
>
> Key: AXIS2-4407
> URL: https://issues.apache.org/jira
Axis 2 does not pick up wsdl2.0 which is modified to include whttp:location and
whttp:method for Restful services
Key: AXIS2-4407
URL: https
[
https://issues.apache.org/jira/browse/AXIS2-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Scheuerle resolved AXIS2-4391.
---
Resolution: Fixed
Second Revision:786126
> JAX-WS: Two Services Cannot Have the Same N
will prevent the different threads from using the same name.
I am working on the final testing of the fix.
> JAX-WS: Two Services Cannot Have the Same Name Error
>
>
> Key: AXIS2-4391
>
[
https://issues.apache.org/jira/browse/AXIS2-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen updated AXIS2-4391:
---
Fix Version/s: 1.6
> JAX-WS: Two Services Cannot Have the Same Name Er
[
https://issues.apache.org/jira/browse/AXIS2-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Scheuerle resolved AXIS2-4391.
---
Resolution: Fixed
Committed 785748
> JAX-WS: Two Services Cannot Have the Same Name Er
JAX-WS: Two Services Cannot Have the Same Name Error
Key: AXIS2-4391
URL: https://issues.apache.org/jira/browse/AXIS2-4391
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components
serviceName', is null it just grabs the
first service from the WSDL with a Port, which is not the right one.
> If WSDL has multiple services, DeploymentEngine uses incorrect one
> --
>
>
your patch, but seems like there are test failures so please
re-create the patch.
Thanks,
Deepal
> NPE in OutFaultFlow - when accesing a service having a security policy
> applied - from a client with a no binding specific epr [i.e.
> http://localhost:8080/axis2/services/
and your service name (in the services.xml)
match then the right thing happen.
Thanks,
Deepal
> If WSDL has multiple services, DeploymentEngine uses incorrect one
> --
>
> Key: AXIS2-4362
>
[
https://issues.apache.org/jira/browse/AXIS2-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Reif updated AXIS2-4362:
Description:
We have a WSDL file that defines multiple services. Each service is deployed
within a War as
If WSDL has multiple services, WarBasedAxisConfigurator uses incorrect one
--
Key: AXIS2-4362
URL: https://issues.apache.org/jira/browse/AXIS2-4362
Project: Axis 2.0 (Axis2
Hi Glen,
> Throwing an exception to do this is (IMHO) bad code. It's expensive, slower,
> non-intuitive (what would you expect "getService()" to do?) and just plain
> annoying for people calling this method.
>
Well inactive service treat as same as service is not there in the
system. So I do n
Hi Deepal:
Deepal jayasinghe wrote:
> Yes, there is a difference. One method is for management other method is
> for dispatching.
> So at the runtime when a message receive we call getService, and if we
> want to activate, inactivate we call other method.
Throwing an exception to do this is (IMHO
Yes, there is a difference. One method is for management other method is
for dispatching.
So at the runtime when a message receive we call getService, and if we
want to activate, inactivate we call other method.
So please do not remove the method.
Deepal
> Hi y'all:
>
> So I'm cleaning up a littl
Hi Guys,
I am trying to deploy an annotated POJO class like this one :
...
@WebMethod(operationName = "querySpace")
String[] query(String space, String query) throws SpaceException;
@WebMethod(operationName = "query")
String[] query(String query) throws SpaceException;
..
There
Hi y'all:
So I'm cleaning up a little code and javadoc, and happened to come across
AxisConfiguration.getService()... which *throws an Exception* if you ask for
an inactive service.
...which is why we have a second method called "getServiceForActivation()"
that simply avoids the check and the exc
[PLEASE KEEP REPLIES TO THIS THREAD ON "gene...@ws". If you're not on it and
interested, please subscribe.]
Hi all:
June approaches, and with it another WS PMC board report. After the March
report, we were again asked by the board what's up with our project's
organization. As such, I'd like to
was that jaxws-tools.jar and tools.jar
from JDK were missing from my tomcat classpath. The fix was to copy them to
$TOMCAT_HOME/shared/lib in my case.
I have used POJODeployer and I have not used service.xml.
Regards,
Balint
> JSR 181 annotations web services giving
the changes made when improving Faulty Services handling.
>
>
> Key: AXIS2-4289
> URL: https://issues.apache.org/jira/browse/AXIS2-4289
> Project: Axis 2.0 (Axis2)
>
Refactored the changes made when improving Faulty Services handling.
Key: AXIS2-4289
URL: https://issues.apache.org/jira/browse/AXIS2-4289
Project: Axis 2.0 (Axis2)
Issue
> Test Cases for the Improvements to Axis2 Faulty Services Handling
> -
>
> Key: AXIS2-4286
> URL: https://issues.apache.org/jira/browse/AXIS2-4286
> Project: Axis 2.0 (Axis2)
>
> Improvements to Axis2 Faulty Services Handling
> --
>
> Key: AXIS2-4281
> URL: https://issues.apache.org/jira/browse/AXIS2-4281
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
Test Cases for the Improvements to Axis2 Faulty Services Handling
-
Key: AXIS2-4286
URL: https://issues.apache.org/jira/browse/AXIS2-4286
Project: Axis 2.0 (Axis2)
Issue Type
-2009-01.txt
Patches are attached
> Test Cases for the Improvements to Axis2 Faulty Services Handling
> -
>
> Key: AXIS2-4286
> URL: https://issues.apache.org/jira/browse/AXIS2-4286
>
[
https://issues.apache.org/jira/browse/AXIS2-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sameera Jayasoma updated AXIS2-4281:
Attachment: patch-axis2-trunk-22-03-2009-03.txt
> Improvements to Axis2 Faulty Servi
[
https://issues.apache.org/jira/browse/AXIS2-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sameera Jayasoma updated AXIS2-4281:
Attachment: patch-axis2-trunk-22-03-2009-03.txt
> Improvements to Axis2 Faulty Servi
lty Services Handling
> --
>
> Key: AXIS2-4281
> URL: https://issues.apache.org/jira/browse/AXIS2-4281
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components:
Hi devs,
Following jira contains the patches for this improvement.
https://issues.apache.org/jira/browse/AXIS2-4281
Thanks
Sameera
--
Sameera Jayasoma
Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://tech.jayasoma.org
-2009-02.txt
patch-axis2-trunk-22-03-2009-01.txt
Attached the patch files.
> Improvements to Axis2 Faulty Services Handling
> --
>
> Key: AXIS2-4281
> URL: https://issues.apache.org/jira/br
: nightly
> Improvements to Axis2 Faulty Services Handling
> --
>
> Key: AXIS2-4281
> URL: https://issues.apache.org/jira/browse/AXIS2-4281
> Project: Axis 2.0 (Axis2)
> Is
Improvements to Axis2 Faulty Services Handling
--
Key: AXIS2-4281
URL: https://issues.apache.org/jira/browse/AXIS2-4281
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Reporter
1 - 100 of 749 matches
Mail list logo
