I really don't know much about the stream stuff. It SOUNDS like it's doing
something to the class loader or similar to make it not find the proper
package-info.class. My suggestion would be to add the -xjc-npa flag to the
CXF code generation to get all the information moved out of the packa
On Sep 24, 2013, at 3:10 PM, Aki Yoshida wrote:
> maybe this is just a guess, but shouldn't adding those referenced
> schemas to the relevant BP namespace handlers's schema lookup code
> would solve this look up problem? I think those schemas were not
> included there because we don't directly u
Silly me Dan provided the reason in original reply.
I will chase up in our code
Thanks
Jason
Sent from my Android phone
On 25/09/2013 6:55 AM, "Jason Pell" wrote:
> No internet is better than a corporate proxy situation that causes
> internet requests to take a longgg time to timeout. I
No internet is better than a corporate proxy situation that causes internet
requests to take a longgg time to timeout. I had been using the
spring mappings but perhaps I missed some.
Any idea why this shows itself in 2.7.7 and not 2.7.6
Sent from my Android phone
On 25/09/2013 5:11 AM, "A
maybe this is just a guess, but shouldn't adding those referenced
schemas to the relevant BP namespace handlers's schema lookup code
would solve this look up problem? I think those schemas were not
included there because we don't directly use those namespaces in
blueprint.xml.
the relative path pr
Erg…. copy paste apparently cut off the locations.
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.
Ran into this yesterday while trying to diagnose a similar issue with Colm.
It's a result of: https://issues.apache.org/jira/browse/CXF-5181
Apparently there is a complete miss match between Spring and Blueprint in this
regards. If we use full absolute paths, blueprint goes off to the interne
I am aware of the change that we needed to make in the schema lookup
entries for trunk after its api+core packages were refactored.
But I don't know if there was any change in 2.7.x line that can affect
the schema lookup.
regards, aki
2013/9/24 Jason Pell :
> I think this issue is causing hangin
Hi all,
Context:
We are having some troubles with CXF (2.7.5) and xstream on Tomcat 7.
The CXF libraries and xstream used by the webapps are in a common folder.
We've got several webapps that invoke our CXF web services.
We also have a webapp that needs to be initialized on tomcat startup. This
we
