JBI on WebSphere6.0

Hello,
has anybody experience in installing JBI 1.1 on a IBM WebSphere 6.x Application Server?
Greetz,
M. Stiller

The reference implementation serves the role of demonstrating a new Java technology (JSR) in an executable form. It shows that the technology is viable (can actually be realized in code), and helps other implementors of the technology as a kind of highly detailed specification.
An RI also serves as a technology "test drive" for interested users. An RI is usually not meant to be a commercial-grade product; it is written for clarity and correctness. (An RI for a JSR is a required before the JSR can be finalized, by the rules of the Java Community Process.)
JBI has seen a lot of activity in both the commercial and open-source areas. We are still in the early days of this new technology; you can expect a lot of choices for JBI implementations in the near future.
-Ron

Similar Messages

  • Cannot install sun-http-binding jbi component

    Hello!
    I'm trying to install httpbc.jar into a cluster environment and I'm faced with a following error message:
    java.lang.Integer cannot be cast to java.lang.String at com.sun.jbi.management.facade.Installer.addComponentToTarget(Installer.java:942) at com.sun.jbi.management.facade.Installer.installComponentToTarget(Installer.java:567) at com.sun.jbi.management.facade.Installer.install(Installer.java:215) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:93) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:27) at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:208) at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:120) at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262) at javax.management.StandardMBean.invoke(StandardMBean.java:391) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761) at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:178) at com.sun.esb.management.base.services.AbstractServiceMBeansImpl.invokeMBeanOperation(AbstractServiceMBeansImpl.java:498) at com.sun.esb.management.base.services.AbstractServiceMBeansImpl.invokeMBeanOperation(AbstractServiceMBeansImpl.java:639) at com.sun.esb.management.impl.installation.InstallationServiceMBeanImpl.installComponent(InstallationServiceMBeanImpl.java:135) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:93) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:27) at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:208) at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:120) at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262) at javax.management.StandardMBean.invoke(StandardMBean.java:391) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761) at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:178) at com.sun.esb.management.base.services.AbstractServiceImpl.invokeMBeanOperation(AbstractServiceImpl.java:330) at com.sun.esb.management.impl.installation.InstallationServiceImpl.installComponent(InstallationServiceImpl.java:111) at com.sun.jbi.ui.client.JBIAdminCommandsClientImpl.installComponent(JBIAdminCommandsClientImpl.java:409) at com.sun.jbi.jsf.bean.InstallationBean.installValidatedArchiveToTarget(InstallationBean.java:501) at com.sun.jbi.jsf.bean.InstallationBean.tryInstallToOneTarget(InstallationBean.java:410) at com.sun.jbi.jsf.bean.InstallationBean.installValidatedArchive(InstallationBean.java:175) at com.sun.jbi.jsf.handlers.InstallationHandlers.install(InstallationHandlers.java:1566) at com.sun.jbi.jsf.handlers.InstallationHandlers.jbiInstallValidatedArchive(InstallationHandlers.java:474) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.jsftemplating.layout.descriptors.handler.Handler.invoke(Handler.java:421) at com.sun.jsftemplating.layout.descriptors.LayoutElementBase.dispatchHandlers(LayoutElementBase.java:343) at com.sun.jsftemplating.layout.descriptors.LayoutElementBase.dispatchHandlers(LayoutElementBase.java:317) at com.sun.jsftemplating.layout.event.CommandActionListener.invokeCommandHandlers(CommandActionListener.java:133) at com.sun.jsftemplating.layout.event.CommandActionListener.processAction(CommandActionListener.java:81) at javax.faces.event.ActionEvent.processListener(ActionEvent.java:77) at javax.faces.component.UIComponentBase.broadcast(UIComponentBase.java:746) at javax.faces.component.UICommand.broadcast(UICommand.java:368) at com.sun.webui.jsf.component.WebuiCommand.broadcast(WebuiCommand.java:160) at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:447) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:752) at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:97) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) at com.sun.faces.extensions.avatar.lifecycle.PartialTraversalLifecycle.execute(PartialTraversalLifecycle.java:80) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) at com.sun.enterprise.tools.admingui.servlet.DelayedInitFacesServlet.service(DelayedInitFacesServlet.java:89) at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:317) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:198) at com.sun.webui.jsf.util.UploadFilter.doFilter(UploadFilter.java:240) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:230) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:198) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:288) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577) at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:272) at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637) at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568) at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813) at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341) at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:263) at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:214) at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265) at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)
    This seems to be glassfish bug.
    Also, could you please tell me where can I find the sources for com.sun.jbi.management.facade.Installer?
    Thanks in advance!
    Edited by: Koon_Tacker on May 28, 2008 6:46 AM

    The solution comes with the latest release of jbi-runtime. It appears to be fixed in March, 2008

  • Starting out with JBI

    In an attempt to introduce myself to JBI, I looked for something relevant to my field (health) and found the video created by Raghunadh Teegavarapu at http://wiki.open-esb.java.net/attach/HL7BC/HL7BCInboundOriginalACKDemo.wmv
    As I tried to follow the process exactly, I found my Netbeans 6.1 install was missing a few plugins, so I added
    org-netbeans-modules-encoder-hl7-aip.nbm
    org-netbeans-modules-encoder-ui-basic.nbm
    org-netbeans-modules-wsdlextensions-hl7.nbm
    com-sun-encoder-hl7.nbm
    com-sun-encoder.nbm
    And applied the following .jar to my local Glassfish install
    hl7bc.jar
    Everything was looking like I was good at following a video, and getting it all right despite slight differences between the Netbeans build shown and my 6.1 install, until I tried to deploy. At that stage I hit the wall with the result shown below. Can anyone offer any advice as to what I am missing?
    Thanks
    Ianto
    ---Details from build.xml (run) window---
    pre-init:
    init-private:
    init-userdir:
    init-user:
    init-project:
    do-init:
    post-init:
    init-check:
    init:
    init-deploy:
    deps-jar:
    init:
    Building jar: D:\JavaDevelopment\XXExperimental\HL7_Original_ACK_Demo\build\SEDeployment.jar
    dist_se:
    Expanding: D:\JavaDevelopment\XXExperimental\HL7_Original_ACK_Demo\build\SEDeployment.jar into
    D:\JavaDevelopment\XXExperimental\HL7_Original_ACK_DemoCA\src\jbiServiceUnits\HL7_Original_ACK_Demo
    Moving 1 file to D:\JavaDevelopment\XXExperimental\HL7_Original_ACK_DemoCA\src\jbiServiceUnits\HL7_Original_ACK_Demo
    Moving 1 file to D:\JavaDevelopment\XXExperimental\HL7_Original_ACK_DemoCA\src\jbiServiceUnits\META-INF\HL7_Original_ACK_Demo
    deps-javaee-jar:
    jbi-build:
    Building jar: D:\JavaDevelopment\XXExperimental\HL7_Original_ACK_DemoCA\build\BCDeployment.jar
    Validating CompApp project...
    Resolving connections...
    Writing connections out to connections.xml...
    Generating Service Assembly jbi.xml...
    Merging component projects' catalogs...
    Generating Binding Component Service Units...
    creating sun-file-binding.jar
    creating sun-hl7-binding.jar
    Creating/Updating CASA...
    Filtering Java EE Endpoints...
    Deleting: D:\JavaDevelopment\XXExperimental\HL7_Original_ACK_DemoCA\build\BCDeployment.jar
    Building jar: D:\JavaDevelopment\XXExperimental\HL7_Original_ACK_DemoCA\dist\HL7_Original_ACK_DemoCA.zip
    run-jbi-deploy:
    [deploy-service-assembly]
    Deploying a service assembly...
    host=localhost
    port=4848
    file=D:\JavaDevelopment\XXExperimental\HL7_Original_ACK_DemoCA/dist/HL7_Original_ACK_DemoCA.zip
    [start-service-assembly]
    Starting a service assembly...
    host=localhost
    port=4848
    name=HL7_Original_ACK_DemoCA
    ERROR: Successful execution of Start: HL7_Original_ACK_DemoCA
    WARNING: (JBIMA0405) Start of service assembly HL7_Original_ACK_DemoCA succeeded partially; some service units failed to start.
    * Component: sun-hl7-binding
    ERROR: (HL7BC_START_1) Error starting service unit due to: null
    * Component: sun-bpel-engine
    INFO: (JBIMA0409) Lifecycle operation start succeeded for Service Unit HL7_Original_ACK_DemoCA-HL7_Original_ACK_Demo.
    * Component: sun-file-binding
    INFO: (JBIMA0409) Lifecycle operation start succeeded for Service Unit HL7_Original_ACK_DemoCA-sun-file-binding.
    Cleaning up...
    [stop-service-assembly]
    Stopping a service assembly...
    host=localhost
    port=4848
    name=HL7_Original_ACK_DemoCA
    [shutdown-service-assembly]
    Shutting down a service assembly...
    host=localhost
    port=4848
    name=HL7_Original_ACK_DemoCA
    [undeploy-service-assembly]
    Undeploying a service assembly...
    host=localhost
    port=4848
    name=HL7_Original_ACK_DemoCA
    D:\JavaDevelopment\XXExperimental\HL7_Original_ACK_DemoCA\nbproject\build-impl.xml:213: Start failure.
    BUILD FAILED (total time: 8 seconds)

    Here are details from the server.log at time of attempted deployment:
    [#|2008-06-26T07:54:49.125+1000|INFO|sun-appserver9.1|com.sun.jbi.framework|_ThreadID=30;_ThreadName=JBI-Ready-Sync;|JBIFW0012: JBI framework startup complete.|#]
    [#|2008-06-26T07:55:27.640+1000|INFO|sun-appserver9.1|com.sun.jbi.management|_ThreadID=31;_ThreadName=httpWorkerThread-4848-0;|Deploying service assembly HL7_Original_ACK_DemoCA to target server.|#]
    [#|2008-06-26T07:55:27.968+1000|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=32;_ThreadName=HL7_Original_ACK_DemoCA-sun-file-binding;_RequestID=e8711635-8e71-471f-a65f-880d66bc1fc7;|Cannot find CatalogManager.properties|#]
    [#|2008-06-26T07:55:28.000+1000|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=32;_ThreadName=HL7_Original_ACK_DemoCA-sun-file-binding;|
    Retrieving document at 'D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-file-binding\sun-file-binding\HL7_Original_ACK_Demo\Filewrite_wsdl.wsdl'.|#]
    [#|2008-06-26T07:55:28.078+1000|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=32;_ThreadName=HL7_Original_ACK_DemoCA-sun-file-binding;|
    Retrieving document at 'D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-file-binding\sun-file-binding\HL7_Original_ACK_Demo\hl7receive_wsdl.wsdl'.|#]
    [#|2008-06-26T07:55:28.109+1000|INFO|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.HL7BindingDeployer|_ThreadID=33;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;HL7_Original_ACK_DemoCA-sun-hl7-binding;D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-hl7-binding\sun-hl7-binding;|Deploying service unit: HL7_Original_ACK_DemoCA-sun-hl7-binding from D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-hl7-binding\sun-hl7-binding.|#]
    [#|2008-06-26T07:55:28.125+1000|INFO|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.ServiceUnitImpl|_ThreadID=33;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;|ServiceUnit deploy method called.|#]
    [#|2008-06-26T07:55:28.140+1000|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=33;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;_RequestID=3c2d789c-457f-41db-a31a-d3c9ded95d92;|
    Cannot find CatalogManager.properties|#]
    [#|2008-06-26T07:55:28.156+1000|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=33;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;|
    Retrieving document at 'D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-hl7-binding\sun-hl7-binding\HL7_Original_ACK_Demo\Filewrite_wsdl.wsdl'.|#]
    [#|2008-06-26T07:55:28.218+1000|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=33;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;|
    Retrieving document at 'D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-hl7-binding\sun-hl7-binding\HL7_Original_ACK_Demo\hl7receive_wsdl.wsdl'.|#]
    [#|2008-06-26T07:55:28.250+1000|INFO|sun-appserver9.1|com.sun.jbi.management.DeploymentService|_ThreadID=31;_ThreadName=httpWorkerThread-4848-0;|JBIMA0402: Service Assembly file:/D:/Program Files/glassfish-v2ur2/domains/domain1/jbi/tmp/upload/7deaef5611ac1b8a7f57fe1/HL7_Original_ACK_DemoCA.zip has been deployed.|#]
    [#|2008-06-26T07:55:28.328+1000|INFO|sun-appserver9.1|com.sun.jbi.management|_ThreadID=31;_ThreadName=httpWorkerThread-4848-0;|Starting service assembly HL7_Original_ACK_DemoCA on target server.|#]
    [#|2008-06-26T07:55:28.406+1000|INFO|sun-appserver9.1|com.sun.jbi.engine.bpel.BPELSEDeployer|_ThreadID=34;_ThreadName=HL7_Original_ACK_DemoCA-HL7_Original_ACK_Demo;|BPELSEDeployer.starting_BPELSE_deploy_process|#]
    [#|2008-06-26T07:55:34.406+1000|INFO|sun-appserver9.1|com.sun.jbi.engine.bpel.EngineHelper|_ThreadID=34;_ThreadName=HL7_Original_ACK_DemoCA-HL7_Original_ACK_Demo;|BPJBI-4016:Loaded BPEL, WSDL and XSD documents for HL7_Original_ACK_DemoCA-HL7_Original_ACK_Demo.|#]
    [#|2008-06-26T07:55:34.484+1000|INFO|sun-appserver9.1|com.sun.jbi.engine.bpel.BPELSEDeployer|_ThreadID=34;_ThreadName=HL7_Original_ACK_DemoCA-HL7_Original_ACK_Demo;|BPJBI-5008:Activated an endpoint. Service name {http://enterprise.netbeans.org/bpel/HL7_Original_ACK_Demo/bpelprocess}PartnerLink1, endpoint name hl7receive_wsdlPortTypeRole_myRole|#]
    [#|2008-06-26T07:55:34.484+1000|INFO|sun-appserver9.1|com.sun.jbi.engine.bpel.BPELSEDeployer|_ThreadID=34;_ThreadName=HL7_Original_ACK_DemoCA-HL7_Original_ACK_Demo;|BPELSEDeployer.BPELSE_deploy_process_finished|#]
    [#|2008-06-26T07:55:34.500+1000|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=35;_ThreadName=HL7_Original_ACK_DemoCA-sun-file-binding;_RequestID=4410f26f-6686-4535-ba7a-8660e40bc5d9;|
    Cannot find CatalogManager.properties|#]
    [#|2008-06-26T07:55:34.500+1000|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=35;_ThreadName=HL7_Original_ACK_DemoCA-sun-file-binding;|
    Retrieving document at 'D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-file-binding\sun-file-binding\HL7_Original_ACK_Demo\Filewrite_wsdl.wsdl'.|#]
    [#|2008-06-26T07:55:34.515+1000|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=35;_ThreadName=HL7_Original_ACK_DemoCA-sun-file-binding;|
    Retrieving document at 'D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-file-binding\sun-file-binding\HL7_Original_ACK_Demo\hl7receive_wsdl.wsdl'.|#]
    [#|2008-06-26T07:55:36.265+1000|INFO|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.HL7BindingDeployer|_ThreadID=36;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;HL7_Original_ACK_DemoCA-sun-hl7-binding;D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-hl7-binding\sun-hl7-binding;|Initializing service unit: HL7_Original_ACK_DemoCA-sun-hl7-binding from D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-hl7-binding\sun-hl7-binding.|#]
    [#|2008-06-26T07:55:36.265+1000|INFO|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.ServiceUnitImpl|_ThreadID=36;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;|ServiceUnit init method called.|#]
    [#|2008-06-26T07:55:36.265+1000|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=36;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;_RequestID=5ed8e1b9-af37-4cd5-ad23-140a112d3d28;|
    Cannot find CatalogManager.properties|#]
    [#|2008-06-26T07:55:36.265+1000|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=36;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;|
    Retrieving document at 'D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-hl7-binding\sun-hl7-binding\HL7_Original_ACK_Demo\Filewrite_wsdl.wsdl'.|#]
    [#|2008-06-26T07:55:36.265+1000|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=36;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;|
    Retrieving document at 'D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-hl7-binding\sun-hl7-binding\HL7_Original_ACK_Demo\hl7receive_wsdl.wsdl'.|#]
    [#|2008-06-26T07:55:37.109+1000|INFO|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.HL7BindingDeployer|_ThreadID=36;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;HL7_Original_ACK_DemoCA-sun-hl7-binding;|HL7BC_Complete_init_SU|#]
    [#|2008-06-26T07:55:37.140+1000|INFO|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.HL7BindingDeployer|_ThreadID=37;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;HL7_Original_ACK_DemoCA-sun-hl7-binding;|Starting service unit: HL7_Original_ACK_DemoCA-sun-hl7-binding.|#]
    [#|2008-06-26T07:55:37.140+1000|INFO|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.ServiceUnitImpl|_ThreadID=37;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;|ServiceUnit start method called.|#]
    [#|2008-06-26T07:55:37.140+1000|SEVERE|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.ServiceUnitImpl|_ThreadID=37;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;hl7receive_wsdlPort;_RequestID=04f2a675-cd21-4a08-b61f-56da459eeef5;|Failed to start inbound message processor for endpoint: hl7receive_wsdlPort.|#]
    [#|2008-06-26T07:55:37.140+1000|SEVERE|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.ServiceUnitImpl|_ThreadID=37;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;{http://j2ee.netbeans.org/wsdl/hl7receive_wsdl}hl7receive_wsdlService;hl7receive_wsdlPort;_RequestID=04f2a675-cd21-4a08-b61f-56da459eeef5;|Failed to start the end point with service name {http://j2ee.netbeans.org/wsdl/hl7receive_wsdl}hl7receive_wsdlService and endpoint name hl7receive_wsdlPort: null|#]
    [#|2008-06-26T07:55:37.140+1000|SEVERE|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.HL7BindingDeployer|_ThreadID=37;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;_RequestID=04f2a675-cd21-4a08-b61f-56da459eeef5;|Error starting service unit due to: null|#]
    [#|2008-06-26T07:55:37.156+1000|INFO|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.HL7BindingDeployer|_ThreadID=38;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;HL7_Original_ACK_DemoCA-sun-hl7-binding;|Shutting down service unit: HL7_Original_ACK_DemoCA-sun-hl7-binding.|#]
    [#|2008-06-26T07:55:37.156+1000|INFO|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.ServiceUnitImpl|_ThreadID=38;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;|ServiceUnit shutdown method called.|#]
    [#|2008-06-26T07:55:37.156+1000|INFO|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.ServiceUnitImpl|_ThreadID=38;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;HL7_Original_ACK_DemoCA-sun-hl7-binding;|Successfully shutdown service unit: HL7_Original_ACK_DemoCA-sun-hl7-binding.|#]
    [#|2008-06-26T07:55:37.218+1000|INFO|sun-appserver9.1|com.sun.jbi.management|_ThreadID=31;_ThreadName=httpWorkerThread-4848-0;|Stopping service assembly HL7_Original_ACK_DemoCA on target server.|#]
    [#|2008-06-26T07:55:37.265+1000|INFO|sun-appserver9.1|sun-file-binding.com.sun.jbi.filebc.ServiceUnitImpl|_ThreadID=39;_ThreadName=HL7_Original_ACK_DemoCA-sun-file-binding;|ServiceUnit stop method called.|#]
    [#|2008-06-26T07:55:37.265+1000|INFO|sun-appserver9.1|sun-file-binding.com.sun.jbi.filebc.ServiceUnitImpl|_ThreadID=39;_ThreadName=HL7_Original_ACK_DemoCA-sun-file-binding;HL7_Original_ACK_DemoCA-sun-file-binding;|Successfully stopped service unit: HL7_Original_ACK_DemoCA-sun-file-binding.|#]
    [#|2008-06-26T07:55:37.312+1000|INFO|sun-appserver9.1|com.sun.jbi.management|_ThreadID=31;_ThreadName=httpWorkerThread-4848-0;|Shutting down service assembly HL7_Original_ACK_DemoCA on target server.|#]
    [#|2008-06-26T07:55:37.453+1000|INFO|sun-appserver9.1|com.sun.jbi.management|_ThreadID=31;_ThreadName=httpWorkerThread-4848-0;|Undeploying service assembly HL7_Original_ACK_DemoCA from target server.|#]
    [#|2008-06-26T07:55:37.546+1000|INFO|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.HL7BindingDeployer|_ThreadID=40;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;HL7_Original_ACK_DemoCA-sun-hl7-binding;D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-hl7-binding\sun-hl7-binding;|Undeploying service unit: HL7_Original_ACK_DemoCA-sun-hl7-binding from D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-hl7-binding\sun-hl7-binding.|#]
    [#|2008-06-26T07:55:37.562+1000|INFO|sun-appserver9.1|com.sun.jbi.management.DeploymentService|_ThreadID=31;_ThreadName=httpWorkerThread-4848-0;|JBIMA0412: Service Assembly with ID : HL7_Original_ACK_DemoCA has been undeployed.|#]
    I felt suspicious about the entry
    hl7receive_wsdlService and endpoint name hl7receive_wsdlPort: null
    So I went hunting in the code, and re-visitted the video to see if I had missed something in amongst the bindings, but I'm not good with wsdl, and everything seemed to match the code shown in the example, so I haven't found a point at which to make a change.
    Thanks for the advice on the e-mail alias, I will post there too.
    Ianto

  • JBIMR0025 JBI Error while invoking webservices

    Hi All,
    We have exposed a webservice in websphere server (JAVA 1.6 ) using JAX RPC. This webservice works perfectly fine, when tested using SOAP UI.
    This webservice is consumed by an external team, seems like they are trying to consume it using JBI Open ESB. When the external team is trying to invoke the same webservice it is failing with the following error :
    [#|2013-10-17T15:40:03.102-0700|WARNING|sun-appserver2.1|com.sun.jbi.httpsoapbc.OutboundMessageProcessor|_ThreadID=41;_ThreadName=HTTPBC-OutboundReceiver-5;_RequestID=e410120b-07ac-42e6-8eb6-9bef3cebbe93;|HTTPBC-E00759: An exception occured while processing a reply message. HTTPBC-W00759: Reply SOAP Message specifies a Fault that is malformed, or has no detail, or is undefined for operation lowTouchServiceTwoRating.
    javax.jbi.messaging.MessagingException: HTTPBC-W00759: Reply SOAP Message specifies a Fault that is malformed, or has no detail, or is undefined for operation lowTouchServiceTwoRating.
         at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.dispatch(OutboundMessageProcessor.java:1088)
         at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processRequestReplyOutbound(OutboundMessageProcessor.java:661)
         at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:243)
         at com.sun.jbi.httpsoapbc.OutboundAction.run(OutboundAction.java:63)
         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
         at java.lang.Thread.run(Thread.java:619)
    |#]
    [#|2013-10-17T15:40:03.102-0700|WARNING|sun-appserver2.1|com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider|_ThreadID=42;_ThreadName=HTTPBC-OutboundReceiver-1;_RequestID=ec51ff09-a896-4577-abc5-6299c83e3254;|HTTPBC-E00799: Message denormalization failed
    javax.jbi.messaging.MessagingException: javax.jbi.messaging.MessagingException: HTTPBC-E00799: Message denormalization failed
         at com.sun.jbi.httpsoapbc.jaxwssupport.JAXWSDenormalizer.denormalize(JAXWSDenormalizer.java:102)
         at com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider.onReply(AsyncJBIProvider.java:255)
         at com.sun.jbi.httpsoapbc.MessageExchangeSupport.notifyOfReply(MessageExchangeSupport.java:108)
         at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processRequestReplyInbound(OutboundMessageProcessor.java:423)
         at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:241)
         at com.sun.jbi.httpsoapbc.OutboundAction.run(OutboundAction.java:63)
         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
         at java.lang.Thread.run(Thread.java:619)
    Caused by: javax.jbi.messaging.MessagingException: HTTPBC-E00799: Message denormalization failed
         at com.sun.jbi.httpsoapbc.SoapDenormalizer.denormalize(SoapDenormalizer.java:226)
         at com.sun.jbi.httpsoapbc.jaxwssupport.JAXWSDenormalizer.denormalize(JAXWSDenormalizer.java:92)
         ... 8 more
    Caused by: com.sun.jbi.nms.wsdl11wrapper.WrapperProcessingException: The WSDL definition provided does not contain a definition for the normalized message {http:/lowtouch.uwc.kp.org/wsdl/LowTouchProcess}SOAPFault
         at com.sun.jbi.nms.wsdl11wrapper.impl.WrapperParserImpl.parse(WrapperParserImpl.java:83)
         at com.sun.jbi.httpsoapbc.SoapDenormalizer.denormalize(SoapDenormalizer.java:189)
         ... 9 more
    |#]
    [#|2013-10-17T15:40:03.118-0700|WARNING|sun-appserver2.1|com.sun.jbi.httpsoapbc.OutboundMessageProcessor|_ThreadID=42;_ThreadName=HTTPBC-OutboundReceiver-1;_RequestID=ec51ff09-a896-4577-abc5-6299c83e3254;|HTTPBC-E00759: An exception occured while processing a reply message. javax.jbi.messaging.MessagingException: HTTPBC-E00799: Message denormalization failed
    javax.jbi.messaging.MessagingException: javax.jbi.messaging.MessagingException: HTTPBC-E00799: Message denormalization failed
         at com.sun.jbi.httpsoapbc.jaxwssupport.JAXWSDenormalizer.denormalize(JAXWSDenormalizer.java:102)
         at com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider.onReply(AsyncJBIProvider.java:255)
         at com.sun.jbi.httpsoapbc.MessageExchangeSupport.notifyOfReply(MessageExchangeSupport.java:108)
         at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processRequestReplyInbound(OutboundMessageProcessor.java:423)
         at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:241)
         at com.sun.jbi.httpsoapbc.OutboundAction.run(OutboundAction.java:63)
         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
         at java.lang.Thread.run(Thread.java:619)
    Caused by: javax.jbi.messaging.MessagingException: HTTPBC-E00799: Message denormalization failed
         at com.sun.jbi.httpsoapbc.SoapDenormalizer.denormalize(SoapDenormalizer.java:226)
         at com.sun.jbi.httpsoapbc.jaxwssupport.JAXWSDenormalizer.denormalize(JAXWSDenormalizer.java:92)
         ... 8 more
    Caused by: com.sun.jbi.nms.wsdl11wrapper.WrapperProcessingException: The WSDL definition provided does not contain a definition for the normalized message {http:/lowtouch.uwc.kp.org/wsdl/LowTouchProcess}SOAPFault
         at com.sun.jbi.nms.wsdl11wrapper.impl.WrapperParserImpl.parse(WrapperParserImpl.java:83)
         at com.sun.jbi.httpsoapbc.SoapDenormalizer.denormalize(SoapDenormalizer.java:189)
         ... 9 more
    |#]
    [#|2013-10-17T15:40:03.118-0700|WARNING|sun-appserver2.1|com.sun.jbi.engine.bpel.BPELSEInOutThread|_ThreadID=16;_ThreadName=BPELSEInOutThread0;_RequestID=aed9924b-a298-49ae-b86b-aaaaa47e2193;|BPJBI-6004:caught exception while processing message
    java.lang.NullPointerException
         at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:230)
         at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:191)
    |#]
    [#|2013-10-17T15:40:03.118-0700|WARNING|sun-appserver2.1|com.sun.jbi.engine.bpel.BPELSEHelper|_ThreadID=16;_ThreadName=BPELSEInOutThread0;_RequestID=aed9924b-a298-49ae-b86b-aaaaa47e2193;|BPJBI-6001:Sending ERROR status (Service Name = {http://lowtouch.uwc.kp.org/bpel/LowTouchService/LowTouchGetRatingDataProcess}LowTouchGetRatingDataProcess, Endpoint Name = LowTouchGetRatingDataProcessPortTypeRole_myRole, Operation Name = {http://lowtouch.uwc.kp.org/wsdl/LowTouchGetRatingDataProcess}LowTouchGetRatingDataProcessOperation, Message Exchange Id = 151561174326859-64975-136013424009460107)
    Error properties
    com.sun.jbi.crl.faultcode = Server
    com.sun.jbi.crl.faultstring = null
    com.sun.jbi.crl.faultactor = sun-bpel-engine
    com.sun.jbi.crl.faultdetail =
    null
    java.lang.NullPointerException
         at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:230)
         at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:191)
    |#]
    [#|2013-10-17T15:40:03.118-0700|WARNING|sun-appserver2.1|com.sun.jbi.engine.bpel.BPELSEInOutThread|_ThreadID=16;_ThreadName=BPELSEInOutThread0;_RequestID=aed9924b-a298-49ae-b86b-aaaaa47e2193;|BPJBI-6004:caught exception while processing message
    java.lang.IllegalStateException: JBIMR0025: Unexpected illegal state change. Pattern (http://www.w3.org/2004/08/wsdl/in-out) TARGET-State (5)
         at com.sun.jbi.messaging.MessageExchangeProxy.nextState(MessageExchangeProxy.java:787)
         at com.sun.jbi.messaging.MessageExchangeProxy.setError(MessageExchangeProxy.java:311)
         at com.sun.jbi.engine.bpel.BPELSEHelper.sendError(BPELSEHelper.java:253)
         at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:328)
         at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:191)
    |#]
    Any idea what could be the root cause for the above error ?

    Sabarish,
    Are you using Workshop to invoke this Web Service ? If you are please attach
    the wsdl for the wls 61sp4 Web Service. If you are not using Workshop and
    are using WebLogic Web Service, please post this question in the
    weblogic.developer.interest.webservices newsgroup.
    Thanks
    Raj Alagumalai
    WebLogic Workshop Support
    "Sabarish" <[email protected]> wrote in message
    news:3f45d759$[email protected]..
    Folks,
    I am using WL6.1 sp4. I generated a webservice using the wsgen anttask. It got deployed without error. Now, when I try to invoke the service I
    get the following error :
    >
    Exception in thread "main" java.io.IOException: Server returned HTTPresponse co
    de: 500 for URL: http://192.168.149.224:7001/chws/chwsuri
    atsun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon
    nection.java:604)
    atsun.net.www.protocol.http.HttpURLConnection.getHeaderFieldKey(HttpURL
    Connection.java:903)
    atweblogic.soap.WebServiceProxy.getSessionCookie(WebServiceProxy.java:5
    55)
    at weblogic.soap.WebServiceProxy.receive(WebServiceProxy.java:523)
    at weblogic.soap.WebServiceProxy.invoke(WebServiceProxy.java:492)
    at weblogic.soap.SoapMethod.invoke(SoapMethod.java:186)
    at DClient.main(DClient.java:28)
    Any pointers to this.
    Thanx in advance
    --Sabarish

  • Error while running the command "maven jbi:createArchetype"

    Hi all,
    I installed maven 1.0.2 and copied the plugin maven-jbi-plugin-1.0.jar into the <maven_home>/plugin directory as said in the url http://docs.codehaus.org/display/SM/Spring+Client+Toolkit
    Then when I ran the command maven jbi:createArchetype, I am getting the following error.
    =========================================================
    Attempting to download dom4j-1.4-dev-8.jar.
    Error retrieving artifact from [http://www.ibiblio.org/maven/dom4j/jars/dom4j-1.4-dev-8.jar]: java.net.ConnectException: Connection timed out: connect
    WARNING: Failed to download dom4j-1.4-dev-8.jar.
    Attempting to download commons-jelly-20030902.160215.jar.
    Error retrieving artifact from [http://www.ibiblio.org/maven/commons-jelly/jars/commons-jelly-20030902.160215.jar]: java.net.ConnectException: Connection timed out: connect
    WARNING: Failed to download commons-jelly-20030902.160215.jar.
    Attempting to download commons-jelly-tags-jsl-20030211.143151.jar.
    Error retrieving artifact from [http://www.ibiblio.org/maven/commons-jelly/jars/commons-jelly-tags-jsl-20030211.143151.jar]: java.net.ConnectException: Connection timed out: connect
    WARNING: Failed to download commons-jelly-tags-jsl-20030211.143151.jar.
    Attempting to download commons-jelly-tags-log-20030211.142821.jar.
    Error retrieving artifact from [http://www.ibiblio.org/maven/commons-jelly/jars/commons-jelly-tags-log-20030211.142821.jar]: java.net.ConnectException: Connection timed out: connect
    WARNING: Failed to download commons-jelly-tags-log-20030211.142821.jar.
    Attempting to download commons-jelly-tags-velocity-20030303.205659.jar.
    Error retrieving artifact from [http://www.ibiblio.org/maven/commons-jelly/jars/commons-jelly-tags-velocity-20030303.205659.jar]: java.net.ConnectException: Connection timed out: connec
    WARNING: Failed to download commons-jelly-tags-velocity-20030303.205659.jar.
    Attempting to download commons-jelly-tags-xml-20040613.030723.jar.
    Error retrieving artifact from [http://www.ibiblio.org/maven/commons-jelly/jars/commons-jelly-tags-xml-20040613.030723.jar]: java.net.ConnectException: Connection timed out: connect
    WARNING: Failed to download commons-jelly-tags-xml-20040613.030723.jar.
    Attempting to download commons-logging-1.0.3.jar.
    Error retrieving artifact from [http://www.ibiblio.org/maven/commons-logging/jars/commons-logging-1.0.3.jar]: java.net.ConnectException: Connection timed out: connect
    WARNING: Failed to download commons-logging-1.0.3.jar.
    Attempting to download velocity-1.4-dev.jar.
    Error retrieving artifact from [http://www.ibiblio.org/maven/velocity/jars/velocity-1.4-dev.jar]: java.net.ConnectException: Connection timed out: connect
    WARNING: Failed to download velocity-1.4-dev.jar.
    Attempting to download velocity-dvsl-0.45.jar.
    Error retrieving artifact from [http://www.ibiblio.org/maven/velocity-dvsl/jars/velocity-dvsl-0.45.jar]: java.net.ConnectException: Connection timed out: connect
    WARNING: Failed to download velocity-dvsl-0.45.jar.
    Attempting to download xml-apis-1.0.b2.jar.
    Error retrieving artifact from [http://www.ibiblio.org/maven/xml-apis/jars/xml-apis-1.0.b2.jar]: java.net.ConnectException: Connection timed out: connect
    WARNING: Failed to download xml-apis-1.0.b2.jar.
    The build cannot continue because of the following unsatisfied dependencies:
    dom4j-1.4-dev-8.jar
    commons-jelly-20030902.160215.jar
    commons-jelly-tags-jsl-20030211.143151.jar
    commons-jelly-tags-log-20030211.142821.jar
    commons-jelly-tags-velocity-20030303.205659.jar
    commons-jelly-tags-xml-20040613.030723.jar (try downloading from http://jakarta.apache.org/commons/jelly/libs/xml/)
    commons-logging-1.0.3.jar
    velocity-1.4-dev.jar
    velocity-dvsl-0.45.jar
    xml-apis-1.0.b2.jar
    Total time: 3 minutes 35 seconds
    Finished at: Thu Aug 25 12:12:38 IST 2005
    ========================================================
    Somebody pls help me out in solving this.
    Thanks in advance.
    Regards,
    Venkat

    Hi there -
    I inherited a project that uses Maven to compile a jar file. I have downloaded and installed V1.0.2 and have followed the steps and verified that it was installed correctly. I have even connected it to the existing repository on a share drive. When I attempt to run Maven for the first time, I get an error indicating that it can not download particular jars from www.ibilio.org/maven/***/jar/***.jar
    Below is partial output. I have verified that these files do exist already in our central repository and I'm starting to think I need to set the proxy settings. I can not find the file in which I should update. Am I crazy???
    Here is the error message:
    C:\EPS\resources>maven project.xml
    | \/ |__ Apache_ ___
    | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
    |_| |_\__,_|\_/\___|_||_| v. 1.0.2
    Attempting to download log4j-1.2.8.jar.
    Error retrieving artifact from [http://www.ibiblio.org/maven/log4j/jars/log4j-1.
    2.8.jar]: java.net.UnknownHostException: www.ibiblio.org
    WARNING: Failed to download log4j-1.2.8.jar.
    Attempting to download junit-3.8.1.jar.
    Error retrieving artifact from [http://www.ibiblio.org/maven/junit/jars/junit-3.
    8.1.jar]: java.net.UnknownHostException: www.ibiblio.org
    WARNING: Failed to download junit-3.8.1.jar.
    Attempting to download ant-1.5.3-1.jar.
    Error retrieving artifact from [http://www.ibiblio.org/maven/ant/jars/ant-1.5.3-
    1.jar]: java.net.UnknownHostException: www.ibiblio.org
    WARNING: Failed to download ant-1.5.3-1.jar.
    Attempting to download jdbc2_0-stdext.jar.
    Error retrieving artifact from [http://www.ibiblio.org/maven/jdbc/jars/jdbc2_0-s
    tdext.jar]: java.net.UnknownHostException: www.ibiblio.org
    WARNING: Failed to download jdbc2_0-stdext.jar.
    Attempting to download 8171classes12.zip.
    Error retrieving artifact from [http://www.ibiblio.org/maven/jdbc/jars/8171class
    es12.zip]: java.net.UnknownHostException: www.ibiblio.org
    WARNING: Failed to download 8171classes12.zip.
    Attempting to download pg73jdbc3.jar.
    Error retrieving artifact from [http://www.ibiblio.org/maven/jdbc/jars/pg73jdbc3
    .jar]: java.net.UnknownHostException: www.ibiblio.org
    WARNING: Failed to download pg73jdbc3.jar.
    Attempting to download commons-digester-1.4.1.jar.
    Error retrieving artifact from [http://www.ibiblio.org/maven/commons-digester/ja
    rs/commons-digester-1.4.1.jar]: java.net.UnknownHostException: www.ibiblio.org
    WARNING: Failed to download commons-digester-1.4.1.jar.
    Attempting to download commons-collections-2.1.jar.
    Error retrieving artifact from [http://www.ibiblio.org/maven/commons-collections
    /jars/commons-collections-2.1.jar]: java.net.UnknownHostException: www.ibiblio.o
    rg
    WARNING: Failed to download commons-collections-2.1.jar.
    Attempting to download commons-logging-1.0.3.jar.
    Error retrieving artifact from [http://www.ibiblio.org/maven/commons-logging/jar
    s/commons-logging-1.0.3.jar]: java.net.UnknownHostException: www.ibiblio.org
    WARNING: Failed to download commons-logging-1.0.3.jar.
    Attempting to download commons-beanutils-1.6.1.jar.
    Error retrieving artifact from [http://www.ibiblio.org/maven/commons-beanutils/j
    ars/commons-beanutils-1.6.1.jar]: java.net.UnknownHostException: www.ibiblio.org
    WARNING: Failed to download commons-beanutils-1.6.1.jar.
    Attempting to download ldap.jar.
    Error retrieving artifact from [http://www.ibiblio.org/maven/novell-ldap/jars/ld
    ap.jar]: java.net.UnknownHostException: www.ibiblio.org
    WARNING: Failed to download ldap.jar.
    Attempting to download utilities.jar.
    Error retrieving artifact from [http://www.ibiblio.org/maven/novell-ldap/jars/ut
    ilities.jar]: java.net.UnknownHostException: www.ibiblio.org
    WARNING: Failed to download utilities.jar.
    Attempting to download xerces-1.4.4.jar.
    Error retrieving artifact from [http://www.ibiblio.org/maven/xerces/jars/xerces-
    1.4.4.jar]: java.net.UnknownHostException: www.ibiblio.org
    WARNING: Failed to download xerces-1.4.4.jar.
    Attempting to download servlet-2.3.jar.
    Error retrieving artifact from [http://www.ibiblio.org/maven/servlet/jars/servle
    t-2.3.jar]: java.net.UnknownHostException: www.ibiblio.org
    WARNING: Failed to download servlet-2.3.jar.
    Attempting to download mail.jar.
    Error retrieving artifact from [http://www.ibiblio.org/maven/mail/jars/mail.jar]
    : java.net.UnknownHostException: www.ibiblio.org
    WARNING: Failed to download mail.jar.
    The build cannot continue because of the following unsatisfied dependencies:
    log4j-1.2.8.jar
    junit-3.8.1.jar
    ant-1.5.3-1.jar (try downloading from http://jakarta.apache.org/regexp/)
    jdbc2_0-stdext.jar
    8171classes12.zip
    pg73jdbc3.jar
    commons-digester-1.4.1.jar (try downloading from http://jakarta.apache.org/commons/)
    commons-collections-2.1.jar (try downloading from http://jakarta.apache.org/commons/)
    commons-logging-1.0.3.jar (try downloading from http://jakarta.apache.org/commons/)
    commons-beanutils-1.6.1.jar (try downloading from http://jakarta.apache.org/commons/)
    ldap.jar
    utilities.jar
    xerces-1.4.4.jar (try downloading from http://xml.apache.org/xerces2-j/)
    servlet-2.3.jar
    mail.jar
    Total time: 6 seconds
    Finished at: Thu Oct 27 09:46:39 EDT 2005

  • Technical Article on Service-oriented Integration Using JBI Posted

    I've just posted an article on the open-esb site about using JBI for what we have come to call service-oriented integration: enterprise integration atop a SOA fabric. The article includes an example of a simple adapter pattern implementation that includes message transformation and protocol hopping.
    See https://open-esb.dev.java.net/ for the PDF download.

    At last!!
    Finally an article about the real JBI and what JBI is all about. I don't know what's going on with people's understanding of JBI.
    At JavaOne, I remember one of the expert group, from Oracle I think, proudly claiming that JBI will be one of the core architectures that companies will be delivering their integration business upon. Now I wonder where Oracle's, SAP's and IONA's contributions are so far. Oracle for example really contributed to JSR 208 by marketing and implementing SCA.
    Although in early stages, I think open source implementations are missing the point as well. Using open source implementation X, I couldn't see a scenario that shows the power of the concept, while implementation Y just did not like service units, service connections and link types, then tried to invent its own configuration and routing descriptors, wasting very valuable time.
    Anyway, may be one just have to wait and see!!
    Thanks Ron for such contribution.

  • JBI Installation Error on Windows

    The problem:
    JBI default install fails on windows. We have solved the problem with a workaround, listed below.
    Our configuration is:
    * JBI 1.0
    * Application server Q2
    * Windows 2000
    We get the following symptoms:
    * After JBI is installed, the application server admin web page fails to load.
    * server.log reports "NoClassDefFoundError: javax/jbi/JBIException"
    * jbi install log reports "The input line is too long."
    Our solution:
    1) Replace C:\Sun\AppServer\bin\asant.bat with the file listed below. We have moved setting the class path from the command line to an environment variable.
    2) Re-run the installation scripts:
    C:\Sun\jbi\install>C:\Sun\Appserver\bin\asant.bat -DAS_INSTALL=C:\Sun\Appserver -DJBI_HOME=C:\Sun\jbi -DJBI_DOMAIN_ROOT=C:\Sun\Appserver\domains\domain1 -f install_jbi_domain.ant
    C:\Sun\jbi\install>C:\Sun\Appserver\bin\asant.bat -DJBI_HOME=C:\Sun\jbi -DJBI_DOMAIN_ROOT=C:\Sun\Appserver\domains\domain1 -f C:\Sun\jbi\install\install_sample_components.xml
    C:\Sun\AppServer\bin\asant.bat
    @echo off
    rem
    rem Copyright 2004 Sun Microsystems, Inc. All rights reserved.
    rem SUN PROPRIETARY/CONFIDENTIAL. Use is subject to license terms.
    rem
    @setlocal
    call "C:\Sun\AppServer\config\asenv.bat"
    set JAVA_HOME=%AS_JAVA%
    set ANT_HOME=%AS_ANT%
    set ANT_OPTS="-Dos.name=Windows_NT"
    set CLASSPATH=
    if exist "%HOME%\antrc_pre.bat" call "%HOME%\antrc_pre.bat"
    if "%OS%"=="Windows_NT" @setlocal
    rem %~dp0 is expanded pathname of the current script under NT
    set DEFAULT_ANT_HOME=%~dp0..
    if "%ANT_HOME%"=="" set ANT_HOME=%DEFAULT_ANT_HOME%
    set DEFAULT_ANT_HOME=
    rem Slurp the command line arguments. This loop allows for an unlimited number
    rem of arguments (up to the command line limit, anyway).
    set ANT_CMD_LINE_ARGS=%1
    if ""%1""=="""" goto doneStart
    shift
    :setupArgs
    if ""%1""=="""" goto doneStart
    set ANT_CMD_LINE_ARGS=%ANT_CMD_LINE_ARGS% %1
    shift
    goto setupArgs
    rem This label provides a place for the argument list loop to break out
    rem and for NT handling to skip to.
    :doneStart
    rem find ANT_HOME if it does not exist due to either an invalid value passed
    rem by the user or the %0 problem on Windows 9x
    if exist "%ANT_HOME%\lib\ant.jar" goto checkJava
    rem check for ant in Program Files on system drive
    if not exist "%SystemDrive%\Program Files\ant" goto checkSystemDrive
    set ANT_HOME=%SystemDrive%\Program Files\ant
    goto checkJava
    :checkSystemDrive
    rem check for ant in root directory of system drive
    if not exist %SystemDrive%\ant\lib\ant.jar goto checkCDrive
    set ANT_HOME=%SystemDrive%\ant
    goto checkJava
    :checkCDrive
    rem check for ant in C:\ant for Win9X users
    if not exist C:\ant\lib\ant.jar goto noAntHome
    set ANT_HOME=C:\ant
    goto checkJava
    :noAntHome
    echo ANT_HOME is set incorrectly or ant could not be located. Please set ANT_HOME.
    goto end
    :checkJava
    set _JAVACMD=%JAVACMD%
    set LOCALCLASSPATH=%CLASSPATH%
    for %%i in ("%ANT_HOME%\lib\*.jar") do call "%ANT_HOME%\bin\lcp.bat" %%i
    call "%ANT_HOME%\bin\lcp.bat" %AS_INSTALL%\lib\sun-appserv-ant.jar
    if "%JAVA_HOME%" == "" goto noJavaHome
    if not exist "%JAVA_HOME%\bin\java.exe" goto noJavaHome
    if "%_JAVACMD%" == "" set JAVACMD=%JAVAHOME%\bin\java.exe
    if exist "%JAVA_HOME%\lib\tools.jar" set LOCALCLASSPATH=%JAVA_HOME%\lib\tools.jar;%LOCALCLASSPATH%
    if exist "%JAVA_HOME%\lib\classes.zip" set LOCALCLASSPATH=%JAVA_HOME%\lib\classes.zip;%LOCALCLASSPATH%
    goto checkJikes
    :noJavaHome
    if "%_JAVACMD%" == "" set _JAVACMD=java.exe
    echo.
    echo Warning: JAVA_HOME environment variable is not set.
    echo If build fails because sun.* classes could not be found
    echo you will need to set the JAVA_HOME environment variable
    echo to the installation directory of java.
    echo.
    :checkJikes
    if not "%JIKESPATH%"=="" goto runAntWithJikes
    :runAnt
    set CLASSPATH="%AS_INSTALL%/lib/appserv-se.jar";"%AS_INSTALL%/lib/admin-cli.jar";"%AS_INSTALL%/lib/appserv-admin.jar";"%AS_INSTALL%/lib/j2ee.jar";"%AS_INSTALL%/lib/appserv-ext.jar";"%AS_INSTALL%/lib/appserv-rt.jar";"%AS_INSTALL%/lib/commons-launcher.jar";"%AS_INSTALL%/lib/install/applications/jmsra/imqjmsra.jar";"%LOCALCLASSPATH%"
    "%_JAVACMD%" %ANT_OPTS% -Dcom.sun.aas.installRoot="%AS_INSTALL%" -Djava.library.path="%AS_INSTALL%\bin;%AS_ICU_LIB%" "-Dant.home=%ANT_HOME%" org.apache.tools.ant.Main %ANT_ARGS% %ANT_CMD_LINE_ARGS%
    goto end
    :runAntWithJikes
    set CLASSPATH="%AS_INSTALL%/lib/appserv-se.jar";"%AS_INSTALL%/lib/admin-cli.jar";"%AS_INSTALL%/lib/appserv-admin.jar";"%AS_INSTALL%/lib/j2ee.jar";"%AS_INSTALL%/lib/appserv-ext.jar";"%AS_INSTALL%/lib/appserv-rt.jar";"%AS_INSTALL%/lib/commons-launcher.jar";"%AS_INSTALL%/lib/install/applications/jmsra/imqjmsra.jar";"%LOCALCLASSPATH%"
    "%_JAVACMD%" %ANT_OPTS% -Dcom.sun.aas.installRoot="%AS_INSTALL%" -Djava.library.path="%AS_INSTALL%\bin;%AS_ICU_LIB%" "-Dant.home=%ANT_HOME%" "-Djikes.class.path=%JIKESPATH%" org.apache.tools.ant.Main %ANT_ARGS% %ANT_CMD_LINE_ARGS%
    goto end
    :end
    set LOCALCLASSPATH=
    set _JAVACMD=
    set ANT_CMD_LINE_ARGS=
    if "%OS%"=="Windows_NT" @endlocal
    :mainEnd
    if exist "%HOME%\antrc_post.bat" call "%HOME%\antrc_post.bat"
    ---------------------------------------------

    I tried your updated asant.bat file. Now I am getting following error.
    BUILD FAILED
    C:\Sun\jbi\examples\Demo\demo.ant:228: as.install.dir: ${as.install.dir} does not exist. EXIT
    can u help?
    -k

  • Bug in JBI?

    All,
    I am evaluating JBI. I understand that the WSDL 2.0 implementation is based on a draft and not on the final version therefore I decided to revert to WSDL 1.1.
    My problem is in com.sun.jbi.messaging.util.WSDLHelper#getOperationsForService11(Document , QName). To understand the problem, lets look at the way the "porttypes" and the "operations" are found:
    #getPortType: definitions.getElementsByTagNameNS(WSDL_11, PORTTYPE)
    #getOperationsForService11: portType.getElementsByTagNameNS(WSDL_11, OPERATION)
    this does specify the namespace as WSDL_11. Now when it tries to look for "input" and "ouput" within an "operation" it goes by the following code:
    NodeList ins = op.getElementsByTagName(IN_MSG);
    NodeList outs = op.getElementsByTagName(OUT_MSG);
    Hence no namespace therefore my generated WSDL has to be modified from:
    <wsdl:operation name="sendMail">
    <wsdl:input name="sendMailRequest" message="impl:sendMailRequest"/>
    <wsdl:output name="sendMailResponse" message="impl:sendMailResponse"/>
    </wsdl:operation>
    to
    <wsdl:operation name="sendMail">
    <input name="sendMailRequest" message="impl:sendMailRequest"/>
    <output name="sendMailResponse" message="impl:sendMailResponse"/>
    </wsdl:operation>
    which is a pain because I really would like to automate the process. Am I missing something?
    Regards
    Yoram

    Thanks, I've tried but I have a problem (probably me being stupid but here we go)
    This is my WSDL
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions
    targetNamespace="http://localhost/namespace/jbi/com.test.jbi.ItineraryConfirmationService.wsdl"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:apachesoap="http://xml.apache.org/xml-soap"
    xmlns:impl="http://localhost/namespace/jbi/com.test.jbi.ItineraryConfirmationService.wsdl"
    xmlns:intf="http://localhost/namespace/jbi/com.test.jbi.ItineraryConfirmationService.wsdl"
    xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <!--WSDL created by Apache Axis version: 1.4
    Built on Apr 22, 2006 (06:55:48 PDT)-->
    <types>
    <schema elementFormDefault="qualified"
    targetNamespace="http://localhost/namespace/jbi/com.test.jbi.ItineraryConfirmationService.wsdl" xmlns="http://www.w3.org/2001/XMLSchema">
    <element name="sendMail">
    <complexType>
    <sequence>
    <element name="in0" type="xsd:string"/>
    <element name="in1" type="xsd:string"/>
    </sequence>
    </complexType>
    </element>
    <element name="sendMailResponse">
    <complexType/>
    </element>
    </schema>
    </types>
    <message name="sendMailRequest">
    <part element="impl:sendMail" name="parameters"/>
    </message>
    <message name="sendMailResponse">
    <part element="impl:sendMailResponse" name="parameters"/>
    </message>
    <portType name="ItineraryConfirmationServiceOperations">
    <operation name="sendMail">
    <input message="impl:sendMailRequest" name="sendMailRequest"/>
    <output message="impl:sendMailResponse" name="sendMailResponse"/>
    </operation>
    </portType>
    <binding name="itineraryconfirmation.wsdlSoapBinding" type="impl:ItineraryConfirmationServiceOperations">
    <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="sendMail">
    <wsdlsoap:operation soapAction=""/>
    <input name="sendMailRequest">
    <wsdlsoap:body use="literal"/>
    </input>
    <output name="sendMailResponse">
    <wsdlsoap:body use="literal"/>
    </output>
    </operation>
    </binding>
    <service name="ItineraryConfirmationServiceOperationsService">
    <port binding="impl:itineraryconfirmation.wsdlSoapBinding" name="itineraryconfirmation.wsdl">
    <wsdlsoap:address location="http://localhost/jbi/itineraryconfirmation.wsdl"/>
    </port>
    </service>
    </definitions>
    When I use this code I get the namespaceURI
         public static void main(String[] args)
              throws Exception
              DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
              factory.setNamespaceAware(true);
              DocumentBuilder builder = factory.newDocumentBuilder();
              Document doc = builder.parse(new File("C:/b-wsdl.xml"));
              System.out.println(doc.getDocumentElement().getNamespaceURI());
    but when this code is used in JBI (WSDLHelper), getWSDLVersion returns null, and since there is no check in getOperationsForServices I get a nullpointerexception
    public static HashMap getOperationsForService(Document serviceDesc, QName serviceName)
    throws javax.jbi.messaging.MessagingException
    version = getWSDLVersion(serviceDesc);
    private static String getWSDLVersion(Document description)
    return description.getDocumentElement().getNamespaceURI();
    }

  • Dynamic queue publication in JBI

    In Jcaps513 jcd you could dynamically publish to a queue with the sendTo() method, perhaps based upon incoming message type. How would you do something similar in JBI/BPEL coding?
    Rupert

    Mikael
    Its is possible in the BPEL code by assigning a value to the JMS BC/Outbound/Destination property in the properties section of the outbound partner link in an assign activity.How is that dynamic, in that you can set the value on-the-fly at runtime?
    Michael
    Can/t do that. There is no support for the JMS BC to use a message part to set destination.Consider using JCA MDB with the JMS JCA Adapter instead.
    Ok, thanks.
    Rupert

  • Unable to install JBI correctly

    Hello,
    I am installing JBI at "C:\Sun\Jbi" and it says JBI installation finished, but I can find only one file in tht directory and that one is "Uninstall.class". below is the content of the installation log file
    =======file name Java_Business_Integration_SDK_1.0_install.B04280948=======
    Installing Java Business Integration SDK 1.0
    Log file: C:\DOCUME~1\maiyu\LOCALS~1\Temp\Java_Business_Integration_SDK_1.0_install.B04280948
    Installed: C:\Sun\jbi\Uninstall.class
    Uninstaller is at: C:\Sun\jbi\Uninstall.class
    Skipping component SoftwareComponent: Uninstaller because it is already installed.
    Skipping component SoftwareComponent: Sample Components because it is already installed.
    Skipping component SoftwareComponent: Server Core because it is already installed.
    Skipping component SoftwareComponent: Demo Files because it is already installed.
    Skipping component SoftwareComponent: Javadocs because it is already installed.
    Install complete.
    ======================END===========================
    one point I want to make is, priviously I had an installation which I uninstalled successfully but now when I am tryin to install yet again its havin problem.
    I have tried with windows registry (cleanin up neccessary things) but was of no use. :-(
    can some one pls tell me whats needed to be done, thanks in adavance
    thanks and regards,
    Maiyu

    Raffles10 wrote:
    hbekel wrote:
    Raffles10 wrote:I've had that problem too, when I install arch now I don't test X, I just go on to install the DE and everything works fine. I'm not even sure that X server test is valid anymore. If it appears that X installed ok just proceed and don't bother testing it.
    If you don't know why or how something you did worked out, please don't present it here as a "solution". To give no advice at all is better than giving bad advice. (no vodoo, please)
    The Beginners Guide has all the necessary information.
    It certainly does, including:
    Note:  Some users have found after the upgrade to Xorg 1.6 that this test fails (no hollow X appears and no capacity for cursor movement is enabled), but this does not indicate a problem with the installation of X. You may want to double check by running the next test in this guide.
    When the X test fails during installation we could spend ages trying to figure out why, but if everything is actually installed and working as it should be, why waste the time ? Especially for a newbie, installation can be difficult enough without trying to solve things that don't actually indicate a problem.;)
    majiq, I'm glad I'm not the only one that actually reads the Beginners Guide.:)
    Well, I screwed up, admitted.
    @Raffles: sorry for wrongly accusing you, I aplologize. Your post might have been a little clearer, but as it wasn't, I should certainly have double checked. I did check the Guide for the input hotplugging and Ctrl+Alt+Backspace stuff, but I obviously missed the note about the failing test.

  • How can I deploy JBI Application in Sun Java System Application Server 9?

    I developed a demo "Loan Processing Composite Application " in Netbeans.org(http://www.netbeans.org/kb/55/loanprocessing.html).
    The guide only show the deployment using Netbeans6.Now I want to deploy it directly using Server9 , how can I do?
    How to deploy a soa application in Sun Java System Application Server 9? Is there any doc?
    Please~~I'm puzzled.

    To deploy a JBI application to Sun's App Server, you will need a JBI compliant ESB installed. OpenESB would be my first choice here. Then as far as installing your components without Netbeans, there are two choices. 1) Copy your SA's to the JBI/ESB autodeploy directory and you binding components and service engines to the JBI/ESB autoinstall directory. 2) Use the ant tasks that the JBI specification (http://jcp.org/en/jsr/detail?id=208) requires for all JBI implementations. OpenESB's JBI tasks are detailed here: http://wiki.open-esb.java.net/Wiki.jsp?page=JBIAntTaskReference. These ant tasks can be wrapped with maven goals if needed.
    Jeff

  • JBI Shared Libraries

    Hi. I have arrived to a new project and they are working with JBI (developing BPEL) with Glassfish + openESB.
    I have no experience with JBI and I've been request to do some research about JBI Shared libraries. The problem comes for us when two composite aplications have to share one resource (in this case an .xsd file that includes other schema files). I don't know how to do such a thing. What I've done so far is:
    - create a new project (as a java project in netbeans) with the needed files
    - create the jbi.xml file under the META-INF folder
    <?xml version="1.0" encoding="UTF-8"?>
    <jbi
        xmlns="http://java.sun.com/xml/ns/jbi" version="1.0"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xmlns:identification="http://www.sun.com/jbi/descriptor/identification/v1.0">
        <!-- identification information about this shared library-->
        <shared-library class-loader-delegation="self-first">
            <identification>
                <name>my-shared-lib</name>
                <description>JBI shared library</description>
                <identification:VersionInfo component-version="1.0.0" build-number="000001"/>
            </identification>
            <shared-library-class-path>
                <path-element>./xsd/Requests/request1.xsd</path-element>
                <path-element>./xsd/Requests/types.xsd</path-element>
            </shared-library-class-path>
        </shared-library>
    </jbi>- deploy in the glassfish server via web interface
    But when the POJO class that needs that file it is not available (neither in the classpath). What I have to do or what I'm doing wrong?.
    Thanks in advance

    "Also with regards shared libraries - whn some people come out of their browsers they clear their temporary internet folders of everything ie: cached/cookies too. So those people would have to redownload everytime. Is that right?"
    Cookies do not matter for caching. If they set their browser to clear cache - ALL files will be loaded every time new sessions starts.
    "So even if I create that framework to test for changes which I doubt I can do then
    it sounds like an excellent idea to have various shared libraries just for the fact that it doesn't matter
    about file size but the positive is that if I change one library the other remain unchanged.
    Would that be a correct assumption?"
    There is no single correct answer or even recommendation to how to deal with RSLs (Runtime Shared Libraries). Each application dictates its own rules that depend on objects availability at the points they need to be consumed. Size may or may not matter (again, answer depends on architecture and internal application business logic).
    From the standpoint of choices of what to load and what is changed, if there is no mechanism that detects changes and because of how caching is done - it is only all or nothing approach (either all RSLs have to be loaded per session or one relies exclusively on browser cache).
    Change detection is pretty difficult to implement if you rely on client side only because, again, how cahing is handled.
    Also, conceptually RSLs must be very stable entities and shouldn't be something that changes often if ever. If they are meant to change often - it is definitely a critical design flaw. Perhaps, this case indicates that what is actually happens is that RSLs attempt to represent data/information/presentation layers. Data MUST EXIST TOTALLY separate from logic and presentation. I cannot stress it strong enough - mixing information, presentation and logic leads to major inefficiencies if not disasters.

  • [beginner] Relationship between app server and JBI container

    Hello,
    I downloaded the Sun app server as well as the JBI SDK and I would like to understand how they relate to each other. Is the JBI SDK a plug-in in the app server? Does it run on top of it? What part of J2ee are used by JBI?(servlets, ejbs, JCA???).
    Thanks in advance,
    Julien.
    PS
    Any answer is welcome. I am a complete beginner in JBI and I am looking for some primer that will help me get started with the spec...

    JBI is a specification; its up to the implementations to decide how they interact with different application servers. e.g. Sun's RI may work in Sun's app server and, say, JBoss. ServiceMix is already integrated into Apache Geronimo but has deployers for any Servlet engine and JBoss.
    Typically a JBI container will use servlets for HTTP bindings and can use EJBs if required. JCA integration is an option too - e.g. ServiceMix can either integrate with the application servers JCA engine or can use its own embedded JCA engine - Jencks (http://jencks.org).
    James
    http://logicblaze.com/

  • JMX interface of JBI

    Hi people,
    I have been looking for a way to develop, in my web application, some kind of administration console for starting/stopping/deploying/undeploying services to an ESB.
    I want to do this because I have to configure all web services registered in my web application in some ESB. And I have to do this for JBossESB, OpenESB, Mule, Sonic and IBM ESBs.
    What I really want to do is allow that my web application connects to some ESBs to configure services into them. It's like to have the web interface that some of them provide to make the configuration from my web application.
    I have been talking about this with some guys and two possibilities that they gave me are:
    1. To develop everything into the web application and send the information through JMX.
    2. To develop a generator of XML content (in memory) and send it the ESB, where it would has another implementation made by me, like a module (one of the guys said me that this could be a JBI Service Engine), which would receive the XML content generated by the web application.
    Using the first one possibility, I would have all solution into my application and developing the other one, I would have one implementation to each ESB that I want to connect to if it wouldn't be done with JBI (I think.. right? Because it seams that it would be the same if I do it with JBI).
    One guy told me that the second one would be the best, because, until he knows (based on the PoCs (proof of concept) he made, with JBossESB, Mule and WebSphere ESB), some of the ESBs he tested require some manual configuration to publish the services to be accessed through the ESB. He didn't do anything with JBI and didn't know anything about this.
    Another thing is that if I deploy only once a JBI Service Engine (SE), I can do the configuration of every service I want to publish in the ESB through this SE. In other words, I won't need to ask to the admin of ESB do the configuration to me (or do it through the web interface of ESB).
    After talk to some guys and expose these ideias to another one, this third guy told me that the best way would be to develop it through JMX interface of JBI.
    In this way, I would like ask you guys where can I find some examples related to this kind of implementation (JMX interface of JBI).
    I thank you in advance!
    Regards,
    Luiz

    Hi,
    You can search SDN for the same, there are lots of document/wiki pages available here.
    To find the details of interface you need the IDOC number or msg type. Your question is not very clear to me.. Can you be specific what the requirement ?

  • Javax.jbi.messaging.MessagingException: More than one operation defined

    Hi,
    i had already implemented a web service consisting of 6 methods that works fine. Now i want to access this service via JBI. Therefore i developed a service assembly containing only of a soap binding component. When i try to access the jbi environment via the inbound endpoint OpenESB throws following exception:
    [#|2006-07-26T16:23:50.531+0200|WARNING|sun-appserver-pe9.0|com.sun.jbi.component.com.sun.httpsoapbc-1.0-2com.sun.jbi.httpsoapbc.embedded.GrizzlyRequestProcessor|_ThreadID=32;_ThreadName=httpWorkerThread-12010-2;_RequestID=a33dbb24-d088-4a6a-9642-96187c32bb36;|Exception in processing request.
    javax.jbi.messaging.MessagingException: More than one operation defined. Unable to resolve operation: {http://service}UseRepositoryService,UseRepository,inbound
         at com.sun.jbi.httpsoapbc.InboundMessageProcessor.execute(InboundMessageProcessor.java:214)
         at com.sun.jbi.httpsoapbc.embedded.GrizzlyRequestProcessor.processAsynchRequest(GrizzlyRequestProcessor.java:214)
         at com.sun.jbi.httpsoapbc.embedded.GrizzlyRequestProcessor.service(GrizzlyRequestProcessor.java:173)
         at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
         at com.sun.jbi.httpsoapbc.embedded.JBIGrizzlyAsyncFilter.doFilter(JBIGrizzlyAsyncFilter.java:70)
         at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.invokeFilters(DefaultAsyncExecutor.java:143)
         at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.interrupt(DefaultAsyncExecutor.java:132)
         at com.sun.enterprise.web.connector.grizzly.async.AsyncProcessorTask.doTask(AsyncProcessorTask.java:81)
         at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
         at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
    How can i specify in my service assembly that if i send a SOAP request for method X on my client that OpenESB routes this message to the correct Outbound endpoint?
    Thank you
    Thomas

    Hello Andi,
    thanks for your reply. To exclude the soap action error i will post the complete wsdl file now. But in my opinion every operation has its own input and output definition.
    The consumer wsdl:
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions targetNamespace="http://service" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://service" xmlns:intf="http://service" xmlns:tns1="http://types" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <!--WSDL created by Apache Axis version: 1.2.1
    Built on Jun 14, 2005 (09:15:57 EDT)-->
    <wsdl:types>
    <schema elementFormDefault="qualified" targetNamespace="http://service" xmlns="http://www.w3.org/2001/XMLSchema">
    <import namespace="http://types"/>
    <element name="loadEcore">
    <complexType>
    <sequence>
    <element name="ecoreId" type="xsd:long"/>
    </sequence>a
    </complexType>
    </element>
    <element name="loadEcoreResponse">
    <complexType>
    <sequence>
    <element name="loadEcoreReturn" type="xsd:base64Binary"/>
    </sequence>
    </complexType>
    </element>
    <element name="loadInstance">
    <complexType>
    <sequence>
    <element name="instanceId" type="xsd:long"/>
    </sequence>
    </complexType>
    </element>
    <element name="loadInstanceResponse">
    <complexType>
    <sequence>
    <element name="loadInstanceReturn" type="xsd:base64Binary"/>
    </sequence>
    </complexType>
    </element>
    <element name="loadInstanceForProject">
    <complexType>
    <sequence>
    <element name="instanceId" type="xsd:long"/>
    </sequence>
    </complexType>
    </element>
    <element name="loadInstanceForProjectResponse">
    <complexType>
    <sequence>
    <element name="loadInstanceForProjectReturn" type="xsd:base64Binary"/>
    </sequence>
    </complexType>
    </element>
    <element name="deleteInstance">
    <complexType>
    <sequence>
    <element name="instanceId" type="xsd:long"/>
    </sequence>
    </complexType>
    </element>
    <element name="deleteInstanceResponse">
    <complexType>
    <sequence>
    <element name="deleteInstanceReturn" type="xsd:boolean"/>
    </sequence>
    </complexType>
    </element>
    <element name="getAllInstancesFromDB">
    <complexType/>
    </element>
    <element name="getAllInstancesFromDBResponse">
    <complexType>
    <sequence>
    <element maxOccurs="unbounded" name="getAllInstancesFromDBReturn" type="tns1:InstancePackageValueBean"/>
    </sequence>
    </complexType>
    </element>
    <element name="saveInstance">
    <complexType>
    <sequence>
    <element name="resourceBytes" type="xsd:base64Binary"/>
    <element name="fileName" type="xsd:string"/>
    </sequence>
    </complexType>
    </element>
    <element name="saveInstanceResponse">
    <complexType>
    <sequence>
    <element name="saveInstanceReturn" type="xsd:boolean"/>
    </sequence>
    </complexType>
    </element>
    </schema>
    <schema elementFormDefault="qualified" targetNamespace="http://types" xmlns="http://www.w3.org/2001/XMLSchema">
    <complexType name="InstancePackageValueBean">
    <sequence>
    <element name="ecoreId" type="xsd:long"/>
    <element name="fileName" nillable="true" type="xsd:string"/>
    <element name="id" type="xsd:long"/>
    <element name="name" nillable="true" type="xsd:string"/>
    <element name="usedModels" nillable="true" type="xsd:string"/>
    </sequence>
    </complexType>
    </schema>
    </wsdl:types>
    <wsdl:message name="loadEcoreRequest">
    <wsdl:part element="impl:loadEcore" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="loadEcoreResponse">
    <wsdl:part element="impl:loadEcoreResponse" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="saveInstanceResponse">
    <wsdl:part element="impl:saveInstanceResponse" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="loadInstanceForProjectResponse">
    <wsdl:part element="impl:loadInstanceForProjectResponse" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="loadInstanceResponse">
    <wsdl:part element="impl:loadInstanceResponse" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="getAllInstancesFromDBRequest">
    <wsdl:part element="impl:getAllInstancesFromDB" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="loadInstanceRequest">
    <wsdl:part element="impl:loadInstance" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="getAllInstancesFromDBResponse">
    <wsdl:part element="impl:getAllInstancesFromDBResponse" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="loadInstanceForProjectRequest">
    <wsdl:part element="impl:loadInstanceForProject" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="saveInstanceRequest">
    <wsdl:part element="impl:saveInstance" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="deleteInstanceRequest">
    <wsdl:part element="impl:deleteInstance" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="deleteInstanceResponse">
    <wsdl:part element="impl:deleteInstanceResponse" name="parameters"/>
    </wsdl:message>
    <wsdl:portType name="UseRepository">
    <wsdl:operation name="loadEcore">
    <wsdl:input message="impl:loadEcoreRequest" name="loadEcoreRequest"/>
    <wsdl:output message="impl:loadEcoreResponse" name="loadEcoreResponse"/>
    </wsdl:operation>
    <wsdl:operation name="loadInstance">
    <wsdl:input message="impl:loadInstanceRequest" name="loadInstanceRequest"/>
    <wsdl:output message="impl:loadInstanceResponse" name="loadInstanceResponse"/>
    </wsdl:operation>
    <wsdl:operation name="loadInstanceForProject">
    <wsdl:input message="impl:loadInstanceForProjectRequest" name="loadInstanceForProjectRequest"/>
    <wsdl:output message="impl:loadInstanceForProjectResponse" name="loadInstanceForProjectResponse"/>
    </wsdl:operation>
    <wsdl:operation name="deleteInstance">
    <wsdl:input message="impl:deleteInstanceRequest" name="deleteInstanceRequest"/>
    <wsdl:output message="impl:deleteInstanceResponse" name="deleteInstanceResponse"/>
    </wsdl:operation>
    <wsdl:operation name="getAllInstancesFromDB">
    <wsdl:input message="impl:getAllInstancesFromDBRequest" name="getAllInstancesFromDBRequest"/>
    <wsdl:output message="impl:getAllInstancesFromDBResponse" name="getAllInstancesFromDBResponse"/>
    </wsdl:operation>
    <wsdl:operation name="saveInstance">
    <wsdl:input message="impl:saveInstanceRequest" name="saveInstanceRequest"/>
    <wsdl:output message="impl:saveInstanceResponse" name="saveInstanceResponse"/>
    </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="UseRepositorySoapBinding" type="impl:UseRepository">
    <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsdl:operation name="loadEcore">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="loadEcoreRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="loadEcoreResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="loadInstance">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="loadInstanceRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="loadInstanceResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="loadInstanceForProject">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="loadInstanceForProjectRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="loadInstanceForProjectResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="deleteInstance">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="deleteInstanceRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="deleteInstanceResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="getAllInstancesFromDB">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="getAllInstancesFromDBRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="getAllInstancesFromDBResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="saveInstance">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="saveInstanceRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="saveInstanceResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="UseRepositoryService">
    <wsdl:port binding="impl:UseRepositorySoapBinding" name="UseRepository">
    <wsdlsoap:address location="http://localhost:12010/service/repository"/>
    </wsdl:port>
    </wsdl:service>
    </wsdl:definitions>
    Except for the service name, port, address etc the provider wsdl is the same.
    Could you tell me if it works when i will only use one operation for example?
    I had already implemented a service assembly which contained only one operation. That SA worked fine.
    If the Service Assembly and Binding Component descriptors had wrong references e.g. the wrong interface-name, would OpenESB throws an exception while deployment?
    In addition, could you tell me a good link to a nice bpel engine example? How is the interaction between client ans service using the bpel engine?
    I think using the SoapBC the interaction is following:
    Client --> BC --> Service
    With Bpel engine?
    Client --> BC --> bpel --> BC2 --> service?
    Thanks a lot
    Thomas

Maybe you are looking for

  • FSCM-CR Case types for Documented Credit Decision (FDCD, FDCA) missing.

    Hi FSCM community I am looking at the FSCM CR module and got some issues here and there. Here's one of them. Documentation for the SAP IMG node: FSCM -> Credit Management -> Credit Risk Monitoring -> Documented Credit Decision -> Settings in the Case

  • Opening Old Documents in Numbers 3.0

    After updating to Mavericks and Numbers 3.0 I can't open Numbers documents that were saved to the computer previous to the update. I get an error that says it can't be opened because it is from an unidentified developer.

  • How do I let a inserted picture flow over the other text boxes

    I am creating a poster.  I have a text box on top and one on the bottom.  I want to insert a picture in the middle and want the picture to kind of flow around the other two text boxes without blacking out the two text boxes.  Also, how can I curve th

  • Query builder within application

    Hi , is that possible to call query builder as a pop up window from the application ? Thanks ...

  • Errors Handling Tips

    Hi basically I have task to enhanced the error handling in software. Can someone give the common errors to check for  when dealing with embedded hardware and CCA card. The interface we are using is GPIB . I wanted  to start at least by incorporating