[CXF 7711] compiler instance to java to ws #19
Conversation
Use Messages.properties and change message to better indicate that an error occurred during error handling, preventing further action.
CXF-7604 Refine error message during error handling
Most CXF modules depend on annotation 1.3, but MP Rest Client 1.0 is part of MP 1.3 which prereqs EE7 (annotation 1.2). This is required so that MP Rest Client 1.0 will operate in an EE7 environment.
JAX-RS 2.1 defaults the no-longer-used getSize method to -1, but in order to run an JAX-RS 2.0, we must have an implementation of this method.
We should not need to call handleMapper for the ResponseExceptionMappers - they already require the parameterized type to be a subclass of Throwable. And the handleMapper method checks whether the Throwable class can be assigned to the type in the user's REM - which it never will be (unless they define ResponseExceptionMapper<Throwable>). This also adds unit tests ensuring that the REM is executed.
[CXF-7597] Fix suspicious class loader findResource calls
Handle ResponseExceptionMappers
…stent even if not sampling (apache#367)
…egration implementation. Adding support for customizations (dynamic base path)
…ferent classifier
…t be present in the token
….CachedOutputStream.Threshold" property
…ead in one of the demos
… when generating ws client jars with jaxws bindings
fix wrong log warning "Unable to recognize the addressing policy"
…n-validation feature
[CXF-7707] JAXB doesn't (un)marshall property with @XmlElementRef
…een broadcasting and closing the broadcaster)
|
Looks like there are too many git commits included in this pull request, maybe the pull request was created against a different branch than intended? |
|
I see that it is but I don't understand how that can be. I did a rebase from upstream master to origin master before I created the branch minutes later. And I committed and submitted the code with in minutes after that. |
|
Time is not a factor, only the commit graph matters. Rebasing will not always correctly identify the list of commits, particularly if the commits you are interested in have a divergent ancestry from the place you're trying to bring them to. For simplicity's sake, you may want to do a hard reset to the base branch, and then cherry-pick each commit you want to bring in, in order. |
|
My intent is to sync my master to the upstream master and commit my changes against that. I'm no power user of git. I don't understand why rebasing to upstream master and creating my branch and commit as described above did not do that. Why all these other commits? I don't see that my changes are affected by any of those previous commits. |
|
I'm closing this and trying again. |
|
I'm not checking all the commits in the PR here, but please note that the last commit on master here is ~3yrs old. The upstream apache cxf master has clearly evolved in the mean time so it's likely hundreds of commits are missing here to synch with upstream master. |
Enables custom compiler to be used by JavaToWS