Nabble - CXF

svn commit: r704146 - in /cxf/sandbox/dosgi: dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/ dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/service/ dsw/cxf-dsw/src/test/java/org/apache/cxf/dosgi/dsw/ felix/framework/ felix/framework/src/main/j...

2008-10-13T09:06:46Z

Author: sergeyb
Date: Mon Oct 13 09:06:45 2008
New Revision: 704146

URL: http://svn.apache.org/viewvc?rev=704146&view=rev
Log:
DOSGI : applying CXF-1862 patch on behalf of David B.

Added:
cxf/sandbox/dosgi/felix/framework/src/main/java/org/osgi/service/distribution/
cxf/sandbox/dosgi/felix/framework/src/main/java/org/osgi/service/distribution/DistributionProvider.java
- copied, changed from r703569, cxf/sandbox/dosgi/felix/framework/src/main/java/org/osgi/service/dsw/DistributionProvider.java
Removed:
cxf/sandbox/dosgi/felix/framework/src/main/java/org/osgi/service/dsw/
Modified:
cxf/sandbox/dosgi/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/Activator.java
cxf/sandbox/dosgi/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/service/CxfDistributionProvider.java
cxf/sandbox/dosgi/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/service/DistributionProviderImpl.java
cxf/sandbox/dosgi/dsw/cxf-dsw/src/test/java/org/apache/cxf/dosgi/dsw/ActivatorTest.java
cxf/sandbox/dosgi/felix/framework/pom.xml
cxf/sandbox/dosgi/felix/main/pom.xml
cxf/sandbox/dosgi/felix/main/src/main/resources/config.properties

Modified: cxf/sandbox/dosgi/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/Activator.java
URL: http://svn.apache.org/viewvc/cxf/sandbox/dosgi/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/Activator.java?rev=704146&r1=704145&r2=704146&view=diff
==============================================================================
--- cxf/sandbox/dosgi/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/Activator.java (original)
+++ cxf/sandbox/dosgi/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/Activator.java Mon Oct 13 09:06:45 2008
@@ -42,7 +42,7 @@
import org.osgi.framework.hooks.service.ListenerHook;
import org.osgi.service.cm.ConfigurationException;
import org.osgi.service.cm.ManagedService;
-import org.osgi.service.dsw.DistributionProvider;
+import org.osgi.service.distribution.DistributionProvider;

public class Activator implements BundleActivator, ServiceListener, ManagedService {

Modified: cxf/sandbox/dosgi/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/service/CxfDistributionProvider.java
URL: http://svn.apache.org/viewvc/cxf/sandbox/dosgi/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/service/CxfDistributionProvider.java?rev=704146&r1=704145&r2=704146&view=diff
==============================================================================
--- cxf/sandbox/dosgi/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/service/CxfDistributionProvider.java (original)
+++ cxf/sandbox/dosgi/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/service/CxfDistributionProvider.java Mon Oct 13 09:06:45 2008
@@ -21,7 +21,7 @@
import java.util.Map;

import org.osgi.framework.ServiceReference;
-import org.osgi.service.dsw.DistributionProvider;
+import org.osgi.service.distribution.DistributionProvider;

public interface CxfDistributionProvider extends DistributionProvider {
void addExposedService(ServiceReference serviceReference, Map<String, String> publicationProperties);

Modified: cxf/sandbox/dosgi/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/service/DistributionProviderImpl.java
URL: http://svn.apache.org/viewvc/cxf/sandbox/dosgi/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/service/DistributionProviderImpl.java?rev=704146&r1=704145&r2=704146&view=diff
==============================================================================
--- cxf/sandbox/dosgi/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/service/DistributionProviderImpl.java (original)
+++ cxf/sandbox/dosgi/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/service/DistributionProviderImpl.java Mon Oct 13 09:06:45 2008
@@ -25,7 +25,7 @@
import java.util.Set;

import org.osgi.framework.ServiceReference;
-import org.osgi.service.dsw.DistributionProvider;
+import org.osgi.service.distribution.DistributionProvider;

public class DistributionProviderImpl implements DistributionProvider, CxfDistributionProvider {

Modified: cxf/sandbox/dosgi/dsw/cxf-dsw/src/test/java/org/apache/cxf/dosgi/dsw/ActivatorTest.java
URL: http://svn.apache.org/viewvc/cxf/sandbox/dosgi/dsw/cxf-dsw/src/test/java/org/apache/cxf/dosgi/dsw/ActivatorTest.java?rev=704146&r1=704145&r2=704146&view=diff
==============================================================================
--- cxf/sandbox/dosgi/dsw/cxf-dsw/src/test/java/org/apache/cxf/dosgi/dsw/ActivatorTest.java (original)
+++ cxf/sandbox/dosgi/dsw/cxf-dsw/src/test/java/org/apache/cxf/dosgi/dsw/ActivatorTest.java Mon Oct 13 09:06:45 2008
@@ -19,7 +19,7 @@
import org.osgi.framework.Bundle;
import org.osgi.framework.BundleContext;
import org.osgi.framework.ServiceRegistration;
-import org.osgi.service.dsw.DistributionProvider;
+import org.osgi.service.distribution.DistributionProvider;

public class ActivatorTest extends TestCase{

Modified: cxf/sandbox/dosgi/felix/framework/pom.xml
URL: http://svn.apache.org/viewvc/cxf/sandbox/dosgi/felix/framework/pom.xml?rev=704146&r1=704145&r2=704146&view=diff
==============================================================================
--- cxf/sandbox/dosgi/felix/framework/pom.xml (original)
+++ cxf/sandbox/dosgi/felix/framework/pom.xml Mon Oct 13 09:06:45 2008
@@ -86,7 +86,7 @@
<Bundle-Name>Apache Felix Framework</Bundle-Name>
<Bundle-Description>OSGi R4 framework implementation.</Bundle-Description>
<Bundle-Vendor>The Apache Software Foundation</Bundle-Vendor>
- <Export-Package>org.osgi.framework;-split-package:=merge-first,org.osgi.framework.hooks.service;-split-package:=merge-first,org.osgi.service.packageadmin,org.osgi.service.url,org.osgi.service.discovery,org.osgi.service.dsw,org.osgi.service.startlevel,org.osgi.util.tracker</Export-Package>
+ <Export-Package>org.osgi.framework;-split-package:=merge-first,org.osgi.framework.hooks.service;-split-package:=merge-first,org.osgi.service.packageadmin,org.osgi.service.url,org.osgi.service.discovery,org.osgi.service.distribution,org.osgi.service.startlevel,org.osgi.util.tracker</Export-Package>
<Private-Package>org.apache.felix.moduleloader.*,org.apache.felix.framework.*</Private-Package>
<Import-Package>!*</Import-Package>
<Include-Resource>META-INF/LICENSE=LICENSE,META-INF/NOTICE=NOTICE,{src/main/resources/},org/osgi/framework/=target/classes/org/osgi/framework/</Include-Resource>

Copied: cxf/sandbox/dosgi/felix/framework/src/main/java/org/osgi/service/distribution/DistributionProvider.java (from r703569, cxf/sandbox/dosgi/felix/framework/src/main/java/org/osgi/service/dsw/DistributionProvider.java)
URL: http://svn.apache.org/viewvc/cxf/sandbox/dosgi/felix/framework/src/main/java/org/osgi/service/distribution/DistributionProvider.java?p2=cxf/sandbox/dosgi/felix/framework/src/main/java/org/osgi/service/distribution/DistributionProvider.java&p1=cxf/sandbox/dosgi/felix/framework/src/main/java/org/osgi/service/dsw/DistributionProvider.java&r1=703569&r2=704146&rev=704146&view=diff
==============================================================================
--- cxf/sandbox/dosgi/felix/framework/src/main/java/org/osgi/service/dsw/DistributionProvider.java (original)
+++ cxf/sandbox/dosgi/felix/framework/src/main/java/org/osgi/service/distribution/DistributionProvider.java Mon Oct 13 09:06:45 2008
@@ -15,7 +15,7 @@
* See the License for the specific language governing permissions and
* limitations under the License.
*/
-package org.osgi.service.dsw;
+package org.osgi.service.distribution;

import java.util.Map;

Modified: cxf/sandbox/dosgi/felix/main/pom.xml
URL: http://svn.apache.org/viewvc/cxf/sandbox/dosgi/felix/main/pom.xml?rev=704146&r1=704145&r2=704146&view=diff
==============================================================================
--- cxf/sandbox/dosgi/felix/main/pom.xml (original)
+++ cxf/sandbox/dosgi/felix/main/pom.xml Mon Oct 13 09:06:45 2008
@@ -165,7 +165,7 @@
<Bundle-Name>Apache Felix</Bundle-Name>
<Bundle-Description>OSGi R4 framework.</Bundle-Description>
<Bundle-Vendor>The Apache Software Foundation</Bundle-Vendor>
- <Private-Package>org.apache.felix.main.*,org.apache.felix.moduleloader.*;-split-package:=merge-first,org.apache.felix.framework.*;-split-package:=merge-first,org.osgi.framework;-split-package:=merge-first,org.osgi.framework.hooks.service;-split-package:=merge-first,org.osgi.service.packageadmin;-split-package:=merge-first,org.osgi.service.startlevel;-split-package:=merge-first,org.osgi.service.url;-split-package:=merge-first,org.osgi.service.discovery;-split-package:=merge-first,org.osgi.service.dsw;-split-package:=merge-first,org.osgi.util.tracker;-split-package:=merge-first</Private-Package>
+ <Private-Package>org.apache.felix.main.*,org.apache.felix.moduleloader.*;-split-package:=merge-first,org.apache.felix.framework.*;-split-package:=merge-first,org.osgi.framework;-split-package:=merge-first,org.osgi.framework.hooks.service;-split-package:=merge-first,org.osgi.service.packageadmin;-split-package:=merge-first,org.osgi.service.startlevel;-split-package:=merge-first,org.osgi.service.url;-split-package:=merge-first,org.osgi.service.discovery;-split-package:=merge-first,org.osgi.service.distribution;-split-package:=merge-first,org.osgi.util.tracker;-split-package:=merge-first</Private-Package>
<Import-Package>!*</Import-Package>
<Include-Resource>META-INF/LICENSE=LICENSE,META-INF/NOTICE=NOTICE,{src/main/resources/}</Include-Resource>
<!-- Include these properties here because we want them

Modified: cxf/sandbox/dosgi/felix/main/src/main/resources/config.properties
URL: http://svn.apache.org/viewvc/cxf/sandbox/dosgi/felix/main/src/main/resources/config.properties?rev=704146&r1=704145&r2=704146&view=diff
==============================================================================
--- cxf/sandbox/dosgi/felix/main/src/main/resources/config.properties (original)
+++ cxf/sandbox/dosgi/felix/main/src/main/resources/config.properties Mon Oct 13 09:06:45 2008
@@ -24,7 +24,7 @@
org.osgi.service.startlevel; version=1.0.0, \
org.osgi.service.url; version=1.0.0, \
org.osgi.service.discovery, \
- org.osgi.service.dsw, \
+ org.osgi.service.distribution, \
org.osgi.util.tracker; version=1.3.2 \
${jre-${java.specification.version}}

From forum: cxf-commits

svn commit: r704141 - in /cxf/sandbox/dosgi/felix/main: pom.xml src/main/resources/config.properties

2008-10-13T08:06:42Z

Author: sergeyb
Date: Mon Oct 13 08:06:42 2008
New Revision: 704141

URL: http://svn.apache.org/viewvc?rev=704141&view=rev
Log:
DOSGI: adding felix eventadmin and pax logging services to the list of required bundles

Modified:
cxf/sandbox/dosgi/felix/main/pom.xml
cxf/sandbox/dosgi/felix/main/src/main/resources/config.properties

Modified: cxf/sandbox/dosgi/felix/main/pom.xml
URL: http://svn.apache.org/viewvc/cxf/sandbox/dosgi/felix/main/pom.xml?rev=704141&r1=704140&r2=704141&view=diff
==============================================================================
--- cxf/sandbox/dosgi/felix/main/pom.xml (original)
+++ cxf/sandbox/dosgi/felix/main/pom.xml Mon Oct 13 08:06:42 2008
@@ -110,7 +110,31 @@
</exclusion>
</exclusions>
</dependency>
-
+ <dependency>
+ <groupId>${pom.groupId}</groupId>
+ <artifactId>org.apache.felix.eventadmin</artifactId>
+ <version>1.0.0</version>
+ <exclusions>
+ <exclusion>
+ <groupId>${pom.groupId}</groupId>
+ <artifactId>org.osgi.compendium</artifactId>
+ </exclusion>
+ <exclusion>
+ <groupId>${pom.groupId}</groupId>
+ <artifactId>org.osgi.core</artifactId>
+ </exclusion>
+ </exclusions>
+ </dependency>
+ <dependency>
+ <groupId>org.ops4j.pax.logging</groupId>
+ <artifactId>pax-logging-api</artifactId>
+ <version>1.1.1</version>
+ </dependency>
+ <dependency>
+ <groupId>org.ops4j.pax.logging</groupId>
+ <artifactId>pax-logging-service</artifactId>
+ <version>1.1.1</version>
+ </dependency>
</dependencies>
<build>
<plugins>
@@ -214,6 +238,30 @@
<overWrite>true</overWrite>
<outputDirectory>${project.build.directory}/bundle</outputDirectory>
</artifactItem>
+ <artifactItem>
+ <groupId>${pom.groupId}</groupId>
+ <artifactId>org.apache.felix.eventadmin</artifactId>
+ <version>1.0.0</version>
+ <type>jar</type>
+ <overWrite>true</overWrite>
+ <outputDirectory>${project.build.directory}/bundle</outputDirectory>
+ </artifactItem>
+ <artifactItem>
+ <groupId>org.ops4j.pax.logging</groupId>
+ <artifactId>pax-logging-api</artifactId>
+ <version>1.1.1</version>
+ <type>jar</type>
+ <overWrite>true</overWrite>
+ <outputDirectory>${project.build.directory}/bundle</outputDirectory>
+ </artifactItem>
+ <artifactItem>
+ <groupId>org.ops4j.pax.logging</groupId>
+ <artifactId>pax-logging-service</artifactId>
+ <version>1.1.1</version>
+ <type>jar</type>
+ <overWrite>true</overWrite>
+ <outputDirectory>${project.build.directory}/bundle</outputDirectory>
+ </artifactItem>
</artifactItems>
</configuration>
</execution>
@@ -250,4 +298,12 @@
</resource>
</resources>
</build>
+ <repositories>
+ <repository>
+ <id>central</id>
+ <name>Default maven repo</name>
+ <url>http://repo1.maven.org/maven2/</url>
+ </repository>
+ </repositories>
+
</project>

Modified: cxf/sandbox/dosgi/felix/main/src/main/resources/config.properties
URL: http://svn.apache.org/viewvc/cxf/sandbox/dosgi/felix/main/src/main/resources/config.properties?rev=704141&r1=704140&r2=704141&view=diff
==============================================================================
--- cxf/sandbox/dosgi/felix/main/src/main/resources/config.properties (original)
+++ cxf/sandbox/dosgi/felix/main/src/main/resources/config.properties Mon Oct 13 08:06:42 2008
@@ -34,7 +34,10 @@
file:bundle/org.apache.felix.shell-1.0.1.jar \
file:bundle/org.apache.felix.shell.tui-1.1.0-cxf_dosgi-SNAPSHOT.jar \
file:bundle/org.apache.felix.bundlerepository-1.0.3.jar \
- file:bundle/org.apache.felix.configadmin-1.0.1.jar
+ file:bundle/org.apache.felix.eventadmin-1.0.0.jar \
+ file:bundle/org.apache.felix.configadmin-1.0.1.jar \
+ file:bundle/pax-logging-api-1.1.1.jar \
+ file:bundle/pax-logging-service-1.1.1.jar

felix.log.level=1
felix.startlevel.framework=1

From forum: cxf-commits

Commented: (CXF-1860) JMS Transport - JMSDestination no room left on workqueue in JMSListenerThread

2008-10-13T07:38:44Z

[ https://issues.apache.org/jira/browse/CXF-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639067#action_12639067 ]

Willem Jiang commented on CXF-1860:
-----------------------------------

Hi Richard,

There are some refacting works of JMS Transport[1][2][3][4] in CXF 2.1.3 snapshot, the JMSDestination has been changed a lot.
Could you try your test cast against latest CXF 2.1.3 snapshot[4] to see if the issue is still there?

[1]https://issues.apache.org/jira/browse/CXF-1773
[2]https://issues.apache.org/jira/browse/CXF-1783
[3]https://issues.apache.org/jira/browse/CXF-1827
[4]https://issues.apache.org/jira/browse/CXF-1832
[5] http://cwiki.apache.org/CXF/download.html

Willem

> JMS Transport - JMSDestination no room left on workqueue in JMSListenerThread
> -----------------------------------------------------------------------------
>
> Key: CXF-1860
> URL: https://issues.apache.org/jira/browse/CXF-1860
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.1.2
> Reporter: Richard Holt
> Priority: Critical
> Attachments: JMSDestination.java
>
>
> when running a mass test against a CXF/JMS endpoint we discovered that our solution was disposing of messages. On further investigation we discovered that the code in the JMSListenerThread when it runs out of threads on the workqueue doesn't loop like the comment suggests but rather disposes of the message.
> We altered the code to follow the comments advice (shown below) and now it calls into the code held in the else statement (which just runs the message in the listener thread, maybe not ideal from an architectural viewpoint but we don't lose messages).
> //FIXME - no room left on workqueue, what to do
> //for now, loop until it WILL fit on the queue,
> //although we could just dispatch on this thread.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: cxf-issues

Re: [VOTE] Release CXF 2.0.9

2008-10-13T07:15:29Z

Hi Christian,

If you want me include your last fix into the CXF 2.0.9.
You need to vote -1 for my current cut version which does not include
the fixing of supporting JMS 1.0.2 by default in CXF JMS transport.
I will cut a new vote version to include it.

If you feel the fix can be include in CXF 2.0.10 or you have some walk
around method, we could add it as an known issue for current CXF 2.0.9
vote version.

Please give me your vote :)

Willem
Christian Schneider wrote:

> +1
>
> Please include my last fix in the release
>
> Willem Jiang schrieb:
> This is a vote to release CXF 2.0.9
>
> Once again, there have been a bunch of bug fixes and enhancements that
> have been done compared to the 2.0.9 release. Over 37 JIRA issues
> are resolved for 2.0.9 which is a large number of fixes for the 2.0.x
> branch.
>
> List of issues:
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&pid=12310511&fixfor=12313314
>
>
> The staging area is at:
> http://people.apache.org/~ningjiang/stage_cxf/2.0.9
>
> The distributions are in the "dist" directory. The "maven" directory
> contains the stuff that will by pushed to the central repository.
>
> This release is tagged at:
> http://svn.apache.org/repos/asf/cxf/tags/cxf-2.0.9
>
>
> Here is my +1. The vote will be open here for at least 72 hours.
>
> Willem
>>
>>

From forum: cxf-dev

Updated: (CXF-1862) Rename org.osgi.service.dsw.DistributionProvider to org.osgi.service.distribution.DistributionProvider

2008-10-13T06:50:44Z

[ https://issues.apache.org/jira/browse/CXF-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Bosschaert updated CXF-1862:
----------------------------------

Attachment: DistributionProvider_PackageRename.patch

Fix provided in the attached patch.

> Rename org.osgi.service.dsw.DistributionProvider to org.osgi.service.distribution.DistributionProvider
> ------------------------------------------------------------------------------------------------------
>
> Key: CXF-1862
> URL: https://issues.apache.org/jira/browse/CXF-1862
> Project: CXF
> Issue Type: Improvement
> Components: OSGi
> Affects Versions: 2.2
> Reporter: David Bosschaert
> Assignee: David Bosschaert
> Attachments: DistributionProvider_PackageRename.patch
>
>

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: cxf-issues

Re: Resource management and cleanup

2008-10-13T06:38:29Z

Hi Ulhas,

Thanks for your last post.

I've removed the Bus creation to a static member of the Handler class I am using. I've got a monitor thread which kicks in every 2 minutes and acts as a heartbeat to a WS. This basically boils down to creating a new instance of the following class and then calling 'process' :

public class WSEnabledHandler {
private static Bus bus = null;
private IDSWSPortType webService = null;

public void process() {
createPortService();

// call the WS
webService.authenticate();

endProcess();
}

private void createPortService() {
if(bus == null) {
bus = BusFactory.newInstance().createBus();
BusFactory.setDefaultBus(bus);
BusFactory.setThreadDefaultBus(bus);
}
JaxWsProxyFactoryBean factory = new JaxWsProxyFactoryBean();
factory.setBus(bus);
factory.setServiceClass(IDSWSPortType.class);
factory.setAddress(wsConfig.getWSDLUrl());
webService = (IDSWSPortType) factory.create();

// turn chunking off
Client client = ClientProxy.getClient(webService);
HTTPConduit httpConduit = (HTTPConduit) client.getConduit();
HTTPClientPolicy httpClientPolicy = new HTTPClientPolicy();
httpClientPolicy.setAllowChunking(false);
httpConduit.setClient(httpClientPolicy);
}
private void endProcess() {
// does nothing, but should it?
}
}

I'm getting a slow leak on memory - roughly 0.7Mb per call. With this background thread, together with user activity (which does similar to above), we're quite quickly running out of memory. Do I need to do anything to explicitly release resources tied up in the JaxWsProxyFactoryBean or Client?

Regards

Matt

From forum: cxf-user

Use SOAP 1.1 and SOAP 1.2 in the same service (Binding)

2008-10-13T06:37:45Z

Hello,

I try to use SOAP 1.1 & 1.2 bindings in the same service but I didn't
find how defining 2 bindings on 1 service.

I try this:

<jaxws:server id="MyService" serviceClass="com.MyService"
address="/MyService">

<jaxws:binding>

<soap:soapBinding id="MyServiceSoap11" version="1.1"/>

<soap:soapBinding id="MyServiceSoap12" version="1.2"/>

</jaxws:binding>

</jaxws:server>

But it only generates one binding :-(

I try also to set list but the result is the same :-(

If someone has a configuration which permits to do this of an idea
please help me ;)

Thanks for reading,

Maxime

This email was sent to you by Thomson Reuters, the global news and information company.
Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Thomson Reuters.

From forum: cxf-user

svn commit: r704117 - /cxf/sandbox/dosgi/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/hooks/CxfListenerHook.java

2008-10-13T06:32:36Z

Author: sergeyb
Date: Mon Oct 13 06:32:35 2008
New Revision: 704117

URL: http://svn.apache.org/viewvc?rev=704117&view=rev
Log:
Excluding system services when doing look ups

Modified:
cxf/sandbox/dosgi/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/hooks/CxfListenerHook.java

Modified: cxf/sandbox/dosgi/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/hooks/CxfListenerHook.java
URL: http://svn.apache.org/viewvc/cxf/sandbox/dosgi/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/hooks/CxfListenerHook.java?rev=704117&r1=704116&r2=704117&view=diff
==============================================================================
--- cxf/sandbox/dosgi/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/hooks/CxfListenerHook.java (original)
+++ cxf/sandbox/dosgi/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/hooks/CxfListenerHook.java Mon Oct 13 06:32:35 2008
@@ -18,6 +18,9 @@
*/
package org.apache.cxf.dosgi.dsw.hooks;

+import java.util.HashSet;
+import java.util.Set;
+import java.util.logging.Logger;
import java.util.regex.Matcher;
import java.util.regex.Pattern;

@@ -28,10 +31,19 @@

public class CxfListenerHook extends AbstractClientHook implements ListenerHook {

+ private static final Logger LOG = Logger.getLogger(CxfListenerHook.class.getName());
+
+
private final static String CLASS_NAME_EXPRESSION =
".*\$" + Constants.OBJECTCLASS + "=([a-zA-Z_0-9.]+)\$.*";
private final static Pattern CLASS_NAME_PATTERN =
Pattern.compile(CLASS_NAME_EXPRESSION);
+ private static final Set<String> SYSTEM_PACKAGES;
+
+ static {
+ SYSTEM_PACKAGES = new HashSet<String>();
+ SYSTEM_PACKAGES.add("org.osgi.service");
+ }

private ThreadLocal<Boolean> findCallsInProgress
= new ThreadLocal<Boolean>() {
@@ -75,10 +87,11 @@
return;
}
String className = getClassNameFromFilter(listener.getFilter());
- if (className == null) {
+ if (!isClassSupported(className)) {
return;
}

+
processClientDescriptions(listener.getBundleContext(),
className,
listener.getFilter(),
@@ -103,8 +116,8 @@
String filter,
boolean allServices) {

- if (className == null) {
- return;
+ if (!isClassSupported(className)) {
+ return;
}

if (isCallInProgress()) {
@@ -130,4 +143,20 @@
private void setCallCompleted() {
findCallsInProgress.set(Boolean.FALSE);
}
+
+
+
+ private static boolean isClassSupported(String className) {
+ if (className == null) {
+ return false;
+ }
+
+ for (String p : SYSTEM_PACKAGES) {
+ if (className.startsWith(p)) {
+ LOG.fine("Lookup for " + className + " is ignored");
+ return false;
+ }
+ }
+ return true;
+ }
}

From forum: cxf-commits

RE: Aegis versus jaxrs

2008-10-13T06:26:15Z

Hi Benson

Lets add AbstractJAXBProvider.setContextProperties(Map<String, Object>)
and pass those props to the JAXBContext creation calls. If none is
explicitly passed from Spring then a default empty Map can be used
instead. In fact, I just removed that code in my previous merge as I
thought there was no use for it.
About Schema : I presume you ask about the one from javax.xml.validation
?
I just added it recently to support the optional schema validation...

Cheers, Sergey

-----Original Message-----
From: Benson Margulies [mailto:bimargulies@...]
Sent: 12 October 2008 12:13
To: dev@...
Subject: Re: Aegis versus jaxrs

I think I finally have a sensible question by analogy with JAXB.

JAXBContext objects have a variety of options and properties. The
JAXBDataBinding allows the CXF app to control these items. The user
can make their own context and inject it into the data binding, or the
user can set various properties of ours that our code uses to tune the
context.

If I'm reading the JAX-RS code correctly, AbstractJAXBProvider just
creates a JAXBContext per package or class and uses it. Any app that
wanted to customize it would be required to make their own subclass of
AbstractJAXBProvider, or so it seems to me. Am I missing anything?

Anyway, I'm going to bang something together.

On Fri, Oct 10, 2008 at 12:42 PM, Sergey Beryozkin
<sergey.beryozkin@...> wrote:

> Hi
>
>> Sergey,
>>
>> I'm not feeling like I'm doing a very good job of explaining myself
>> here. It's probably true that the best way for me to proceed is to
>> code something and with some comments that say: 'Sergey, I'm
>> frustrated HERE.' ...
>
> Yea, please do it :-) ! I do hope though that you wouldn't need to get

into
> the details of the actual
> JAX-RS runtime impl, hopefully you'd be able to craft a basic Aegis
support
> inside the 'shell' of the (Aegis)
> JAX-RS MessageBodyReader/Writer implementation...If we could say limit
the
> support to pure Aegis (that is without it also supporting JAXB - which
is
> something CXF Aegis can do as far as I understand) then it would be
super...

>
> Cheers, Sergey
>
>>
>> --benson
>>
>> On Fri, Oct 10, 2008 at 11:44 AM, Sergey Beryozkin
>> <sergey.beryozkin@...> wrote:
>>>
>>> Hi Benson
>>>
>>> I'm sorry If I'm too slow :-) but I'm still not getting what is it

that
>>> you're proposing.
>>> That said, I believe that may be we should postponse the discussion
on
>>> how
>>> to improve the overall
>>> JAX-RS implementation until after it reaches 1.0.
>>>
>>> In meantime, if we had even a basic JAX-RS Aegis provider such that
>>> peopple
>>> could start doing Aegis and REST or indeed combining SOAP and REST
with
>>> the
>>> help of Aegis, then it would be cool IMHO....
>>>
>>> Cheers, Sergey
>>>
>>>
>>>
>>>> I think I'm beginning to get the idea of what I'm trying to
complain
>>>> about.
>>>>
>>>> An AegisDatabinding object has input configuration and it has
state.

>>>> As it goes along, it constructs mappings for types.
>>>>
>>>> I'm having trouble swallowing a situation in which each individual
>>>> JAX-RS item does this independently, as opposed to all the of the
>>>> items in a service sharing a single state. Am I just confused?
>>>
>>> ----------------------------
>>> IONA Technologies PLC (registered in Ireland)
>>> Registered Number: 171387
>>> Registered Address: The IONA Building, Shelbourne Road, Dublin 4,

Ireland
>>>
>
> ----------------------------
> IONA Technologies PLC (registered in Ireland)
> Registered Number: 171387
> Registered Address: The IONA Building, Shelbourne Road, Dublin 4,
Ireland
>

From forum: cxf-dev

Created: (CXF-1862) Rename org.osgi.service.dsw.DistributionProvider to org.osgi.service.distribution.DistributionProvider

2008-10-13T06:00:44Z

Rename org.osgi.service.dsw.DistributionProvider to org.osgi.service.distribution.DistributionProvider
------------------------------------------------------------------------------------------------------

Key: CXF-1862
URL: https://issues.apache.org/jira/browse/CXF-1862
Project: CXF
Issue Type: Improvement
Components: OSGi
Affects Versions: 2.2
Reporter: David Bosschaert
Assignee: David Bosschaert

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: cxf-issues

Created: (CXF-1861) WSDLQueryHandler error

2008-10-13T05:16:44Z

WSDLQueryHandler error
----------------------

Key: CXF-1861
URL: https://issues.apache.org/jira/browse/CXF-1861
Project: CXF
Issue Type: Bug
Components: Documentation
Affects Versions: 2.0.8
Reporter: Luis Olivera
Priority: Minor

I'm trying to run hello world sample but when I request http://localhost/services/helloWorld?wsdl I got the following error:

java.lang.NoSuchMethodError: org.w3c.dom.Document.setXmlStandalone(Z)V
org.apache.cxf.transport.http.WSDLQueryHandler.updateDoc(WSDLQueryHandler.java:253)
org.apache.cxf.transport.http.WSDLQueryHandler.writeResponse(WSDLQueryHandler.java:201)
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:152)
org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFServlet.java:174)
org.apache.cxf.transport.servlet.AbstractCXFServlet.doGet(AbstractCXFServlet.java:156)
javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

My web.xml is as follow:

<servlet>
<servlet-name>CXFServlet</servlet-name>
<servlet-class>org.apache.cxf.transport.servlet.CXFServlet</servlet-class>
<load-on-startup>2</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>CXFServlet</servlet-name>
<url-pattern>/services/*</url-pattern>
</servlet-mapping>

and I got the following maven lib configuration:

<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-rt-core</artifactId>
<version>2.0.8</version>
</dependency>
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-rt-frontend-simple</artifactId>
<version>2.0.8</version>
</dependency>
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-rt-frontend-jaxws</artifactId>
<version>2.0.8</version>
</dependency>
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-rt-transports-http</artifactId>
<version>2.0.8</version>
</dependency>
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-common-utilities</artifactId>
<version>2.0.8</version>
</dependency>

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: cxf-issues

Problems using encryption together with username token

2008-10-13T04:40:58Z

Hi there,

as the subject says, i have problems to get my web service running with encryption and username token activated. But when I only use encryption everything is fine.

Here is my config for the server:

1) cxf.xml:
<jaxws:inInterceptors>
<bean class="org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor">
<constructor-arg>
<map>
<entry key="action" value="Encrypt UsernameToken" />
<entry key="decryptionPropFile" value="server.properties" />
<entry key="passwordCallbackClass"
value="de.sms_stiewi.services.PwCallbackHandler" />
</map>
</constructor-arg>
</bean>
</jaxws:inInterceptors>

2) server.properties:
org.apache.ws.security.crypto.provider=org.apache.ws.security.components.crypto.Merlin
org.apache.ws.security.crypto.merlin.keystore.type=jks
org.apache.ws.security.crypto.merlin.keystore.alias=serveralias
org.apache.ws.security.crypto.merlin.keystore.password=serversecret
org.apache.ws.security.crypto.merlin.file=serverkeystore.jks

3) PwCallbackHandler Class:
public class PwCallbackHandler implements CallbackHandler {
public void handle(Callback[] callbacks) throws IOException, UnsupportedCallbackException {
WSPasswordCallback passwordCallback = (WSPasswordCallback) callbacks[0];

if (passwordCallback.getIdentifer().equals("Anonymous")) {
passwordCallback.setPassword("secret");
}
}
}

And here the configuration for the client to test it:

1) Interceptor configuration:
WSS4JOutInterceptor wss4jOutInterceptor = new WSS4JOutInterceptor();
wss4jOutInterceptor.setProperty(WSHandlerConstants.ACTION, WSHandlerConstants.USERNAME_TOKEN + " " + WSHandlerConstants.ENCRYPT);
wss4jOutInterceptor.setProperty(WSHandlerConstants.USER, "Anonymous");
wss4jOutInterceptor.setProperty(WSHandlerConstants.PW_CALLBACK_CLASS, "de.sms_stiewi.services.PwCallbackHandler");
wss4jOutInterceptor.setProperty(WSHandlerConstants.ENC_PROP_FILE, "client.properties");

2) client.properties:
org.apache.ws.security.crypto.provider=org.apache.ws.security.components.crypto.Merlin
org.apache.ws.security.crypto.merlin.keystore.type=jks
org.apache.ws.security.crypto.merlin.keystore.alias=clientalias
org.apache.ws.security.crypto.merlin.keystore.password=clientsecret
org.apache.ws.security.crypto.merlin.file=clientkeystore.jks

3) PwCallbackHandler Class:
public class PwCallbackHandler implements CallbackHandler {
public void handle(Callback[] callbacks) throws IOException, UnsupportedCallbackException {
WSPasswordCallback passwordCallback = (WSPasswordCallback) callbacks[0];

passwordCallback.setPassword("secret");
}
}

But if I run the client, i get the following Exception:
org.apache.cxf.binding.soap.SoapFault: Security processing failed.
at org.apache.cxf.ws.security.wss4j.WSS4JOutInterceptor$WSS4JOutInterceptorInternal.handleMessage(WSS4JOutInterceptor.java:234)
at org.apache.cxf.ws.security.wss4j.WSS4JOutInterceptor$WSS4JOutInterceptorInternal.handleMessage(WSS4JOutInterceptor.java:107)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:220)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:296)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:242)
at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:178)
at $Proxy46.importiereKlrStammdaten(Unknown Source)
at de.sms_stiewi.services.MainClient.main(MainClient.java:37)
Caused by: org.apache.ws.security.WSSecurityException: WSHandler: Encryption: error during message processingorg.apache.ws.security.WSSecurityException: General security error (Unexpected number of X509Data: for Encryption)
at org.apache.ws.security.action.EncryptionAction.execute(EncryptionAction.java:65)
at org.apache.ws.security.handler.WSHandler.doSenderAction(WSHandler.java:197)
at org.apache.cxf.ws.security.wss4j.WSS4JOutInterceptor.access$200(WSS4JOutInterceptor.java:47)
at org.apache.cxf.ws.security.wss4j.WSS4JOutInterceptor$WSS4JOutInterceptorInternal.handleMessage(WSS4JOutInterceptor.java:219)
... 8 more

When I only use encryption, I had to set the USER property of the out-interceptor to the alias in the keystore (e.g. "clientalias"). But when I do this with UsernameToken activated, I get the following Exception:
Exception in thread "main" javax.xml.ws.soap.SOAPFaultException: General security error (WSSecurityEngine: Callback supplied no password for: serveralias)
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:199)
at $Proxy46.importiereKlrStammdaten(Unknown Source)
at de.sms_stiewi.services.MainClient.main(MainClient.java:37)
Caused by: org.apache.cxf.binding.soap.SoapFault: General security error (WSSecurityEngine: Callback supplied no password for: serveralias)
at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:70)
at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:35)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:220)
at org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:96)
at org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:69)
at org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:34)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:220)
at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:449)
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:2029)
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1865)
at org.apache.cxf.io.CacheAndWriteOutputStream.postClose(CacheAndWriteOutputStream.java:47)
at org.apache.cxf.io.CachedOutputStream.close(CachedOutputStream.java:170)
at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66)
at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:593)
at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:220)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:296)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:242)
at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:178)
... 2 more

If someone can help me, I would be very thankful.

Greetings
Christian

From forum: cxf-user

Re: Memory leak in CXF HTTP transport in Solaris ?

2008-10-13T04:14:37Z

Dear Bharat,

1. I have tested on three OS Env
             >Win XP
             >Solaris 10
             >SuSE Linux (on ATCA)

2. Yes, on windows the behavior is not- alarming. Its stable. But solaris and Linux shows a memory Increase, as i have explained in the prev Post.

3. I have used JConsole and rational Purify to monitor the Heap/non-heap/Perm Generations of Memory.
"prstat" utility was used on Solaris to observe the memory claimed by the process.Also "pmap"

4. <i>//The memory of the server continously increases from ~90M to ~350M which
never comes down.
How did you check this?</i>
At startup prstat gives a value around 80M Resident Memory and total Mem 164M. After the load testing (around 800,000 continuous requests) the value goes very high, ie 325M RSS and 388M Total Memory.
At the same time Heap shows negligible increase after GC, as i have shown in the table.

One word about the table:
Table has the following columns
     > Total Mem as shown in prstat
     > RSS Mem as shown in prstat
            eg:
PID USERNAME SIZE   RSS STATE PRI NICE      TIME CPU PROCESS/NLWP
3769 root      207M 124M sleep   59    0   0:02:09 4.4% java/40
    and..
     >Used
     >Commited
     >Maximum allowed
Memory as per JConsole of JDK 5
And the RSS and total mem used for the process never goes down from the high
value even after GC (but this is the behavior of process on Solaris ?)
5. This memory Increase happens only in HTTP transport. in JMS its fine, as Hubert observed.

6. I can send the pmap dump and other details, if required.

anoopPrasad

Two roads diverged in a wood, and I -- I took the one less traveled by, and that has made all the difference!

HUAWEI TECHNOLOGIES CO.,LTD.

Address: Huawei Industrial Base
Bantian Longgang
Shenzhen 518129, P.R.China
www.huawei.com
-------------------------------------------------------------------------------------------------------------------------------------
This e-mail and its attachments contain confidential information from HUAWEI, which
is intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!

From forum: cxf-dev

Updated: (CXF-1860) JMS Transport - JMSDestination no room left on workqueue in JMSListenerThread

2008-10-13T03:26:44Z

[ https://issues.apache.org/jira/browse/CXF-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Holt updated CXF-1860:
------------------------------

Attachment: JMSDestination.java

fix to allow the messages to post to the listener thread

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: cxf-issues

Created: (CXF-1860) JMS Transport - JMSDestination no room left on workqueue in JMSListenerThread

2008-10-13T03:26:44Z

JMS Transport - JMSDestination no room left on workqueue in JMSListenerThread
-----------------------------------------------------------------------------

Key: CXF-1860
URL: https://issues.apache.org/jira/browse/CXF-1860
Project: CXF
Issue Type: Bug
Components: Transports
Affects Versions: 2.1.2
Reporter: Richard Holt
Priority: Critical
Attachments: JMSDestination.java

when running a mass test against a CXF/JMS endpoint we discovered that our solution was disposing of messages. On further investigation we discovered that the code in the JMSListenerThread when it runs out of threads on the workqueue doesn't loop like the comment suggests but rather disposes of the message.

We altered the code to follow the comments advice (shown below) and now it calls into the code held in the else statement (which just runs the message in the listener thread, maybe not ideal from an architectural viewpoint but we don't lose messages).

//FIXME - no room left on workqueue, what to do
//for now, loop until it WILL fit on the queue,
//although we could just dispatch on this thread.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: cxf-issues

RE: Change the bindingName

2008-10-13T03:16:13Z

Hello Daniel,

I tried to add the bindingNamePostfix but it didn't work :(

I see in the different XSD that soapBinding can only accept:
- mtomEnabled, version, style, use.

None about the bindingName nor bindingNamePostfix...

But I succeed when I defined a new BindingConfiguration class like you
said previously here:
http://markmail.org/message/6qqguevxo4sxkzsw#query:bindingName%20cxf+pag
e:1+mid:e5zzcovmprd3mtbi+state:results

Thanks again for your help.

-----Original Message-----
From: Daniel Kulp [mailto:dkulp@...]
Sent: 10 October 2008 19:39
To: users@...
Cc: Maxime Orain
Subject: Re: Change the bindingName

There certainly isn't an "easy" way to do this. Nothing in any of the
specs
really allows control over this.

In spring config, you can specify a binding configuration object. The
SoapBindingConfiguration object has a bindingNamePostfix which can be
configured in Spring to reset it to something else. Kind of like:

<jaxws:endpoint id="simpleWithBinding"
implementor="#greeter"
address="http://localhost:8080/simpleWithAddress3">
<jaxws:binding>
<soap:soapBinding bindingNamePostfix="HttpBinding"/>
</jaxws:binding>
</jaxws:endpoint>

(I think, haven't actually tried it)

Dan

On Friday 10 October 2008 12:56:05 pm Maxime Orain wrote:

> Re Hello to all!
>
>
>
> When I generate the WSDL from Java I get my Binding name set to :
> SERVICE_NAME + "SoapBinding"
>
>
>
> Is there a way to change this?
>
>
>
> I would change it to SERVICE_NAME + "HttpBinding" (Like XFire did it)
>
>
>
> Thanks for your help!
>
>
>
>
>
> This email was sent to you by Thomson Reuters, the global news and
> information company. Any views expressed in this message are those of

the
> individual sender, except where the sender specifically states them to
be
> the views of Thomson Reuters.

--
Daniel Kulp
dkulp@...
http://dankulp.com/blog

This email was sent to you by Thomson Reuters, the global news and information company.
Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Thomson Reuters.

From forum: cxf-user

Created: (CXF-1859) mtom-enabled property case sensitive

2008-10-13T03:00:44Z

mtom-enabled property case sensitive
------------------------------------

Key: CXF-1859
URL: https://issues.apache.org/jira/browse/CXF-1859
Project: CXF
Issue Type: Bug
Components: Configuration
Affects Versions: 2.0.8
Environment: jdk1.5
Reporter: Adrian Corcoran
Priority: Minor

Setting of jax-ws endpoint property mtom-enabled is case sensitive - setting value to 'TRUE' rather than 'true' will not enable mtom.

The root of this problem is in MessageUtils.

public static boolean isTrue(Object value) {
if (Boolean.TRUE.equals(value) || "true".equals(value)) {
return true;
}

return false;
}

This should obviously be

public static boolean isTrue(Object value) {
return Boolean.valueOf(value.toString());
}

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: cxf-issues

Intercept http 302 response

2008-10-13T02:37:01Z

Hi,

I'm using a jax-ws webservice generated from WSDL. It's SOAP document style and everything works fine. The server is protected by Suns Policy agent, so the client passes a session token as a cookie in the http header. However, if the token is incorrect, the policy agent will return an empty http 302 redirect message. This has no body and so the client throws a SOAP fault.

Would anyone know what kind of interceptor I need to write for the client that will catch the 302 response before CXF tries to parse the SOAP body? Also, how would I exit the chain without the rest of the interceptors being called?

Thanks for any help..
Here's the code to setup my client..

QName serviceName = new QName("http://tempuri.org/", "MyService");
QName portName = new QName("http://tempuri.org/", "BasicHttpBinding_IMyService");
String address = "http://sample.com/Webservices/MyService/Service.svc";

// create port
Service service = Service.create(serviceName);
service.addPort(portName, SOAPBinding.SOAP11HTTP_BINDING, address);
servicePort = (IMyService)service.getPort(portName, IMyService.class);

From forum: cxf-user

Re: Memory leak in CXF HTTP transport in Solaris ?

2008-10-13T01:36:25Z

I have verified the same test on Windows with the same JDK. My memory usage
looks stable.
Could anyone try on Solaris?

Anoop,

Have you tried the test on any non-solaris OS?
//The memory of the server continously increases from ~90M to ~350M which
never comes down.
How did you check this?

Thanks,
Bharath

On Fri, Oct 10, 2008 at 5:39 PM, anoopPrasad <anoopp@...> wrote:

>
> Dear Bharat,
>
> I have observed the same behavior. Allow me to present the details u seek.
>
> Server:
> Created a Sample HTTP Service with CXF 2.0.3(publishing Greeter interface
> provided in sample )
> Service was published using :
> Endpoint ep = Endpoint.publish("http://localhost:9000/Greeter", new
> GreeterImpl());
> and GreeterImpl has "String greetMe(String me)" which just returns a
> string.
> Server is running on a Solaris 10 machine with java version "1.5.0_14"
> Server does nothing else.
>
> The libs in classpath are
> -classpath
>
> lib:/lib/cxf/asm-2.2.3.jar:lib/cxf/commons-logging-1.1.jar:lib/cxf/cxf-2.0.3-incubator.jar:lib/cxf/geronimo-activation_1.1_spec-1.
>
> 0-M1.jar:lib/cxf/geronimo-annotation_1.0_spec-1.1.jar:lib/cxf/geronimo-javamail_1.4_spec-1.0-M1.jar:lib/cxf/geronimo-jms_1.1_spec-
>
> 1.1.jar:lib/cxf/geronimo-servlet_2.5_spec-1.1-M1.jar:lib/cxf/geronimo-ws-metadata_2.0_spec-1.1.1.jar:lib/cxf/jaxb-api-2.0.jar:lib/
>
> cxf/jaxb-impl-2.0.5.jar:lib/cxf/jaxb-xjc-2.0.jar:lib/cxf/jaxen-1.1.jar:lib/cxf/jaxws-api-2.0.jar:lib/cxf/jetty-6.1.12.rc2.jar:lib/
>
> cxf/jetty-util-6.1.12.rc2.jar:lib/cxf/jra-1.0-alpha-4.jar:lib/cxf/js-1.6R5.jar:lib/cxf/neethi-2.0.2.jar:lib/cxf/saaj-api-1.3.jar:l
>
> ib/cxf/saaj-impl-1.3.jar:lib/cxf/slf4j-api-1.3.1.jar:lib/cxf/slf4j-jdk14-1.3.1.jar:lib/cxf/spring-beans-2.0.6.jar:lib/cxf/spring-c
>
> ontext-2.0.6.jar:lib/cxf/spring-core-2.0.6.jar:lib/cxf/stax-api-1.0.1.jar:lib/cxf/stax-utils-20060502.jar:lib/cxf/wsdl4j-1.6.1.jar
>
> :lib/cxf/wss4j-1.5.1.jar:lib/cxf/wstx-asl-3.2.1.jar:lib/cxf/xalan-2.7.0.jar:lib/cxf/xbean-2.2.0.jar:lib/cxf/xml-apis-1.3.02.jar:li
>
> b/cxf/xml-resolver-1.2.jar:lib/cxf/XmlSchema-1.3.2.jar:lib/activemq-core-5.0.0.jar:lib/geronimo-j2ee-management_1.0_spec-1.0.jar
>
> Server is run with JVM parameters "-Xmx129m -XX:MaxPermSize=128m ". No
> other
> tuning parameters added in server[However, a lot of other tuning were tried
> (like, -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled
> -XX:+CMSPermGenSweepingEnabled) and found that the result is not favorable]
>
> Client:
> Client written in CXF, sends requests continuously to the server.(infinite
> loop)
>
> Behavior:
> The memory of the server continously increases from ~90M to ~350M which
> never comes down.
> But through jconsole we know that the Heap, or non-heap memory hasn't
> increased much.
> Below table contains mem usage details over a period of 1Hr (800,000
> Request/Response)
>
> prstat Heap Non-Heap
> CMS PermGen
> Total RSS Used Comitd Max Used Comitd Max
> Used Comitd Max
> 176 103 3 36 120 16 30 163
> 14 28 131
> 184 124 2 35 120 20 24 163
> 16 20 131
> 184 129 2 13 120 22 25 163
> 16 20 131
> 200 145 2 19 120 22 25 163
> 16 20 131
> 204 149 2 45 120 22 25 163
> 16 20 131
> 253 207 5 18 120 19 20 163
> 14 16 131
>
> Same test was carried out with CXF Version 2.1.2 and it behaves the same
> way.
>
>
>
> OS : Solaris 10
> root@SUN50 # psrinfo -v
> Status of virtual processor 0 as of: 03/31/2000 22:38:54
> on-line since 03/25/2000 04:24:44.
> The sparcv9 processor operates at 1593 MHz,
> and has a sparcv9 floating point processor.
> Status of virtual processor 1 as of: 03/31/2000 22:38:54
> on-line since 03/25/2000 04:24:44.
> The sparcv9 processor operates at 1593 MHz,
> and has a sparcv9 floating point processor.
> Status of virtual processor 2 as of: 03/31/2000 22:38:54
> on-line since 03/25/2000 04:24:44.
> The sparcv9 processor operates at 1593 MHz,
> and has a sparcv9 floating point processor.
> Status of virtual processor 3 as of: 03/31/2000 22:38:54
> on-line since 03/25/2000 04:24:43.
> The sparcv9 processor operates at 1593 MHz,
> and has a sparcv9 floating point processor.
>
> root@SUN50 # prtconf | grep Memory
> Memory size: 8192 Megabytes
>
>
> Please help us identify the reason for this mem increase.
>
> regards
> anoopPrasad
>
>
>
> bharath-5 wrote:
> >
> > Hi Hubert,
> >
> > Is the leak replicable? Is is that the memory was just high or it was a
> > leak? Did you see an OOM?
> > Will be of great help if you can send the test case.
> > Also let me know which CXF version you are using?
> >
> > Thanks,
> > Bharath
> > IBM - India Software Labs
> >
> > http://thoughts.bharathganesh.com
> >
> > On Tue, Sep 23, 2008 at 5:36 AM, Sky-Tiger
> > <darktemplarster@...>wrote:
> >
> >>
> >> Dear Dan,
> >> I wrote a very simple application using CXF, just like Helloworld.
> >> Firstly, I run the application using JMS as tranport layer,
> >> erverything is ok.
> >> But when i change the JMS with HTTP, I find the memory will
> >> increase
> >> slowly. And such increasing can not be checked by Jconsole.
> >> Are there some issues in CXF or Jetty for memory leak?
> >>
> >> Regards
> >>
> >> Hubert.
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Memory-leak--tp19619011p19619011.html
> >> Sent from the cxf-dev mailing list archive at Nabble.com.
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Memory-leak--tp19619011p19917037.html
> Sent from the cxf-dev mailing list archive at Nabble.com.
>
>

From forum: cxf-dev

Issues with Attachments: week of 2008-10-13

2008-10-13T01:14:00Z

CXF - Monday, October 13, 2008

13 Issues with Attachments

(sorted oldest to newest)

[CXF-1648] org.apache.cxf.binding.soap.SoapFault: Error reading XMLStreamReader.
(2008-06-12 - Sub-task - victor escutia)
http://issues.apache.org/jira/browse/CXF-1648

[CXF-1785] wsdlLocation attribute and XmlBeans: Getting NullPointerException/UNMARSHALL_ERROR
(2008-09-05 - Bug - Juan Velez)
http://issues.apache.org/jira/browse/CXF-1785

[CXF-1817] wsdl2java RandomValueProvider gives StackOverflowException on bidirectional reference
(2008-09-23 - Bug - Bob Fields)
http://issues.apache.org/jira/browse/CXF-1817

[CXF-1818] java2ws -createxsdimports with packages that reference other packages should have schemaLocation in schema import
(2008-09-23 - Bug - Bob Fields)
http://issues.apache.org/jira/browse/CXF-1818

[CXF-1828] inFaultInterceptors doesn't work as expected
(2008-09-27 - Bug - Dmitry)
http://issues.apache.org/jira/browse/CXF-1828

[CXF-1829] xmlbean binding can not handle Exception
(2008-09-28 - Bug - quzhe)
http://issues.apache.org/jira/browse/CXF-1829

[CXF-1832] Third step of Refactoring JMS Transport
(2008-09-29 - Improvement - Christian Schneider)
http://issues.apache.org/jira/browse/CXF-1832

[CXF-1841] Some issues with outbound jca connector
(2008-10-06 - Bug - William Tam)
http://issues.apache.org/jira/browse/CXF-1841

[CXF-1846] Attribute namespaces added in handler are not preserved after processing by interceptors
(2008-10-07 - Bug - Jonathan Miller)
http://issues.apache.org/jira/browse/CXF-1846

[CXF-1847] AttachmentDeserializer cannot handle attachments with Quoted Printable content transfer encoding
(2008-10-07 - Bug - aaron pieper)
http://issues.apache.org/jira/browse/CXF-1847

[CXF-1850] org.apache.cxf.endpoint.ServerImpl does not shut down destination in stop() when MultipleEndpointObserver is used.
(2008-10-08 - Bug - Gyorgy Orban)
http://issues.apache.org/jira/browse/CXF-1850

[CXF-1852] Provider classes must implement Provider<T> even when superclass does
(2008-10-09 - Bug - Andrew Clegg)
http://issues.apache.org/jira/browse/CXF-1852

[CXF-1854] Create a multi-bundle distribution of DOSGi - DSW
(2008-10-09 - Improvement - David Bosschaert)
http://issues.apache.org/jira/browse/CXF-1854

From forum: cxf-issues