Error when building openesb-components

classic Classic list List threaded Threaded
26 messages Options
12
Reply | Threaded
Open this post in threaded view
|

AW: Error when building openesb-components

Stefan Müller-Wilken

>I've clean and setup entirely my OE components repository to build it again... without issue at all :(

 

Well, but wouldn’t you at least have faced the missing jar errors for Saxon, JSR173 and for jdbc-stdext? I just can’t see how those could relate to my setup…

 

Cheers

Stefan


Acando GmbH, Millerntorplatz 1, 20359 Hamburg, Germany | Geschäftsführer: Guido Ahle | Amtsgericht Hamburg, HRB 76048 | Ust.Ident-Nr.:DE208833022

Reply | Threaded
Open this post in threaded view
|

AW: Error when building openesb-components

Stefan Müller-Wilken
In reply to this post by Stefan Müller-Wilken
>I've clean and setup entirely my OE components repository to build it again... without issue at all :(

 

Well, but wouldn’t you at least have faced the missing jar errors for Saxon, JSR173 and for jdbc-stdext? I just can’t see how those could relate to my setup…

 

Cheers

Stefan



Acando GmbH, Millerntorplatz 1, 20359 Hamburg, Germany | Geschäftsführer: Guido Ahle | Amtsgericht Hamburg, HRB 76048 | Ust.Ident-Nr.:DE208833022

Reply | Threaded
Open this post in threaded view
|

AW: Error when building openesb-components

Stefan Müller-Wilken
In reply to this post by Stefan Müller-Wilken

Okay, I have finally successfully worked my way through the build process. What was left to do was pushing schedulerbc by copying jbi.xml to a second location and switching Ant from 1.7.1 to 1.9.7 and then „mvn clean“ing and „mvn install“ing again.

 

While this was a little bumpy, it is light years away from the building complexity of past times. Very good job, David & Co.!

 

Cheers

Stefan


Acando GmbH, Millerntorplatz 1, 20359 Hamburg, Germany | Geschäftsführer: Guido Ahle | Amtsgericht Hamburg, HRB 76048 | Ust.Ident-Nr.:DE208833022

Reply | Threaded
Open this post in threaded view
|

RE: Error when building openesb-components

hammad.karamat
This post has NOT been accepted by the mailing list yet.

Good to know that and Congratulations Stefan. How great it would be if you could have your “way through” documented for others as well.

 

Cheers.

HKD

 

From: Stefan Müller-Wilken [via OpenESB Community Forum] [mailto:ml-node+[hidden email]]
Sent: Thursday, December 15, 2016 8:36 PM
To: Hammad Karamat Dar
Subject: AW: Error when building openesb-components

 

Okay, I have finally successfully worked my way through the build process. What was left to do was pushing schedulerbc by copying jbi.xml to a second location and switching Ant from 1.7.1 to 1.9.7 and then „mvn clean“ing and „mvn install“ing again.

 

While this was a little bumpy, it is light years away from the building complexity of past times. Very good job, David & Co.!

 

Cheers

Stefan


Acando GmbH, Millerntorplatz 1, 20359 Hamburg, Germany | Geschäftsführer: Guido Ahle | Amtsgericht Hamburg, HRB 76048 | Ust.Ident-Nr.:DE208833022

 


If you reply to this email, your message will be added to the discussion below:

http://openesb-community-forum.794670.n2.nabble.com/Error-when-building-openesb-components-tp7581356p7581391.html

To start a new topic under OpenESB Community Forum, email [hidden email]
To unsubscribe from OpenESB Community Forum, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

RE: Error when building openesb-components

rrialq
This post has NOT been accepted by the mailing list yet.
This post was updated on .

Hello.
These are the steps I followed to get a successfull build in Linux:

  1. Download my attached file setBuildingEnvironment.sh to the same folder as openesb-components folder (not inside), and give it execution permission
    chmod +x ./setBuildEnvironment.sh
  2. At shell execute the script for setting the environment (if not exists the artifact javax.sql:jdbc-stdext, the script downloads and install it to the repository).
    source ./setBuildEnvironment
  3. Modify ojc-core/component-common/xmlbeans/modified/m2.ant:
    • Line 122: Replace http://freefr.dl.sourceforge.net/project/saxon/Saxon-B/8.8.0.7/saxonb8-8-0-7j.zip with http://ufpr.dl.sourceforge.net/project/saxon/Saxon-B/8.8.0.7/saxonb8-8-0-7j.zip.
    • Line 143: Replace http://apache.xmlcity.org/java-repository/xmlbeans/jars/jsr173_1.0_api_bundle.jar with http://source.sakaiproject.org/maven/xmlbeans/jars/jsr173_1.0_api_bundle.jar.
  4. In ./openesb-components/ojc-core/httpsoapbc/httpsoapbcimpl/pom.xml the artifact webservices-rt is needed for a successfull build, so add (I take the version from another pom.xml)
        <dependency>
            <groupId>org.glassfish.metro</groupId>
            <artifactId>webservices-rt</artifactId>
            <version>2.2.0-4</version>
        </dependency>
    after
        <dependency>
            <groupId>open-esb</groupId>
            <artifactId>jbi-ext</artifactId>
        </dependency>
  5. mvn -Dmaven.repo.local=${REPO_LOCAL} clean
  6. mvn -Dmaven.repo.local=${REPO_LOCAL} install
You will need JDK6 for build the components, because JDK7 breaks compilation of some java files because of the encoding (some files are not UTF-8). I hope these little instructions help to somebody.
Reply | Threaded
Open this post in threaded view
|

RE: Error when building openesb-components

rrialq
This post has NOT been accepted by the mailing list yet.
With the above steps and the component built with the openesb-restbc repository  code, when I deploy a CA I've got the following log INFO:
 
2017-03-05T16:37:11.574+0100 FINE [com.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle] (SSOCA-sun-http-binding)ClassName=com.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle;MethodName=endpointActivated; About to start port 9080, protocol is: http...
2017-03-05T16:37:11.574+0100 FINE [com.sun.jbi.httpsoapbc.jaxwssupport.JAXWSEndpointFactory] (SSOCA-sun-http-binding)ClassName=com.sun.jbi.httpsoapbc.jaxwssupport.JAXWSEndpointFactory;MethodName=createWSEndpoint; Creating WSEndpoint with primary WSDL URL: file:/home/rrialq/apps/OE-Instance-3.0.5/server/jbi/service-assemblies/SSOCA/SSOCA-sun-http-binding/sun-http-binding/SSOCA.wsdl
2017-03-05T16:37:11.575+0100 FINE [com.sun.jbi.httpsoapbc.jaxwssupport.JAXWSEndpointFactory] (SSOCA-sun-http-binding)ClassName=com.sun.jbi.httpsoapbc.jaxwssupport.JAXWSEndpointFactory;MethodName=createWSEndpoint; Adding imported WSDL document with URL: file:/home/rrialq/apps/OE-Instance-3.0.5/server/jbi/service-assemblies/SSOCA/SSOCA-sun-http-binding/sun-http-binding/SSOBPEL/sso.wsdl to the list of SDDocumentSource...
2017-03-05T16:37:11.597+0100 FINE [org.glassfish.gmbal.impl] (SSOCA-sun-http-binding)ClassName=org.glassfish.gmbal.impl.TypeConverterImpl;MethodName=handleAsString; "GMBAL820: No <init>(String) constructor available for class com.sun.xml.ws.api.BindingID"
CONTEXT:
	(  0): constructMean(com.sun.xml.ws.server.MonitorRootService@53ea63b,SSOCAService1-identityPort)
	(  1): getSkeleton(com.sun.xml.ws.server.MonitorRootService)
	(  2): analyzeAttributes(ClassAnalyzer[com.sun.xml.ws.server.MonitorRootService com.sun.xml.ws.server.MonitorBase java.lang.Object])
	(  3): getTypeConverter(com.sun.xml.ws.api.BindingID)
	(  4): makeTypeConverter(com.sun.xml.ws.api.BindingID,ManagedObjectManagerImpl[domain=com.sun.metro])
	(  5): handleClass(type,com.sun.xml.ws.api.BindingID)
2017-03-05T16:37:11.607+0100 FINE [org.glassfish.gmbal.impl] (SSOCA-sun-http-binding)ClassName=org.glassfish.gmbal.impl.TypeConverterImpl;MethodName=handleAsString; "GMBAL820: No <init>(String) constructor available for class com.sun.xml.ws.api.server.Container"
CONTEXT:
	(  0): constructMean(com.sun.xml.ws.server.MonitorRootService@53ea63b,SSOCAService1-identityPort)
	(  1): getSkeleton(com.sun.xml.ws.server.MonitorRootService)
	(  2): analyzeAttributes(ClassAnalyzer[com.sun.xml.ws.server.MonitorRootService com.sun.xml.ws.server.MonitorBase java.lang.Object])
	(  3): getTypeConverter(com.sun.xml.ws.api.server.Container)
	(  4): makeTypeConverter(com.sun.xml.ws.api.server.Container,ManagedObjectManagerImpl[domain=com.sun.metro])
	(  5): handleClass(type,com.sun.xml.ws.api.server.Container)
2017-03-05T16:37:11.618+0100 INFO [com.sun.xml.ws.monitoring] (SSOCA-sun-http-binding) Metro monitoring rootname successfully set to: com.sun.metro:pp=/,type=WSEndpoint,name=SSOCAService1-identityPort
2017-03-05T16:37:11.619+0100 WARNING [org.glassfish.gmbal.impl] (SSOCA-sun-http-binding) "GMBAL901: JMX exception on registration of MBean MBeanImpl[type=WSEndpoint,name=SSOCAService1-identityPort,oname=com.sun.metro:pp=/,type=WSEndpoint,name=SSOCAService1-identityPort]"
2017-03-05T16:37:11.644+0100 FINE [com.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle] (SSOCA-sun-http-binding)ClassName=com.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle;MethodName=endpointActivated; Registered an external endpoint with service name: {SSOCA}SSOCAService1 and endpoint name: identityPort

The problem seems to be with services-rt-2.2.0-4.jar. May be configuring it as dependency in the pom.xml, as I've done, is not a solution as introduces transitive dependencies. I'll continue investigating it.
Somebody had this problem before?
12