It looks like the clean target under jbossws-core doesn't actually clean
everything.
After merging but before committing I run clean and then deploy JBossWS
and run the testsuite, however it looks like I still have an old version
of the JBossWSTest class left behind.
[darranl@darran_laptop jbossws]$ find -name JBossWSTest.class
./integration/spi/output/classes/org/jboss/wsf/spi/test/JBossWSTest.class
./integration/spi/output/classes/org/jboss/wsf/test/JBossWSTest.class
./integration/spi/…
[View More]output/eclipse/org/jboss/wsf/test/JBossWSTest.class
--
Regards,
Darran Lofthouse.
Senior Software Maintenance Engineer
JBoss, a division of Red Hat
-------- Forwarded Message --------
> From: jbossws-commits(a)lists.jboss.org
> Reply-To: jbossws-commits(a)lists.jboss.org
> To: jbossws-commits(a)lists.jboss.org
> Subject: [jbossws-commits] JBossWS SVN: r4010 -
> trunk/jbossws-core/src/test/java/org/jboss/test/ws/tools/jbws1723.
> Date: Thu, 26 Jul 2007 15:38:33 -0400
>
> Author: thomas.diesler(a)jboss.com
> Date: 2007-07-26 15:38:33 -0400 (Thu, 26 Jul 2007)
> New Revision: 4010
>
> Modified:
> trunk/jbossws-core/src/test/java/org/jboss/test/ws/tools/jbws1723/JBWS1723TestCase.java
> Log:
> [JBWS-1723] Test WSDL with bound headers defined as anonymous types.
> Fix import
>
> Modified: trunk/jbossws-core/src/test/java/org/jboss/test/ws/tools/jbws1723/JBWS1723TestCase.java
> ===================================================================
> --- trunk/jbossws-core/src/test/java/org/jboss/test/ws/tools/jbws1723/JBWS1723TestCase.java 2007-07-26 16:51:02 UTC (rev 4009)
> +++ trunk/jbossws-core/src/test/java/org/jboss/test/ws/tools/jbws1723/JBWS1723TestCase.java 2007-07-26 19:38:33 UTC (rev 4010)
> @@ -27,10 +27,10 @@
> import org.jboss.test.ws.tools.fixture.JBossSourceComparator;
> import org.jboss.test.ws.tools.validation.JaxrpcMappingValidator;
> import org.jboss.ws.tools.WSTools;
> -import org.jboss.wsf.spi.test.JBossWSTest;
> +import org.jboss.wsf.test.JBossWSTest;
>
> /**
> - * Test WSDL with bound headers defined as anonymous types.
> + * [JBWS-1723] Test WSDL with bound headers defined as anonymous types.
> *
> * @see http://jira.jboss.com/jira/browse/JBWS-1723
> *
>
> _______________________________________________
> jbossws-commits mailing list
> jbossws-commits(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossws-commits
[View Less]
I am just about to commit a change to both branches/jbossws-2.0 and
trunk - within the Jira issue should I set the fix version to both
jbossws-2.0.1 and jbossws-2.1.0?
--
Regards,
Darran Lofthouse.
Senior Software Maintenance Engineer
JBoss, a division of Red Hat
In WSSecurityDispatcher is see
| if (operationConfig.getUsername() != null)
| {
| Object user = ctx.get(Stub.USERNAME_PROPERTY);
| Object pass = ctx.get(Stub.PASSWORD_PROPERTY);
|
| if (user != null && pass != null)
| {
| operations.add(new OperationDescription<EncodingOperation>(SendUsernameOperation.class, null, user.toString(), pass.toString(), null));
| ctx.put(StubExt.…
[View More]PROPERTY_AUTH_TYPE, StubExt.PROPERTY_AUTH_TYPE_WSSE);
| }
| }
|
which indeed only processes the jaxrpc stub properties.
More generally, StubExt needs to be refactored such that it applies to both jaxrpc and jaxws.
Could you please create
org.jboss.test.ws.jaxws.samples.wssecurity.SimpleUsernameTestCase
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067348#4067348
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067348
[View Less]
Magesh sais:
I am aware that the UserPrinciapl and Credentials are checked with this
test case and the details are passed via the HTTPRequest, but the real
question is about wsse:UsernameToken and its presence in SOAPHeader and
not in HTTPRequest.
When we set the BindingProvider properties we are able to login and this
testcase passes, but when we set the jboss-wsse-*.xml
configuration this does not appear in the SOAPHeader, whereas it works
for JAXRPC style webservices and it works for …
[View More]JAXWS clients too if we
set the properties like this:
(BindingProvider)port).getRequestContext().put("javax.xml.rpc.security.auth.username", "kermit");
((BindingProvider)port).getRequestContext().put("javax.xml.rpc.security.auth.password", "thefrog");
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067347#4067347
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067347
[View Less]
The hooks work mutually exclusive. i.e. there is one hook for every type of deployment. The hooks themselves delegate to a DeloymentAspectManager, which excecutes the DeploymentAspects - the work of those aspects are rolled back on failure.
| // start the deployment
| for (int i = 0; i < getDeploymentAspects().size(); i++)
| {
| DeploymentAspect aspect = getDeploymentAspects().get(i);
| try
| {
| logInvocation(aspect, "…
[View More]Start");
| aspect.start(dep);
| }
| catch (RuntimeException rte)
| {
| while (i-- >= 0)
| {
| // destroy the deployment
| failsafeDestroy(aspect, dep);
| }
| throw rte;
| }
| }
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066606#4066606
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066606
[View Less]