June 2008 - jboss-dev-forums - Jboss List Archives

[Design of EJB 3.0] - Re: trunk Ejb3Deployment is incompatible with jbossas trunk

by ALRubinger

VSF Beta13 was released the 3rd of June...: http://repository.jboss.org/maven2/org/jboss/jboss-vfs/2.0.0.Beta13/ EJB3 Core has no dependency on this. Try upgrading from 11 to 13? S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156145#4156145 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156145

17 years, 10 months

1
0
0 / 0

[Design of EJB 3.0] - Re: trunk Ejb3Deployment is incompatible with jbossas trunk

by scott.stark＠jboss.org

I have it compiling, and starting, but runtime is showing vfs version issues: | 16:39:12,728 ERROR [AbstractKernelController] Error installing to Start: name=persistence.units:ear=ejb3_pm_basic_vehicles.ear,unitName=CTS-EM state=Create | java.lang.NoSuchMethodError: org.jboss.virtual.VFSUtils.isNestedFile(Lorg/jboss/virtual/VirtualFile;)Z | at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:227) | What vfs version is needed? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156144#4156144 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156144

17 years, 10 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JAXWSClientMetaDataBuilder

by thomas.diesler＠jboss.com

The problem with InputStream is, that it cannot deal with with relative imports. So your wsdl cannot reference other wsdls nor external xsd files. You could also use the wsld4j API directly. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156141#4156141 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156141

17 years, 10 months

1
0
0 / 0

[Design of JBoss Web Services] - verbose logging issue

by thomas.diesler＠jboss.com

There seems to be a logging issue | 01:18:28,391 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core | 01:18:28,391 INFO [NativeServerConfig] 3.0.2-SNAPSHOT | 01:18:29,127 INFO [BareWSFRuntime] null -> RequestHandlerFactory: org.jboss.wsf.stack.jbws.RequestHandlerFactoryImpl@1f86f75 | 01:18:29,127 INFO [BareWSFRuntime] null -> TransportManagerFactory: org.jboss.wsf.container.jboss50.transport.BareTransportManagerFactory@15daaef | 01:18:29,127 INFO [BareWSFRuntime] WebserviceJSERuntime -> DeploymentAspectManager: WSDeploymentAspectManagerJSE :org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl@4b2d10 | 01:18:29,127 INFO [BareWSFRuntime] WebserviceJSERuntime -> EndpointRegistry: org.jboss.wsf.framework.management.ManagedEndpointRegistry@17b84f9 | 01:18:29,128 INFO [BareWSFRuntime] null -> RequestHandlerFactory: org.jboss.wsf.stack.jbws.RequestHandlerFactoryImpl@1f86f75 | 01:18:29,128 INFO [BareWSFRuntime] null -> DeploymentAspectManager: WSDeploymentAspectManagerEndpointAPI :org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl@572554 | 01:18:29,128 INFO [BareWSFRuntime] null -> EndpointRegistry: org.jboss.wsf.framework.management.ManagedEndpointRegistry@17b84f9 | 01:18:29,128 INFO [BareWSFRuntime] null -> TransportManagerFactory: org.jboss.wsf.container.jboss50.transport.BareTransportManagerFactory@153ccbe | 01:18:29,129 INFO [BareWSFRuntime] null -> DeploymentAspectManager: WSDeploymentAspectManagerEJB :org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl@a70e3a | 01:18:29,129 INFO [BareWSFRuntime] WebserviceEJBRuntime -> RequestHandlerFactory: org.jboss.wsf.stack.jbws.RequestHandlerFactoryImpl@1f86f75 | 01:18:29,129 INFO [BareWSFRuntime] WebserviceEJBRuntime -> EndpointRegistry: org.jboss.wsf.framework.management.ManagedEndpointRegistry@17b84f9 | 01:18:29,129 INFO [BareWSFRuntime] WebserviceEJBRuntime -> TransportManagerFactory: org.jboss.wsf.container.jboss50.transport.BareTransportManagerFactory@1970646 | 01:18:30,302 INFO [TomcatDeployment] deploy, ctxPath=/jbossws, vfsUrl=jbossws.sar/jbossws-management.war | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156140#4156140 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156140

17 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - Cannot build jbpm3/tags/jpdl_3_2_2

by thomas.diesler＠jboss.com

I can't seem to build jpdl-3.2.2 | [tdiesler@tdvaio build]$ ant -p | Buildfile: build.xml | | Main targets: | | build.bpel builds bpel and all its dependent jbpm subprojects | build.jpdl builds jpdl and all its dependent jbpm subprojects | clean cleans all subprojects | cruise the nightly integration test build | get.dependencies gets all the dependencies. after this target, you should be able to build without a network connection. | install.jbpm.ant copies junit and clover jars to the directory ${ant.home}/lib | test.jpdl builds and then tests all testable subprojects | Default target: build.jpdl | [tdiesler@tdvaio build]$ ant build.jpdl | ... | [javadoc] 23 warnings | [zip] Building zip: /home/tdiesler/cvs/jbpm3/tags/jpdl_3_2_2/jpdl/jar/target/jbpm-jpdl-javadoc.zip | | install.javadoc: | [copy] Copying 1 file to /home/tdiesler/jbpm/repository/jbpm/jpdl/3.2.2/lib | | jpdl.javadoc.fetch.from.repo: | | jpdl.userguide: | | jpdl.userguide.build.from.source: | | BUILD FAILED | /home/tdiesler/cvs/jbpm3/tags/jpdl_3_2_2/build/build.xml:35: The following error occurred while executing this line: | /home/tdiesler/cvs/jbpm3/tags/jpdl_3_2_2/build/base.project.build.xml:619: The following error occurred while executing this line: | /home/tdiesler/cvs/jbpm3/tags/jpdl_3_2_2/build/base.project.build.xml:624: The following error occurred while executing this line: | /home/tdiesler/cvs/jbpm3/tags/jpdl_3_2_2/jpdl/userguide/build.xml:17: Cannot find /home/tdiesler/jbpm/repository/docbook-support/support.xml imported from /home/tdiesler/cvs/jbpm3/tags/jpdl_3_2_2/jpdl/userguide/build.xml | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156138#4156138 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156138

17 years, 10 months

1
0
0 / 0

[Design of EJB 3.0] - Re: trunk Ejb3Deployment is incompatible with jbossas trunk

by scott.stark＠jboss.org

I'll look at getting the ejb3 module working with 0.1.2. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156137#4156137 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156137

17 years, 10 months

1
0
0 / 0

[Design of EJB 3.0] - Re: trunk Ejb3Deployment is incompatible with jbossas trunk

by ALRubinger

I've released EJB3 Core 0.1.2. So now we've got a chicken/egg thing. I couldn't test this against AS because of the API conflict, and Ales couldn't resolve the API conflict until I released. :) Both Anil and I tried Ales' patch in this Thread to resolve AS to no avail. Ales, how'd you like to proceed? You can upgrade AS locally, check your patch by running the new AS TestSuite Smoke tests, and if that's good, push the upgrade on your own. Alternatively you can send me another patch to the "ejb3" module and I'll doing testing and make the final commits. Other projects waiting on this, so this is a bit of a priority. After this is resolved, I'll recommit my changes to introduce EJB3 Proxy into EJB3 Core, and do a follow-up release. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156136#4156136 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156136

17 years, 10 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Re: Ability to restart a Connect with SocketServerInvoker

by ron.sigal＠jboss.com

Thanks, Brian. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156118#4156118 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156118

17 years, 10 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Use of

by bstansberry＠jboss.com

BTW, anyone reading this thread, please ignore my example above. The thirdparty/pom.xml has a maven-buildmagic-thirdparty-plugin with a plugin config that uses a bunch "dependency" elements inside a "mappedDependencies" element. Don't put a lib without a "mapping" element there; it doesn't work. Scroll down and put it in the regular maven dependencies section. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156116#4156116 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156116

17 years, 10 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Re: Ability to restart a Connect with SocketServerInvoker

by bstansberry＠jboss.com

Done. http://jira.jboss.com/jira/browse/JBAS-5590 . I opened a separate JIRA for the SocketServerInvoker problem ( http://jira.jboss.com/jira/browse/JBREM-992 ). That's not a big deal to me personally; just something I stumbled across. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156114#4156114 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156114

17 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums June 2008