[JBoss Seam] - Numerics and Decimals in mysql 5
by jdijkmeijer
Hi I'm using seam-gen (seam 1.1GA) and jboss 4.0.5 GA non clustered ejb3 together with mysql.
In de createdb script of mysql I create a colum like amount NUMERIC(10,2), looking at it by desc table shows decimal (10,2). MySQL chooses not to use numerics but decimals instead. What's in a name.
seam generate-entitiies works fine, but the scale is omitted, no problem I can add that by hand. However with the added scale I still get an expected numeric exception on deployment, I checked the dialect (mysql) and I'm a bit lost at this moment. Nor do I see any reference to this problem, which makes me wonder whether I'm doing something very unusual (unlikely numerics are widely used at my work (oracle)), or very stupid...?
any help would be appreciated.
(mysql 5.02, jboss 4.0.5GA seam1.1GA, winxp sp2).
regards,
Jeroen.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996016#3996016
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996016
19 years, 7 months
[Installation, Configuration & Deployment] - Timeout SSL connection
by sponiza
Hi,
I run the JBOSS 3.2 server in a production environment with a HTTPS (SSL) connection. For one of my clients the following happens. He sets up a connection to the JBOSS server for using the web-application. The connection he sets up never closes (unless he switches of his computer). I can see this connection after running netstat on our server. After running a tcpdump I can see that his computer sends every 2 minutes an acknowledgement frame.
I would like to configure the JBOSS server so that after a 1 minute lapse with no sending of any frames connections are closed and returned to the connection pool. Is this possible? How can I do this?
In the jboss-service.xml file I have set the connectionTimeout parameter to 60000 (i.e. 60 seconds). But this does not solve the problem. Is there another parameter or attribute I should set? If so, which parameter and where can I set it? Thanks for any information at all.
Sponiza
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996010#3996010
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996010
19 years, 7 months
[EJB/JBoss] - Embeddable roadmap
by MichaelCouck
Hi,
I have looked around but can't seem to find anything relating to the remote capabilities of the embedded EJB container. This would be paramount for a decision. Could anyone please tell me if and when JBoss will develop the remote communication for the embedded container, and if they will support this in the future? Not only the JMS remotely but the JNDI access and of course the session beans, i.e. remote access.
All works well locally of course. Setup the container with about five lines of code, all is deployed from the classpath scan by the container! Great one, couldn't be easier. But the remote thing is REALLY important. Without which I'll have to use OpenEJB, but fiddling around with configuration files and the like really annoys me. So please tell me that the enbedded container will go remote soon.
Thanks in advance.
Michael
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996000#3996000
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996000
19 years, 7 months
[Clustering/JBoss] - Re: What is processCallbacks status 2?
by Lauri
I'm getting this error too.
Approximately once per 20 minutes.
related line from server.log
2006-12-23 06:41:52,445 WARN [org.apache.jk.common.ChannelSocket] processCallbacks status 2
--------- configuration details -----------------
I'm using jboss behind apache2, mod_jk
block from server.xml of jboss's tomcat:
apache configuration:
a) workers.properties
# Define list of workers that will be used
# for mapping requests
worker.list=jboss,status
# Define Node1
# modify the host as your host IP or DNS name.
worker.jboss.port=8009
worker.jboss.host=localhost
worker.jboss.type=ajp13
worker.jboss.local_worker=1
worker.jboss.cachesize=10
# Status worker for managing load balancer
worker.status.type=status
b) uriworkermap.properties
# Mount the Servlet context to the ajp13 worker
JkMount /* jboss
c) .conf
# Load mod_jk module
# Specify the filename of the mod_jk lib
LoadModule jk_module modules/mod_jk.so
# Where to find workers.properties
JkWorkersFile conf/workers.properties
# Where to put jk logs
JkLogFile logs/mod_jk.log
# Set the jk log level [debug/error/info]
JkLogLevel error
# Select the log format
JkLogStampFormat "[%a %b %d %H:%M:%S %Y]"
# JkOptions indicates to send SSK KEY SIZE
JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories
# JkRequestLogFormat
JkRequestLogFormat "%w %V %T"
JkShmFile logs/jk.shm
JkShmSize 1024
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995998#3995998
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995998
19 years, 7 months
[JBoss Seam] - Validation Error Messages...
by tony.herstell＠gmail.com
Getting a validation message raised in an Action to appear in the GUI next to the right field?
| if (usernameExists) {
| //facesMessages.addFromResourceBundle(FacesMessage.SEVERITY_WARN, "username", "user_create_username_exists");
| facesMessages.addFromResourceBundle("submitAttempt", "user_create_username_exists");
| return null;
| } else {
|
| <div align="right">
| <ice:outputLabel for="username" value="#{messages.label_username}"/>
| </div>
| <s:decorate>
| <ice:inputText id="username" value="#{user.username}"
| required="true" title="#{messages.hint_username}" /> <!-- partialSubmit="true" - Don't use yet as something eats the input focus [Bug with IceFaces team]-->
| </s:decorate>
| <ice:outputText value="#{messages.tag_mandatory}" styleClass="mandatory" />
| <ice:outputText value=""/>
| <div align="left">
| <ice:message errorClass="error" for="username" />
| </div>
| <ice:outputText value=""/>
|
| <ice:panelGrid columns="2" width="100%">
| <div align="right">
| <ice:commandButton action="#{userRegistrationManager.cancel}" value="#{messages.button_cancel}" immediate="true" type="submit" />
| <ice:commandButton id="submitAttempt" type="submit" value="#{messages.button_create}" action="#{userRegistrationManager.processUserDetails}" styleClass="button" /> <!-- disabled="#{!user.readyForSubmission}" -->
| </div>
| </ice:panelGrid>
|
| <ice:panelGrid columns="1">
| <ice:message infoClass="error" for="submitAttempt" />
| </ice:panelGrid>
|
In the above code segment I want to see the error message with the username (as per the commented out line) field as apposed to the button... however how do you make it appear?
The severtity appears to have no effect.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995995#3995995
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995995
19 years, 7 months
[Messaging, JMS & JBossMQ] - Sending Entities in Messages?
by SmokingAPipe
I'm new to JMS so please forgive the basicness of this question:
I have an enterprise application, distributed as an EAR. It uses Seam and EJB3 for most of its work.
However, there is one Servlet on it which takes input and does some processing. At the end of its processing, it grabs an EntityManager and persists a new entity.
After that entity has been persisted, it needs to send that entity over to a message queue, where some other things are going to pick up the entity and do stuff with it. That way, the Servlet can finish off the HTTP request immediately, and the processessing (which can take a few minutes) will happen in the background.
So, here's the question: I can see an easy way to pass the entity ID within a message; I just use a MapMessage and put the integer right into it. Great. Then the MDB can use an entity manager to fetch that entity based on the entity ID. It seems like that would work fine.
But that also seems clunky. What's the best-practices way to send an entity bean from a Servlet to a MDB?
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995986#3995986
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995986
19 years, 7 months
[EJB 3.0] - EJB3 and Derby Problems
by enazareno
Hi,
I don't know if this is the right post for this question or if this issue has already been answered. I've just been working with hibernate persistence using embedded Derby and MySQL. In derby, when a table is created, it does not include indexes and unique constraints. so @Column( unique=true ) does not work and so does @uniqueConstraint. I've tested the same entity using MySQL and it does so perfectly.
Is embedded derby not yet fully supported by hibernate? I've plan to include persistence in client side and any changes I would do to the entity would be automatically recreated in the client without manual intervention, i.e. including indexes. If this has been answered, pls. redirect me to the posts. Thanks.
Regards,
Elmo
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995984#3995984
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995984
19 years, 7 months
[JNDI/Naming/Network] - the speed of jndi lookup is fine in one network, but too slo
by wang.565
Installed JBoss 4.0.4 on two servers with same configuration. Deployed an ejb3 application on both of them. On the client side, the following code is used to do the lookup:
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
env.put(Context.PROVIDER_URL, p.getProperty("URL", "server:1099"));
Context c = new InitialContext(env);
System.out.println("Lookup : " + System.currentTimeMillis());
myservice = (myservice) c.lookup(" myservicebean/remote");
System.out.println(System.currentTimeMillis());
The problem is that on one network, it takes about 500ms, and on the other network, it takes 15s. These two network are similar network (windows servers with a bunch of windows client. The slow one doesn't have internet connection though.). If I run the application on server machine only (JBOSS & Client application on same machine instead of two machines. i.e. install client on the server and change the above url to something like "localhost:1099)). The speed is fine.
The network itself seems not a problem. I used ping to test network speed on both network. It seems the slow one even has a faster roundtrip time.
So can anyone give me some hints on how to debug this kind of problem?
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995972#3995972
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995972
19 years, 7 months
[JBoss jBPM] - Re: New tasks have been assigned to: ..... null, null?
by jainer
| Iterator iterator = taskMgmtSession.findTaskInstances(jbpmContext.getActorId()).iterator();
| LoggingInstance loggingInstance = processInstance.getLoggingInstance();
| List assignmentLogs = loggingInstance.getLogs(TaskAssignLog.class);
|
| log.debug("assignmentlogs: " + assignmentLogs);
|
|
| else if (assignmentLogs.size() > 1) {
| String msg = "Nuevas tareas han sido asignadas a: ";
| Iterator iter = assignmentLogs.iterator();
|
| while (iter.hasNext()) {
| TaskAssignLog taskAssignLog = (TaskAssignLog) iter.next();
| msg += taskAssignLog.getTaskNewActorId();
|
| while (iterator.hasNext()) {
| TaskInstance nextTask = (TaskInstance) iterator.next();
|
| if (nextTask.isSignalling()) {
|
| if (taskAssignLog.getTaskNewActorId().equals(jbpmContext.getActorId())) {
|
| jbpmContext.save(taskInstance);
| initialize(nextTask);
| return "task";
| }
| }
| }
| if (iter.hasNext())
| msg += ", ";
| iterator = taskMgmtSession.findTaskInstances(jbpmContext.getActorId()).iterator();
| }
| msg += ".";
|
| JsfHelper.addMessage(msg);
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995962#3995962
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995962
19 years, 7 months
[JNDI/Naming/Network] - Problems with register/lookUp via JNP
by beckmanm
Hello,
I'm using the jboss-4.0.5.GA (default mode) with suse-linux 10.0 for few weeks without any relevant problems.
(wihout any customization of properties/ Start+Stop-Scripts and so on ...)
(I think there was no relevant adjustment on my jboss since that time)
For a short time I have some serious problems to register/invoke RMI-Objects.
Likewise the remote-invocation of stateless/stateful session beans doesn't work.
(The deployment of SessionBeans and MBeans itself works fine on each time!)
All these things worked properly in former times and hangs now on rebind resp. on lookUp. and use all the URL in the same manner:
jnp://127.0.0.1:1099
and use following code to prepare rebind/lookup:
properties.put(InitialContext.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
properties.put(InitialContext.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");
properties.put(InitialContext.PROVIDER_URL, "jnp://127.0.0.1:1099");
Context ctx = new InitialContext(properties);
In contrast - the JBoss-Admin-Url: http://127.0.0.1:8080/jmx-console/ works fine
The server.log shows no error at start up (if it starts JRMP):
/j2ee/jboss/jboss-4.0.5.GA/server/default/log$ cat server.log | grep -i rmi
2006-12-22 21:48:50,933 DEBUG [org.jboss.system.ServiceController] Creating service jboss.rmi:type=RMIClassLoader
2006-12-22 21:48:50,933 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.rmi:type=RMIClassLoader dependents are: []
2006-12-22 21:48:51,046 DEBUG [org.jboss.naming.NamingService] Creating NamingServer stub, theServer=org.jnp.server.NamingServer@1758500,rmiPort=1098,clientSocketFactory=null,serverSocketFactory=org.jboss.net.sockets.DefaultSocketFactory(a)fbc4815d[bindAddress=/0.0.0.0]
2006-12-22 21:48:51,103 DEBUG [org.jboss.naming.NamingService] JNDI bootstrap JNP=/0.0.0.0:1099, RMI=/0.0.0.0:1098, backlog=50, no client SocketFactory, Server SocketFactory=org.jboss.net.sockets.DefaultSocketFactory(a)fbc4815d[bindAddress=/0.0.0.0]
2006-12-22 21:48:51,191 DEBUG [org.jboss.system.ServiceController] starting service jboss.rmi:type=RMIClassLoader
2006-12-22 21:48:51,191 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.rmi:type=RMIClassLoader dependent components: []
2006-12-22 21:48:51,289 DEBUG [org.jboss.invocation.jrmp.server.JRMPInvoker] RMI Port='4444'
2006-12-22 21:48:52,282 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] added type-mapping: InformixDB
2006-12-22 21:48:59,432 DEBUG [org.jboss.system.ServiceConfigurator] considering XATerminatorName with object name jboss:service=TransactionManager
2006-12-22 21:48:59,442 DEBUG [org.jboss.system.ServiceConfigurator] considering XATerminatorName with object name jboss:service=TransactionManager
2006-12-22 21:49:02,101 DEBUG [org.jboss.web.WebPermissionMapping] Qualified url patterns: {/=PatternInfo[pattern=/,type=3,isOverriden=false,qualifiers=[PatternInfo[pattern=/restricted/*,type=1,isOverriden=false,qualifiers=[]]]], /restricted/*=PatternInfo[pattern=/restricted/*,type=1,isOverriden=false,qualifiers=[]]}
2006-12-22 21:49:03,403 DEBUG [org.jboss.web.WebPermissionMapping] Qualified url patterns: {/=PatternInfo[pattern=/,type=3,isOverriden=false,qualifiers=[]]}
2006-12-22 21:49:04,075 DEBUG [org.jboss.web.WebPermissionMapping] Qualified url patterns: {/=PatternInfo[pattern=/,type=3,isOverriden=false,qualifiers=[]]}
2006-12-22 21:49:04,278 DEBUG [org.jboss.web.WebPermissionMapping] Qualified url patterns: {/=PatternInfo[pattern=/,type=3,isOverriden=false,qualifiers=[PatternInfo[pattern=/restricted/*,type=1,isOverriden=false,qualifiers=[]]]], /restricted/*=PatternInfo[pattern=/restricted/*,type=1,isOverriden=false,qualifiers=[]]}
2006-12-22 21:49:06,005 DEBUG [org.jboss.system.ServiceConfigurator] JndiName set to jmx/invoker/RMIAdaptor in jboss.jmx:type=adaptor,name=Invoker,protocol=jrmp,service=proxyFactory
2006-12-22 21:49:06,018 DEBUG [org.jboss.system.ServiceCreator] About to create bean: jboss.jmx:alias=jmx/rmi/RMIAdaptor with code: org.jboss.naming.NamingAlias
2006-12-22 21:49:06,019 DEBUG [org.jboss.system.ServiceCreator] Created bean: jboss.jmx:alias=jmx/rmi/RMIAdaptor
2006-12-22 21:49:06,020 DEBUG [org.jboss.system.ServiceConfigurator] FromName set to jmx/rmi/RMIAdaptor in jboss.jmx:alias=jmx/rmi/RMIAdaptor
2006-12-22 21:49:06,021 DEBUG [org.jboss.system.ServiceConfigurator] ToName set to jmx/invoker/RMIAdaptor in jboss.jmx:alias=jmx/rmi/RMIAdaptor
2006-12-22 21:49:06,021 DEBUG [org.jboss.system.ServiceController] recording that jboss.jmx:alias=jmx/rmi/RMIAdaptor depends on jboss:service=Naming
2006-12-22 21:49:06,033 DEBUG [org.jboss.system.ServiceController] Creating service jboss.jmx:alias=jmx/rmi/RMIAdaptor
2006-12-22 21:49:06,034 DEBUG [org.jboss.naming.NamingAlias] Creating jboss.jmx:alias=jmx/rmi/RMIAdaptor
2006-12-22 21:49:06,034 DEBUG [org.jboss.naming.NamingAlias] Created jboss.jmx:alias=jmx/rmi/RMIAdaptor
2006-12-22 21:49:06,034 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.jmx:alias=jmx/rmi/RMIAdaptor dependents are: []
2006-12-22 21:49:06,037 DEBUG [org.jboss.system.ServiceController] starting service jboss.jmx:alias=jmx/rmi/RMIAdaptor
2006-12-22 21:49:06,037 DEBUG [org.jboss.naming.NamingAlias] Starting jboss.jmx:alias=jmx/rmi/RMIAdaptor
2006-12-22 21:49:06,038 DEBUG [org.jboss.util.naming.Util] atom: RMIAdaptor
Content: jmx/invoker/RMIAdaptor
2006-12-22 21:49:06,038 DEBUG [org.jboss.util.naming.Util] Bound link jmx/rmi/RMIAdaptor to jmx/invoker/RMIAdaptor
2006-12-22 21:49:06,038 DEBUG [org.jboss.naming.NamingAlias] Started jboss.jmx:alias=jmx/rmi/RMIAdaptor
2006-12-22 21:49:06,039 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.jmx:alias=jmx/rmi/RMIAdaptor dependent components: []
2006-12-22 21:49:06,055 DEBUG [org.jboss.invocation.jrmp.server.JRMPProxyFactory] Bound proxy under jndiName=jmx/invoker/RMIAdaptor
2006-12-22 21:49:06,166 DEBUG [org.jboss.web.WebPermissionMapping] Qualified url patterns: {/=PatternInfo[pattern=/,type=3,isOverriden=false,qualifiers=[]]}
2006-12-22 21:49:11,773 DEBUG [org.jboss.ejb.EjbModule] creating binding for sessions/SLMatheservice:stateless-rmi-invoker
2006-12-22 21:49:11,810 DEBUG [org.jboss.ejb.EjbModule] creating binding for sessions/CallingMatheservice:stateful-rmi-invoker
2006-12-22 21:49:11,922 DEBUG [org.jboss.ejb.StatefulSessionContainer] Mapped multipliziere HASH 455983099to public int j2eeWithJBoss.chap9.CallingMatheserviceBean.multipliziere(int,int) throws java.rmi.RemoteException
2006-12-22 21:49:12,331 DEBUG [org.jboss.ejb.EjbModule] creating binding for sessions/SFMatheservice:stateful-rmi-invoker
2006-12-22 21:49:12,439 DEBUG [org.jboss.web.WebPermissionMapping] Qualified url patterns: {/=PatternInfo[pattern=/,type=3,isOverriden=false,qualifiers=[]]}
I tried to do a raw-connect via telnet (to exclude simple network problems) - it works properly :
marko@linux:/data/marko$ telnet localhost 1099
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
??srjava.rmi.MarshalledObject|????IhashlocBytest[BobjBytesq~xp???ur[B??T?xp'??thttp://localhost:8083/q~q~uq~??sr org.jnp.server.NamingServer_Stubxrjava.rmi.server.RemoteStub????xrjava.rmi.server.RemoteObject???
a3xpw:
UnicastRef2192.168.129.200J?\???h?xConnection closed by foreign host.
I see in server.log that a lot of service are bound on URL:0.0.0.0.
Should I adjust this via jboss.bind.address-Property to 127.0.0.1?
Any idea - to solve my problem ...?
Thx in advance - marko
PS: enlosed my network-setup:
root@linux:/data/marko$ ifconfig
dsl0 Protokoll:Punkt-zu-Punkt Verbindung
inet Adresse:84.140.77.222 P-z-P:217.0.116.104 Maske:255.255.255.255
UP PUNKTZUPUNKT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:2322 errors:0 dropped:0 overruns:0 frame:0
TX packets:2499 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 Sendewarteschlangenlänge:3
RX bytes:1044318 (1019.8 Kb) TX bytes:365229 (356.6 Kb)
eth0 Protokoll:Ethernet Hardware Adresse 00:13:CE:A4:F9:F5
inet6 Adresse: fe80::213:ceff:fea4:f9f5/64 Gültigkeitsbereich:Verbindung
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7600 errors:0 dropped:0 overruns:0 frame:0
TX packets:9074 errors:0 dropped:0 overruns:0 carrier:1
collisions:0 Sendewarteschlangenlänge:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11 Basisadresse:0x8000 Speicher:a8401000-a8401fff
eth1 Protokoll:Ethernet Hardware Adresse 00:15:58:09:26:10
inet6 Adresse: fe80::215:58ff:fe09:2610/64 Gültigkeitsbereich:Verbindung
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4557 errors:0 dropped:0 overruns:0 frame:0
TX packets:5158 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 Sendewarteschlangenlänge:1000
RX bytes:2757356 (2.6 Mb) TX bytes:973226 (950.4 Kb)
Interrupt:11
lo Protokoll:Lokale Schleife
inet Adresse:127.0.0.1 Maske:255.0.0.0
inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1590 errors:0 dropped:0 overruns:0 frame:0
TX packets:1590 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 Sendewarteschlangenlänge:0
RX bytes:244407 (238.6 Kb) TX bytes:244407 (238.6 Kb)
root@linux:/data/marko$ netstat -r
Kernel IP Routentabelle
Ziel Router Genmask Flags MSS Fenster irtt Iface
217.0.116.104 * 255.255.255.255 UH 0 0 0 dsl0
loopback * 255.0.0.0 U 0 0 0 lo
default 217.0.116.104 0.0.0.0 UG 0 0 0 dsl0
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995956#3995956
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995956
19 years, 7 months
[Installation, Configuration & Deployment] - Re: JBoss JAXB class loading problem
by ajay662
DerJohannes, were you able to get it working?If so, can you post your solution here.
I am in a silimiar situation where I need to use JAXB 2.0 with jboss 4.0.5, but in my case I am getting a classCastException
15:59:10,469 ERROR [STDERR] java.lang.ClassCastException: javax.xml.bind.JAXBElement
| 15:59:10,469 ERROR [STDERR] at com.covergence.enms.servlets.TemplateManagerServlet.updateTemplateConfig(TemplateManagerServlet.java:518)
| 15:59:10,469 ERROR [STDERR] at com.covergence.enms.servlets.TemplateManagerServlet.doPost(TemplateManagerServlet.java:183)
| 15:59:10,469 ERROR [STDERR] at com.covergence.enms.servlets.TemplateManagerServlet.doGet(TemplateManagerServlet.java:146)
| 15:59:10,469 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
| 15:59:10,469 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
| 15:59:10,484 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| 15:59:10,500 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| 15:59:10,500 ERROR [STDERR] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| 15:59:10,500 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| 15:59:10,500 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| 15:59:10,500 ERROR [STDERR] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
| 15:59:10,500 ERROR [STDERR] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
| 15:59:10,500 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
| 15:59:10,500 ERROR [STDERR] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
| 15:59:10,500 ERROR [STDERR] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| 15:59:10,500 ERROR [STDERR] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| 15:59:10,500 ERROR [STDERR] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| 15:59:10,500 ERROR [STDERR] at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| 15:59:10,500 ERROR [STDERR] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| 15:59:10,500 ERROR [STDERR] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| 15:59:10,500 ERROR [STDERR] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
| 15:59:10,500 ERROR [STDERR] at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
| 15:59:10,500 ERROR [STDERR] at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| 15:59:10,500 ERROR [STDERR] at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| 15:59:10,500 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
This is what I have done so far
Included following JAXB jars with my EAR
jaxb-api.jar
| jaxb-impl.jar
|
|
| Added following to jboss-app.xml
| <loader-repository> javax.xml.bind:loader=ENMSApp.ear
| | <loader-repository-config> java2ParentDelegation=false
| | </loader-repository-config>
| | </loader-repository>
|
|
| Changed META-INF/MANIFEST.MF for my EJB JAR and WAR to include classpath. MANIFEST.MF now looks like the following for both:
|
| Manifest-Version: 1.0
| | Ant-Version: Apache Ant 1.6.2
| | Created-By: 1.5.0_08-b03 (Sun Microsystems Inc.)
| | Class-Path: jaxb-api.jar jaxb-impl.jar
|
|
| What am I missing? Why am I still getting classCastException?
|
| I am sure many people have already solved this problem. Would really appreciate if somebody could post their solution here. Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995955#3995955
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995955
19 years, 7 months
[JBoss Seam] - Trinidad + Tomahawk + Seam + A4J
by antispart
I'm getting these warnings in my server log:
15:44:14,858 ERROR [STDERR] Dec 22, 2006 3:44:14 PM org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl verifyFilterIsInstalled
| WARNING: The TrinidadFilter has not been installed. Apache Trinidad requires this filter for proper execution.
This is also resulting in weird behavior with some tomahawk components where before integrating Trinidad things worked fine.
I'm wondering whether anyone has successfully used Trinidad + Tomahawk + Seam + A4J in one project.
Maybe there are some clues in my config files?
faces-config.xml
<?xml version="1.0" encoding="UTF-8"?>
| <faces-config version="1.2" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd">
| <application>
| <el-resolver>org.jboss.seam.jsf.SeamELResolver</el-resolver>
| <locale-config>
| <default-locale>en</default-locale>
| <supported-locale>en</supported-locale>
| </locale-config>
| <message-bundle>messages</message-bundle>
|
| <!-- Use the Trinidad RenderKit -->
| <default-render-kit-id>org.apache.myfaces.trinidad.core</default-render-kit-id>
| </application>
|
| <lifecycle>
| <phase-listener>org.jboss.seam.jsf.SeamExtendedManagedPersistencePhaseListener</phase-listener>
| </lifecycle>
| ...
| </faces-config>
|
web.xml
<?xml version="1.0" encoding="UTF-8"?>
| <web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
|
| <context-param>
| <param-name>org.apache.myfaces.trinidad.ALTERNATE_VIEW_HANDLER</param-name>
| <param-value>org.jboss.seam.ui.facelet.SeamFaceletViewHandler</param-value>
| </context-param>
| <context-param>
| <param-name>org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION</param-name>
| <param-value>true</param-value>
| </context-param>
| <context-param>
| <param-name>org.apache.myfaces.trinidad.resource.DEBUG</param-name>
| <param-value>true</param-value>
| </context-param>
| <context-param>
| <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
| <param-value>.xhtml</param-value>
| </context-param>
| <context-param>
| <param-name>com.sun.faces.verifyObjects</param-name>
| <param-value>false</param-value>
| </context-param>
| <context-param>
| <param-name>com.sun.faces.validateXml</param-name>
| <param-value>true</param-value>
| </context-param>
| <context-param>
| <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
| <param-value>client</param-value>
| </context-param>
| <context-param>
| <param-name>org.jboss.seam.core.init.jndiPattern</param-name>
| <param-value>#{ejbName}/local</param-value>
| </context-param>
| <context-param>
| <param-name>facelets.DEVELOPMENT</param-name>
| <param-value>true</param-value>
| </context-param>
| <context-param>
| <param-name>facelets.LIBRARIES</param-name>
| <param-value>
| /WEB-INF/sandbox.taglib.xml;
| /WEB-INF/tomahawk.taglib.xml;
| </param-value>
| </context-param>
|
| <servlet>
| <servlet-name>Faces Servlet</servlet-name>
| <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
| <load-on-startup>1</load-on-startup>
| </servlet>
| <servlet>
| <servlet-name>Seam Remoting</servlet-name>
| <servlet-class>org.jboss.seam.remoting.SeamRemotingServlet</servlet-class>
| </servlet>
|
| <servlet-mapping>
| <servlet-name>Faces Servlet</servlet-name>
| <url-pattern>*.xhtml</url-pattern>
| </servlet-mapping>
| <servlet-mapping>
| <servlet-name>Seam Remoting</servlet-name>
| <url-pattern>/seam/remoting/*</url-pattern>
| </servlet-mapping>
|
| <!-- Ajax4jsf (must come first!) -->
| <filter>
| <display-name>Ajax4jsf Filter</display-name>
| <filter-name>ajax4jsf</filter-name>
| <filter-class>org.ajax4jsf.Filter</filter-class>
| </filter>
| <!-- MYFACES TOMAHAWK -->
| <filter>
| <filter-name>MyFacesExtensionsFilter</filter-name>
| <filter-class>org.apache.myfaces.webapp.filter.ExtensionsFilter</filter-class>
| <init-param>
| <description>Set the size limit for uploaded files.
| Format: 10 - 10 bytes
| 10k - 10 KB
| 10m - 10 MB
| 1g - 1 GB
| </description>
| <param-name>maxFileSize</param-name>
| <param-value>20m</param-value>
| </init-param>
| </filter>
| <!-- Trinidad -->
| <filter>
| <filter-name>trinidad</filter-name>
| <filter-class>org.apache.myfaces.trinidad.webapp.TrinidadFilter</filter-class>
| </filter>
| <!-- SEAM -->
| <filter>
| <filter-name>Seam Redirect Filter</filter-name>
| <filter-class>org.jboss.seam.servlet.SeamRedirectFilter</filter-class>
| </filter>
| <filter>
| <filter-name>Seam Exception Filter</filter-name>
| <filter-class>org.jboss.seam.servlet.SeamExceptionFilter</filter-class>
| </filter>
|
| <filter-mapping>
| <filter-name>trinidad</filter-name>
| <servlet-name>Faces Servlet</servlet-name>
| <dispatcher>REQUEST</dispatcher>
| <dispatcher>FORWARD</dispatcher>
| <dispatcher>INCLUDE</dispatcher>
| </filter-mapping>
| <filter-mapping>
| <filter-name>ajax4jsf</filter-name>
| <servlet-name>Faces Servlet</servlet-name>
| <dispatcher>REQUEST</dispatcher>
| <dispatcher>FORWARD</dispatcher>
| <dispatcher>INCLUDE</dispatcher>
| </filter-mapping>
| <filter-mapping>
| <filter-name>MyFacesExtensionsFilter</filter-name>
| <servlet-name>Faces Servlet</servlet-name>
| </filter-mapping>
| <filter-mapping>
| <filter-name>MyFacesExtensionsFilter</filter-name>
| <url-pattern>/faces/myFacesExtensionResource/*</url-pattern>
| </filter-mapping>
| <filter-mapping>
| <filter-name>Seam Redirect Filter</filter-name>
| <url-pattern>*.xhtml</url-pattern>
| </filter-mapping>
| <filter-mapping>
| <filter-name>Seam Exception Filter</filter-name>
| <url-pattern>*.xhtml</url-pattern>
| </filter-mapping>
|
|
| <!-- trinidad resources servlet -->
| <servlet>
| <servlet-name>resources</servlet-name>
| <servlet-class>org.apache.myfaces.trinidad.webapp.ResourceServlet</servlet-class>
| </servlet>
|
| <listener>
| <listener-class>org.jboss.seam.servlet.SeamListener</listener-class>
| </listener>
| <listener>
| <listener-class>com.sun.faces.config.ConfigureListener</listener-class>
| </listener>
| <listener>
| <listener-class>org.apache.commons.chain.web.ChainListener</listener-class>
| </listener>
|
| <session-config>
| <session-timeout>30</session-timeout>
| </session-config>
|
| <welcome-file-list>
| <welcome-file>index.xhtml</welcome-file>
| </welcome-file-list>
|
| </web-app>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995950#3995950
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995950
19 years, 7 months