From rsearls at redhat.com Tue May 6 17:10:37 2014 From: rsearls at redhat.com (Rebecca Searls) Date: Tue, 6 May 2014 17:10:37 -0400 (EDT) Subject: [jbossws-dev] JXM bean, ServerConfig access question In-Reply-To: <2102379769.2379261.1399410626984.JavaMail.zimbra@redhat.com> Message-ID: <1308919150.2379321.1399410637862.JavaMail.zimbra@redhat.com> I'm adding a new property to ServerConfig. I have confirmed that my sample app works properly. I've hit a snag when adding a test to (https://svn.jboss.org/repos/jbossws/stack/cxf/branches/rsearls) modules/testsuite/shared-tests/src/test/java/org/jboss/test/ws/jaxws/jbws2150/JBWS2150TestCaseForked.java The exiting test updates a like property as follows Attribute attr = new Attribute("WebServiceHost", value); getServer().setAttribute(SERVER_CONFIG_OBJECT_NAME, attr); On the server side org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer is being called. In JBWS2150TestCaseForked I am setting my property in a like manner. Attribute attr = new Attribute("WebServicePath", value); getServer().setAttribute(SERVER_CONFIG_OBJECT_NAME, at However it fails, "WebServicePath" is not found. This seems to be a JMX bean setup issues. Any advise as to how to resolve would be appreciated. From ema at redhat.com Wed May 7 03:06:14 2014 From: ema at redhat.com (Jim Ma) Date: Wed, 07 May 2014 15:06:14 +0800 Subject: [jbossws-dev] JXM bean, ServerConfig access question In-Reply-To: <1308919150.2379321.1399410637862.JavaMail.zimbra@redhat.com> References: <1308919150.2379321.1399410637862.JavaMail.zimbra@redhat.com> Message-ID: <5369DB66.9040809@redhat.com> Did you add the getter and setter for the "WebServicePat" in ServerConfig ? On 05/07/2014 05:10 AM, Rebecca Searls wrote: > > I'm adding a new property to ServerConfig. I have confirmed that my sample > app works properly. I've hit a snag when adding a test to (https://svn.jboss.org/repos/jbossws/stack/cxf/branches/rsearls) > modules/testsuite/shared-tests/src/test/java/org/jboss/test/ws/jaxws/jbws2150/JBWS2150TestCaseForked.java > The exiting test updates a like property as follows > > Attribute attr = new Attribute("WebServiceHost", value); > getServer().setAttribute(SERVER_CONFIG_OBJECT_NAME, attr); > > On the server side org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer is being > called. > > In JBWS2150TestCaseForked I am setting my property in a like manner. > > Attribute attr = new Attribute("WebServicePath", value); > getServer().setAttribute(SERVER_CONFIG_OBJECT_NAME, at > > However it fails, "WebServicePath" is not found. > This seems to be a JMX bean setup issues. > > Any advise as to how to resolve would be appreciated. > > _______________________________________________ > jbossws-dev mailing list > jbossws-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbossws-dev From rsearls at redhat.com Wed May 7 10:29:27 2014 From: rsearls at redhat.com (Rebecca Searls) Date: Wed, 7 May 2014 10:29:27 -0400 (EDT) Subject: [jbossws-dev] JXM bean, ServerConfig access question In-Reply-To: <5369DB66.9040809@redhat.com> References: <1308919150.2379321.1399410637862.JavaMail.zimbra@redhat.com> <5369DB66.9040809@redhat.com> Message-ID: <457341980.3101711.1399472967057.JavaMail.zimbra@redhat.com> Hi Jim, This enhancement crosses 4 repos. I've implemented the getters and setters as follows. 1 In repo jbossws/spi the interface file is src/main/java/org/jboss/wsf/spi/management/ServerConfig.java I added stmts String getWebServicePath(); void setWebServicePath(String path); 2 In repo jbossws/container/wildfly80 I added impls of the ServerConfig methods to server-integration/src/main/java/org/jboss/as/webservices/config/ServerConfigImpl.java 3 And these changes are mirrored in wildfly-next/webservices/server-integration And I added the following test to server-integration/src/test/java/org/jboss/as/webservices/config/ServerConfigImplTestCase.java and that runs successfully. internalTestSingleAttributeUpdate(new Callback() { @Override public void setAttribute(ServerConfig sc) throws Exception { sc.setWebServicePath("MY/TEST/PATH"); } }); 4 In repo jbossws/common file src/main/java/org/jboss/ws/common/management/AbstractServerConfig.java has impls public String getWebServicePath() public void setWebServicePath(String path) Finally there is an archive build hierarchy of these repos. I created SNAPSHOT versions of these repos and updated the pom files. Here is the dep tree. I've checked that I have the proper version ref. + wildfly-webservices:8.0.1.Final-SNAPSHOT - jbossws-cxf - jbossws-common - jbossws-spi + jbossws-cxf - jbossws-wildfly800-parent - jbossws-common - jbossws-spi + jbossws-wildfly800-parent - jbossws-common - jbossws-spi + jbossws-common - jbossws-spi I think I'm missing some ref specifically related to the JMX bean config. I was able to back track the execution thread to org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer where it fails to find "WebServicePath", but I'm baffled as to what else I'm missing since "WebServiceHost" is found. ----- Original Message ----- > From: "Jim Ma" > To: "Rebecca Searls" > Cc: jbossws-dev at lists.jboss.org > Sent: Wednesday, May 7, 2014 3:06:14 AM > Subject: Re: [jbossws-dev] JXM bean, ServerConfig access question > > Did you add the getter and setter for the "WebServicePat" in ServerConfig ? > > > On 05/07/2014 05:10 AM, Rebecca Searls wrote: > > > > I'm adding a new property to ServerConfig. I have confirmed that my sample > > app works properly. I've hit a snag when adding a test to > > (https://svn.jboss.org/repos/jbossws/stack/cxf/branches/rsearls) > > modules/testsuite/shared-tests/src/test/java/org/jboss/test/ws/jaxws/jbws2150/JBWS2150TestCaseForked.java > > The exiting test updates a like property as follows > > > > Attribute attr = new Attribute("WebServiceHost", value); > > getServer().setAttribute(SERVER_CONFIG_OBJECT_NAME, attr); > > > > On the server side > > org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer is being > > called. > > > > In JBWS2150TestCaseForked I am setting my property in a like manner. > > > > Attribute attr = new Attribute("WebServicePath", value); > > getServer().setAttribute(SERVER_CONFIG_OBJECT_NAME, at > > > > However it fails, "WebServicePath" is not found. > > This seems to be a JMX bean setup issues. > > > > Any advise as to how to resolve would be appreciated. > > > > _______________________________________________ > > jbossws-dev mailing list > > jbossws-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/jbossws-dev > > From asoldano at redhat.com Wed May 7 10:39:42 2014 From: asoldano at redhat.com (Alessio Soldano) Date: Wed, 07 May 2014 16:39:42 +0200 Subject: [jbossws-dev] JXM bean, ServerConfig access question In-Reply-To: <457341980.3101711.1399472967057.JavaMail.zimbra@redhat.com> References: <1308919150.2379321.1399410637862.JavaMail.zimbra@redhat.com> <5369DB66.9040809@redhat.com> <457341980.3101711.1399472967057.JavaMail.zimbra@redhat.com> Message-ID: <536A45AE.8000109@redhat.com> Hi Rebecca, by scanning you commits, I believe you might have forgotten to modify the org.jboss.ws.common.management.AbstractServerConfigMBean which is the interface defining what is exposed on JMX by the ServerConfig. Cheers Alessio On 07/05/14 16:29, Rebecca Searls wrote: > Hi Jim, > > This enhancement crosses 4 repos. I've implemented the getters and setters as > follows. > > 1 In repo jbossws/spi the interface file is src/main/java/org/jboss/wsf/spi/management/ServerConfig.java > I added stmts > String getWebServicePath(); > void setWebServicePath(String path); > > 2 In repo jbossws/container/wildfly80 > I added impls of the ServerConfig methods to server-integration/src/main/java/org/jboss/as/webservices/config/ServerConfigImpl.java > 3 And these changes are mirrored in wildfly-next/webservices/server-integration > > And I added the following test to server-integration/src/test/java/org/jboss/as/webservices/config/ServerConfigImplTestCase.java > and that runs successfully. > > internalTestSingleAttributeUpdate(new Callback() { > @Override > public void setAttribute(ServerConfig sc) throws Exception { > sc.setWebServicePath("MY/TEST/PATH"); > } > }); > > 4 In repo jbossws/common file src/main/java/org/jboss/ws/common/management/AbstractServerConfig.java > has impls > public String getWebServicePath() > public void setWebServicePath(String path) > > Finally there is an archive build hierarchy of these repos. I created SNAPSHOT > versions of these repos and updated the pom files. Here is the dep tree. > I've checked that I have the proper version ref. > > + wildfly-webservices:8.0.1.Final-SNAPSHOT > - jbossws-cxf > - jbossws-common > - jbossws-spi > + jbossws-cxf > - jbossws-wildfly800-parent > - jbossws-common > - jbossws-spi > + jbossws-wildfly800-parent > - jbossws-common > - jbossws-spi > + jbossws-common > - jbossws-spi > > > I think I'm missing some ref specifically related to the JMX bean config. > I was able to back track the execution thread to org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer > where it fails to find "WebServicePath", but I'm baffled as to what else I'm > missing since "WebServiceHost" is found. > > > > ----- Original Message ----- >> From: "Jim Ma" >> To: "Rebecca Searls" >> Cc: jbossws-dev at lists.jboss.org >> Sent: Wednesday, May 7, 2014 3:06:14 AM >> Subject: Re: [jbossws-dev] JXM bean, ServerConfig access question >> >> Did you add the getter and setter for the "WebServicePat" in ServerConfig ? >> >> >> On 05/07/2014 05:10 AM, Rebecca Searls wrote: >>> >>> I'm adding a new property to ServerConfig. I have confirmed that my sample >>> app works properly. I've hit a snag when adding a test to >>> (https://svn.jboss.org/repos/jbossws/stack/cxf/branches/rsearls) >>> modules/testsuite/shared-tests/src/test/java/org/jboss/test/ws/jaxws/jbws2150/JBWS2150TestCaseForked.java >>> The exiting test updates a like property as follows >>> >>> Attribute attr = new Attribute("WebServiceHost", value); >>> getServer().setAttribute(SERVER_CONFIG_OBJECT_NAME, attr); >>> >>> On the server side >>> org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer is being >>> called. >>> >>> In JBWS2150TestCaseForked I am setting my property in a like manner. >>> >>> Attribute attr = new Attribute("WebServicePath", value); >>> getServer().setAttribute(SERVER_CONFIG_OBJECT_NAME, at >>> >>> However it fails, "WebServicePath" is not found. >>> This seems to be a JMX bean setup issues. >>> >>> Any advise as to how to resolve would be appreciated. >>> >>> _______________________________________________ >>> jbossws-dev mailing list >>> jbossws-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbossws-dev >> > _______________________________________________ > jbossws-dev mailing list > jbossws-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbossws-dev -- Alessio Soldano Web Service Lead, JBoss From rsearls at redhat.com Wed May 7 14:25:04 2014 From: rsearls at redhat.com (Rebecca Searls) Date: Wed, 7 May 2014 14:25:04 -0400 (EDT) Subject: [jbossws-dev] JXM bean, ServerConfig access question In-Reply-To: <536A45AE.8000109@redhat.com> References: <1308919150.2379321.1399410637862.JavaMail.zimbra@redhat.com> <5369DB66.9040809@redhat.com> <457341980.3101711.1399472967057.JavaMail.zimbra@redhat.com> <536A45AE.8000109@redhat.com> Message-ID: <808201993.3243138.1399487104771.JavaMail.zimbra@redhat.com> Yep, that was the missing piece. Thanks. ----- Original Message ----- > From: "Alessio Soldano" > To: "Rebecca Searls" > Cc: "Jim Ma" , jbossws-dev at lists.jboss.org > Sent: Wednesday, May 7, 2014 10:39:42 AM > Subject: Re: [jbossws-dev] JXM bean, ServerConfig access question > > Hi Rebecca, > by scanning you commits, I believe you might have forgotten to modify > the org.jboss.ws.common.management.AbstractServerConfigMBean which is > the interface defining what is exposed on JMX by the ServerConfig. > Cheers > Alessio > > On 07/05/14 16:29, Rebecca Searls wrote: > > Hi Jim, > > > > This enhancement crosses 4 repos. I've implemented the getters and setters > > as > > follows. > > > > 1 In repo jbossws/spi the interface file is > > src/main/java/org/jboss/wsf/spi/management/ServerConfig.java > > I added stmts > > String getWebServicePath(); > > void setWebServicePath(String path); > > > > 2 In repo jbossws/container/wildfly80 > > I added impls of the ServerConfig methods to > > server-integration/src/main/java/org/jboss/as/webservices/config/ServerConfigImpl.java > > 3 And these changes are mirrored in > > wildfly-next/webservices/server-integration > > > > And I added the following test to > > server-integration/src/test/java/org/jboss/as/webservices/config/ServerConfigImplTestCase.java > > and that runs successfully. > > > > internalTestSingleAttributeUpdate(new Callback() { > > @Override > > public void setAttribute(ServerConfig sc) throws Exception { > > sc.setWebServicePath("MY/TEST/PATH"); > > } > > }); > > > > 4 In repo jbossws/common file > > src/main/java/org/jboss/ws/common/management/AbstractServerConfig.java > > has impls > > public String getWebServicePath() > > public void setWebServicePath(String path) > > > > Finally there is an archive build hierarchy of these repos. I created > > SNAPSHOT > > versions of these repos and updated the pom files. Here is the dep tree. > > I've checked that I have the proper version ref. > > > > + wildfly-webservices:8.0.1.Final-SNAPSHOT > > - jbossws-cxf > > - jbossws-common > > - jbossws-spi > > + jbossws-cxf > > - jbossws-wildfly800-parent > > - jbossws-common > > - jbossws-spi > > + jbossws-wildfly800-parent > > - jbossws-common > > - jbossws-spi > > + jbossws-common > > - jbossws-spi > > > > > > I think I'm missing some ref specifically related to the JMX bean config. > > I was able to back track the execution thread to > > org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer > > where it fails to find "WebServicePath", but I'm baffled as to what else > > I'm > > missing since "WebServiceHost" is found. > > > > > > > > ----- Original Message ----- > >> From: "Jim Ma" > >> To: "Rebecca Searls" > >> Cc: jbossws-dev at lists.jboss.org > >> Sent: Wednesday, May 7, 2014 3:06:14 AM > >> Subject: Re: [jbossws-dev] JXM bean, ServerConfig access question > >> > >> Did you add the getter and setter for the "WebServicePat" in ServerConfig > >> ? > >> > >> > >> On 05/07/2014 05:10 AM, Rebecca Searls wrote: > >>> > >>> I'm adding a new property to ServerConfig. I have confirmed that my > >>> sample > >>> app works properly. I've hit a snag when adding a test to > >>> (https://svn.jboss.org/repos/jbossws/stack/cxf/branches/rsearls) > >>> modules/testsuite/shared-tests/src/test/java/org/jboss/test/ws/jaxws/jbws2150/JBWS2150TestCaseForked.java > >>> The exiting test updates a like property as follows > >>> > >>> Attribute attr = new Attribute("WebServiceHost", value); > >>> getServer().setAttribute(SERVER_CONFIG_OBJECT_NAME, attr); > >>> > >>> On the server side > >>> org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer is being > >>> called. > >>> > >>> In JBWS2150TestCaseForked I am setting my property in a like manner. > >>> > >>> Attribute attr = new Attribute("WebServicePath", value); > >>> getServer().setAttribute(SERVER_CONFIG_OBJECT_NAME, at > >>> > >>> However it fails, "WebServicePath" is not found. > >>> This seems to be a JMX bean setup issues. > >>> > >>> Any advise as to how to resolve would be appreciated. > >>> > >>> _______________________________________________ > >>> jbossws-dev mailing list > >>> jbossws-dev at lists.jboss.org > >>> https://lists.jboss.org/mailman/listinfo/jbossws-dev > >> > > _______________________________________________ > > jbossws-dev mailing list > > jbossws-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/jbossws-dev > > > -- > Alessio Soldano > Web Service Lead, JBoss > > From asoldano at redhat.com Wed May 14 13:29:51 2014 From: asoldano at redhat.com (Alessio Soldano) Date: Wed, 14 May 2014 19:29:51 +0200 Subject: [jbossws-dev] Changes to target containers on JBossWS trunk Message-ID: <5373A80F.2090908@redhat.com> Folks, FYI, I've just committed a bunch of changes to make JBossWS-CXF trunk consume jbossws-spi 3.0.0-SNAPSHOT and jbossws-common 3.0.0-SNAPSHOT. The AS720 and WFLY800 integration layers have been updated accordingly and 5.0.0-SNAPSHOT versions of them are consumed by the stack. I've also modified the wilfly810 target, which currently uses the WildFly 8.0.0.CR2 release (will change that to 8.0.0.Final once that's released too). Finally, a new wildfly900 target is available: due to the above mentioned changes to jbossws-spi, the wildfly master is not usable as is, so for now my fork here can be used: https://github.com/asoldano/wildfly/commits/jbossws5 Tomorrow I'll update the Hudson instance on jbossws-qa.jboss.org. Cheers Alessio -- Alessio Soldano Web Service Lead, JBoss From asoldano at redhat.com Thu May 15 13:47:04 2014 From: asoldano at redhat.com (Alessio Soldano) Date: Thu, 15 May 2014 19:47:04 +0200 Subject: [jbossws-dev] Changes to target containers on JBossWS trunk In-Reply-To: <5373A80F.2090908@redhat.com> References: <5373A80F.2090908@redhat.com> Message-ID: <5374FD98.2020604@redhat.com> The JBoss AS 7.2.0 integration has also just been dropped (see https://issues.jboss.org/browse/JBWS-3780 ). This now allows completing the removal of any references to JBossWS-Native stack, as JAXRPC has been pruned on WildFly. Cheers Alessio On 14/05/14 19:29, Alessio Soldano wrote: > Folks, > FYI, I've just committed a bunch of changes to make JBossWS-CXF trunk > consume jbossws-spi 3.0.0-SNAPSHOT and jbossws-common 3.0.0-SNAPSHOT. > The AS720 and WFLY800 integration layers have been updated accordingly > and 5.0.0-SNAPSHOT versions of them are consumed by the stack. > > I've also modified the wilfly810 target, which currently uses the > WildFly 8.0.0.CR2 release (will change that to 8.0.0.Final once that's > released too). > > Finally, a new wildfly900 target is available: due to the above > mentioned changes to jbossws-spi, the wildfly master is not usable as > is, so for now my fork here can be used: > https://github.com/asoldano/wildfly/commits/jbossws5 > > Tomorrow I'll update the Hudson instance on jbossws-qa.jboss.org. > > Cheers > Alessio > -- Alessio Soldano Web Service Lead, JBoss