Hi,
I am trying to process attachments in my web service. I access it like this:
MessageContext msgCtx = context.getMessageContext();
Map attachments = (Map)msgCtx.get(
MessageContext.INBOUND_MESSAGE_ATTACHMENTS
);
InputStream is = null;
// assuming I always get a single atta
What does your client code look like? Caching only works for the same
client proxy. If you are closing the proxy, or else creating a new one,
then the cached SecurityContextToken will not be retrieved. If you are
re-using the same client proxy, then the SecurityContextToken should be
retrieved from
It indeed worked by creating a factory bean for each service, so according to
my example:
JaxWsServerFactoryBean srvBean = new JaxWsServerFactoryBean();
srvBean.setBus(getBus());
srvBean.setAddress("/legacyService1");
srvBean.setServiceBean(new SoapDispatcherServiceImpl("legacyService1"));
> On Jun 23, 2015, at 1:00 AM, ellen wrote:
>
> Hi Dear all,
>
> I would like to use ws-polciy in my project.
>
> I see I can state this policy is: wsp:Optional or wsp:Ignorable.
>
> But are these attributes Case sensitive?
Yes. They are defined in the schema for ws-policy and thus would h
I have a situation where I'd like a @PathParam to be optional. For example
I'd like for the path /{tenant}/resource/{id} to be matched for both
.../myTenant/resource/12345 and .../resource/12345, the second case passing
in null for the tenant @PathParam.
I did some research and it seemed like usi
I tend to prefer solutions to things like this that will be obviously
understood when I pass responsibility for the code on to someone else in
the future, especially if that person is (like me) not particularly fluent
at regexp syntax :-). How about just going for two resource methods with
individ
That is my fallback plan and isn't that much extra work. Was just wanting
to see if JAX-RS had a way to help with it.
On Tue, Jun 23, 2015 at 6:22 PM, Craig McClanahan
wrote:
> I tend to prefer solutions to things like this that will be obviously
> understood when I pass responsibility for the
Realistically in REST, path params are never optional. What you're trying
to do is bind the same service to two different URIs. This might be a
reason why you want to use sub resources to do the implementation.
Assuming you have some wrapper level around this, adding these two methods
should wor
We have Basic Authentication working for the dynamic client with user &
password,
But have not been able to figure out how to set Host, Port, and Realm.
Our current code is similar to below:
HTTPConduit httpc = (HTTPConduit) client.getConduit();
AuthorizationPolicy authorizationPolicy = new Aut
