[jira] Work stopped: (SM-807) Add jboss-service.xml to servicemix component so they can be properly deployed in jboss.
[ https://issues.apache.org/activemq/browse/SM-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SM-807 stopped by Eric Dofonsou. > Add jboss-service.xml to servicemix component so they can be properly > deployed in jboss. > > > Key: SM-807 > URL: https://issues.apache.org/activemq/browse/SM-807 > Project: ServiceMix > Issue Type: Improvement > Components: servicemix-assembly, servicemix-audit, servicemix-bpe, > servicemix-common, servicemix-components, servicemix-core, servicemix-drools, > servicemix-eip, servicemix-file, servicemix-ftp, servicemix-http, > servicemix-jbi, servicemix-jms, servicemix-jsr181, servicemix-lwcontainer, > servicemix-quartz, servicemix-saxon, servicemix-sca, servicemix-script, > servicemix-soap, servicemix-wsn2005 >Affects Versions: 3.1 > Environment: JBoss 4.0.5 GA >Reporter: Eric Dofonsou > Assigned To: Eric Dofonsou > Fix For: 3.2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Right now there are no dependencies set on the servicemix components to > ensure that they are loaded after the servicemix deployer. This can cause > bugs when the component are deployed before the servicemix deployer, and thus > are not handled by servicemix (and therefore not available). > The fix for this is do include a dependence in the META-INF/jboss-service.xml > of the component .zip file. here is the content of the file : > - > > > org.servicemix:service=Deployer > > - > PS : The servicemix-http component already has a jboss-web.xml see issue > (SM-584) file this should be deleted and the content of the new > jboss-service.xml file should now be : > - > > > > org.apache.commons.httpclient:loader=commons-httpclient-3.0.jar > > > org.servicemix:service=Deployer > > --- > Eric, -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Work started: (SM-807) Add jboss-service.xml to servicemix component so they can be properly deployed in jboss.
[ https://issues.apache.org/activemq/browse/SM-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SM-807 started by Eric Dofonsou. > Add jboss-service.xml to servicemix component so they can be properly > deployed in jboss. > > > Key: SM-807 > URL: https://issues.apache.org/activemq/browse/SM-807 > Project: ServiceMix > Issue Type: Improvement > Components: servicemix-assembly, servicemix-audit, servicemix-bpe, > servicemix-common, servicemix-components, servicemix-core, servicemix-drools, > servicemix-eip, servicemix-file, servicemix-ftp, servicemix-http, > servicemix-jbi, servicemix-jms, servicemix-jsr181, servicemix-lwcontainer, > servicemix-quartz, servicemix-saxon, servicemix-sca, servicemix-script, > servicemix-soap, servicemix-wsn2005 >Affects Versions: 3.1 > Environment: JBoss 4.0.5 GA >Reporter: Eric Dofonsou > Assigned To: Eric Dofonsou > Fix For: 3.2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Right now there are no dependencies set on the servicemix components to > ensure that they are loaded after the servicemix deployer. This can cause > bugs when the component are deployed before the servicemix deployer, and thus > are not handled by servicemix (and therefore not available). > The fix for this is do include a dependence in the META-INF/jboss-service.xml > of the component .zip file. here is the content of the file : > - > > > org.servicemix:service=Deployer > > - > PS : The servicemix-http component already has a jboss-web.xml see issue > (SM-584) file this should be deleted and the content of the new > jboss-service.xml file should now be : > - > > > > org.apache.commons.httpclient:loader=commons-httpclient-3.0.jar > > > org.servicemix:service=Deployer > > --- > Eric, -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-808) Servicemix jboss deployer
[
https://issues.apache.org/activemq/browse/SM-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37857
]
Eric Dofonsou commented on SM-808:
--
I've done a quick check online for the jboss version of Xalan seems to be
missing the xsltc part :
http://jira.jboss.com/jira/browse/JBAS-2155
Judging from the size of the files, the one with jboss version is only 1.7 meg
while the one in servicemix repository is 2 megs.
{quote}
--([EMAIL PROTECTED])-(/media/DATA/devtools/jboss-4.0.5.GA/lib/endorsed)--
--(1045:Wed,10 Jan 07:$)-- ls -al xalan.jar
-rwxrwx--- 1 root plugdev 1713696 2006-12-19 14:38 xalan.jar
--([EMAIL PROTECTED])-(/media/DATA/devtools/jboss-4.0.5.GA/lib/endorsed)--
--(1048:Wed,10 Jan 07:$)-- ls -al
~/.m2/repository/xalan/xalan/2.7.0/xalan-2.7.0.jar
-rw-r--r-- 1 ewrick ewrick 2730442 2006-12-18 09:41
/home/ewrick/.m2/repository/xalan/xalan/2.7.0/xalan-2.7.0.jar
--([EMAIL PROTECTED])-(/media/DATA/devtools/jboss-4.0.5.GA/lib/endorsed)--
{quote}
What do you mean by removing that hard dependency ? do you want to provide an
external document builder wrapper around xalan ?
> Servicemix jboss deployer
> -
>
> Key: SM-808
> URL: https://issues.apache.org/activemq/browse/SM-808
> Project: ServiceMix
> Issue Type: Bug
> Environment: JBoss 4.0.5 GA
>Reporter: Eric Dofonsou
> Fix For: 3.1
>
>
> The servicemix-jboss-deployer-3.1-SNAPSHOT.sar file generated by the jboss
> depolyer does not include the xalan-2.7.0.jar file in the lib. This is
> required by servicemix and is not included in jboss.
> Adding the jar to the .sar file fixed the issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SM-808) Servicemix jboss deployer
[ https://issues.apache.org/activemq/browse/SM-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37843 ] Eric Dofonsou commented on SM-808: -- humm I also have 4.0.5 GA, with the EJB3 install and that does not have xalan, must my install procedure then. I will try coping it in the lib folder and see Indded the log files should be removed. > Servicemix jboss deployer > - > > Key: SM-808 > URL: https://issues.apache.org/activemq/browse/SM-808 > Project: ServiceMix > Issue Type: Bug > Environment: JBoss 4.0.5 GA >Reporter: Eric Dofonsou > Fix For: 3.1 > > > The servicemix-jboss-deployer-3.1-SNAPSHOT.sar file generated by the jboss > depolyer does not include the xalan-2.7.0.jar file in the lib. This is > required by servicemix and is not included in jboss. > Adding the jar to the .sar file fixed the issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SM-808) Servicemix jboss deployer
Servicemix jboss deployer - Key: SM-808 URL: https://issues.apache.org/activemq/browse/SM-808 Project: ServiceMix Issue Type: Bug Environment: JBoss 4.0.5 GA Reporter: Eric Dofonsou Fix For: 3.1 The servicemix-jboss-deployer-3.1-SNAPSHOT.sar file generated by the jboss depolyer does not include the xalan-2.7.0.jar file in the lib. This is required by servicemix and is not included in jboss. Adding the jar to the .sar file fixed the issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SM-807) Add jboss-service.xml to servicemix component so they can be properly deployed in jboss.
Add jboss-service.xml to servicemix component so they can be properly deployed in jboss. Key: SM-807 URL: https://issues.apache.org/activemq/browse/SM-807 Project: ServiceMix Issue Type: Improvement Components: servicemix-assembly, servicemix-audit, servicemix-bpe, servicemix-common, servicemix-components, servicemix-core, servicemix-drools, servicemix-eip, servicemix-file, servicemix-ftp, servicemix-http, servicemix-jbi, servicemix-jms, servicemix-jsr181, servicemix-lwcontainer, servicemix-quartz, servicemix-saxon, servicemix-sca, servicemix-script, servicemix-soap, servicemix-wsn2005 Affects Versions: 3.1 Environment: JBoss 4.0.5 GA Reporter: Eric Dofonsou Fix For: 3.1 Right now there are no dependencies set on the servicemix components to ensure that they are loaded after the servicemix deployer. This can cause bugs when the component are deployed before the servicemix deployer, and thus are not handled by servicemix (and therefore not available). The fix for this is do include a dependence in the META-INF/jboss-service.xml of the component .zip file. here is the content of the file : - org.servicemix:service=Deployer - PS : The servicemix-http component already has a jboss-web.xml see issue (SM-584) file this should be deleted and the content of the new jboss-service.xml file should now be : - org.apache.commons.httpclient:loader=commons-httpclient-3.0.jar org.servicemix:service=Deployer --- Eric, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SM-584) Servicemix archive for Jboss
Servicemix archive for Jboss Key: SM-584 URL: https://issues.apache.org/activemq/browse/SM-584 Project: ServiceMix Issue Type: Bug Components: servicemix-core, servicemix-http Affects Versions: 3.0 Environment: All environement Reporter: Eric Dofonsou I've found the following issue with the way servicemix works in JBOSS. I'am building endpoints that uses the servicemix-http component. For this to work I need to add these two files to the $JBOSS_HOME/server/default/lib folder : 1- geronimo-j2ee-management_1.0_spec-1.0.1.jar 2- commons-httpclient-3.0.jar The geronimo-j2ee-management jar is required by the .sar file (Should this not be included in the sar archive ?) The Common-httpclient is required by the servicemix-http module (however there is an older version of this lib included with JBoss). So for this too work we have to delete the old version and replace it with this version. The ideal work around would be to include a jboss-web.xml file that specifies to jboss that we want to use our versino of common-httpclient for this application. Here is the content of the jboss-web.xml file that should be included in the servicemix-http-*-zip service assembly file (should be in the META-INF folder) : - org.apache.commons.httpclient:loader=commons-httpclient-3.0.jar --- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SM-379) Wrong transportURI when usnig the servicemix-http with a JSR181 endpoint.
Wrong transportURI when usnig the servicemix-http with a JSR181 endpoint.
-
Key: SM-379
URL: https://issues.apache.org/activemq/browse/SM-379
Project: ServiceMix
Type: Bug
Components: servicemix-http
Environment: ALL
Reporter: Eric Dofonsou
Fix For: 3.0
Attachments: HttpEndpoint.java
When I tried to generate stub's from a servicemix-jsr181 component, the WSDL
generated has a bad transport attribut with fails when the ws-import task is
called. here is the current binding transport value (generated by the JSR181
component):
transport=http://java.sun.com/xml/ns/jbi/binding/service+engine
This fails when trying to generate the stub source code since this is not a
valid transport. Output from the console :
[wsimport] warning: ignoring SOAP port "LogServicePort": unrecognized
transport [wsimport] warning: Service "LogService" does not contain any usable
ports
The correct tranport value should be :
http://schemas.xmlsoap.org/soap/http"; />
I've attached the new version of HttpEndpoint.
Here is the diff for the source code modification:
$ diff /cygdrive/d/My\ Received\ Files/HttpEndpoint.java HttpEndpoint.java
20a21
> import javax.wsdl.Binding;
26a28
> import javax.wsdl.extensions.soap.SOAPBinding;
34a37
> import com.ibm.wsdl.extensions.soap.SOAPBindingImpl;
39c42
< * @version $Revision$
---
> * @version $Revision: 389216 $
79,84d81
< } else if (targetService != null) {
< svc = def.getService(targetService);
< if (svc != null) {
< Iterator it = svc.getPorts().values().iterator();
< port = (it.hasNext()) ? (Port) it.next() : null;
< }
101a99,102
> SOAPBinding binding = getSOAPTransport(port.getBinding());
> if(binding!=null) {
> binding.setTransportURI("http://schemas.xmlsoap.org/soap
/http");
> }
113a115,123
>
> protected SOAPBinding getSOAPTransport(Binding binding) {
> ExtensibilityElement extensElm;
> for(Iterator it = binding.getExtensibilityElements().iterator();it.hasNe
xt();) {
> extensElm = (ExtensibilityElement) it.next();
> if(extensElm instanceof SOAPBinding) { return (SOAPBinding)exten
sElm; }
> }
> return null;
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
