[
https://issues.apache.org/jira/browse/AXIS2C-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luis Bilo updated AXIS2C-1283:
--
Attachment: op_ns_uri.diff
Proposed patch.
Improvement for REST. Allows HTTP methods without post
1)reads all http headers from the request and adds them to the msg_ctx, they
were missing. 2)Allows custumized http status and http headers for rest
requests(don't affect soap requests). 3) Adds missing http forbidden definitions
[
https://issues.apache.org/jira/browse/AXIS2C-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luis Bilo updated AXIS2C-1282:
--
Attachment: http_forbidden.diff
apache_http_headers_and_rest_enhancement.diff
Improvement for REST. Allows HTTP methods without post data to have the correct
namespace associated by default. This default associated namespace can be
defined in service.xml for each operation.
I have a need to use axis within an existing system that has it's own
ways of opening/closing/rotating logs and I've found the existing axis
log interfaces to be a bit lacking. I have some patches, but before I
submit a issue in jira I wanted to run the changes past some people to
see if what I'm
[
https://issues.apache.org/jira/browse/AXIS2C-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12644862#action_12644862
]
Peter Bruun-Rasmussen commented on AXIS2C-1272:
---
Quickfix - Change the lines
[
https://issues.apache.org/jira/browse/AXIS2C-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12644862#action_12644862
]
pbr edited comment on AXIS2C-1272 at 11/3/08 4:27 PM:
[
https://issues.apache.org/jira/browse/AXIS2C-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12644885#action_12644885
]
Manjula Peiris commented on AXIS2C-1280:
Eric,
Is this happen with gcc 4.x.x also
[
https://issues.apache.org/jira/browse/AXIS2C-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12644893#action_12644893
]
Dimuthu Gamage commented on AXIS2C-1271:
Hi,
Thanks for the patch. I agree with
wsdl2java generated contains QName( , whihc results in Uexpected sublement
error when client code is executed
---
Key: AXIS2-4116
URL:
[
https://issues.apache.org/jira/browse/AXIS-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12644661#action_12644661
]
Himanshu Arora commented on AXIS-2574:
--
Hi Jochen,
I'm new to patching, I did
[
https://issues.apache.org/jira/browse/AXIS-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12644662#action_12644662
]
Himanshu Arora commented on AXIS-2574:
--
Also, can you please pass me the exact path for
On Mon, Nov 3, 2008 at 8:53 AM, Sanjiva Weerawarana
[EMAIL PROTECTED]wrote:
Hi Jarek,
Hmmm .. good question. I've actually been thinking for a while that the
idea of associating a folder to a specific extension was a mistake. To me
that's very static thinking and its much more convenient to
Hi Jarek,
Hmmm .. good question. I've actually been thinking for a while that
the idea of associating a folder to a specific extension was a mistake.
Nope we are not , you can have all the extensions you want in a single
folder too. for example inside the POJO directory you can have both
we can do some thing like that Jboss does. In Jboss if you want to
deploy a web application either it should be put as .war file or under
a directory of which name ends with .war .
i.e in axis2 point of view either it should be bar.aar file or bar.aar
directory.
In my point of view always
I have read your emails but I did not find an explanation of why you think
we're a shell of what we used to be.
While I of course realize that you have personal issues against me, this
is a community discussion and you should try to keep the conversation
about the community and not about your
Deepal, proposing an improvement is not saying some idea that was
implemented some time ago was bad. That was the best we could do given the
information we had then, but this is about improving things going forward.
There's no need to be defensive about decisions we made many years ago ..
no
Amila Suriarachchi wrote:
we can do some thing like that Jboss does. In Jboss if you want to
deploy a web application either it should be put as .war file or under a
directory of which name ends with .war .
i.e in axis2 point of view either it should be bar.aar file or bar.aar
directory.
Deepal, proposing an improvement is not saying some idea that was
implemented some time ago was bad. That was the best we could do given
the information we had then, but this is about improving things going
forward.
Nope I did not say I am against the improvement what I told was we
should
Thanks for your kind words and sharing of your profound wisdom. Of
course, you are totally right once again
-- dims
On Mon, Nov 3, 2008 at 8:25 AM, Sanjiva Weerawarana
[EMAIL PROTECTED] wrote:
I have read your emails but I did not find an explanation of why you think
we're a shell of what
Hey,
I've been working on this problem and ran into some issues and would
like to get your comments before committing a fix. The
RepositoryListener.findServicesInDirectory() scans the services
directory and tries to deploy service modules (.jar or .aar files)
using ServiceDeployer. But
Hi All ,
Axis2 mailing list used to be a very active and very friendly mailing
list , so let's try to keep that as it is. I would like to request from
everyone , let's not try to use this list for any personal attack.
Whether we agree with someone or not we all try to do something good for
the
[
https://issues.apache.org/jira/browse/AXIS2-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya reassigned AXIS2-4114:
-
Assignee: Nandana Mihindukulasooriya
Problem to retrieve the
Glen,
Was looking at http://wiki.apache.org/ws/FrontPage/Proposals/Axis2TLPProposal
Any thoughts on why leave behind XmlSchema, Neethi, Axiom?
Reasons why:
- Very few people are working on these 3 projects
- Any changes to these 3 projects needs almost immediate changes in Axis2
- We have
Hi devs,
Until recently we used to have commented out blocks of JMS SMTP sample
configurations within axis2.xml. But I do not see these now.
Were these removed on purpose? Or did these get deleted accidentally during
recent transport module relocation? If so shall I add them back?
I want to add a
ok. i agree now.
thanks,
dims
On Mon, Nov 3, 2008 at 10:30 AM, Daniel Kulp [EMAIL PROTECTED] wrote:
On Monday 03 November 2008 10:14:30 am Davanum Srinivas wrote:
Glen,
Was looking at
http://wiki.apache.org/ws/FrontPage/Proposals/Axis2TLPProposal
Any thoughts on why leave behind
Glen
The following page has been changed by GlenDaniels:
http://wiki.apache.org/ws/FrontPage/Proposals/Axis2TLPProposal
RESOLVED, that the Apache Axis2 Project be and hereby
is tasked with the migration and rationalization of the
following Apache Web Services
Sumedha
Until recently we used to have commented out blocks of JMS SMTP
sample configurations within axis2.xml. But I do not see these now.
Were these removed on purpose? Or did these get deleted accidentally
during recent transport module relocation? If so shall I add them back?
I want to add
Asankha,
I agree. But let's let Glen edit the pages based on consensus.
thanks,
dims
On Mon, Nov 3, 2008 at 10:33 AM, Asankha Perera [EMAIL PROTECTED] wrote:
Glen
The following page has been changed by GlenDaniels:
http://wiki.apache.org/ws/FrontPage/Proposals/Axis2TLPProposal
I've given concrete examples if you bothered to read my emails. At
this point, i'll say get lost!
thanks,
dims
On Sat, Nov 1, 2008 at 11:57 PM, Sanjiva Weerawarana
[EMAIL PROTECTED] wrote:
If you want to have a conversation about this topic then you should be ready
to explain your statements.
[
https://issues.apache.org/jira/browse/AXIS2-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12644746#action_12644746
]
Samuel commented on AXIS2-4108:
---
I'm sorry to bother you, but I'm in late for my project. Do
[
https://issues.apache.org/jira/browse/AXIS2-4020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12644710#action_12644710
]
Harinandan Reddy commented on AXIS2-4020:
-
This xml used to handled fine in Axis
[
https://issues.apache.org/jira/browse/AXIS2-4117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
juergen schad updated AXIS2-4117:
-
Attachment: LebenService-2.1.0.1.0.wsdl
wsdl-file
InstantiationError using abstract types
Hi Asankha:
Asankha Perera wrote:
* WS-Commons Transports
The WS-Commons transports should not belong to an Axis2 TLP - as it has
a life of its own and is heavily used by Synapse - probably even more
than by Axis2! Shall I edit the proposal directly to remove this?
Does Synapse
[
https://issues.apache.org/jira/browse/AXIS2-4117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
juergen schad updated AXIS2-4117:
-
Description:
We are using jaxb-databinding and unmarshalling of requests fails during
Daniel Kulp wrote:
On Monday 03 November 2008 10:14:30 am Davanum Srinivas wrote:
Glen,
Was looking at
http://wiki.apache.org/ws/FrontPage/Proposals/Axis2TLPProposal
Any thoughts on why leave behind XmlSchema, Neethi, Axiom?
Because they are used by several other projects that have nothing
[
https://issues.apache.org/jira/browse/AXIS2-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
murali mohan dingari updated AXIS2-4116:
Description:
the generated code contains lot of places QName(,
for example
1)
Using Axis2 (v1.4) with Websphere 6.0.x
---
Key: AXIS2-4118
URL: https://issues.apache.org/jira/browse/AXIS2-4118
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Affects Versions: 1.4
Environment:
So, should all synapse and cxf folks have access to all these
projects? What say you?
-- dims
On Mon, Nov 3, 2008 at 12:11 PM, Glen Daniels [EMAIL PROTECTED] wrote:
Daniel Kulp wrote:
On Monday 03 November 2008 10:14:30 am Davanum Srinivas wrote:
Glen,
Was looking at
I don't think that we should AUTOMATICALLY grant access to every
Synapse/CXF (or Axis2 for that matter, into the future) committer, no.
But I do think the barrier to entry for those folks should be a lot
lower (pretty much if they ask - but I do think there should be a formal
separation).
hDaniel Kulp wrote:
On Monday 03 November 2008 12:46:42 pm Davanum Srinivas wrote:
So, should all synapse and cxf folks have access to all these
projects? What say you?
No. It's still a community and thus the normal meritocracy rules apply.
That said, some of those projects may need a
Sanjiva Weerawarana wrote:
Glen, why do you think Axiom as a TLP is not a good idea?
Not big enough project, not enough of a community around just that, fits
very tightly with Neethi/XmlSchema, etc...
I think you can go too far with factoring, and for me this trips that
sensor.
--Glen
Right. Hopefully the PMC members will take a look at the VOTE
happening on commons-dev@ when they get a minute off the axis-dev
mailing list.
-- dims
On Mon, Nov 3, 2008 at 1:10 PM, Daniel Kulp [EMAIL PROTECTED] wrote:
On Monday 03 November 2008 12:46:42 pm Davanum Srinivas wrote:
So, should
InstantiationError using abstract types
---
Key: AXIS2-4117
URL: https://issues.apache.org/jira/browse/AXIS2-4117
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: databinding
Affects
As simple as Just send a note to [EMAIL PROTECTED] and you will get it... +100
thanks,
dims
On Mon, Nov 3, 2008 at 12:51 PM, Glen Daniels [EMAIL PROTECTED] wrote:
I don't think that we should AUTOMATICALLY grant access to every Synapse/CXF
(or Axis2 for that matter, into the future) committer,
Axis2 GUI wizard shows empty parameters on Service Skeleton Java Bean
Configuration screen
--
Key: AXIS2-4119
URL: https://issues.apache.org/jira/browse/AXIS2-4119
On one hand, given that the transports have been split into several
modules, it makes sense to not activate the less common ones by
default, because it would result in an error when they are not on the
classpath. But I also see your point, Asankha, that if these
transports are on the classpath, it
Glen,
Synapse uses the transport through Axis2. My point of view has always
been that it makes sense to have the transports in a separate project
(- independent release cycle) but that the most natural solution
would be as a subproject of Axis2, so I completely agree with you on
that point.
On Mon, Nov 3, 2008 at 12:51 PM, Glen Daniels [EMAIL PROTECTED] wrote:
I don't think that we should AUTOMATICALLY grant access to every Synapse/CXF
(or Axis2 for that matter, into the future) committer, no. But I do think
+1
the barrier to entry for those folks should be a lot lower (pretty
Glen
* WS-Commons Transports
The WS-Commons transports should not belong to an Axis2 TLP - as it
has a life of its own and is heavily used by Synapse - probably even
more than by Axis2! Shall I edit the proposal directly to remove this?
Does Synapse call these transports directly
Well, the issue in hand is not that complex, we could keep the transports
declarations commented on the axis2.xml there is no harm in keeping them
commented and we need to document the steps required to uncomment those
commented transports.
That is how we had them earlier, for example jms
On Mon, Nov 3, 2008 at 6:55 PM, Deepal jayasinghe [EMAIL PROTECTED] wrote:
we can do some thing like that Jboss does. In Jboss if you want to
deploy a web application either it should be put as .war file or under
a directory of which name ends with .war .
i.e in axis2 point of view
[
https://issues.apache.org/jira/browse/AXIS-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Wiedmann resolved AXIS-2574.
---
Resolution: Fixed
Assignee: Jochen Wiedmann
Applied to the Axis trunk.
Reading an
53 matches
Mail list logo
