+1
Glen
--
View this message in context:
http://cxf.547215.n5.nabble.com/VOTE-CXF-2-7-5-2-6-8-tp5727223p5727340.html
Sent from the cxf-dev mailing list archive at Nabble.com.
Dan's quote: According to the agreements Apache has with Oracle, we really
cannot "release" code that doesn't pass the TCK (which the 2.0 works would
not).
I'm confused -- Apache FOP, Maven and Tomcat can release whenever they want,
even though none of them even remotely pass the JAX-RS TCK either
Oli, in your commits yesterday, "Spring2Security" example[1], which uses
Spring 2.0.8 (last updated in January 2008 and now at EOL[2]), seems to be a
contradiction, how do you place security on top of obsolete/no longer
supported software? (Why teach such a thing? You certainly can't look good
do
OK, I just debugged the Metro source code to determine how they can read the
Tomcat tomcat-users.xml file in order to do validation of UsernameToken
passwords.
Basically, if no sc:ValidatorConfiguration defined in the service-side WSDL:
https://github.com/gmazza/blog-samples/blob/master/metro_user
Hi folks, I just confirmed by testing Metro w/UsernameToken over SSL
transport (haven't tried UT via their symmetric binding yet), that if I
*don't* configure a server-side password callback handler like here:
https://github.com/gmazza/blog-samples/blob/master/metro_usernametoken_profile/service/sr
Please go to the CXF User's List for your questions; we're there too. This
list is for development of CXF itself.
My MTOM tutorial might be of help:
http://www.jroller.com/gmazza/entry/using_mtom_and_apache_fop
Glen
mcardle wrote
> I've created a mock web service using a wsdl and CXF plugin in
Up to you, as far as I'm concerned, but two new branches one quarter
separated from each other seems like it would be adding a lot of additional
(busy)work -- CXF itself does not move to a new branch with that kind of
frequency. If what you're planning for Release 1.2 can be added to Release
1.1 i
Team, I noticed we're configuring the JMS info in the jms-spec-demo sample
WSDL in three places[1]: within the wsdl:binding, under the wsdl:service,
and under the wsdl:port. I believe one location alone will suffice--just
the wsdl:binding section. Unless any objections, I'll simplify the WSDL to
Hi team, I'm wondering if we should delete these two pages that are listed in
the CXF Table of Contents here:
https://cwiki.apache.org/confluence/display/CXF20DOC/Index:
"Aegis Databinding (2.0.x) β For CXF up to 2.0.x"
"Maven Java2WSDL plugin (CXF 2.0.x only. Removed in 2.1 and replaced with
Jav
+1
Glen
--
View this message in context:
http://cxf.547215.n5.nabble.com/VOTE-Apache-CXF-2-7-0-tp5715902p5715994.html
Sent from the cxf-dev mailing list archive at Nabble.com.
+1
Glen
--
View this message in context:
http://cxf.547215.n5.nabble.com/VOTE-Release-Apache-CXF-2-4-10-2-5-6-2-6-3-tp5715901p5715993.html
Sent from the cxf-dev mailing list archive at Nabble.com.
Hi Oli, I noticed you have a Fediz 1.1 in JIRA but not a Fediz 1.0.2 -- I
created the latter thinking before I realized you already have Fediz 1.1
listed. Is your intention to remain with just one branch (but let it be 1.1
only, and no 1.0.2), or do you want both branches--1.0.2 and 1.1? (The
for
If you wish and if it would make you happy, but additional branches are more
busywork and overhead for you to maintain, taking away time you can spend on
putting Good Stuff in. So long as you're just adding functionality that
doesn't affect what's already there--such as (2) below and possibly even
Willem.Jiang wrote
>
> I totally agree with you that we could add a sentence to help people to
> search the simple front end on the document if they want. Now my
> question is will we rename the module name of the simple frontend in the
> code ?
> If not, we still need to add a mapping between
Hi Willem, was my response sufficient for you to lift your veto or would you
still like to prevent the proposed change?
Thanks,
Glen
--
View this message in context:
http://cxf.547215.n5.nabble.com/PROPOSAL-Rename-Simple-Frontend-No-Annotation-Frontend-tp5713384p5713669.html
Sent from the cxf
Willem.Jiang wrote
>
> Hi, I don't think it is a good idea to just rename it in the wiki page as
> we still to provide a reference link for the people who want to search for
> the Simple Frontend.
>
If that's a concern, no problem, I'll happily put in a sentence saying that
it used to be the si
Team, I'd like to rename our Simple Front End
(https://cwiki.apache.org/confluence/display/CXF20DOC/Simple+Frontend) in
our Confluence docs.
The problem with naming it "simple" is that it (1) falsely implies to
newcomers that JAX-WS is difficult and something nasty to be avoided, and
(2) its "simp
OK, I've counted 11 +1 votes (10 binding) and no other votes. This vote
passes, I'll be releasing Fediz 1.0.1 shortly.
Thanks,
Glen
Sergey Beryozkin-5 wrote
>
> +1
>> On Aug 24, 2012, at 1:02 PM, Glen Mazza<glen.mazza@> wrote:
>>
>>> Hi
Hi all, this new release provides significant documentation updates within
the samples as well as new sample keys to help clarify necessary trust
requirements. Oli has also gotten some programmatic fixes/enhancements in.
List of issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
+1
Glen
--
View this message in context:
http://cxf.547215.n5.nabble.com/VOTE-New-features-xml-for-2-5-5-1-tp5712981p5713125.html
Sent from the cxf-dev mailing list archive at Nabble.com.
Hi Oli, comments below:
Oliver Wulff-2 wrote
>
> I came across an issue in processing the claims encoded within a SAML 1.1
> and 2.0 attribute statement. Right now, the
> ClaimsAttributeStatementProvider creates the name of an attribute like
> this:
>
> SAML 2.0
>
> Current example:
>
>
(Resending...) +1
Glen
--
View this message in context:
http://cxf.547215.n5.nabble.com/VOTE-Release-Apache-CXF-2-4-9-2-5-5-2-6-2-tp5712591p5712650.html
Sent from the cxf-dev mailing list archive at Nabble.com.
+1
Glen
--
View this message in context:
http://cxf.547215.n5.nabble.com/WS-Security-interopfest-examples-tp5711998p5712024.html
Sent from the cxf-dev mailing list archive at Nabble.com.
/ws-trust/200512/}SecurityTokenService";);
@@ -250,6 +287,7 @@ public class SAMLRenewUnitTest extends A
stsClient.setRequiresEntropy(true);
stsClient.setKeySize(128);
stsClient.setAddressingNamespace("http://www.w3.org/2005/08/addressing";);
+stsClient.setSendRenewing(sendRenewing);
return
stsClient.requestSecurityToken("https://localhost:8081/doubleit/services/doubleittransport";);
}
--
Glen Mazza
Talend Community Coders
coders.talend.com
blog: www.jroller.com/gmazza
any problems or want to send feedback of any kind, please e-mail
the
+CXF dev list, dev@cxf.apache.org. You can also file issues in JIRA at:
+
+http://issues.apache.org/jira/browse/FEDIZ
+
+
+5. Migration notes:
+
+N.A.
+
+
+6. Specific issues, features, and improvements fixed in this version
+
+** Bug
+
+** Improvement
+
+** New Feature
+
+** Task
+
+** Test
+
+
+
--
Glen Mazza
Talend Community Coders
coders.talend.com
blog: www.jroller.com/gmazza
Hi, I noticed some STS classes (packages) are missing from our online
JavaDocs: http://cxf.apache.org/javadoc/latest/
In particular, org.apache.cxf.sts.operation.AbstractOperation and its
subclasses listed here:
http://fusesource.com/docs/esbent/7.0/apidoc/cxf/org/apache/cxf/sts/operation/class-u
Jetty:-)
>
> On Mon, Apr 23, 2012 at 1:46 PM, Glen Mazza <glen.mazza@> wrote:
>>
>> Benson Margulies wrote
>>>
>>> Last year, I took a look at tomcat as an alternative to Jetty for
>>> embedding purposes.
>>>
>>> I ran aground, I was
Benson Margulies wrote
>
> Last year, I took a look at tomcat as an alternative to Jetty for
> embedding purposes.
>
> I ran aground, I was just too ignorant.
>
> Since I seem, again, to be hitting jetty bugs that close 'idle'
> connections inappropriately, I've got myself interested again.
>
The online JavaDocs for the 2.3/2.4/2.5 series still need updating. Also,
this class:
http://www.jarvana.com/jarvana/view/org/apache/cxf/services/sts/cxf-services-sts-core/2.5.1/cxf-services-sts-core-2.5.1-javadoc.jar!/org/apache/cxf/sts/token/realm/SAMLRealm.html
-- for some reason is not in our
+1
Glen
--
View this message in context:
http://cxf.547215.n5.nabble.com/VOTE-Release-Apache-CXF-2-6-0-tp5636705p5638535.html
Sent from the cxf-dev mailing list archive at Nabble.com.
rba.processors.idl;
-
- import java.io.*;
- import java.util.Vector;
- import java.util.Hashtable;
+
+ package org.apache.cxf.tools.corba.processors.idl;
+
+ import java.io.*;
+ import java.util.Vector;
+ import java.util.Hashtable;
public interface IDLTokenTypes {
int EOF = 1;
Team, the CXF "js_browser_client_java_first" sample, which works fine in both
CXF 2.4.x and CXF 2.5.x, is inoperative in the CXF 2.6 trunk branch. While
Jetty starts OK, the page the README tells us to go to:
http://localhost:9000/Beverages.html is inaccessible. I think the problem
is that the c
Andrei Shakirin wrote
>
> Could you give me some advises what is the right way to do it:
> a) not sure how to update CXF User's Guide and User's Guide Table of
> Content: should I provide a JIRA patch or is it editable via apache cwiki?
>
Please edit it directly. The URL which Confluence gives
Andrei, the CXF Wiki is not a good place for "articles" -- that information
you wish to impart to the community should either go to an external blog
with a reference on our Resources page or incorporated within the CXF User's
Guide, where everyone can update it and we don't have to maintain duplica
cxf-to-compile-WSDL-in-eclipse-Dynamic-Web-Project-tp5479086p5479086.html
Sent from the cxf-issues mailing list archive at Nabble.com.
--
Glen Mazza
Talend Community Coders - coders.talend.com
blog: www.jroller.com/gmazza
at didn't help.
So if you guys could please help me.
Thanks in advance.
--
View this message in context:
http://cxf.547215.n5.nabble.com/Generating-Java-from-WSDL-tp4954507p4954507.html
Sent from the cxf-issues mailing list archive at Nabble.com.
--
Glen Mazza
Talend - http://www
+1
Glen
Daniel Kulp wrote:
>
> It's been over 6 month since 2.4.0 was released. Since then, we've added
> quite a bit of new functionality, new features, enhancements, etc...
> Thus,
> time for a release!
>
>
> The maven staging area:
> https://repository.apache.org/content/repositories
new Fault("COULD_NOT_REDA_XML_STREAM_CAUSED_BY", LOG, e,
e.getMessage());
+throw new Fault("COULD_NOT_REDA_XML_STREAM_CAUSED_BY", LOG, e,
+e.getClass().getCanonicalName(), e.getMessage());
}
}
--
Glen Mazza
Talend - http://www.talend.com/apache
Blog - http://www.jroller.com/gmazza
Twitter - glenmazza
+1
Glen
Christian Schneider wrote:
>
> +1
>
> Christian
>
>
> Am 04.10.2011 20:09, schrieb Daniel Kulp:
>>
>> We've resolved over 94 issues since 2.4.2 and thus is time for a release
>> and
>> over 40 issues ported back for 2.3.7.
>>
>> List of issues:
>> 2.4.3:
>> https://issues.apache.or
x) {
+assertTrue("WebServiceException is expected", ex instanceof
javax.xml.ws.WebServiceException);
+assertTrue("RespectBindingFeature message is expceted",
expected
Regards,
Glen
--
Glen Mazza
Talend - http://www.talend.com/products/tsf
Blog - http://www.jroller.com/gmazza
Twitter - glenmazza
f this
attribute is set to true or omitted, ignored otherwise.
+
+
+Set the maximum Idle time for a connection, the timer will be
reset if there is any read and write option on the under layer
stream.
I'm not sure what you mean here by "option" and &quo
Team, with the exception of removing the JBI functionality, the CXF
integration/JCA examples[1] have not been touched in 3 yrs. 10 months--and
then just to add WebLogic[2], 4 yrs. 10 months in everything else[3].
Should we nuke them from TRUNK and CXF 2.4.x branches? They seem to be
obsolete (ins
al
that we should be steering clear of it rather than trying to document it for
them and include examples for it.
Glen
Freeman-2 wrote:
>
> +1 to exclude it from binary kit, just keep them in svn and src kit.
>
> Freeman
> On 2011-9-22, at δΈε1:28, Glen Mazza wrote:
>
>
Nuking appears appropriate. If MTOSI's WSDL's are well designed, no special
example for it would be needed (either our already existing Java-first or
WSDL-first samples would suffice.) If they're not and need special tweaks,
it's the responsibility of the MTOSI team (assuming such a team exists)
Hi Team, we have two MTOSI examples in the CXF samples list -- they're rather
old (presently not Mavenized). MTOSI seems to be largely inactive, with the
last blog post on it 17 months ago and no real analysis since mid-2009.
Should we nuke them (2.4 and Trunk branches)? If we're down to just 1
is change, according to the JavaDoc, the above
two statements are equivalent:
http://download.oracle.com/javase/6/docs/api/java/lang/String.html#isEmpty%28%29
Glen
if (status == 200) {
okResponse = responseEls.get(i);
+1
Glen
Daniel Kulp wrote:
>
> We've resolved over 100 issues since 2.4.1 and thus is time for a release.
>
--
View this message in context:
http://cxf.547215.n5.nabble.com/VOTE-Release-Apache-CXF-2-4-1-take-2-tp4474979p4476203.html
Sent from the cxf-dev mailing list archive at Nabble.com.
+1
On 04/13/2011 09:51 AM, Daniel Kulp wrote:
> It's been about 6 months since the release of 2.3 and we've done a
> fantastic
> job implenting new features and cleaning up various parts of the code and
> integrating new versions of libraries like WSS4J, Neethi, XmlSchema,
> etc...
> that provide
Sounds good. My WSDL-first tutorial shows how Ant can be used
(http://www.jroller.com/gmazza/entry/web_service_tutorial), I can
incorporate that into a new CXF sample (I've been meaning to rip out the Ant
from that tutorial anyway), or we can leverage the Ant scripts in the simple
wsdl-first and j
(1)'s my first choice, I can help with the Mavenization of the samples
(standard directory structure) if we go that route. Reasons:
1.) Providing Ant builds is for the benefit of those developers whose
capabilities are between what is needed to use Ant and what is needed to use
Maven (anyone pas
Thanks, appreciate it!
On 2/28/2011 4:40 PM, Jeff Genender wrote:
Forgiven. Thanks for the apology.
Jeff
On Feb 28, 2011, at 2:26 PM, Glen Mazza wrote:
Agreed. The CXF PMC also held that Jeff's email simply didn't reach a level
warranting public airing, given the general view
Agreed. The CXF PMC also held that Jeff's email simply didn't reach a
level warranting public airing, given the general view--in which I've
grown more in agreement with--that *no* email warrants such airing. Any
types of questionable emails are best sent to the internal
priv...@cxf.apache.org
, the practical
impact of 1.6 is tiny. No one working on CXF is deprived of any
interesting learning opportunities or functionality by continuing to
stick to 1.5.
--benson
--
Glen Mazza
Software Engineer, Talend (http://www.talend.com)
blog: http://www.jroller.com/gmazza
sing number of people
out there who have barely bothered to stop requiring *1.4*. We could
put the animal sniffer to work to help head off any unfortunate
accidental dependencies on 1.6 APIs.
On Wed, Feb 23, 2011 at 7:53 AM, Glen Mazza wrote:
Well, older versions of CXF--2.3.x and earlier--of
t any further
communication is private.
What do you think?
I do not want to judge what happened between Jeff and you as I do not
know all the details. So I can only ask both of you to try to bring this
back to a normal level.
Christian
Am 27.02.2011 08:31, schrieb Glen Mazza:
Folks, if Jeff Genende
Glen
--
Subject: [offlist again and no, onlist is not fine!] Re: [onlist is
fine!] Re: [offlist] Re: SOAP over JMS and CXF.
Date: Sat, 26 Feb 2011 04:11:50 +0100
From: Jeff Genender
To: Glen Mazza
CC: Daniel Kulp
Hi Glen!
You are right, I didn't have to go off list. I se
t] Re: SOAP over JMS and CXF.
Date: Sat, 26 Feb 2011 04:11:50 +0100
From: Jeff Genender
To: Glen Mazza
CC: Daniel Kulp
Hi Glen!
You are right, I didn't have to go off list. I sent you the private email out
of respect to you. But that clearly was all for naught - what a
eathe before pushing the send button. Feel free to hit
me up on IRC if you need to discuss.
Thanks,
Jeff
On Feb 25, 2011, at 8:01 AM, Glen Mazza wrote:
Bill, I'm all for plugging but if you could spend some time on fixing
the five (rather simple) RESTEasy bugs I reported (RESTEAST-494, 4
try to keep things more cordial and pleasant.
Thanks!
Dan
On Friday 25 February 2011 10:01:52 AM Glen Mazza wrote:
Bill, I'm all for plugging but if you could spend some time on fixing
the five (rather simple) RESTEasy bugs I reported (RESTEAST-494, 495,
496, 497, and 502) over a month ag
> errors. I apologize your bug reports weren't given my immediate full
> attention, no matter how minor (or nonexistent) they were.
>
> On 2/25/11 10:01 AM, Glen Mazza wrote:
>> Bill, I'm all for plugging but if you could spend some time on fixing
>> the five (ra
s and service extensions defined by this spec be
>>> better suited in a supported WSDL or WADL?
>>>
>>> I assume WADL as supported by CXF?
>>>
>>> Thanks!
>>>
>>>
--
Glen Mazza
Software Engineer, Talend (http://www.talend.com)
blog: http://www.jroller.com/gmazza
The User's list would be more appropriate for this question, also is it
not already answered within our user's guide?
Glen
On 2/24/2011 2:26 PM, robert wrote:
Does CXF use something in place of the WSDL JMS Extension and this
namespace: http://schemas.xmlsopa.org/wsdl/jms?
Thanks!
that I've seen.
- Dennis
On 02/02/2011 12:17 PM, Glen Mazza wrote:
Yes, it may be time for placing it in Apache Attic.
On 01.02.2011 18:00, Gary Gregory wrote:
Sound like this project page should be better annotated or the
project moved to some dormant area of the site...
Gary Gregory
Se
Best to ask on the CXF User's list, devs are on both, but many more
people are on Users.
You can look over the wire to see what is being sent/received[1]
differently--it could be something different, or in addition to, the NaN
issue. I believe we went from JAXB 2.1 to 2.2 between CXF 2.2 and
You can at least view the WADL using ?_wadl at the end of the service
string in a browser.
Unsure, but JMS/REST would seem to be a contradiction, because REST is
based on the HTTP transport.
Glen
On 2/24/2011 9:17 AM, robert wrote:
The Web Application Description Language (WADL) is new to m
+1
Glen
On 2/23/2011 6:23 PM, Eric Johnson wrote:
+1
On Wed, Feb 23, 2011 at 6:04 PM, Sergey Beryozkin wrote:
+1
thanks, Sergey
On Wed, Feb 23, 2011 at 8:30 PM, Daniel Kulp wrote:
We've resolved over 50 issues since 2.3.2. Thus, we really should get 2.3.3
out, especially since 2.3.2
Well, older versions of CXF--2.3.x and earlier--of course would
perpetually support JRE 5.0. It's just a question of moving forward, it
looks like right now 2.4 will still support 5.0 and maybe we'll switch
to 6.0 minimum in CXF 2.5. I didn't know about royalty concerns (do
you have a link f
Probably nice to drop Java 5 with CXF 2.4.0, especially if there's any
architectural cobwebs in CXF necessitated by supporting it; apparently
though ActiveMQ still supports Java 5
(http://activemq.apache.org/getting-started.html#GettingStarted-PreInstallationRequirements).
Glen
On 2/22/2011
On 2/19/2011 8:24 AM, Christian Schneider wrote:
The next thing is how to document our architecture. We have a good
starting point at
https://cwiki.apache.org/confluence/display/CXF20DOC/CXF+Architecture
but I think some important things are lacking. This page
describes the key structural eleme
ommit privileges to Dennis (dsosnoski at apache
dot org).
Thanks,
Glen
On 2/16/2011 12:53 AM, Glen Mazza wrote:
Hello Team,
Here's a vote to make Dennis Sosnoski a committer on the CXF project.
Of course we all know Dennis from his extensive IBM developerWorks
articles[1] on web services,
On 2/17/2011 11:20 PM, dk...@apache.org wrote:
Author: dkulp
Date: Fri Feb 18 04:20:06 2011
New Revision: 1071879
URL: http://svn.apache.org/viewvc?rev=1071879&view=rev
Log:
Push more stuff to Neethi
Cleanup some policy API's
Modified:
cxf/trunk/api/src/main/java/org/apache/cxf/ws/policy/Asse
Hello Team,
Here's a vote to make Dennis Sosnoski a committer on the CXF project.
Of course we all know Dennis from his extensive IBM developerWorks
articles[1] on web services, which has allowed him to provide many
substantive responses[2] to user list questions. He's also reported,
and in
Actually, Kerek best to ask CXF questions on the us...@cxf.apache.org
list (also on Nabble), which has virtually everybody on dev (for
internal development of CXF only) plus tons of users.
I think you're running wsdl2java with the "-validate" option, the error
below might be WS-I Basic Profile
Thanks!
On 2/11/2011 4:26 AM, Willem Jiang wrote:
Hi Glen,
Your fix has some side effect, I just committed another patch[1] to fix
the test error of SecurityPolicyTest.
[1]http://svn.apache.org/viewvc?rev=1069716&view=rev
Willem
On 2/10/11 11:47 PM, Glen Mazza wrote:
Fixed on 2.3.2
Fixed on 2.3.2 and upcoming 2.4. Also, I checked the official CXF
treasury ($0.00), sorry no money for the Monster drink.
Thanks,
Glen
On 09.02.2011 14:40, Glen Mazza wrote:
Hmm, seems like the CXF team owes Aaron a Monster energy drink (unless
he's become partial to other beverages).
wouldn't make much sense if it were deliberate.
- Aaron
--
Glen Mazza
Software Engineer, Talend (http://www.talend.com)
blog: http://www.jroller.com/gmazza
tes. Apache is
not a locale for horn tooting.
Jeff
On Feb 2, 2011, at 7:23 PM, Glen Mazza wrote:
Unless it is blatant lies (i.e., non-reputable companies), I say let the companies do a
little bit of advertising on the Support page, even if they contradict each other or
embellish a bit. W
JAX-WS, WS-Security, etc... to make sure any bugs
and issues can be resolved quickly and accurately.
Change Notification Preferences
View Online | Add Comment
--
Glen Mazza
Software Engineer, Talend (http://www.talend.com)
blog: http://www.jroller.com/gmazza
Hi, we have an IONA reference in one of our namespaces:
http://cxf.apache.org/apidocs/constant-values.html#org.apache.cxf.tools.corba.common.ReferenceConstants.REFERENCE_NAMESPACE
Can/should we switch that to something CXF specific?
Thanks,
Glen
--
Glen Mazza
Software Engineer, Talend (http
JAXB?
Thanks,
Glen
--
Glen Mazza
Software Engineer, Talend (http://www.talend.com)
blog: http://www.jroller.com/gmazza
I don't think a new vote is necessary, because as stated the vote covers
both portions. So everyone has voted +1 and +1 up to Jim.
To be valid, a veto must have a justifiable reason, and Jim certainly
does have one for CXF 2.3.2 but not CXF XJC 2.3.2, so the latter can
still proceed (if desir
+1
Glen
On 17.01.2011 23:26, Daniel Kulp wrote:
We've had a busy 8 weeks or so despite the holidays. We've managed to fix
over 75 JIRA issues since 2.3.1 which is quite remarkable . This also fixes a
bunch of OSGi related issues that are needed for
Camel and ServiceMix.
Note: this vote a
Does it make sense to have a CONTENT_TYPE key but no value for it -- any
legitimate use case? Otherwise it may be better (if possible) to throw
some runtime exception to alert the developer of the client or web
service provider that he or she is erroneously adding the CONTENT_TYPE
key but not
On 10.01.2011 12:06, cohei...@apache.org wrote:
Author: coheigea
Date: Mon Jan 10 17:06:06 2011
New Revision: 1057283
URL: http://svn.apache.org/viewvc?rev=1057283&view=rev
Log:
[CXF-3236] - Add support for an Issued Token extracted from a SAML assertion
- Upgrading to use WSS4J 1.5.11-SNAPSHO
posal?
Can I help to finalize its integration in a future version?
Regards
lmg
--
Glen Mazza
gmazza at apache dot org
http://www.jroller.com/gmazza
Best to ask these questions on the User list, all the Devs are on it as
well. You can also search the CXF-Users list on Nabble and get dozens
of hits to your question.
Glen
On 12/10/2010 09:03 AM, phper...@gmail.com wrote:
Hello,
How a basic authentifiaction should be set up ?
I suppose i
AS WAS 6.1 is built on Axis2, perhaps this thread would be better moved
to the Axis2 Dev list.
Glen
On 12/08/2010 06:29 PM, Andreas Veithen wrote:
On Wed, Dec 8, 2010 at 22:58, Craig Tataryn wrote:
On 2010-12-08, at 3:33 PM, Andreas Veithen wrote:
Looks like you made the same mis
Just be thankful you have hair to get gray. :)
On 12/08/2010 03:26 PM, Craig Tataryn wrote:
We were using WAS 6.1 and we needed to support HL7 payloads. Axis wasn't up to
snuff. Then trying to get modern versions of JAXB and XML APIs to work with WAS
wasted soo much time and money. It w
Not to be hated, but is getPassword() one of those functions that should
be returning a char array instead of a string?
Glen
On 12/06/2010 04:40 PM, dk...@apache.org wrote:
Author: dkulp
Date: Mon Dec 6 21:40:18 2010
New Revision: 1042803
URL: http://svn.apache.org/viewvc?rev=1042803&view=re
+1
On 12/05/2010 09:34 PM, Jim Ma wrote:
+1
On Sun, Dec 5, 2010 at 12:08 AM, Alessio Soldano wrote:
+1
On 12/02/2010 03:51 PM, Daniel Kulp wrote:
Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.2.11 release. Over 43 JIRA is
+1
Glen
John Fuhr wrote:
>
> On Thu, Dec 2, 2010 at 3:32 PM, David Bosschaert
> > +1
>>
>> David
>>
>> On 2 December 2010 12:01, Daniel Kulp wrote:
>> >
>> > In the last 2 years, Colm has logged 11 issues with CXF. Every single
>> one of
>> > them came with a patch file to fix the issue:
>>
Sorry, my bad, I did not realize they were actually different tests, I will
revert them.
Glen
Sergey Beryozkin-5 wrote:
>
> Hi Glen
>
> thanks for trying to clean up the tests, but I'd actually like them
> retained, but I agree some code optimization needs to be done though,
> please
> note,
How does one run the interopfest tests? If I make a change to the stsclient
I would want to make sure it doesn't break anything.
Glen
--
View this message in context:
http://cxf.547215.n5.nabble.com/How-to-run-interopfest-tp2644543p2644543.html
Sent from the cxf-dev mailing list archive at Nab
It might be me. For SAML references, I switched to KeyIdentifier instead of
wsse:reference because that's what a Metro web service was expecting, also
that was in harmony with the relevant specifications, as discussed here[1].
To be two-thirds complete, another patch in WSS4J will need to be
ap
I'd ask on the CXF user's list.
raflik-nb wrote:
How to fix that?
Sergey Beryozkin-5 wrote:
>
> Let me put it the other way. I haven't started this thread to complain
> about
> Spring, or start any debate about the use of Spring. What I'd like to
> convey
> is that IMHO it is in the interests of CXF to ensure that those
> integrators
> who prefer to provide no
Sergey Beryozkin-5 wrote:
>
> Don't really get it... Or is it the case of someone missing the point that
> some users of CXF just do not want to use Spring ?
>
I don't know, I just think it would be nice if there was a separate Apache
Banana project that consists of Spring but with its JARs re
Sergey Beryozkin-5 wrote:
>
> This causes problems when doing non-Spring CXF deployments.
> Generally, we should really try to keep the Spring related code in .spring
> subpackages as it will make it simpler for CXF be integrated with other
> similar frameworks or deployed in containers providin
Team, our org.apache.cxf.transport.http_jetty.JettyHTTPServerEngine uses
Eclipse's wrapper of the Jetty server (org.eclipse.jetty.server.Server)
instead of the actual object (org.mortbay.jetty.Server). Out of curiosity,
is there a reason for that--is the Eclipse wrappered version more useful or
mo
atform-dependendent. Linux does none at all,
> for example. So it's not safe in general.
>
>
> On Fri, Jul 30, 2010 at 9:50 PM, Glen Mazza wrote:
>> May I ask why this normalization is helpful (instead of just using the
>> intended file path to being with)?
>> D
1 - 100 of 246 matches
Mail list logo
