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 <ja...@pellcorp.com>: > I think this issue is causing hanging of startup of my application. I am > reverting to 2.7.6. > > I will debug and try to figure out what is wrong and raise a jira + fix if > possible. > > Any info anyone of the devs may have though would be appreciated. > > I am running with spring 3.1 and embedded jetty with WS policy username > password with with java first > > Sent from my Android phone > On 24/09/2013 2:49 PM, "Jason Pell" <jp...@apache.org> wrote: > >> Hi, >> >> I upgraded our environment to use 2.7.7 and immediately upon deployment I >> started getting the following error: >> >> org.xml.sax.SAXParseException; systemId: >> http://www.w3.org/2007/02/ws-policy.xsd; lineNumber: 30; columnNumber: >> 69; schema_reference.4: Failed to read schema document >> 'oasis-200401-wss-wssecurity-secext-1.0.xsd', because 1) could not find the >> document; 2) the document could not be read; 3) the root element of the >> document is not <xsd:schema>. >> >> this looks like perhaps there is a spring schemas mapping missing? >> >> I have lowered the logging for now so that I don't see the WARN, but >> wondered if anyone was aware why I would be seeing this now. >> >> I am behind a firewall, but I was behind a firewall in 2.7.6 and did not >> see this message in the logs. >> >> Thanks for any info you might have >>
