[JBoss-dev] [JBoss JIRA] Created: (JBREM-27) Support for HTTP/HTTPS proxy
Support for HTTP/HTTPS proxy Key: JBREM-27 URL: http://jira.jboss.com/jira/browse/JBREM-27 Project: JBoss Remoting Type: Feature Request Components: transport Reporter: Thomas Diesler Assigned to: Tom Elrod Fix For: 1.0.1 beta This request showed up on the web services forum. Proxies are currently suported in axis-ws4ee.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-897) invalid ejb-link
[ http://jira.jboss.com/jira/browse/JBAS-897?page=comments#action_12314712 ] Thomas Diesler commented on JBAS-897: - Ok, please also provide a test case that shows the issue. invalid ejb-link Key: JBAS-897 URL: http://jira.jboss.com/jira/browse/JBAS-897 Project: JBoss Application Server Type: Bug Components: Web Services service Reporter: SourceForge User Assignee: Thomas Diesler SourceForge Submitter: tdiesler . Bill reported: I made a typo in my ejb-jar.xml file so it didn't match the ejb-link within my webservices.xml file. No complaint from JBoss on deployment on this. Bill -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1294) commons-logging.jar should be in default/lib
[ http://jira.jboss.com/jira/browse/JBAS-1294?page=comments#action_12314717 ] Thomas Diesler commented on JBAS-1294: -- Go ahead, I don't see an issue with that. commons-logging.jar should be in default/lib Key: JBAS-1294 URL: http://jira.jboss.com/jira/browse/JBAS-1294 Project: JBoss Application Server Type: Bug Versions: JBossAS-5.0 Alpha Reporter: Ryan Campbell Assignee: Ryan Campbell Priority: Minor commons-logging is a dependency of Tomcat 5.5, however it is included in the default config via the ws4ee sar. Since it is a dependency of both, shouldn't it be removed from ws4ee and added to default lib? So that we go from: ./lib/commons-logging.jar ./server/all/lib/commons-logging.jar ./server/all/deploy/jboss-ws4ee.sar/commons-logging.jar ./server/default/deploy/jboss-ws4ee.sar/commons-logging.jar to: ./lib/commons-logging.jar ./server/all/lib/commons-logging.jar ./server/default/lib/commons-logging.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBWEB-11) 505 error when connection from a .NET client
[ http://jira.jboss.com/jira/browse/JBWEB-11?page=history ] Thomas Diesler updated JBWEB-11: Description: People with .NET clients have no luck connection to JBossWS since .NET defaults to HTTP-1.1. This issue as poped up multiple times now. I don't think it is WS specific. Is there a general HTTP-1.1 issue with Tomcat? See: http://www.jboss.org/index.html?module=bbop=viewtopicp=3862668#3862668 was: People with .NET clients have no luck connection to JBossWS4EE since it defaults to HTTP-1.1. This issue as poped up multiple times now. I don't think it is WS specific. Is there a general HTTP-1.1 issue with Tomcat? See http://www.jboss.org/index.html?module=bbop=viewtopicp=3862668#3862668 505 error when connection from a .NET client Key: JBWEB-11 URL: http://jira.jboss.com/jira/browse/JBWEB-11 Project: JBoss Web Type: Bug Components: Tomcat Versions: JBossWeb-4.0.1 Reporter: Thomas Diesler Assignee: Remy Maucherat People with .NET clients have no luck connection to JBossWS since .NET defaults to HTTP-1.1. This issue as poped up multiple times now. I don't think it is WS specific. Is there a general HTTP-1.1 issue with Tomcat? See: http://www.jboss.org/index.html?module=bbop=viewtopicp=3862668#3862668 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBWEB-11) 505 error when connection from a .NET client
505 error when connection from a .NET client Key: JBWEB-11 URL: http://jira.jboss.com/jira/browse/JBWEB-11 Project: JBoss Web Type: Bug Components: Tomcat Versions: JBossWeb-4.0.1 Reporter: Thomas Diesler Assigned to: Remy Maucherat People with .NET clients have no luck connection to JBossWS4EE since it defaults to HTTP-1.1. This issue as poped up multiple times now. I don't think it is WS specific. Is there a general HTTP-1.1 issue with Tomcat? See http://www.jboss.org/index.html?module=bbop=viewtopicp=3862668#3862668 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBWEB-11) 505 error when connection from a .NET client
[ http://jira.jboss.com/jira/browse/JBWEB-11?page=comments#action_12314770 ] Thomas Diesler commented on JBWEB-11: - Here is a .NET workaround http://www.jboss.org/index.html?module=bbop=viewtopicp=3860297#3860297 505 error when connection from a .NET client Key: JBWEB-11 URL: http://jira.jboss.com/jira/browse/JBWEB-11 Project: JBoss Web Type: Bug Components: Tomcat Versions: JBossWeb-4.0.1 Reporter: Thomas Diesler Assignee: Remy Maucherat People with .NET clients have no luck connection to JBossWS since .NET defaults to HTTP-1.1. This issue as poped up multiple times now. I don't think it is WS specific. Is there a general HTTP-1.1 issue with Tomcat? See: http://www.jboss.org/index.html?module=bbop=viewtopicp=3862668#3862668 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-20) Multiple ports wsdl service element
[ http://jira.jboss.com/jira/browse/JBAS-20?page=history ] Thomas Diesler updated JBAS-20: --- Fix Version: JBossAS-4.0.2 Final Multiple ports wsdl service element --- Key: JBAS-20 URL: http://jira.jboss.com/jira/browse/JBAS-20 Project: JBoss Application Server Type: Bug Components: Web Services service Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossAS-4.0.2 Final A wsdl can potentially have more than one port associated with a wsdl service element. This is ok for a server deployment, which can give give the port name in webservices.xml. A client requesting the wsdl from the server, does not have this option in service-ref. We should adjust the returned wsdl such that it only contatains the port the client was asking for in the ?WSDL request. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-21) Cannot find wsdl in client deployment
[ http://jira.jboss.com/jira/browse/JBAS-21?page=history ] Thomas Diesler updated JBAS-21: --- Fix Version: JBossAS-4.0.2 Final Cannot find wsdl in client deployment - Key: JBAS-21 URL: http://jira.jboss.com/jira/browse/JBAS-21 Project: JBoss Application Server Type: Bug Components: Web Services service Reporter: Thomas Diesler Assignee: Thomas Diesler Priority: Trivial Fix For: JBossAS-4.0.2 Final The wsdl-file was not null in this case but pointed to WEB-INF which did not exist Caused by: java.lang.IllegalArgumentException: WSDL file argument cannot be null at org.jboss.webservice.WSDLDefinitionFactory$WSDLLocatorImpl.init(WSDLDefinitionFactory.java:95) at org.jboss.webservice.WSDLDefinitionFactory.parse(WSDLDefinitionFactory.java:58) at org.jboss.metadata.ServiceRefMetaData.getWsdlDefinition(ServiceRefMetaData.java:170) at org.jboss.webservice.ServiceClientDeployer.setupServiceRefEnvironment(ServiceClientDeployer.java:63) ... 30 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1235) TimedObject id persistence fails on restart
[ http://jira.jboss.com/jira/browse/JBAS-1235?page=history ] Thomas Diesler updated JBAS-1235: - Fix Version: JBossAS-4.0.2 Final TimedObject id persistence fails on restart --- Key: JBAS-1235 URL: http://jira.jboss.com/jira/browse/JBAS-1235 Project: JBoss Application Server Type: Bug Components: CMP service Versions: JBossAS-4.0.0 Final Reporter: SourceForge User Assignee: Thomas Diesler Fix For: JBossAS-4.0.2 Final SourceForge Submitter: cstach . Upon restarting JBoss, persisted timers throw this SQL exception because it seems that the entity bean that implements the TimedObject had its primary key (Long) converted into a byte array. java.sql.SQLException: Cannot convert class [B to SQL type requested due to java.lang.ClassCastException - null at com.mysql.jdbc.PreparedStatement.setObject (PreparedStatement.java:922) at com.mysql.jdbc.PreparedStatement.setObject (PreparedStatement.java:944) at org.jboss.resource.adapter.jdbc.WrappedPreparedStatem ent.setObject(WrappedPreparedStatement.java:615) at org.jboss.ejb.plugins.cmp.jdbc.JDBCParameterSetter$5.se tNotNull(JDBCParameterSetter.java:130) at org.jboss.ejb.plugins.cmp.jdbc.JDBCParameterSetter$JDB CAbstractParameterSetter.set (JDBCParameterSetter.java:56) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCAbstractCMPFi eldBridge.setArgumentParameters (JDBCAbstractCMPFieldBridge.java:354) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCAbstractCMPFi eldBridge.setPrimaryKeyParameters (JDBCAbstractCMPFieldBridge.java:343) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.se tPrimaryKeyParameters(JDBCEntityBridge.java:770) at org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.e xecute(JDBCLoadEntityCommand.java:157) at org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.e xecute(JDBCLoadEntityCommand.java:72) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.loadEnt ity(JDBCStoreManager.java:631) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.loadEnt ity(JDBCStoreManager.java:613) at org.jboss.ejb.plugins.CMPPersistenceManager.loadEntity (CMPPersistenceManager.java:391) at org.jboss.resource.connectionmanager.CachedConnection Interceptor.loadEntity (CachedConnectionInterceptor.java:351) at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.inv oke(EntitySynchronizationInterceptor.java:232) at org.jboss.resource.connectionmanager.CachedConnection Interceptor.invoke (CachedConnectionInterceptor.java:185) at org.jboss.ejb.plugins.EntityReentranceInterceptor.invoke (EntityReentranceInterceptor.java:111) at org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke (EntityInstanceInterceptor.java:211) at org.jboss.ejb.plugins.EntityLockInterceptor.invoke (EntityLockInterceptor.java:89) at org.jboss.ejb.plugins.EntityCreationInterceptor.invoke (EntityCreationInterceptor.java:53) at org.jboss.ejb.plugins.CallValidationInterceptor.invoke (CallValidationInterceptor.java:48) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext (AbstractTxInterceptor.java:105) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransacti ons(TxInterceptorCMT.java:283) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke (TxInterceptorCMT.java:149) at org.jboss.ejb.plugins.SecurityInterceptor.invoke (SecurityInterceptor.java:128) at org.jboss.ejb.plugins.LogInterceptor.invoke (LogInterceptor.java:191) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invok e(ProxyFactoryFinderInterceptor.java:122) at org.jboss.ejb.EntityContainer.internalInvoke (EntityContainer.java:514) at org.jboss.ejb.Container.invoke (Container.java:854) at org.jboss.ejb.txtimer.TimedObjectInvokerImpl.callTimeout (TimedObjectInvokerImpl.java:63) at org.jboss.ejb.txtimer.TimerImpl$TimerTaskImpl.run (TimerImpl.java:472) at java.util.TimerThread.mainLoop (Timer.java:432) at java.util.TimerThread.run(Timer.java:382) 11:44:21,750 ERROR [TimerImpl] Error invoking ejbTimeout: javax.ejb.EJBException: Internal error setting parameters for field id; CausedByException is: Cannot convert class [B to SQL type requested due to java.lang.ClassCastException - null 11:44:21,750 WARN [TimerImpl] Timer was not registered with Tx, reseting state: [id=1target= [target=jboss.j2ee:jndiName=ejb/mdf/Campaign,service=E JB,[EMAIL PROTECTED],remaining=- 59694750,periode=0,in_timeout] 11:44:21,859 ERROR [LogInterceptor] EJBException in method: public abstract void javax.ejb.TimedObject.ejbTimeout(javax.ejb.Timer), causedBy: java.sql.SQLException: Cannot convert class [B to SQL type requested due to java.lang.ClassCastException
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-897) invalid ejb-link
[ http://jira.jboss.com/jira/browse/JBAS-897?page=history ] Thomas Diesler closed JBAS-897: --- Resolution: Done The ServiceDeployer now takes the entire deployment down again when the WS endpoint cannot be started. We have good exceptions for invalid ejb-link, servlet-link entries invalid ejb-link Key: JBAS-897 URL: http://jira.jboss.com/jira/browse/JBAS-897 Project: JBoss Application Server Type: Bug Components: Web Services service Reporter: SourceForge User Assignee: Thomas Diesler Fix For: JBossAS-4.0.2 Final SourceForge Submitter: tdiesler . Bill reported: I made a typo in my ejb-jar.xml file so it didn't match the ejb-link within my webservices.xml file. No complaint from JBoss on deployment on this. Bill -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1115) bad path to included xsd gets built in WSDLFilePublisher
[ http://jira.jboss.com/jira/browse/JBAS-1115?page=comments#action_12315208 ] Thomas Diesler commented on JBAS-1115: -- Thanks for the good feedback bad path to included xsd gets built in WSDLFilePublisher Key: JBAS-1115 URL: http://jira.jboss.com/jira/browse/JBAS-1115 Project: JBoss Application Server Type: Bug Components: Web Services service Versions: JBossAS-4.0.0 Final Reporter: SourceForge User Assignee: Thomas Diesler Fix For: JBossAS-4.0.2 Final SourceForge Submitter: mazzgolf . Problem when deploying a web service whose WSDL imports/includes other WSDL/schemas. See attached for a simple hello.war that illustrates this problem. To replicate, simply place the war file in the JBoss deploy directory and start. I don't think this has anything to do with platforms, but just in case - this is on JBoss 4.0, JDK 1.4.2, Windows XP SP1. Description: My web service WSDL imports another WSDL which in turn includes a schema (these are WSRF specification files). It looks like WSDLFilePublisher is not building the path correctly to that included schema. It's missing a / in one spot and has a double slash // in another spot. While debugging in WSDLFilePublisher, line 206 results in this as value for resourcePath: WEB-INF/wsdl//services/../spec/wsrfWS- ResourceProperties-1_1.xsd Note that there is a / missing between the last directory wsrf and the schema filename WS- ResourceProperties-1_1.xsd. There is also a double slash // in there as well. The double-slash is probably OK and most file systems will parse it fine, however, obviously the missing slash is going to cause problems (which it does on my box). The value of this.expLocation was WEB-INF/wsdl/ and the value of schemaLocation was WS- ResourceProperties-1_1.xsd. baseURI had a value of file:/C:/mazz/jboss/jboss- 4.0.0/server/default/data/wsdl/jboss- wsdm.war/services/../spec/wsrf/WS-ResourceProperties- 1_1.wsdl. this.di.shortName is jboss-wsdm.war. index is 57. All of those values are correct. The WSDL includes the .xsd like this: wsd:typesxsd:schema xsd:include schemaLocation=WS-ResourceProperties- 1_1.xsd/ ... The resulting exception is (which is actually thrown in line 210): 16:13:24,774 ERROR [ServiceDeployer] Cannot startup webservice for: jboss-wsdm.war org.jboss.deployment.DeploymentException: Cannot publish wsdl to: C:\mazz\jboss\jboss-4.0.0 \server\default\data\wsdl\jboss- wsdm.war\services\sensor.wsdl; - nested throwable: (java.lang.IllegalArgumentException: Cannot find schema import in deployment: WEB-INF/wsdl//services/../spec/wsrfWS- ResourceProperties-1_1.xsd) at org.jboss.webservice.WSDLFilePublisher.publishWsdlFile (WSDLFilePublisher.java:106) If, in my debugger, I fix the resourcePath evaluated on line 205 such that the path has the proper slashes, my web service deploys fine. In this example, its as if I made this fix on line 205 of WSDLFilePublisher.java from: resourcePath = resourcePath.substring(0, resourcePath.lastIndexOf(/)); to: resourcePath = resourcePath.substring(1, resourcePath.lastIndexOf(/) + 1); Obviously, it would be best if no assumptions were made about the location of / (that is to say, don't assume resourcePath has a leading / - I do above and hence the 1 in the first argument to substring). Probably would be better if we do something like this for the first parameter to that substring: resourcePath.charAt(0) == / ? 1 : 0 Same holds true with that second argument. We should not do the +1 if we know the schemaLocation is an absolute path. Otherwise, we'd introduce another double slash. So, perhaps, line 205 should be the following: resourcePath = resourcePath.substring (resourcePath.chatAt(0) == / ? 1 : 0, resourcePath.lastIndexOf(/) + (schemaLocation.charAt (0) == / ? 0 : 1)); I'll leave it up to the commiter to decide the best course of action. John Mazz -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1115) bad path to included xsd gets built in WSDLFilePublisher
[ http://jira.jboss.com/jira/browse/JBAS-1115?page=history ] Thomas Diesler resolved JBAS-1115: -- Resolution: Done Fixed in Branch_4_0 bad path to included xsd gets built in WSDLFilePublisher Key: JBAS-1115 URL: http://jira.jboss.com/jira/browse/JBAS-1115 Project: JBoss Application Server Type: Bug Components: Web Services service Versions: JBossAS-4.0.0 Final Reporter: SourceForge User Assignee: Thomas Diesler Fix For: JBossAS-4.0.2 Final SourceForge Submitter: mazzgolf . Problem when deploying a web service whose WSDL imports/includes other WSDL/schemas. See attached for a simple hello.war that illustrates this problem. To replicate, simply place the war file in the JBoss deploy directory and start. I don't think this has anything to do with platforms, but just in case - this is on JBoss 4.0, JDK 1.4.2, Windows XP SP1. Description: My web service WSDL imports another WSDL which in turn includes a schema (these are WSRF specification files). It looks like WSDLFilePublisher is not building the path correctly to that included schema. It's missing a / in one spot and has a double slash // in another spot. While debugging in WSDLFilePublisher, line 206 results in this as value for resourcePath: WEB-INF/wsdl//services/../spec/wsrfWS- ResourceProperties-1_1.xsd Note that there is a / missing between the last directory wsrf and the schema filename WS- ResourceProperties-1_1.xsd. There is also a double slash // in there as well. The double-slash is probably OK and most file systems will parse it fine, however, obviously the missing slash is going to cause problems (which it does on my box). The value of this.expLocation was WEB-INF/wsdl/ and the value of schemaLocation was WS- ResourceProperties-1_1.xsd. baseURI had a value of file:/C:/mazz/jboss/jboss- 4.0.0/server/default/data/wsdl/jboss- wsdm.war/services/../spec/wsrf/WS-ResourceProperties- 1_1.wsdl. this.di.shortName is jboss-wsdm.war. index is 57. All of those values are correct. The WSDL includes the .xsd like this: wsd:typesxsd:schema xsd:include schemaLocation=WS-ResourceProperties- 1_1.xsd/ ... The resulting exception is (which is actually thrown in line 210): 16:13:24,774 ERROR [ServiceDeployer] Cannot startup webservice for: jboss-wsdm.war org.jboss.deployment.DeploymentException: Cannot publish wsdl to: C:\mazz\jboss\jboss-4.0.0 \server\default\data\wsdl\jboss- wsdm.war\services\sensor.wsdl; - nested throwable: (java.lang.IllegalArgumentException: Cannot find schema import in deployment: WEB-INF/wsdl//services/../spec/wsrfWS- ResourceProperties-1_1.xsd) at org.jboss.webservice.WSDLFilePublisher.publishWsdlFile (WSDLFilePublisher.java:106) If, in my debugger, I fix the resourcePath evaluated on line 205 such that the path has the proper slashes, my web service deploys fine. In this example, its as if I made this fix on line 205 of WSDLFilePublisher.java from: resourcePath = resourcePath.substring(0, resourcePath.lastIndexOf(/)); to: resourcePath = resourcePath.substring(1, resourcePath.lastIndexOf(/) + 1); Obviously, it would be best if no assumptions were made about the location of / (that is to say, don't assume resourcePath has a leading / - I do above and hence the 1 in the first argument to substring). Probably would be better if we do something like this for the first parameter to that substring: resourcePath.charAt(0) == / ? 1 : 0 Same holds true with that second argument. We should not do the +1 if we know the schemaLocation is an absolute path. Otherwise, we'd introduce another double slash. So, perhaps, line 205 should be the following: resourcePath = resourcePath.substring (resourcePath.chatAt(0) == / ? 1 : 0, resourcePath.lastIndexOf(/) + (schemaLocation.charAt (0) == / ? 0 : 1)); I'll leave it up to the commiter to decide the best course of action. John Mazz -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-21) Cannot find wsdl in client deployment
[ http://jira.jboss.com/jira/browse/JBAS-21?page=history ] Thomas Diesler resolved JBAS-21: Resolution: Won't Fix I think the exception message is clear enough. Cannot find wsdl in client deployment - Key: JBAS-21 URL: http://jira.jboss.com/jira/browse/JBAS-21 Project: JBoss Application Server Type: Bug Components: Web Services service Reporter: Thomas Diesler Assignee: Thomas Diesler Priority: Trivial Fix For: JBossAS-4.0.2 Final The wsdl-file was not null in this case but pointed to WEB-INF which did not exist Caused by: java.lang.IllegalArgumentException: WSDL file argument cannot be null at org.jboss.webservice.WSDLDefinitionFactory$WSDLLocatorImpl.init(WSDLDefinitionFactory.java:95) at org.jboss.webservice.WSDLDefinitionFactory.parse(WSDLDefinitionFactory.java:58) at org.jboss.metadata.ServiceRefMetaData.getWsdlDefinition(ServiceRefMetaData.java:170) at org.jboss.webservice.ServiceClientDeployer.setupServiceRefEnvironment(ServiceClientDeployer.java:63) ... 30 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1392) Implement EJBVerifier21.isJAXRPCType
Implement EJBVerifier21.isJAXRPCType
Key: JBAS-1392
URL: http://jira.jboss.com/jira/browse/JBAS-1392
Project: JBoss Application Server
Type: Task
Reporter: Thomas Diesler
Assigned to: Scott M Stark
Priority: Optional
Fix For: JBossAS-4.0.2 Final
Current implemention is
protected boolean isJAXRPCType(Class class1)
{
// TODO this should be implemented along the jaxrpc spec
return isRMIIDLValueType(class1);
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1392) Implement EJBVerifier21.isJAXRPCType
[ http://jira.jboss.com/jira/browse/JBAS-1392?page=history ]
Thomas Diesler updated JBAS-1392:
-
Assign To: (was: Scott M Stark)
Implement EJBVerifier21.isJAXRPCType
Key: JBAS-1392
URL: http://jira.jboss.com/jira/browse/JBAS-1392
Project: JBoss Application Server
Type: Task
Reporter: Thomas Diesler
Priority: Optional
Fix For: JBossAS-4.0.2 Final
Current implemention is
protected boolean isJAXRPCType(Class class1)
{
// TODO this should be implemented along the jaxrpc spec
return isRMIIDLValueType(class1);
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1070) Warning message not found when deploying WS4EE Web Service
[ http://jira.jboss.com/jira/browse/JBAS-1070?page=history ] Thomas Diesler resolved JBAS-1070: -- Resolution: Done Refactor EJB verification to incude message properties for EJB21. Warning message not found when deploying WS4EE Web Service -- Key: JBAS-1070 URL: http://jira.jboss.com/jira/browse/JBAS-1070 Project: JBoss Application Server Type: Bug Versions: JBossAS-4.0.0 Final Reporter: SourceForge User Assignee: Thomas Diesler Fix For: JBossAS-4.0.2 Final SourceForge Submitter: davidsalter . When deploying a WS4EE webservice, a message stating no warning message is found is displayed on the console when a method in the endpoint interface does not implement java.rmi.RemoteException. In this situation, the JBoss console instructs the developer to file a bug report. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1183) Verifier warning message not found
[ http://jira.jboss.com/jira/browse/JBAS-1183?page=history ] Thomas Diesler resolved JBAS-1183: -- Resolution: Duplicate Issue Verifier warning message not found -- Key: JBAS-1183 URL: http://jira.jboss.com/jira/browse/JBAS-1183 Project: JBoss Application Server Type: Bug Versions: JBossAS-4.0.0 Final Reporter: SourceForge User Assignee: Thomas Diesler Fix For: JBossAS-4.0.2 Final SourceForge Submitter: murphyp1 . 13:05:47,004 WARN [verifier] EJB spec violation: Bean : /d6501/SentinelMonitor Section: 7.11.1 Warning: No warning message found, please file a Bug report. 13:05:47,035 ERROR [MainDeployer] could not create deployment: file:/C:/home2/jboss/server/aistech/deploy/d6501ws- ejb.jar org.jboss.deployment.DeploymentException: Verification of Enterprise Beans failed, see above for error messages. at org.jboss.ejb.EJBDeployer.create (EJBDeployer.java:553) at org.jboss.deployment.MainDeployer.create (MainDeployer.java:898) at org.jboss.deployment.MainDeployer.deploy (MainDeployer.java:754) at org.jboss.deployment.MainDeployer.deploy (MainDeployer.java:718) at sun.reflect.GeneratedMethodAccessor37.invoke (Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke (Method.java:324) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke (ReflectedDispatcher.java:144) at org.jboss.mx.server.Invocation.dispatch (Invocation.java:80) at org.jboss.mx.interceptor.AbstractInterceptor.invoke (AbstractInterceptor.java:122) at org.jboss.mx.server.Invocation.invoke (Invocation.java:74) at org.jboss.mx.interceptor.ModelMBeanOperationIntercepto r.invoke(ModelMBeanOperationInterceptor.java:131) at org.jboss.mx.server.Invocation.invoke (Invocation.java:74) at org.jboss.mx.server.AbstractMBeanInvoker.invoke (AbstractMBeanInvoker.java:249) at org.jboss.mx.server.MBeanServerImpl.invoke (MBeanServerImpl.java:642) at org.jboss.mx.util.MBeanProxyExt.invoke (MBeanProxyExt.java:175) at $Proxy8.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.de ploy(URLDeploymentScanner.java:305) at org.jboss.deployment.scanner.URLDeploymentScanner.sc an(URLDeploymentScanner.java:463) at org.jboss.deployment.scanner.AbstractDeploymentScann er$ScannerThread.doScan (AbstractDeploymentScanner.java:204) at org.jboss.deployment.scanner.AbstractDeploymentScann er$ScannerThread.loop (AbstractDeploymentScanner.java:215) at org.jboss.deployment.scanner.AbstractDeploymentScann er$ScannerThread.run (AbstractDeploymentScanner.java:194) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1099) Missing EJB verifier message
[ http://jira.jboss.com/jira/browse/JBAS-1099?page=history ] Thomas Diesler resolved JBAS-1099: -- Resolution: Duplicate Issue Missing EJB verifier message Key: JBAS-1099 URL: http://jira.jboss.com/jira/browse/JBAS-1099 Project: JBoss Application Server Type: Bug Versions: JBossAS-4.0.0 Final Reporter: SourceForge User Assignee: Thomas Diesler Fix For: JBossAS-4.0.2 Final SourceForge Submitter: igorfie . I had service-endpoint/ element specified in my ejb-jar.xml file, but forgot to package service endpoint interface. Here is the error message that I got from JBoss: quote 08:27:49,290 WARN [verifier] EJB spec violation: Bean : test/wiki/ejb/Explorer Method : public abstract EJBHome getEJBHome() throws RemoteException Section: 7.11.9 Warning: No warning message found, please file a Bug report. /quote -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1392) Implement EJBVerifier21.isJAXRPCType
[ http://jira.jboss.com/jira/browse/JBAS-1392?page=history ]
Thomas Diesler reassigned JBAS-1392:
Assign To: Thomas Diesler
Implement EJBVerifier21.isJAXRPCType
Key: JBAS-1392
URL: http://jira.jboss.com/jira/browse/JBAS-1392
Project: JBoss Application Server
Type: Task
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Priority: Optional
Fix For: JBossAS-4.0.2 Final
Current implemention is
protected boolean isJAXRPCType(Class class1)
{
// TODO this should be implemented along the jaxrpc spec
return isRMIIDLValueType(class1);
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1065) No redeployment possible after unsuccessful first deployment
[ http://jira.jboss.com/jira/browse/JBAS-1065?page=history ] Thomas Diesler resolved JBAS-1065: -- Resolution: Done Fixed in Branch_4_0 No redeployment possible after unsuccessful first deployment Key: JBAS-1065 URL: http://jira.jboss.com/jira/browse/JBAS-1065 Project: JBoss Application Server Type: Bug Versions: JBossAS-4.0.0 Final Reporter: SourceForge User Assignee: Thomas Diesler Fix For: JBossAS-4.0.2 Final SourceForge Submitter: simongunz . If deployment of ear fails (e.g. because of invalid deployment descriptors) any further deployment of the same (valid, since error corrected) archive fails with the following exception: org.jboss.deployment.DeploymentException: Error in accessing application metadata: ; - nested throwable: (javax.management.InstanceAlreadyExistsException: jboss.j2ee:service=EARDeployment,url='jpi-jboss-iv.ear' already registered.) New deployment only succeeds after restarting JBoss. Since this is very inconvenient this behaviour should be changed so that deployment fails completely if there is a mistake in the deployment descriptor. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1235) TimedObject id persistence fails on restart
[ http://jira.jboss.com/jira/browse/JBAS-1235?page=history ] Thomas Diesler resolved JBAS-1235: -- Resolution: Cannot Reproduce Bug I run the PersistenceTestCase ant -Dtest=org.jboss.test.txtimer.test.PersistenceTestCase one-test with a timer duration of 30s. Killed the jboss server process, and restarted jboss-4.0.2beta After restart the timer event is fired. 11:34:33,432 INFO [Server] JBoss (MX MicroKernel) [4.0.2beta (build: CVSTag=Branch_4_0 date=200502041757)] Started in 24s:109ms 11:34:33,557 INFO [TimerEntityBean] ejbTimeout [pk=1,count=1,[EMAIL PROTECTED] timer=[id=1target=[target=jboss.j2ee:jndiName=test/txtimer/TimerEntity,service=EJB,pk=1],remaining=-5484,periode=0,in_time out] TimedObject id persistence fails on restart --- Key: JBAS-1235 URL: http://jira.jboss.com/jira/browse/JBAS-1235 Project: JBoss Application Server Type: Bug Components: CMP service Versions: JBossAS-4.0.0 Final Reporter: SourceForge User Assignee: Thomas Diesler Fix For: JBossAS-4.0.2 Final SourceForge Submitter: cstach . Upon restarting JBoss, persisted timers throw this SQL exception because it seems that the entity bean that implements the TimedObject had its primary key (Long) converted into a byte array. java.sql.SQLException: Cannot convert class [B to SQL type requested due to java.lang.ClassCastException - null at com.mysql.jdbc.PreparedStatement.setObject (PreparedStatement.java:922) at com.mysql.jdbc.PreparedStatement.setObject (PreparedStatement.java:944) at org.jboss.resource.adapter.jdbc.WrappedPreparedStatem ent.setObject(WrappedPreparedStatement.java:615) at org.jboss.ejb.plugins.cmp.jdbc.JDBCParameterSetter$5.se tNotNull(JDBCParameterSetter.java:130) at org.jboss.ejb.plugins.cmp.jdbc.JDBCParameterSetter$JDB CAbstractParameterSetter.set (JDBCParameterSetter.java:56) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCAbstractCMPFi eldBridge.setArgumentParameters (JDBCAbstractCMPFieldBridge.java:354) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCAbstractCMPFi eldBridge.setPrimaryKeyParameters (JDBCAbstractCMPFieldBridge.java:343) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.se tPrimaryKeyParameters(JDBCEntityBridge.java:770) at org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.e xecute(JDBCLoadEntityCommand.java:157) at org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.e xecute(JDBCLoadEntityCommand.java:72) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.loadEnt ity(JDBCStoreManager.java:631) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.loadEnt ity(JDBCStoreManager.java:613) at org.jboss.ejb.plugins.CMPPersistenceManager.loadEntity (CMPPersistenceManager.java:391) at org.jboss.resource.connectionmanager.CachedConnection Interceptor.loadEntity (CachedConnectionInterceptor.java:351) at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.inv oke(EntitySynchronizationInterceptor.java:232) at org.jboss.resource.connectionmanager.CachedConnection Interceptor.invoke (CachedConnectionInterceptor.java:185) at org.jboss.ejb.plugins.EntityReentranceInterceptor.invoke (EntityReentranceInterceptor.java:111) at org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke (EntityInstanceInterceptor.java:211) at org.jboss.ejb.plugins.EntityLockInterceptor.invoke (EntityLockInterceptor.java:89) at org.jboss.ejb.plugins.EntityCreationInterceptor.invoke (EntityCreationInterceptor.java:53) at org.jboss.ejb.plugins.CallValidationInterceptor.invoke (CallValidationInterceptor.java:48) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext (AbstractTxInterceptor.java:105) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransacti ons(TxInterceptorCMT.java:283) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke (TxInterceptorCMT.java:149) at org.jboss.ejb.plugins.SecurityInterceptor.invoke (SecurityInterceptor.java:128) at org.jboss.ejb.plugins.LogInterceptor.invoke (LogInterceptor.java:191) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invok e(ProxyFactoryFinderInterceptor.java:122) at org.jboss.ejb.EntityContainer.internalInvoke (EntityContainer.java:514) at org.jboss.ejb.Container.invoke (Container.java:854) at org.jboss.ejb.txtimer.TimedObjectInvokerImpl.callTimeout (TimedObjectInvokerImpl.java:63) at org.jboss.ejb.txtimer.TimerImpl$TimerTaskImpl.run (TimerImpl.java:472) at java.util.TimerThread.mainLoop (Timer.java:432) at java.util.TimerThread.run(Timer.java:382) 11:44:21,750 ERROR [TimerImpl] Error invoking ejbTimeout: javax.ejb.EJBException: Internal error setting parameters for field id;
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-20) Multiple ports wsdl service element
[ http://jira.jboss.com/jira/browse/JBAS-20?page=history ] Thomas Diesler closed JBAS-20: -- Resolution: Won't Fix Invalid, because jboss is not in control of the wsdl that is requested from a WS client. Multiple ports wsdl service element --- Key: JBAS-20 URL: http://jira.jboss.com/jira/browse/JBAS-20 Project: JBoss Application Server Type: Bug Components: Web Services service Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossAS-4.0.2 Final A wsdl can potentially have more than one port associated with a wsdl service element. This is ok for a server deployment, which can give give the port name in webservices.xml. A client requesting the wsdl from the server, does not have this option in service-ref. We should adjust the returned wsdl such that it only contatains the port the client was asking for in the ?WSDL request. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1478) Move axis-ws4ee to package org.jboss.org.apache.axis
Move axis-ws4ee to package org.jboss.org.apache.axis Key: JBAS-1478 URL: http://jira.jboss.com/jira/browse/JBAS-1478 Project: JBoss Application Server Type: Task Reporter: Thomas Diesler Fix For: JBossAS-4.0.2 Final -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1478) Move axis-ws4ee to package org.jboss.org.apache.axis
[ http://jira.jboss.com/jira/browse/JBAS-1478?page=history ] Thomas Diesler reassigned JBAS-1478: Assign To: Thomas Diesler Move axis-ws4ee to package org.jboss.org.apache.axis Key: JBAS-1478 URL: http://jira.jboss.com/jira/browse/JBAS-1478 Project: JBoss Application Server Type: Task Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossAS-4.0.2 Final -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBREM-33) Add GET support within HTTP server invoker
[ http://jira.jboss.com/jira/browse/JBREM-33?page=comments#action_12315647 ] Thomas Diesler commented on JBREM-33: - As far as I can see, we don't need support for GET for JBossWS. Add GET support within HTTP server invoker -- Key: JBREM-33 URL: http://jira.jboss.com/jira/browse/JBREM-33 Project: JBoss Remoting Type: Task Components: transport Versions: 1.0.1 beta Reporter: Tom Elrod Assignee: Tom Elrod Fix For: 1.0.1 final Add support for GET request using HTTP invoker (only supports POST at this point) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBREM-27) Support for HTTP/HTTPS proxy
[ http://jira.jboss.com/jira/browse/JBREM-27?page=history ] Thomas Diesler updated JBREM-27: Priority: Optional (was: Major) Fix Version: 1.2.0 beta (was: 1.0.1 final) Support for HTTP/HTTPS proxy Key: JBREM-27 URL: http://jira.jboss.com/jira/browse/JBREM-27 Project: JBoss Remoting Type: Feature Request Components: transport Reporter: Thomas Diesler Assignee: Tom Elrod Priority: Optional Fix For: 1.2.0 beta This request showed up on the web services forum. Proxies are currently suported in axis-ws4ee.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBREM-35) Servlet Invoker - counterpart to HTTP Invoker (runs within web container)
[ http://jira.jboss.com/jira/browse/JBREM-35?page=history ] Thomas Diesler updated JBREM-35: Priority: Optional (was: Minor) Fix Version: 1.2.0 beta (was: 1.0.1 final) It needs to be discussed who this would work with the WS4EE deployment model for JSE. As a reminder, it uses the servlet-class element to the declare the endpoint implemenation bean. What would be the benefit of running server side JBossWS with a dependency on Remoting rather than Tomcat? Servlet Invoker - counterpart to HTTP Invoker (runs within web container) - Key: JBREM-35 URL: http://jira.jboss.com/jira/browse/JBREM-35 Project: JBoss Remoting Type: Feature Request Components: transport Versions: 1.0.1 beta Reporter: Tom Elrod Assignee: Tom Elrod Priority: Optional Fix For: 1.2.0 beta Need a servlet invoker that will be the same as the HTTP Invoker (which is its own web server), but will run inside a web container (such as Tomcat) as a servlet. Will then process request same as HTTP Invoker after doPost()/doGet() called. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1478) Move axis-ws4ee to package org.jboss.org.apache.axis
[ http://jira.jboss.com/jira/browse/JBAS-1478?page=history ] Thomas Diesler resolved JBAS-1478: -- Resolution: Done Moved to org.jboss.axis Move axis-ws4ee to package org.jboss.org.apache.axis Key: JBAS-1478 URL: http://jira.jboss.com/jira/browse/JBAS-1478 Project: JBoss Application Server Type: Task Components: Web Services service Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossAS-4.0.2 Final -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Reopened: (JBAS-1639) Integrate Critical JBWS bug fixes
[ http://jira.jboss.com/jira/browse/JBAS-1639?page=history ] Thomas Diesler reopened JBAS-1639: -- Final CTS testrun is missing Integrate Critical JBWS bug fixes - Key: JBAS-1639 URL: http://jira.jboss.com/jira/browse/JBAS-1639 Project: JBoss Application Server Type: Bug Components: Web Services service Reporter: Scott M Stark Assignee: Thomas Diesler Priority: Critical Fix For: JBossAS-4.0.2 Final This issue links to the outstanding JBWS project issues that need to be included into JBAS 4.0.2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1674) web-console depends on UseJBossWebLoader
web-console depends on UseJBossWebLoader Key: JBAS-1674 URL: http://jira.jboss.com/jira/browse/JBAS-1674 Project: JBoss Application Server Type: Bug Components: Management Service Versions: JBossAS-4.0.2RC1 Reporter: Thomas Diesler with the CTS configuration, I get: 10:27:46,515 ERROR [[/web-console]] Servlet /web-console threw load() exception java.lang.ClassNotFoundException: org.jboss.console.plugins.monitor.CreateSnapshotServlet at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1332) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1181) web-console.war/WEB-INF/web.xml contains servlet servlet-nameCreate Snapshot/servlet-name servlet-classorg.jboss.console.plugins.monitor.CreateSnapshotServlet/servlet-class load-on-startup1/load-on-startup /servlet The class lives in jboss-console.jar, which is not deployed anywhere. With attribute name=UseJBossWebLoadertrue/attribute as it is configured in the default configuration all works fine, but jboss-console.jar is not deployed either -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1674) web-console depends on UseJBossWebLoader=true
[ http://jira.jboss.com/jira/browse/JBAS-1674?page=history ] Thomas Diesler updated JBAS-1674: - Summary: web-console depends on UseJBossWebLoader=true (was: web-console depends on UseJBossWebLoader) web-console depends on UseJBossWebLoader=true - Key: JBAS-1674 URL: http://jira.jboss.com/jira/browse/JBAS-1674 Project: JBoss Application Server Type: Bug Components: Management Service Versions: JBossAS-4.0.2RC1 Reporter: Thomas Diesler with the CTS configuration, I get: 10:27:46,515 ERROR [[/web-console]] Servlet /web-console threw load() exception java.lang.ClassNotFoundException: org.jboss.console.plugins.monitor.CreateSnapshotServlet at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1332) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1181) web-console.war/WEB-INF/web.xml contains servlet servlet-nameCreate Snapshot/servlet-name servlet-classorg.jboss.console.plugins.monitor.CreateSnapshotServlet/servlet-class load-on-startup1/load-on-startup /servlet The class lives in jboss-console.jar, which is not deployed anywhere. With attribute name=UseJBossWebLoadertrue/attribute as it is configured in the default configuration all works fine, but jboss-console.jar is not deployed either -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1675) Integrate Critical CTS bug fixes
Integrate Critical CTS bug fixes Key: JBAS-1675 URL: http://jira.jboss.com/jira/browse/JBAS-1675 Project: JBoss Application Server Type: Bug Components: Web Services service Reporter: Thomas Diesler Assigned to: Thomas Diesler Priority: Critical Fix For: JBossAS-4.0.2 Final This issue links to the outstanding JBWS project issues that need to be included into JBAS 4.0.2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1675) Integrate Critical CTS bug fixes
[ http://jira.jboss.com/jira/browse/JBAS-1675?page=history ] Thomas Diesler updated JBAS-1675: - Description: This issue links to the outstanding JBCTS project issues that need to be included into JBAS 4.0.2. (was: This issue links to the outstanding JBWS project issues that need to be included into JBAS 4.0.2.) Integrate Critical CTS bug fixes Key: JBAS-1675 URL: http://jira.jboss.com/jira/browse/JBAS-1675 Project: JBoss Application Server Type: Bug Components: Web Services service Reporter: Thomas Diesler Assignee: Thomas Diesler Priority: Critical Fix For: JBossAS-4.0.2 Final This issue links to the outstanding JBCTS project issues that need to be included into JBAS 4.0.2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
