Will there be a 3.1.12 early jun? Since last was early April. ..
the code that actually does
the Mtom encoding
Anything additional you can assist me to pinpoint would be appreciated
On 22 Mar 2016 4:00 am, "Daniel Kulp" wrote:
>
> > On Mar 20, 2016, at 7:57 PM, Jason Pell wrote:
> > I wanted to be able to turn MTOM on and off ba
by looking at the service model itself. Any initial guidance
for where I should start would be appreciated.
Regards
Jason
http://cxf.apache.org/cxf-313-release-notes.html
On Fri, Sep 18, 2015 at 4:42 PM, Sobkowiak Krzysztof <
krzys.sobkow...@gmail.com> wrote:
> Hi
>
> For the 3.0.x and 2.x releases you have always provided a release notes
> page like this https://cxf.apache.org/cxf-306-release-notes.html. I would
>
+1 (non binding)
On Thu, Jul 30, 2015 at 11:26 PM, Aki Yoshida wrote:
> +1
>
> aki
>
> 2015-07-27 21:26 GMT+02:00 Alessio Soldano :
> > This is a vote to release 2.7.17. It’s been over 2 months since the last
> > release and we’ve fixed more than 18 issues.
> >
> > Staging area:
> > 2.7.17:
> >
+1 (non binding)
On Wed, Jul 29, 2015 at 11:24 PM, Colm O hEigeartaigh
wrote:
> +1.
>
> Colm.
>
> On Wed, Jul 29, 2015 at 11:18 AM, Alessio Soldano
> wrote:
>
> > +1
> >
> > Thanks
> > Alessio
> >
> > On 28/07/15 20:13, Daniel Kulp wrote:
> >
> >> This is a vote to release 3.0.6 and 3.1.2. We
Ok I feel stupid.
seems another developer on my team added another spring context loader
which generated the premature event
Please ignore my last 2 emails :-(
On 18/06/2015 10:29 AM, "Jason Pell" wrote:
> after further interrogation of the code the start should have been ca
after further interrogation of the code the start should have been called
before spring finished loading
My issue is the ServerRegistry does not contain all the jaxws:endpoints
when the spring application listener fires.
Anyone got any thoughts as to why?
On 18/06/2015 9:30 AM, "Jason
Hi,
As part of starting up my application I want to know when all services have
started. Unfortunately in the case of cxf, the Endpoints have all been
created by the time I get the ApplicationListener
but the servers may actually still be starting.
It would be useful to register a ServerLifeCycl
+1 (non binding)
On 08/06/2015 2:16 AM, "Sergey Beryozkin" wrote:
> +1
>
> Cheers, Sergey
> On 05/06/15 21:49, Daniel Kulp wrote:
>
>> 3.1.1 fixes a bunch of issues in 3.1.0 that would prevent it from working
>> properly in several normal use cases, particularly in OSGi.
>>
>> Staging area:
>> ht
Hi,
If MTOM is enabled, its enabled for all operations, even those which have
no need for it. Is this part of the standard, or would it be possible to
be smarter about when to enable it?
Ideally only operations that accept / return attachments should have MTOM
enabled (at least if this particula
Can you try this on 2.7.15 or 3.0.4?
I don't know why your issue is occurring but a more up to date cxf might
have already fixed it.
Would be good to know
On 25/03/2015 6:17 AM, "Balana, Vishal"
wrote:
> I am giving example below about how I have added wsse header to wsdl:
>
>targetNamespac
Hi Daniel,
How did you go with getting cxf to support the latest checkstyle? Are we
still limited to older than 6.2?
On Sat, Feb 7, 2015 at 8:09 AM, Daniel Kulp wrote:
> Just a warning to the CXF devs: don’t update your eclipse plugin for
> check style. The new version is very incompatible
le to expect 2.7.x to be closed sometime
> later this year, that means to have only a few more releases on 2.7.x.
>
> Maybe we can already mention in the 2.7.15 release note that there
> will be only a few more releases planned (2~3).
>
>
> 2015-02-15 23:15 GMT+01:00 Jason Pell :
> &
t; CXF. Java 7 reaches the end of life in two months. I agree things are
> changing at a much slower rate in the productions. But starting planning
> for a Java 8 trunk is better be done earlier than later :-)
>
> Sergey
>
>
> On 13/02/15 22:32, Jason Pell wrote:
>
>> By
By customers I don't mean my companies customers, I mean users of cxf 2.7
On Sat, Feb 14, 2015 at 9:30 AM, Jason Pell wrote:
> From a purely selfish point of view, I hope that 2.7 end of life is
> announced well in advance, as a lot of customers will have to migrate to
> 3.x.
>
>From a purely selfish point of view, I hope that 2.7 end of life is
announced well in advance, as a lot of customers will have to migrate to
3.x.
On Sat, Feb 14, 2015 at 4:20 AM, Sergey Beryozkin
wrote:
> Hi All,
>
> We've had a brief chat with Dan earlier about the possibility of
> introducing
+1 non binding.
On Fri, Feb 13, 2015 at 1:31 AM, Aki Yoshida wrote:
> But this org.apache.aries.blueprint.reflect is available from
> org.apache.aries.blueprint.core.compatibility, so it isn't a problem
> of CXF, no?
>
> karaf@root()> exports | grep org.apache.aries.blueprint.reflect
>
> org.apa
awesome thanks
On Tue, Feb 10, 2015 at 9:06 PM, Aki Yoshida wrote:
> Hi Jason,
> yes. We had this issue that was caused by some inconsistency with
> jetty8 and jetty9 wiring and it was fixed yesterday.
> regards, aki
>
> 2015-02-06 23:05 GMT+01:00 Jason Pell :
> > Sorry
TPFromWebSocketEndpoint:229
» ServiceUnavailable
JAXRSClientServerWebSocketSpringWebAppTest>JAXRSClientServerWebSocketTest.testStreamRegisterAndUnregister:372
» NullPointer
On Sat, Feb 7, 2015 at 9:04 AM, Jason Pell wrote:
> Is this expected at the moment:
>
> Caused by: java.lang.ClassNotFoundExcept
Is this expected at the moment:
Caused by: java.lang.ClassNotFoundException:
org.eclipse.jetty.websocket.WebSocketFactory$Acceptor
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPri
Hi Dan,
Any thoughts on timeline for next patch release?
sessionTransacted.
Can you have a quick look and make sure my comments are accurate
On Sat, Dec 6, 2014 at 4:42 AM, Jason Pell wrote:
> OK I am going to revert my changes, add a config property to
> JMSConfiguration to optionally disable exception propagation.
>
> The existing b
> should it be rolled back and retried? We’re not going to be able to parse
> it again next time either. If there are issues trying to send the
> response back to the client, sure. I can see that. But most of the
> others seem to cause more problems.
>
>
> Dan
>
>
> >
> harder to document / explain how it works. So we should be sure it makes
> sense.
>
> Christian
>
> On 05.12.2014 11:29, Jason Pell wrote:
>
>> I would like the option of enabling roll backs for runtime exceptions in
>> cxf 3 when I eventually upgrade. Does cxf 3
fort and makes it
> harder to document / explain how it works. So we should be sure it makes
> sense.
>
> Christian
>
> On 05.12.2014 11:29, Jason Pell wrote:
>
>> I would like the option of enabling roll backs for runtime exceptions in
>> cxf 3 when I eventually upgra
I have not found any materials on the net if this
> is the right choice.
> So we should discuss this here.
>
> Christian
>
>
> On 05.12.2014 07:33, Jason Pell wrote:
>
>> Hi Christian,
>>
>> I have added a test case to my github branch which demonstrates th
exactly why the resource holder having the session
means trans = false
Thanks
On Fri, Dec 5, 2014 at 2:42 PM, Jason Pell wrote:
> Would be interested in your feedback regarding the change.
>
>
> https://github.com/pellcorp/apache-cxf/compare/apache:2.7.x-fixes...cxf6136_jms
Would be interested in your feedback regarding the change.
https://github.com/pellcorp/apache-cxf/compare/apache:2.7.x-fixes...cxf6136_jms_ex_rollback?expand=1
On Fri, Dec 5, 2014 at 1:53 PM, Jason Pell wrote:
> Never mind, think I figured it out.
>
> Another question I have, is s
, Jason Pell wrote:
> Ok - in my local tests with both websphere mq and active mq, the trans
> test appears to be doing the right thing, but I am unsure why. I don't
> understand why the sessions are not the same.
>
> However whe
tests-transport-jm the trans test is false because the sessions
match.
I know I must be missing something, and I will continue to debug it to see
if I can figure it out, but perhaps someone might have some insight to
assist me
On Fri, Dec 5, 2014 at 11:20 AM, Jason Pell wrote:
> Hi C
On Fri, Dec 5, 2014 at 9:26 AM, Jason Pell wrote:
> Very annoyed with myself that I did not check the transaction support for
> request response till now. Was on my list of todos. Now I am going to have
> to depend on 2.7.15 snapahot.
>
> I need guaranteed delivery even for reques
needs to survive a server crash
or db issue.
I am not going to use xa transactions though. Will be enough to use good
old jms transaction manager support.
On 05/12/2014 9:13 AM, "Jason Pell" wrote:
> I check that the exception cause is instanceof Exception and not
> propogate. O
t all.
>
> Christian
>
>
> On 04.12.2014 18:09, Jason Pell wrote:
>
>> Hi,
>>
>> I would like to change the existing behavior of JMS destination to NOT
>> rollback the transaction if a checked exception is encountered.
>>
>> https://issues.apache
Not at the moment :-)
On 05/12/2014 6:09 AM, "Daniel Kulp" wrote:
>
> > On Dec 4, 2014, at 12:09 PM, Jason Pell wrote:
> >
> > Hi,
> >
> > I would like to change the existing behavior of JMS destination to NOT
> > rollback the transaction if
Hi,
I would like to change the existing behavior of JMS destination to NOT
rollback the transaction if a checked exception is encountered.
https://issues.apache.org/jira/browse/CXF-6136
Christian suggested I post an email to this list to give everyone an
opportunity to agree or disagree with my
+1 (non binding)
On Thu, Dec 4, 2014 at 3:26 AM, Colm O hEigeartaigh
wrote:
> +1.
>
> Colm.
>
> On Wed, Dec 3, 2014 at 4:20 PM, Daniel Kulp wrote:
>
> > This is a vote to release CXF 2.7.14 and 3.0.3. These versions fix a
> > bunch of bugs users have encountered. They also provide some addit
Sorry not had a chance to get back to this. Should be able to tomorrow
(AEST)
On 01/12/2014 11:00 PM, "Aki Yoshida" wrote:
> I haven't updated my ubuntu box for some time (and I still have 13.10
> with JDK 1.7.0_45).
> On that system, I just ran the test and am seeing the
With both Java 6 (patch 37) and Java 7 (patch 60)
On Mon, Dec 1, 2014 at 2:09 PM, Jason Pell wrote:
> I get the following exception in 3.0.x fixes when running from command
> line on ubuntu 14.04. The same error does not appear when executing from
> Eclipse Luna
>
> Tests run: 2
I get the following exception in 3.0.x fixes when running from command line
on ubuntu 14.04. The same error does not appear when executing from
Eclipse Luna
Tests run: 203, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 3.637 sec
<<< FAILURE! - in org.apache.cxf.systest.jaxrs.JAXRSClientServer
Done I will apply the final 6118 to 3.0 and trunk today
On 29/11/2014 9:21 PM, "Jason Pell" wrote:
> Took me a while but I finally got where you are coming from. Thanks for
> the detailed and informative replies.
> On 29/11/2014 8:46 PM, "Daniel Kulp" wrote:
>
Took me a while but I finally got where you are coming from. Thanks for the
detailed and informative replies.
On 29/11/2014 8:46 PM, "Daniel Kulp" wrote:
>
> > On Nov 29, 2014, at 1:44 AM, Jason Pell wrote:
> >
> > If the same SEI is used for both service endpo
not really too
much of an issue.
On 29/11/2014 3:18 PM, "Daniel Kulp" wrote:
>
> > On Nov 28, 2014, at 10:11 PM, Jason Pell wrote:
> >
> > Its only reversing what's coming from the model. If you define IN in the
> > jaxws properties on the client it will
gt; > On Nov 28, 2014, at 10:11 PM, Jason Pell wrote:
> >
> > Its only reversing what's coming from the model. If you define IN in the
> > jaxws properties on the client it will continue to validate IN on the
> > client as before.
> >
> > If I have IN
weekend.
On 29/11/2014 2:11 PM, "Jason Pell" wrote:
> Its only reversing what's coming from the model. If you define IN in the
> jaxws properties on the client it will continue to validate IN on the
> client as before.
>
> If I have IN defined for a operation using an a
g/repos/asf/cxf/commit/27ce514b
> > Tree: http://git-wip-us.apache.org/repos/asf/cxf/tree/27ce514b
> > Diff: http://git-wip-us.apache.org/repos/asf/cxf/diff/27ce514b
> >
> > Branch: refs/heads/2.7.x-fixes
> > Commit: 27ce514bb97a7693fd78d1ca16685665bca6
ntereceptor.
>
> In any case, I think we should remove these other methods from the
> master version. For the released tracks, we probably need to keep them
> as @deprecated with delegating to MessageUtils impl.
>
>
> 2014-11-27 12:49 GMT+01:00 Jason Pell :
> > Oh
AbstractInDatabindingInterceptor
Anyone know of any reason why that would be problematic?
On Thu, Nov 27, 2014 at 10:45 PM, Jason Pell wrote:
> Hi All
>
> Was wondering if anyone knows why in AbstractOutDatabindingInterceptor,
> isRequestorRole has a definition of:
>
> protected boolean isRequest
Hi All
Was wondering if anyone knows why in AbstractOutDatabindingInterceptor,
isRequestorRole has a definition of:
protected boolean isRequestor(Message message) {
return
Boolean.TRUE.equals(message.containsKey(Message.REQUESTOR_ROLE));
}
Whereas in AbstractInDatabindingInterceptor
I have merged a fix for 2.7 3.0 and master
On 17/10/2014 7:46 AM, "Jason Pell" wrote:
> https://issues.apache.org/jira/browse/CXF-6054
>
> On Fri, Oct 17, 2014 at 1:11 AM, Jason Pell wrote:
>
>> I will create jira and a patch to support the property.
>> O
https://issues.apache.org/jira/browse/CXF-6054
On Fri, Oct 17, 2014 at 1:11 AM, Jason Pell wrote:
> I will create jira and a patch to support the property.
> On 17/10/2014 12:58 AM, "Jason Pell" wrote:
>
>> I don't think I can easily override the wss4j interceptor
I will create jira and a patch to support the property.
On 17/10/2014 12:58 AM, "Jason Pell" wrote:
> I don't think I can easily override the wss4j interceptor as I am using WS
> policy so the interceptors are added for me.
>
> Am eager to understand the security iss
I don't think I can easily override the wss4j interceptor as I am using WS
policy so the interceptors are added for me.
Am eager to understand the security issues with client certs. When will
these be publicized
On 17/10/2014 12:56 AM, "Jason Pell" wrote:
> I would be intere
> false) to all this behaviour.
>
> Colm.
>
> On Thu, Oct 16, 2014 at 2:02 PM, Jason Pell wrote:
>
> > All I get now is the X500Principal of the https token.
> >
> > My policy is below. I am relying on the RequireClientCertificate to have
> > the saml token "
All I get now is the X500Principal of the https token.
My policy is below. I am relying on the RequireClientCertificate to have
the saml token "signed" and thus I would have expected it to be present in
the security context. I am at a loss as to why something like this could
change between point
doIntercept on the PhaseInterceptorChain is called after the select
alternative.
On Fri, Oct 10, 2014 at 11:23 PM, Jason Pell wrote:
> Tried that, the interceptor chain has not been initiated when the
> alternative selector is called.
>
>
> On Fri, Oct 10, 2014 at 10:33 PM, Dan
Tried that, the interceptor chain has not been initiated when the
alternative selector is called.
On Fri, Oct 10, 2014 at 10:33 PM, Daniel Kulp wrote:
>
> On Oct 9, 2014, at 8:01 PM, Jason Pell wrote:
>
> > I can't upgrade to 3.x as yet. So I need to figure out a way to
I refined the hack and just use the endpoint info getProperty directly. No
need to map to a client.
Though I would add a getEndpointInfo method to HttpConduit so I can get rid
of reflection after 2.7.14
On 10/10/2014 12:58 PM, "Jason Pell" wrote:
> I came up with a really dodgy
tunnel is active, or password
if not)
I define a property in the jaxws:client
I know it's nasty and I plan to get rid of it once we can upgrade to cxf 3,
but I think it should suffice for now
On Fri, Oct 10, 2014 at 11:01 AM, Jason Pell wrote:
> I can't u
I can't upgrade to 3.x as yet. So I need to figure out a way to do this in
2.7.
On 10/10/2014 4:18 AM, "Daniel Kulp" wrote:
>
> On Oct 9, 2014, at 5:41 AM, Jason Pell wrote:
>
> > For instance I want to force choosing username password token for one
> > meth
For instance I want to force choosing username password token for one
method call and then a saml bearer token for all others.
I don't have enough info in the assertor http conduit
+1 (non binding)
On Thu, Oct 9, 2014 at 6:01 AM, Dennis Sosnoski wrote:
> +1
>
> - Dennis
>
>
> On 10/09/2014 06:37 AM, Jeff Genender wrote:
>
>> +1
>>
>> Jeff
>>
>>
>> On Oct 8, 2014, at 11:30 AM, Daniel Kulp wrote:
>>
>> This is a vote to release CXF 2.7.13 and 3.0.2.There are over 90
https://issues.apache.org/jira/browse/WSS-516
On 08/10/2014 10:19 AM, "Jason Pell" wrote:
> Would it be acceptable to change cxf to set the saml version on the Saml
> callback before calling the callback.
>
> I want to be able to create a bearer token inside a local ca
Would it be acceptable to change cxf to set the saml version on the Saml
callback before calling the callback.
I want to be able to create a bearer token inside a local callback and I
want to handle saml 1 and 2 automatically based on the wsdl WS policy. At
the moment I can't do that. If I could c
some parts of the mtom
spec and see what you were referring to.
On Aug 13, 2014 12:45 AM, "Jason Pell" wrote:
> Does that not seem strange. What if one particular lient cant suppport
> mtom but the rest can. It seems bad form to return attachments to a client
> that will
aniel Kulp" wrote:
>
> On Aug 10, 2014, at 10:47 PM, Jason Pell wrote:
>
> > I cant seem to find code that controls mtom based on what a client can
> > handle. My understanding is the Accept header should be used. If I have a
> > Accept header which is either a wild
https://issues.apache.org/jira/browse/CXF-5939
On 12/08/2014 9:07 AM, "Jason Pell" wrote:
> If any other devs have info on why this is not enabled and a
> recommendation for where I could add this code either to existing
> interceptor or use my new one.
>
> I tried
, "Jason Pell" wrote:
> In the mean time I created an interceptor to override the mtom-enabled
> property based on the Accept property. I would prefer to use something
> build into cxf, but this seems to work for my use case.
>
>
> https://github.com/pellcorp/cxf/blob/ma
/interceptor/MtomOutInterceptor.java
On Mon, Aug 11, 2014 at 12:47 PM, Jason Pell wrote:
> I cant seem to find code that controls mtom based on what a client can
> handle. My understanding is the Accept header should be used. If I have a
> Accept header which is either a wild card or includes ap
I cant seem to find code that controls mtom based on what a client can
handle. My understanding is the Accept header should be used. If I have a
Accept header which is either a wild card or includes application/xop+xml
use mtom if con figured on endpoint otherwise fall back to inlined base 64.
I t
+1 (non binding)
On 16/07/2014 8:02 AM, "Christian Schneider"
wrote:
> +1
>
> Christian
>
> Am 15.07.2014 21:57, schrieb Daniel Kulp:
>
>> This is a vote to release the latest patch releases on all three branches.
>>
>> There are over 80 fixes for 3.0.1 with most back ported to 2.7.12 and
>> some
That definitely sounds good. I am so sick of system properties for
configuration.
On 10/07/2014 10:30 PM, "Daniel Kulp" wrote:
>
> Alessio,
>
> Two thoughts:
>
> 1) There is a java.xml.stream.util.StreamReaderDelegate class available
> from StAX apis, is there really a need for another delegate i
HI,
The commit:
commit 22e6b39db88ab99c175ba59bbcf623830614d1d1
Author: Daniel Kulp
Date: Thu Jun 12 12:37:26 2014 -0400
Optimization to only load the first extension found when only one is
asked for.
Broke some code our project uses. We are overriding the
JettyHTTPServerEngineFactory w
Deleted all org/apache/wss4j out of m2 repository and build continues
Weird
On Sun, Jun 15, 2014 at 1:28 PM, Jason Pell wrote:
> Downgrading to maven 3.0.3 got me past that one, but then I hit another
> issue.
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-
Downgrading to maven 3.0.3 got me past that one, but then I hit another
issue.
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.1:compile
(default-compile) on project cxf-rt-security: Compilation failure:
Compilation failure:
[ERROR]
/home/jason/Development/Github
Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.308 sec
<<< FAILURE! - in org.apache.cxf.transport.jms.uri.URIConfiguredConduitTest
testSendReceive(org.apache.cxf.transport.jms.uri.URIConfiguredConduitTest)
Time elapsed: 0.02 sec <<< ERROR!
java.lang.RuntimeException: peer (vm://
Even better, integration with gnome key ring
http://stackoverflow.com/questions/13385690/how-to-use-git-with-gnome-keyring-integration
On Sun, Jun 15, 2014 at 11:26 AM, Jason Pell wrote:
> Answered my own question, sort of
>
> git config --global credential.helper 'cache
t 11:15 AM, Jason Pell wrote:
> Hi,
>
> I can't find reference to being able to authenticate to the cxf git repo
> using ssh. I am not very comfortable having my password in .netrc file.
>
> I sent an email off to the infrastructure team, but figured I would ask
> the que
Hi,
I can't find reference to being able to authenticate to the cxf git repo
using ssh. I am not very comfortable having my password in .netrc file.
I sent an email off to the infrastructure team, but figured I would ask the
question here as well. What are others doing on linux (OSX as differen
Hi,
Just noticed this thread. I have managed to be able to configure the
conduit using properties, but its not exactly standard. And it won't work
with OSGI. Its documented here
https://issues.apache.org/jira/browse/CXF-4811?focusedCommentId=13578150&page=com.atlassian.jira.plugin.system.issueta
I would think getting users to modify a pom to exclude jaxb core is
acceptable for 3.0.1. I certainly would not have a problem especially if it
were in the release notes and clearly highlighted.
We use our own version of jaxb jaxb facets. But it will be sometime before
we upgrade to 3.x anyway.
M
I would think hosting javadocs only online would make most sense.
On 03/04/2014 5:39 AM, "Daniel Kulp" wrote:
>
> For 2.x, we basically generated 2 different sets of Javadoc for 2
> different purposes:
>
> 1) We generated the javadoc ONLY for the cxf-api. This is the javadoc
> that we stuck in t
+1 (non binding)
First release in a while I have not been eagerly waiting for :-)
Sent from my android phone
On 30/01/2014 11:21 pm, "Christian Schneider"
wrote:
> +1
>
> Did some tests in karaf 3 to verify the features.
>
> Christian
>
> On 29.01.2014 23:03, Daniel Kulp wrote:
>
>>
>> We've re
The policy is applied but not embedded from memory. When you define the
ref to the policy in the @WebService its embedded, both uri and also spring
bean refs.
Since the policy annotations in web services suited me i did not pursue why
it was not being embedded very far.
On 19/11/2013 7:07 AM, "Ol
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
docs.oasis-open.o
> >> http://www.w3.org/2000/09/xmldsig#
> http://www.w3.org/TR/xmldsig-core/xmldsig-core-schema.xsd
> >>
> >> that will likely fix it.
> >>
> >> I'm going to try and dig into Aries blueprint to see if we can fix the
with WS policy username
password with with java first
Sent from my Android phone
On 24/09/2013 2:49 PM, "Jason Pell" wrote:
> Hi,
>
> I upgraded our environment to use 2.7.7 and immediately upon deployment I
> started getting the following error:
>
> org.xml.sax.SAXPars
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-w
+1 (non binding)
On Thu, Sep 19, 2013 at 3:08 AM, Daniel Kulp wrote:
>
>
> We've resolved over 90 issues since 2.7.6 and almost 50 ported back to
> 2.6.10. This second attempt fixes some regressions in the JAX-WS TCK as
> well as some issues within Eclipse RCP framework.
>
>
> This also inclu
+1 (non binding)
On 14/09/2013 10:37 PM, "Daniel Kulp" wrote:
>
>
> We've resolved over 90 issues since 2.7.6 and almost 50 ported back to
> 2.6.10.
>
> This also includes an update release of our build-utils to get the PMD
> stuff needed to work with the latest Eclipse.
>
>
> List of issues:
> 2
Sent from my Android phone
On 10/09/2013 2:13 AM, "Daniel Kulp" wrote:
>
> If you tell m2eclipse to import the projects with the m2eclipse profile
> enabled, then it switched to a different PMD ruleset that doesn't have the
> custom rule.
>
> That said, I do have to wonder if we really need the c
Please be sure to post back saying how you solved it...
On 02/09/2013 6:45 PM, "Jana Weschenfelder" <
jana.weschenfel...@student.htw-berlin.de> wrote:
> Hello,
>
> many thanks for the reply. I got a hint from an expert an hour ago.
> I would like to try this first. I agree that my undertaking is n
Just wondering where the code to turn off out schema validation is going to
land? Its gone from message mode out interceptor but the diff does not seem
to add it in anywhere.
I am without a computer so I can't check the code out to look but wanted to
make sure it was not lost-
On Aug 14, 2013 11:5
Can you see if there is a mix of spring versions on the classpath.
On Jul 27, 2013 1:58 AM, "Iyappan Raman"
wrote:
> I am getting below error when i changed from 2.5.1 to 2.7.5, please let me
> know if i need to add any dependencies.
> Thank You
> Iyappan
>
> Caused by: org.springframework.beans.
https://issues.apache.org/jira/browse/CXF-5151
On Tue, Jul 23, 2013 at 11:54 PM, Jason Pell wrote:
> I have created a jira and I will play around with refactoring WSDL Get
> Interceptor to support GZIP encoding and see what I come up with.
>
>
>
>
> On Tue, Jul 23, 2013 a
I have created a jira and I will play around with refactoring WSDL Get
Interceptor to support GZIP encoding and see what I come up with.
On Tue, Jul 23, 2013 at 9:59 PM, Jason Pell wrote:
> So next question.
>
> What would make most sense?
>
> Modify wsdlgetinterceptor to not
executing the soap request
stuff.
Seems like a big change but is probably reasonably clean approach.
Or alternative is to execute gzip out interceptor logic in wsdl get
interceptor.
On Jul 23, 2013 8:12 PM, "Jason Pell" wrote:
> I checked the code and WSDLGetInterceptor aborts t
http://cxf.apache.org/cxf-276-release-notes.html
Is the correct 2.7.6 link
On Tue, Jul 23, 2013 at 7:56 PM, Gary Gregory wrote:
> The release notes link is incorrect, it points to the wrong version.
>
> Gary
>
> On Jul 23, 2013, at 4:10, Daniel Kulp wrote:
>
> >
> > The Apache CXF team is prou
s, so
not really that big of a deal.
Thanks for taking the time to do it, and apologies that I had not done it
myself, it was quite low on my list of priorities as ehcache 2.5.1 was
working fine for my day job.
Cheers
Jason
On Tue, Jul 16, 2013 at 9:04 PM, Aki Yoshida wrote:
> Hi Jason,
>
> 2013/7/7 Jason Pell :
> > I might have time end of next week so leave with me for the moment.
> >
> > On Jul 7, 2013 6:54 AM, "Aki Yoshida" wrote:
> >>
> >> Hi Jason,
> >>
> >> I wanted to have a patched snapshot sometime next week.
1 - 100 of 135 matches
Mail list logo
