[JBossWS] - Can someone confirm this wsconsume ant task behavior?
by babernat
I'm using the version included with JBoss AS 5.1.0.GA and it appears the wsdl attribute is using the location of the build file as the base directory for the relative path instead of what is defined in the basedir attribute for the ant project.
For example if I have the following ant build script located in a directory C:/myproject/build
| <project name="MyProject" basedir="../">
| <property environment="env"/>
| <path id="jboss.client.classpath">
| <fileset dir="${JBoss.client.lib}">
| <include name="**/*.jar"/>
| </fileset>
| </path>
| <taskdef name="wsconsume" classname="org.jboss.wsf.spi.tools.ant.WSConsumeTask" classpathref="jboss.client.classpath"/>
| <target name="generate-service">
| <wsconsume keep="true" package="com.whatever" destdir="build/gen" wsdl="build/tmpxml/MyProject.wsdl" verbose="true"/>
| </target>
| </project>
|
It appears that wsconsume is looking for the wsdl in:
c:\myproject\build\build\tmpxml\MyProject.wsdl
instead of:
c:\myproject\build\tmpxml\MyProject.wsdl
Since the basedir on the project is set to: ../ I would expect it to look for the wsdl relative to one directory higher. In fact this is how even the destdir attribute works. The way the wsdl attribute references files seems to be different from destdir and most other ant tasks I've seen.
Am I completely stupid and just missing something or does this not seem right?
Thanks.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240482#4240482
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240482
15 years
[EJB/JBoss] - Migrating JBoss 4.0.2 -> JBoss 5.0.0
by joaocarlos86
All,
i've suceffull migrate from jboss 4.0.2 to jboss 5.0.0, but when i try to deploy my app the exception is related:
| org.hibernate.AnnotationException: @OneToOne or @ManyToOne on br.unp.portal.menuPaginas.dominio.ItemAdministrativoPagina.itemAdministrativo references an unknown entity: br.unp.portal.usuariosPermissoes.dominio.ItemAdministrativo
| at org.hibernate.cfg.FkSecondPass.doSecondPass(FkSecondPass.java:56)
| at org.hibernate.cfg.AnnotationConfiguration.processFkSecondPassInOrder(AnnotationConfiguration.java:474)
| at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:295)
| at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1319)
| at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:915)
| at br.unp.arq.dao.Database.getSessionFactory(Database.java:56)
| at br.unp.arq.dao.Database.getSessionRequest(Database.java:111)
| at br.unp.arq.dao.Database.getSessionNoLog(Database.java:76)
| at br.unp.arq.dao.GenericDAO.getSession(GenericDAO.java:299)
| at br.unp.arq.dao.GenericDAO.<init>(GenericDAO.java:42)
| at br.unp.arq.dao.GenericDAO.<init>(GenericDAO.java:53)
| at br.unp.arq.controller.AbstractControllerCadastro.<init>(AbstractControllerCadastro.java:29)
| at br.unp.portal.controller.AbstractControllerPortal.<init>(AbstractControllerPortal.java:33)
| at br.unp.portal.menuPaginas.controller.JPortalMBean.<init>(JPortalMBean.java:199)
| at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
| at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
| at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
| at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
| at java.lang.Class.newInstance0(Class.java:355)
| at java.lang.Class.newInstance(Class.java:308)
| at org.apache.myfaces.config.annotation.TomcatAnnotationLifecycleProvider.newInstance(TomcatAnnotationLifecycleProvider.java:48)
| at org.apache.myfaces.config.ManagedBeanBuilder.buildManagedBean(ManagedBeanBuilder.java:85)
| at org.apache.myfaces.el.unified.resolver.ManagedBeanResolver.createManagedBean(ManagedBeanResolver.java:198)
| at org.apache.myfaces.el.unified.resolver.ManagedBeanResolver.getValue(ManagedBeanResolver.java:164)
| at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53)
| at org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:140)
| at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53)
| at org.apache.el.parser.AstIdentifier.getValue(AstIdentifier.java:61)
| at org.apache.el.parser.AstValue.getValue(AstValue.java:107)
| at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
| at org.apache.jasper.runtime.PageContextImpl.proprietaryEvaluate(PageContextImpl.java:925)
| at org.apache.jsp.jportal.sites.sistemas.autoatendimento.principal.cpdj5_jsp._jspService(cpdj5_jsp.java:111)
| at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
| at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369)
| at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:322)
| at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:249)
| 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.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:638)
| at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:444)
| at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:382)
| at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:310)
| at org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(ServletExternalContextImpl.java:341)
| at org.apache.myfaces.application.jsp.JspViewHandlerImpl.buildView(JspViewHandlerImpl.java:486)
| at org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:337)
| at org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41)
| at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:140)
| at javax.faces.webapp.FacesServlet.service(FacesServlet.java:155)
| at org.apache.myfaces.webapp.MyFacesServlet.service(MyFacesServlet.java:103)
| at br.unp.arq.controller.ArquiteturaFacesController.service(ArquiteturaFacesController.java:43)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:341)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| 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:235)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
| at org.jboss.web.tomcat.service.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:109)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
| at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
| at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
| 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:158)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
| at java.lang.Thread.run(Thread.java:619)
|
i'm using the default version of hibernate/annotation that come on with jboss 5.0.0.
after reading some in google about this i've found conflicting versions of hibernate/annotation and i'm adjusting this, removing the old implementation on lib folder of my project. the same annotations works in jboss 4.0.2 and i just dont know what to do. thanks folks.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240481#4240481
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240481
15 years
[Clustering/JBoss] - Re: ConcurrentModificationException during session serializa
by bstansberry＠jboss.com
To answer your #1 and #3, the key thing is to hold the WL for the minimum required time. You only have to hold it long enough to:
a) Accurately determine if anything needs to be replicated
b) Copy that into the DTO that's passed to the replication layer.
c) Serialize attributes.
Ideally a) and b) can be combined into one very quick step, although that would take some rework of logic. Then the WL could be acquired separately for c), which again should be quick. So you don't want to hold the WL for the duration of the replication.
Hmm, although that somewhat defeats the point, which is to get a consistent snapshot of the session. Separately locking for the serialization allows a request thread to sneak in and change the state of an attribute value.
#2 is more of an issue. By relying on synchronizing on the facade, we're basically giving priority to getting the replication out over consistency, and then letting the app enforce consistency by synchronizing on the facade.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240463#4240463
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240463
15 years