[Design of AOP on JBoss (Aspects/JBoss)] - Re: Some maven updates
by pgier
"kabir.khan(a)jboss.com" wrote : "pgier" wrote :
| | To compile the JRockit stuff you have to pass JROCKIT_HOME to maven.
| |
| Does maven have the concept of a local.properties file? It would be nice not to manually pass in this system property every time
|
There is a properties plugin that can be used to load properties, but I don't think this can be used to activate a profile (for the conditional compilation and jar). The other option would be to put the conditional logic in ant (in the antrun plugin) but I think the plugin only allows one target so you can't conditionally call the target. I'll try to come up with a better way to handle this part of the build.
"kabir.khan(a)jboss.com" wrote :
| mvn install from the top-level folder gives me OutOfMemoryErrors
|
It looks like you and Hudson are both getting this error when maven compiles the test classes. Since ant is doing this anyway, I'll take this part out for now and see if that prevents running out of memory.
"kabir.khan(a)jboss.com" wrote :
| I think JRockitPluggableClassPreProcessor.class should be in jrockit-pluggable-instrumentor.jar
|
Should JRockitClassPreProcessor also be included only in the jrockit jar? Currently it is only being included in the main jboss-aop.jar.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178071#4178071
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178071
17 years, 3 months
[Design of POJO Server] - Re: Testing Bootstrap Dependencies
by istudens＠redhat.com
I have completely rethought basic idea about the implementation of this test. Although I had consulted the issue with both Dominik and Jiri, I thought I was testing a nonsense. Maybe it will be better to reformulate the issue, because it is very brief.
I think the issue is about testing of bootstrap dependencies between services already in the profile. Therefore, for example the EJB3 test should contain a SAR using some EJB3 beans (stateless, stateful) with an appropriate dependency to Ejb3Container wrote in its jboss-service.xml.
The snippet of the EJB3's SAR code:
public class BootstrapDependencyEJB3Test
| extends ServiceMBeanSupport
| implements BootstrapDependencyEJB3TestMBean
| {
| ...
|
| @EJB
| DummyStatelessLocal stateless;
|
| @Override
| protected void startService() throws Exception
| {
| log.debug("BootstrapDependencyTest's SAR is starting");
|
| stateless.testCall(); // do nothing special
|
| log.debug("BootstrapDependencyTest's SAR is started");
| }
| ...
| }
The SAR's jboss-service.xml:
<?xml version="1.0" encoding="UTF-8"?>
| <deployment xmlns="urn:jboss:bean-deployer:2.0">
| <bean name="BootstrapDependencyEJB3Test" class="org.jboss.test.deployers_jbas5349.sar.BootstrapDependencyEJB3Test">
| <depends>Ejb3Deployer</depends>
| </bean>
| </deployment>
After start of the JBoss server the testcase tests just if the SAR was started.
Of course, the name of the SAR will be something like Aaa-bootstrap-dependency-jbas5349-ejb3.sar.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178062#4178062
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178062
17 years, 3 months
[Design of JBossXB] - org.jboss.ws.WSException: org.jboss.ws.core.binding.BindingE
by richard.opalka＠jboss.com
Hi folks,
we're dealing with strange problem on our QA machine (see http://jbossws.jboss.org:8180/hudson/job/Native-Core-AS-4.2.2/lastBuild/t...).
It's strange because we're not able to reproduce this problem locally.
Do you have an idea folks, what could be the problem and/or how we could debug it much more? Any help is highly appreciated. Here's the stack trace that we can see in our log files:
org.jboss.ws.WSException: org.jboss.ws.core.binding.BindingException: org.jboss.ws.core.jaxrpc.binding.jbossxb.UnmarshalException: Failed to parse source: -1:-1 6:92 The reference to entity "Version" must end with the ';' delimiter.
| at org.jboss.ws.core.soap.XMLContent.unmarshallObjectContents(XMLContent.java:248)
| at org.jboss.ws.core.soap.XMLContent.transitionTo(XMLContent.java:95)
| at org.jboss.ws.core.soap.SOAPContentElement.transitionTo(SOAPContentElement.java:139)
| at org.jboss.ws.core.soap.SOAPContentElement.getObjectValue(SOAPContentElement.java:171)
| at org.jboss.ws.core.EndpointInvocation.transformPayloadValue(EndpointInvocation.java:261)
| at org.jboss.ws.core.EndpointInvocation.getRequestParamValue(EndpointInvocation.java:113)
| at org.jboss.ws.core.EndpointInvocation.getRequestPayload(EndpointInvocation.java:133)
| at org.jboss.ws.core.server.DelegatingInvocation.getArgs(DelegatingInvocation.java:80)
| at org.jboss.wsf.container.jboss42.DefaultInvocationHandler.invoke(DefaultInvocationHandler.java:100)
| at org.jboss.wsf.container.jboss42.DefaultInvocationHandlerJAXRPC.invoke(DefaultInvocationHandlerJAXRPC.java:55)
| at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:219)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:476)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131)
| at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:81)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
| at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
| at java.lang.Thread.run(Thread.java:595)
| Caused by: org.jboss.ws.core.binding.BindingException: org.jboss.ws.core.jaxrpc.binding.jbossxb.UnmarshalException: Failed to parse source: -1:-1 6:92 The reference to entity "Version" must end with the ';' delimiter.
| at org.jboss.ws.core.jaxrpc.binding.JBossXBDeserializer.deserialize(JBossXBDeserializer.java:109)
| at org.jboss.ws.core.jaxrpc.binding.JBossXBDeserializer.deserialize(JBossXBDeserializer.java:60)
| at org.jboss.ws.core.binding.DeserializerSupport.deserialize(DeserializerSupport.java:58)
| at org.jboss.ws.core.soap.XMLContent.unmarshallObjectContents(XMLContent.java:178)
| ... 34 more
| Caused by: org.jboss.ws.core.jaxrpc.binding.jbossxb.UnmarshalException: Failed to parse source: -1:-1 6:92 The reference to entity "Version" must end with the ';' delimiter.
| at org.jboss.ws.core.jaxrpc.binding.jbossxb.JBossXBUnmarshallerImpl.unmarshal(JBossXBUnmarshallerImpl.java:63)
| at org.jboss.ws.core.jaxrpc.binding.JBossXBDeserializer.deserialize(JBossXBDeserializer.java:101)
| ... 37 more
| Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: -1:-1 6:92 The reference to entity "Version" must end with the ';' delimiter.
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:179)
| at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:126)
| at org.jboss.ws.core.jaxrpc.binding.jbossxb.JBossXBUnmarshallerImpl.unmarshal(JBossXBUnmarshallerImpl.java:59)
| ... 38 more
| Caused by: org.jboss.xb.binding.JBossXBRuntimeException: -1:-1 6:92 The reference to entity "Version" must end with the ';' delimiter.
| at org.jboss.xb.binding.sunday.unmarshalling.XsdBinderTerminatingErrorHandler.handleError(XsdBinderTerminatingErrorHandler.java:40)
| at org.apache.xerces.impl.xs.XMLSchemaLoader.reportDOMFatalError(Unknown Source)
| at org.apache.xerces.impl.xs.XSLoaderImpl.load(Unknown Source)
| at org.jboss.xb.binding.Util.loadSchema(Util.java:395)
| at org.jboss.xb.binding.sunday.unmarshalling.XsdBinder.bind(XsdBinder.java:175)
| at org.jboss.xb.binding.sunday.unmarshalling.XsdBinder.bind(XsdBinder.java:146)
| at org.jboss.xb.binding.sunday.unmarshalling.DefaultSchemaResolver.resolve(DefaultSchemaResolver.java:247)
| at org.jboss.xb.binding.sunday.unmarshalling.WildcardBinding.getElement(WildcardBinding.java:172)
| at org.jboss.xb.binding.sunday.unmarshalling.SequenceBinding$1.startElement(SequenceBinding.java:300)
| at org.jboss.xb.binding.sunday.unmarshalling.ModelGroupBinding$Cursor.startElement(ModelGroupBinding.java:159)
| at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:364)
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:324)
| at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
| at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
| at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
| at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
| at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
| at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
| at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
| at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:175)
| ... 40 more
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178059#4178059
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178059
17 years, 3 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Branch_1_4 build-messaging.properties...
by timfox
...I notice this contains version information:
| <property name="messaging.version.major" value="1"/>
| <property name="messaging.version.minor" value="4"/>
| <property name="messaging.version.revision" value="1"/>
| <property name="messaging.version.incrementing" value="25"/>
| <property name="messaging.version.tag" value="CR1"/>
| <property name="messaging.version.name" value="WaterMelon"/>
| <property name="messaging.version.cvstag" value="JBossMessaging_1_4_1_CR1"/>
| <property name="module.name" value="messaging"/>
| <property name="module.Name" value="JBoss Messaging"/>
| <property name="module.version" value="${messaging.version.major}.${messaging.version.minor}.${messaging.version.revision}.${messaging.version.tag}"/>
|
| <property name="jms.version.major" value="1"/>
| <property name="jms.version.minor" value="1"/>
| <property name="jms.version" value="1.1"/>
|
This needs to be moved into the build-messaging-as5.xml or build-messaging-eap43.xml files since as5 or eap 43 will have a different version.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178027#4178027
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178027
17 years, 3 months