[JBoss Seam] - StackOverflowError Shenanigans
by jimk1723
I made the mistake of naming one of my Seam components "org" for my organization entities, e.g. @Factory("org"). Seam blew up. Is this one for JIRA or is there a best practices document for component naming?
I'll spare you the 50 page stacktrace and include only the coup de'gras:
| Caused by: javax.faces.el.EvaluationException: Cannot get value for expression '#{org.jboss.seam.core.facesMessages}'
| at org.apache.myfaces.el.ValueBindingImpl.getValue(ValueBindingImpl.java:402)
| at org.jboss.seam.core.Expressions$1.getValue(Expressions.java:51)
| at org.jboss.seam.Component.getInstanceFromFactory(Component.java:1666)
| at org.jboss.seam.Component.getInstance(Component.java:1615)
| at org.jboss.seam.Component.getInstance(Component.java:1592)
| at org.jboss.seam.Component.getInstanceToInject(Component.java:1842)
| at org.jboss.seam.Component.injectFields(Component.java:1342)
| at org.jboss.seam.Component.inject(Component.java:1112)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995938#3995938
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995938
19 years, 7 months
[JBoss Seam] - Re: Question on using @DataModelSelection & open a page in a
by lle
Thank you for your response.
1. I think I got no other choice then put a link in each column. I'll look at Trinidad tr:table to see if there's any other way.
2. s:link target doesn't work in my case since I need to control the look and feel of the new window. I used page action and it seems to work, but then lead to #3.
3. A click on this link spawns a new window and starts a new conversation. When I use page action or @Create, it works fine except that if I refresh the new page, then another new conversation starts, which is bad, especially my page action depends on a row selection made from the main screen. So if I open two windows and then refresh the first one, then it is reloaded with the data of the second one since the selected row now is different. So, I think the only way to overcome this is to use explicit conversation id. However, it is broken in 1.1GA. I think Gavin fixed it in CVS. I'll download the new version. If you know any better solution then using explicit conversation Id, please let me know.
Again, thanks a lot and happy holidays.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995935#3995935
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995935
19 years, 7 months
[JBoss/Spring Integration] - IllegalArgumentException when trying to deploy an ear
by aegana
Hi,
I'm using Jboss-4.0.4, Spring 2.0 and jboss-spring-jdj5.jar patch. Any help would be appreciated. I receive the following error back
14:48:04,463 ERROR [MainDeployer] Could not create deployment: file:/d1/jboss-4.0.4RC1/server/default/tmp/deploy/tmp10339nsaclient.ear-contents/nsaclient-spring.xml
org.jboss.deployment.DeploymentException: Unexpected exception parsing XML document from URL [file:/d1/jboss-4.0.4RC1/server/default/tmp/deploy/tmp10339nsaclient.ear-contents/nsaclient-spring.xml]; nested exception is java.lang.IllegalArgumentException: Class [org.springframework.beans.factory.xml.SimplePropertyNamespaceHandler] does not implement the NamespaceHandler interface; - nested throwable: (org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from URL [file:/d1/jboss-4.0.4RC1/server/default/tmp/deploy/tmp10339nsaclient.ear-contents/nsaclient-spring.xml]; nested exception is java.lang.IllegalArgumentException: Class [org.springframework.beans.factory.xml.SimplePropertyNamespaceHandler] does not implement the NamespaceHandler interface)
at org.jboss.spring.deployment.SpringDeployer.create(SpringDeployer.java:138)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:953)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:943)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:807)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:260)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:190)
at $Proxy6.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:334)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:522)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:207)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:280)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
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:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:260)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:974)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
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:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:260)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:190)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:755)
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:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:260)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:190)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:477)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:357)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:464)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from URL [file:/d1/jboss-4.0.4RC1/server/default/tmp/deploy/tmp10339nsaclient.ear-contents/nsaclient-spring.xml]; nested exception is java.lang.IllegalArgumentException: Class [org.springframework.beans.factory.xml.SimplePropertyNamespaceHandler] does not implement the NamespaceHandler interface
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:427)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:357)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334)
at org.jboss.spring.factory.NamedXmlApplicationContext.loadBeanDefinitions(NamedXmlApplicationContext.java:87)
at org.jboss.spring.factory.NamedXmlApplicationContext.loadBeanDefinitions(NamedXmlApplicationContext.java:82)
at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:94)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:294)
at org.jboss.spring.factory.NamedXmlApplicationContext.(NamedXmlApplicationContext.java:61)
at org.jboss.spring.factory.NamedXmlApplicationContext.(NamedXmlApplicationContext.java:50)
at org.jboss.spring.factory.ApplicationContextLoaderImpl.createBeanFactory(ApplicationContextLoaderImpl.java:38)
at org.jboss.spring.factory.AbstractBeanFactoryLoader.create(AbstractBeanFactoryLoader.java:94)
at org.jboss.spring.deployment.SpringDeployer.create(SpringDeployer.java:132)
... 70 more
Caused by: java.lang.IllegalArgumentException: Class [org.springframework.beans.factory.xml.SimplePropertyNamespaceHandler] does not implement the NamespaceHandler interface
at org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.initHandlerMappings(DefaultNamespaceHandlerResolver.java:119)
at org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.(DefaultNamespaceHandlerResolver.java:96)
at org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.(DefaultNamespaceHandlerResolver.java:82)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.createDefaultNamespaceHandlerResolver(XmlBeanDefinitionReader.java:530)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.createReaderContext(XmlBeanDefinitionReader.java:519)
at org.jboss.spring.factory.NamedXmlBeanDefinitionReader.registerBeanDefinitions(NamedXmlBeanDefinitionReader.java:54)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:407)
... 81 more
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995934#3995934
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995934
19 years, 7 months
[JBoss Messaging] - Re: Exception by getting a reference to the ConnectionFactor
by vvd
were you able to resolve the error received below, I also getting similar error.
java.lang.RuntimeException: Failed to config client side AOP
at org.jboss.jms.client.JBossConnectionFactory.ensureAOPConfigLoaded(JBossConnectionFactory.java:251)
at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:196)
at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:108)
at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:103)
at com.sterlingcommerce.woodstock.services.jms.JmsQueueAdapterServerImpl.createConnection(JmsQueueAdapterServerImpl.java:66)
at com.sterlingcommerce.woodstock.services.jms.AbstractServerImpl.openSession(AbstractServerImpl.java:212)
at com.sterlingcommerce.woodstock.services.jms.AbstractServerImpl.startupAdapter(AbstractServerImpl.java:181)
at com.sterlingcommerce.woodstock.services.jms.JmsQueueAdapterServerImpl.startupAdapter(JmsQueueAdapterServerImpl.java:55)
at com.sterlingcommerce.woodstock.services.IAdapterImpl.startAdapter(IAdapterImpl.java:168)
at com.sterlingcommerce.woodstock.services.controller.StartAdapterThread.run(StartAdapterThread.java:69)
at java.lang.Thread.run(Thread.java:567)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995928#3995928
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995928
19 years, 7 months
[JBoss Seam] - pageflow step description problem
by spambob
The EL in the pageflow description list isn't working!
I use the latest CVS version and my page is configured like this:
<page name="edit" view-id="/editUsecase.xhtml" redirect="true" no-conversation-view-id="/home.xhtml">
| <description>Edit Usecase: #{usecase.name}</description>
| <transition name="cancel" to="home">
| <action expression="#{usecasesBean.cancel}"/>
| </transition>
| <transition name="save" to="home">
| <action expression="#{usecasesBean.save}"/>
| </transition>
| </page>
The conversation switcher is used like this:
<h:form id="conversationForm">
| <h:selectOneMenu value="#{switcher.conversationIdOrOutcome}">
| <f:selectItems value="#{switcher.selectItems}" />
| </h:selectOneMenu>
| <h:commandButton action="#{switcher.select}" value="Switch" />
| </h:form>
The output (in the conversation switcher) list is:
anonymous wrote : Edit Usecase: #{usecase.name}
Because this worked before: is this a bug or was something changed? If the later: how should one put the page description in jpdl.xml files now?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995925#3995925
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995925
19 years, 7 months
[JBoss Seam] - best practice question: SMPC, @OneToOne and <h:selectOneMenu
by hstang
I am encountering PersistenceException in designing a web form that results from using Seam-managed persistence context(SMPC) + @OneToOne and <h:selectOneMenu>. I am trying to use the entity as a pure JSF backing bean. The problem is modifying the department's ID, which is still managed by SMPC.
Does anyone know a clever design/solution to use @OneToOne + <h:selectOneMenu> ? The examples in Seam1.1GA do not appear to have this use case covered. The relevant codes are posted below. Thanks.
| Caused by: org.jboss.tm.JBossRollbackException: Unable to commit, tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=null:1166713106023/32, BranchQual=null:1166713106023, localId=0:32], status=STATUS_NO_TRANSACTION; - nested throwable: (javax.persistence.PersistenceException: org.hibernate.HibernateException: identifier of an instance of Department was altered from 1 to 2)
|
Employee.java
--
| @Name("employee")
| @Entity
| public class Employee {
|
| @Id
| @GeneratedValue
| private Long id;
|
| @OneToOne
| @JoinColumn(name = "departmentId")
| private Department department;
|
| // getters and setters
| }
Department.java
--
@Name("department")
| @Entity
| public class Department {
|
| @Id
| @GeneratedValue
| private Long id;
|
| private String name;
|
| // getters and setters
| }
UserView.java
--
@Name("userView")
| public class UserView {
| @In
| private EntityManager em;
|
| @Factory("departmentList")
| public List<SelectItem> initDepartmentList() {
| // use em; to return an instance of List<SelectItem>
| }
| }
|
user.xhtml
--
anonymous wrote :
| <h:selectOneMenu id="user.department" value="#{employee.department.id}">
| <f:convertNumber/>
| <f:selectItems value="#{departmentList}"/>
| </h:selectOneMenu>
| <h:commandButton value="Update" action="update"/>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995922#3995922
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995922
19 years, 7 months
[JBoss Seam] - Re: Removing jaxws in ejb3-all jar
by daleth
Sure thing. This is bundled up as a war for deployment in any ol' servlet container. Our customer happens to be using Tomcat.
| META-INF/
| META-INF/MANIFEST.MF
| WEB-INF/
| WEB-INF/classes/
| WEB-INF/lib/
| images/
| layout/
| stylesheet/
| AdvancedSearch.xhtml
| AdvancedSearchResults.xhtml
| BasicSearch.xhtml
| BasicSearchResult.xhtml
| SearchResult.xhtml
| WEB-INF/classes/messages_en.properties
| WEB-INF/components.xml
| WEB-INF/faces-config.xml
| WEB-INF/lib/jrobin-1.4.0.jar
| WEB-INF/lib/mc-conf.jar
| WEB-INF/lib/portal.jar
| WEB-INF/lib/seam-1.1.0.GA-commons-beanutils-1.7.0.jar
| WEB-INF/lib/seam-1.1.0.GA-commons-codec-1.3.jar
| WEB-INF/lib/seam-1.1.0.GA-commons-collections-3.1.jar
| WEB-INF/lib/seam-1.1.0.GA-commons-digester-1.6.jar
| WEB-INF/lib/seam-1.1.0.GA-commons-el-1.0.jar
| WEB-INF/lib/seam-1.1.0.GA-commons-lang-2.1.jar
| WEB-INF/lib/seam-1.1.0.GA-debug.jar
| WEB-INF/lib/seam-1.1.0.GA-el-api.jar
| WEB-INF/lib/seam-1.1.0.GA-el-ri.jar
| WEB-INF/lib/seam-1.1.0.GA-hibernate-all.jar
| WEB-INF/lib/seam-1.1.0.GA-httpclient-3.0.1.jar
| WEB-INF/lib/seam-1.1.0.GA-jboss-aop-jdk50.jar
| WEB-INF/lib/seam-1.1.0.GA-jboss-cache-jdk50.jar
| WEB-INF/lib/seam-1.1.0.GA-jboss-ejb3-all.bak
| WEB-INF/lib/seam-1.1.0.GA-jboss-ejb3.jar
| WEB-INF/lib/seam-1.1.0.GA-jbpm-3.1.2.jar
| WEB-INF/lib/seam-1.1.0.GA-jgroups.jar
| WEB-INF/lib/seam-1.1.0.GA-jsf-facelets.jar
| WEB-INF/lib/seam-1.1.0.GA-jstl-1.1.0.jar
| WEB-INF/lib/seam-1.1.0.GA-myfaces-api-1.1.4.jar
| WEB-INF/lib/seam-1.1.0.GA-myfaces-impl-1.1.4.jar
| WEB-INF/lib/seam-1.1.0.GA-thirdparty-all.jar
| WEB-INF/lib/seam-1.1.0.GA-ui.jar
| WEB-INF/lib/seam-1.1.0.GA.jar
| WEB-INF/lib/tomahawk-1.1.3.jar
| WEB-INF/lib/xfire-1.2.3-activation-1.1.jar
| WEB-INF/lib/xfire-1.2.3-jaxb-api-2.0.jar
| WEB-INF/lib/xfire-1.2.3-jaxb-impl-2.0.1.jar
| WEB-INF/lib/xfire-1.2.3-jaxb-xjc-2.0.1.jar
| WEB-INF/lib/xfire-1.2.3-jaxws-api-2.0.jar
| WEB-INF/lib/xfire-1.2.3-jdom-1.0.jar
| WEB-INF/lib/xfire-1.2.3-jsr181-api-1.0-M1.jar
| WEB-INF/lib/xfire-1.2.3-logging-1.0.4.jar
| WEB-INF/lib/xfire-1.2.3-stax-api-1.0.1.jar
| WEB-INF/lib/xfire-1.2.3-wsdl4j-1.5.2.jar
| WEB-INF/lib/xfire-1.2.3-wstx-asl-3.0.1.jar
| WEB-INF/lib/xfire-all-1.2.3.jar
| WEB-INF/navigation.xml
| WEB-INF/web.xml
| .... web pages ....
|
The xfire-1.2.3-jsr181.api-1.0-M1.jar is the jar that contains the WebService annotation that conflicts with the one in the EJB3 jar. Specifically I get the following error:
| Exception in thread "main" java.lang.NoSuchMethodError: javax.jws.WebService.portName()Ljava/lang/String;
| at org.codehaus.xfire.annotations.jsr181.Jsr181WebAnnotations.getWebServiceAnnotation(Jsr181WebAnnotations.java:55)
| at org.codehaus.xfire.annotations.AnnotationServiceFactory.create(AnnotationServiceFactory.java:173)
| at org.codehaus.xfire.service.binding.ObjectServiceFactory.create(ObjectServiceFactory.java:356)
| at gov.nih.nci.cagrid.portal.indexService.IndexServiceClient.createServiceDescriptor(IndexServiceClient.java:145)
| at gov.nih.nci.cagrid.portal.indexService.IndexServiceClient.<init>(IndexServiceClient.java:83)
| at gov.nih.nci.cagrid.portal.indexService.IndexServiceClientExample.main(IndexServiceClientExample.java:17)
|
This occurs if both jars are on the classpath and the EJB3 jar appears first. Unforuantely the EJB3 jar does not contain all the necessary annotations that XFire require. Here's the contents of the jsr181 jar from XFire:
| META-INF/
| META-INF/MANIFEST.MF
| javax/
| javax/jws/
| javax/jws/soap/
| javax/jws/HandlerChain.class
| javax/jws/Oneway.class
| javax/jws/WebMethod.class
| javax/jws/WebParam$Mode.class
| javax/jws/WebParam.class
| javax/jws/WebResult.class
| javax/jws/WebService.class
| javax/jws/soap/InitParam.class
| javax/jws/soap/SOAPBinding$ParameterStyle.class
| javax/jws/soap/SOAPBinding$Style.class
| javax/jws/soap/SOAPBinding$Use.class
| javax/jws/soap/SOAPBinding.class
| javax/jws/soap/SOAPMessageHandler.class
| javax/jws/soap/SOAPMessageHandlers.class
|
While I completely agree with what you've said, I'm not as worried as I might otherwise be. The EJB3 jar seems to have an incomplete version of these annotations. For example, JEE5 specifies the javax.jws.soap package which the EJB3 jar is missing (and XFire needs).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995910#3995910
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995910
19 years, 7 months
[JBoss Seam] - Re: Removing jaxws in ejb3-all jar
by norman.richards＠jboss.com
In general, you should not count on being able to replace/override core Java EE classes in your application. I don't know anything about XFire, but I do know that code that is intended to be run in a Java EE server should NOT have their own copy of the annotations.
So, don't add the annotation classes to your application. If there is a version compatibility between the annotations you need to either find the correct version of XFire for the Java EE version in JBoss or update jbossws.sar in JBoss to a version that works with XFire.
However, in saying that, I really find it hard to believe that they are using incompatible versions of the annotations. Are you sure the problem wasn't simply that you were providing an equivalent class with your application, causing some classloader confusion?
There are still some classloading tricks that might make this work, but it's better not to go there. Could you show your packaging so we can make sure the problem isn't just a simple packaging problem.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995907#3995907
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995907
19 years, 7 months
[Tomcat, HTTPD, Servlets & JSP] - Problem in init ::: java.lang.StringIndexOutOfBoundsExceptio
by abhinav19
Hi all
I am using struts 1.3.5 with jboss 4.0.5
I get this trace when i try to deploy the war file......
I am unable to figure out the reason....
Regards
an
10:59:52,997 ERROR [Tomcat5] Problem in init
java.lang.StringIndexOutOfBoundsException: String index out of range: 0
at java.lang.String.charAt(Unknown Source)
at org.jboss.util.file.JarUtils.unjar(JarUtils.java:273)
at org.jboss.web.AbstractWebContainer.init(AbstractWebContainer.java:325)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
at org.jboss.deployment.SubDeployerInterceptorSupport.init(SubDeployerInterceptorSupport.java:119)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.init(SubDeployerInterceptorSupport.java:172)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:87)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy39.init(Unknown Source)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:872)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy6.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:490)
at java.lang.Thread.run(Unknown Source)
10:59:53,012 ERROR [MainDeployer] Could not initialise deployment: file:/C:/Program Files/jboss-4.0.5.GA/server/default/deploy/ats.war
org.jboss.deployment.DeploymentException: String index out of range: 0; - nested throwable: (java.lang.StringIndexOutOfBoundsException: String index out of range: 0)
at org.jboss.web.AbstractWebContainer.init(AbstractWebContainer.java:374)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
at org.jboss.deployment.SubDeployerInterceptorSupport.init(SubDeployerInterceptorSupport.java:119)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.init(SubDeployerInterceptorSupport.java:172)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:87)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy39.init(Unknown Source)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:872)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy6.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:490)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: 0
at java.lang.String.charAt(Unknown Source)
at org.jboss.util.file.JarUtils.unjar(JarUtils.java:273)
at org.jboss.web.AbstractWebContainer.init(AbstractWebContainer.java:325)
... 88 more
10:59:53,137 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
10:59:53,559 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995899#3995899
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995899
19 years, 7 months
[Security & JAAS/JBoss] - my login method is accessed twice
by sionut2
Hi,
I have the following configuration in my login-config.xml file:
| <?xml version="1.0" encoding="UTF-8"?>
| <!DOCTYPE policy PUBLIC
| "-//JBoss//DTD JBOSS Security Config 3.0//EN"
| "http://www.jboss.org/j2ee/dtd/security_config.dtd">
| <policy>
| <application-policy name="emp-mft">
| <authentication>
| <login-module
| code="org.jboss.security.ClientLoginModule"
| flag="required">
| </login-module>
|
| <login-module
| code="com.xxx.MyCustomLoginModule1"
| flag="sufficient">
| <module-option name="tryFirstPass">true</module-option>
| <module-option name="replacePass">true</module-option>
| </login-module>
|
| <login-module
| code="com.xxx.MyCustomLoginModule2"
| flag="sufficient">
| </login-module>
|
| </authentication>
| </application-policy>
| </policy>
|
I have 2 problems:
1) My login/commit methods in MyCustomLoginModule1 and MyCustomLoginModule2 are called twice. Is it supposed to work like that ?
>From what I read about login modules, I think I should get a single login/commit or login/abort - depending on the overall result.
2) In my current tests MyCustomLoginModule2 does the main work - it is the one that performs the login. As I was saying, I get 2 calls to the login method: one of them is succesfull, the other is not.
- If I set required for MyCustomLoginModule2, I'm getting a failed overall result because one of the logins fails.(if it would be only one, I woulnd't have this problem).
- If I set sufficient for it, my calls pass through, no matter if the credentials are valid or not (and that's because ClientLoginModule is always successful, so the overall is successful). For some weird reason, the login that fails doesn't have any importance here..
Any help would be greatly appreciated !
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995897#3995897
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995897
19 years, 7 months
[JBoss jBPM] - Locating timers from process instance
by arshadnj
I am wondering how can I locate timers associated with a process instance.
Here is more detailed information about our requirement and wondering how JBPM timers will fit in.
Basically, the application is kind of Order management system. When the order goes into to 'Wait for approval from Customer', we need to create a timer, which sends a reminder to customer. The key point here is, this reminder date is based on the business date, which can be changed from some admin users. In other words, we need our timer to work based on a variable of the system instead of some constant interval which we define in the process definition.
So, my question is, can we have a timer whose triggering is associated with some business date? I think NO, so, my next option is, when this date changes, go and update the timer itself. I can do this only if I can locate timers for a given process instance.
I guess, even option is to have a JOB which looks for this date and sends a reminder!
Thanks,
Arshad
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995895#3995895
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995895
19 years, 7 months
[JBoss Seam] - Re: Removing jaxws in ejb3-all jar
by daleth
Testing shows that removing the WS code from the jar isn't sufficient. As I was worried about it, those classes are at least loaded during the container startup.
| 2006-12-22 10:19:25,953 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/portal]] Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener
| java.lang.RuntimeException: exception invoking: startup
| at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:112)
| at org.jboss.seam.Component.callComponentMethod(Component.java:1791)
| at org.jboss.seam.Component.callCreateMethod(Component.java:1739)
| at org.jboss.seam.Component.newInstance(Component.java:1728)
| at org.jboss.seam.contexts.Lifecycle.startup(Lifecycle.java:152)
| at org.jboss.seam.contexts.Lifecycle.endInitialization(Lifecycle.java:126)
| at org.jboss.seam.init.Initialization.init(Initialization.java:430)
| at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:33)
| at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3763)
| at org.apache.catalina.core.StandardContext.start(StandardContext.java:4211)
| at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
| at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
| at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
| 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:585)
| at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
| at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.apache.catalina.core.StandardContext.init(StandardContext.java:5052)
| 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:585)
| at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
| at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:297)
| at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:103)
| at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:371)
| at org.jboss.web.WebModule.startModule(WebModule.java:83)
| at org.jboss.web.WebModule.startService(WebModule.java:61)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
| at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| at sun.reflect.GeneratedMethodAccessor34.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy11.start(Unknown Source)
| at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466)
| 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:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy12.start(Unknown Source)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| 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:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy6.deploy(Unknown Source)
| at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
| at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
| Caused by: java.lang.reflect.InvocationTargetException
| 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:585)
| at org.jboss.seam.util.Reflections.invoke(Reflections.java:18)
| at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:102)
| ... 93 more
| Caused by: java.lang.NoClassDefFoundError: javax/jws/WebService
| at org.jboss.ejb3.ProxyFactoryHelper.getEndpointInterface(ProxyFactoryHelper.java:70)
| at org.jboss.ejb3.ProxyFactoryHelper.getLocalInterfaces(ProxyFactoryHelper.java:101)
| at org.jboss.ejb3.ProxyDeployer.initializeLocalBindingMetadata(ProxyDeployer.java:117)
| at org.jboss.ejb3.SessionContainer.instantiated(SessionContainer.java:71)
| at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:573)
| at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:555)
| at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:536)
| at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:508)
| at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:463)
| at org.jboss.ejb3.embedded.EJB3StandaloneDeployer.create(EJB3StandaloneDeployer.java:437)
| at org.jboss.seam.core.Ejb.startup(Ejb.java:55)
| ... 99 more
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995893#3995893
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995893
19 years, 7 months
[JBoss.NET] - Re: NoClassDefFoundError: org/jboss/axis/encoding/ser/BaseSe
by eogreen
The error occurs on the below call: _call.registerTypeMapping(cls, qName, sf, df, false);
private org.apache.axis.client.Call createCall() throws java.rmi.RemoteException {
| try {
| org.apache.axis.client.Call _call =
| (org.apache.axis.client.Call) super.service.createCall();
| if (super.maintainSessionSet) {
| _call.setMaintainSession(super.maintainSession);
| }
| if (super.cachedUsername != null) {
| _call.setUsername(super.cachedUsername);
| }
| if (super.cachedPassword != null) {
| _call.setPassword(super.cachedPassword);
| }
| if (super.cachedEndpoint != null) {
| _call.setTargetEndpointAddress(super.cachedEndpoint);
| }
| if (super.cachedTimeout != null) {
| _call.setTimeout(super.cachedTimeout);
| }
| if (super.cachedPortName != null) {
| _call.setPortName(super.cachedPortName);
| }
| java.util.Enumeration keys = super.cachedProperties.keys();
| while (keys.hasMoreElements()) {
| java.lang.String key = (java.lang.String) keys.nextElement();
| _call.setProperty(key, super.cachedProperties.get(key));
| }
| // All the type mapping information is registered
| // when the first call is made.
| // The type mapping information is actually registered in
| // the TypeMappingRegistry of the service, which
| // is the reason why registration is only needed for the first call.
| synchronized (this) {
| if (firstCall()) {
| // must set encoding style before registering serializers
| _call.setSOAPVersion(org.apache.axis.soap.SOAPConstants.SOAP11_CONSTANTS);
| _call.setEncodingStyle(org.apache.axis.Constants.URI_SOAP11_ENC);
| for (int i = 0; i < cachedSerFactories.size(); ++i) {
| java.lang.Class cls = (java.lang.Class) cachedSerClasses.get(i);
| javax.xml.namespace.QName qName =
| (javax.xml.namespace.QName) cachedSerQNames.get(i);
| java.lang.Class sf = (java.lang.Class)
| cachedSerFactories.get(i);
| java.lang.Class df = (java.lang.Class)
| cachedDeserFactories.get(i);
| _call.registerTypeMapping(cls, qName, sf, df, false);
| }
| }
| }
| return _call;
| }
| catch (java.lang.Throwable t) {
| throw new org.apache.axis.AxisFault("Failure trying to get the Call object", t);
| }
| }
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995890#3995890
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995890
19 years, 7 months
[JBoss Seam] - Re: session handling of users
by quilleashm
"ask4saif" wrote :
| how can i restrict users from unauthorized access of pages.
|
Probably use a servlet filter for your web application. The filter intercepts all requests to the URLs it is mapped to. If you place something in the session context when a login is succesful the filter can check for the lack of this in the session and block access.
Seam has a finer control mechanism for doing this via a custom interceptor if you only want to apply security to certain pages. See the docs.
"ask4saif" wrote :
| how can i redirect users to login page if their username does not exist in the session.
|
Use a RequestDispatcher in the filter described above to forward the request to the login page.
"ask4saif" wrote :
| how can i check if the form is submitted illeaglly.
|
Not sure what you mean by "submitted illegally"
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995887#3995887
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995887
19 years, 7 months