Probably we are already going too far into implementation details. I
think that the project would have 3 parts:
1. Establishing the general (implementation independent) framework:
- Define protocols: SOAP headers, but also mappings to HTTP headers
(for REST) and JMS properties.
- Define the struc
On Tue, Mar 30, 2010 at 15:11, Glen Daniels wrote:
> I'm a really terribly inconsistent blogger. However, my last actual entry,
> from 2009, was about exactly this:
>
> http://glendaniels.blogspot.com/2009/03/debugging-multi-hop-soa-interactions.html
That comes pretty damn close to what I was th
Hello Everyone,
First let me thank all of you for your valuable inputs.
Now let me ask few questions to make sure that I understood the
suggested approach correctly.
- What are the components that you meant by 'Components who call
RemoteLogger.log()' ? A Custom Message Receiver which logs the
m
[
https://issues.apache.org/jira/browse/AXIS2-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Scheuerle resolved AXIS2-4669.
---
Resolution: Fixed
> JAX-WS: SAAJConverter does not preserve attribute type information
>
JAX-WS: SAAJConverter does not preserve attribute type information
--
Key: AXIS2-4669
URL: https://issues.apache.org/jira/browse/AXIS2-4669
Project: Axis2
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AXIS2-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Scheuerle resolved AXIS2-4668.
---
Resolution: Fixed
> JAX-WS: Error indicating Duplicate @XmlType when using JAX-WS webmethods
[
https://issues.apache.org/jira/browse/AXIS2-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Scheuerle updated AXIS2-4668:
--
Description:
Background:
The JAX-WS runtime builds a JAXBContext to control the marshaling and
JAX-WS: Error indicating Duplicate @XmlType when using JAX-WS webmethods with
@JAXB data objects
Key: AXIS2-4668
URL: https://issues.apache.org/jira/browse/AXIS2-4668
[
https://issues.apache.org/jira/browse/AXIS2-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Scheuerle updated AXIS2-4667:
--
Summary: JAX-WS:NullPointerException in MethodMarshalerUtils (was:
JAX-W:NullPointerException
[
https://issues.apache.org/jira/browse/AXIS2-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Scheuerle resolved AXIS2-4667.
---
Resolution: Fixed
Committed Revision 928871
> JAX-W:NullPointerException in MethodMarshalerU
I'm a really terribly inconsistent blogger. However, my last actual entry,
from 2009, was about exactly this:
http://glendaniels.blogspot.com/2009/03/debugging-multi-hop-soa-interactions.html
I like Andreas' suggestion below, but I think it might be a bit heavyweight
for a GSoC project(?). Mayb
[
https://issues.apache.org/jira/browse/AXIS2-4662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851383#action_12851383
]
Stephan van Hugten commented on AXIS2-4662:
---
After some tinkering I have come up
[
https://issues.apache.org/jira/browse/AXIS2-4662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851383#action_12851383
]
Stephan van Hugten edited comment on AXIS2-4662 at 3/30/10 1:00 PM:
-
[
https://issues.apache.org/jira/browse/AXIS2-4662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851366#action_12851366
]
Stephan van Hugten commented on AXIS2-4662:
---
It's good that you take the bigger s
That runtime monitoring / correlation is what the WSO2 Business Activity
Monitor does / is for ...
See: http://wso2.com/products/business-activity-monitor/
Sanjiva.
On Tue, Mar 30, 2010 at 2:27 PM, Andreas Veithen
wrote:
> I was actually referring to scenarios where a service may call other
> s
[
https://issues.apache.org/jira/browse/AXIS2-4662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851359#action_12851359
]
Andreas Veithen commented on AXIS2-4662:
Stephan,
I've combined your code with PoC
Hello,
We developed a Web Services project server with WebSphere Application Server
6.1 to generate the beans.
We secured the messages according to the standard OASIS Web Services Security :
SOAP Message Security 1.0 (Integrity + Authentication with X509 certificate).
The client is gener
I was actually referring to scenarios where a service may call other
services, which in turn may call again other services. In these
scenarios, it is not sufficient to simply collect received/sent
messages on different hosts, unless the system is isolated
(development environment) or the request ra
Hi Nilupa;
When we collect messages from a one location by installing proper
handler that will intercept and send messages to to that one location
(this one location can be a single server, pub/sub channel etc). There
is many ways to make sense of those collected messages. What Andreas
mentioned (
19 matches
Mail list logo
