[JBoss Tools (users)] - Re: Do the JBoss Tools for SEAM work?
by rob.stryker＠jboss.com
We've recently (today) released jboss tools 2.1.0, which is targeted to wtp 2.0.2.
However... we've had to patch wtp2.0.2 as it did not provide the functionality we required.
Basically, when deciding whether or not to publish a .jar file in the EAR project, wtp tries to open it up and see what type of jar it is. However... if you told it jboss-seam.jar was an ejb, it would crap out while looking for an ejb-jar.xml file.
Now, *I* know, and *you* know, that in jee5, these descriptors are not necessary. However wtp 2.0.2 does not seem to understand this, and instead just shits all over itself and refuses to even recognize the file as a library (for certain purposes).
wtp came out with some patches at their patch site, which *still* didn't fix the problem. Rather than try to wait for them to fix it and roll us another build, we made our own patch zip. It's located at: http://repository.jboss.org/eclipse/webtools/patches/wtp-P-P2008050600312...
However, since we've now just today released jboss tools 2.1.0, I suggest downloading that instead of just the patch ;)
Good luck!
relevent jiras: http://jira.jboss.com/jira/browse/JBIDE-1862
several eclipse bugs linked there as well ;)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4149240#4149240
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4149240
17 years, 11 months
[JBoss Tools (users)] - Re: Do the JBoss Tools for SEAM work?
by wiggy
hokay -
not entirely sure what you have going here - but i see in the error something i have experienced in windows.
Sometimes if you build a new seam project usingt the wizard (do a simple helloo world ear app) and have a look in the eclipse project earContent directory you will find a bunch of jar files that the builder puts there.
bizarely I find that when you deploy the ear (it deploys in exploded format if you use the jboss tools install ontop of eclipse) - it copies the ear structure into the jboss/server/default/deploy directory in exploded format (assumes you have accepted all the standard defaults when defining your jboss server and seam runtime config for the project when you first went thru the wizard.
however what i often find is that the jar files in your top level EarContent directory do Not get deployed to the server. Cant figure out why this does this. one of these jars in the jboss-seam.jar that your trace moans about.
If you then manually copy the jar files in explorer to the same place in the deploy directory - then the deployer detects the paste and it normally then successfuly deploys - at least it does for me.
however i've had another problem - where an app i have built has stopped copying the application.xml in the META-INF directory for the ear - and i have no easy past this - cant figure out why it doesnt deploy - its in the source folder in eclipse project.
as for your note
anonymous wrote :
|
| Caused by: org.apache.commons.logging.LogConfigurationException: User-specified log class 'org.apache.commons.logging.impl.Log4JLogger' cannot be found or is not useable.
|
|
this is usually found in the commons-logging.jar which for me in the the server/defualt/lib directory. This is usually resolved at compile time by ensuring your server runtime libraries are added to the project in the eclipse build. - if you open the runtime library list in the package explorer (Left hand side) in eclipse.
check you have the right runtime library set configured for your eclipse project and check your default/deploy/lib directory has the commons-logging jar there.
i have not had a problem with logging myself
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4149235#4149235
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4149235
17 years, 11 months
[Microcontainer] - Using bean injection tags in a custom XML schema
by david.lloyd＠jboss.com
I'd like to set things up so that the user can do something like this:
| <io:deployment xmlns:io="urn:jboss:io:1.0" xmlns:bean="urn:jboss:bean-deployer:2.0">
| <io:server>
| <io:handler-factory-bean>
| <bean:inject bean="MyHandlerFactory"/>
| </io:handler-factory-bean>
| <io:bind-address>0.0.0.0:12345</io:bind-address>
| <io:bind-address>0.0.0.0:12346</io:bind-address>
| <io:bind-address>0.0.0.0:12347</io:bind-address>
| </io:server>
| <io:connection name="TheConnection">
| <io:handler-bean>
| <bean:inject bean="MyHandler"/>
| </io:handler-bean>
| <io:client>
| <io:connector/>
| <io:connect-address>irc.freenode.net:6667</io:connect-address>
| <io:connect-address>irc.us.freenode.net:6667</io:connect-address>
| <io:connect-address>irc.au.freenode.net:6667</io:connect-address>
| </io:client>
| </io:connection>
| </io:deployment>
|
The "io" tags are my custom schema; the "bean" tags are the regular bean-deployer tags. Is there any way this is possible to do? I've been looking over various docs and code and I'm not seeing any obvious ways to do this.
Specifically I'm trying to make it so that I can let the user use any tag that they'd normally use within a <bean:property> or similar tag, in order to inject beans into those properties.
Am I overthinking this? Maybe I should just accept a bean name instead...
The schema for the "io" tags is:
| <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
| xmlns="urn:jboss:io:1.0"
| targetNamespace="urn:jboss:io:1.0"
| xmlns:bean="urn:jboss:bean-deployer:2.0"
| elementFormDefault="qualified"
| attributeFormDefault="unqualified"
| >
|
| <xs:complexType name="deployment">
| <xs:sequence minOccurs="0" maxOccurs="unbounded">
| <xs:choice minOccurs="0" maxOccurs="unbounded">
| <xs:element name="server" type="server"/>
| <xs:element name="connector" type="connector"/>
| <xs:element name="client" type="client"/>
| <xs:element name="connection" type="connection"/>
| </xs:choice>
| </xs:sequence>
| </xs:complexType>
|
| <xs:complexType name="server">
| <xs:sequence minOccurs="1" maxOccurs="1">
| <xs:element name="handler-factory-bean" type="bean" minOccurs="1" maxOccurs="1"/>
| <xs:sequence minOccurs="1" maxOccurs="unbounded">
| <xs:element name="bind-address" type="xs:string"/>
| </xs:sequence>
| </xs:sequence>
| <xs:attribute name="reuse-address" use="optional" type="xs:boolean"/>
| <xs:attribute name="receive-buffer-size" use="optional" type="xs:int"/>
| <xs:attribute name="backlog" use="optional" type="xs:int"/>
| <xs:attribute name="socket-timeout" use="optional" type="xs:int"/>
| <xs:attribute name="name" type="xs:string"/>
| </xs:complexType>
|
| <xs:complexType name="connector">
| <xs:sequence minOccurs="1" maxOccurs="1">
| <xs:element name="executor-bean" type="bean" minOccurs="0" maxOccurs="1"/>
| </xs:sequence>
| <xs:attribute name="keep-alive" use="optional" type="xs:boolean"/>
| <xs:attribute name="oob-inline" use="optional" type="xs:boolean"/>
| <xs:attribute name="receive-buffer-size" use="optional" type="xs:int"/>
| <xs:attribute name="reuse-address" use="optional" type="xs:boolean"/>
| <xs:attribute name="send-buffer-size" use="optional" type="xs:int"/>
| <xs:attribute name="linger" use="optional" type="xs:boolean"/>
| <xs:attribute name="linger-time" use="optional" type="xs:int"/>
| <xs:attribute name="timeout" use="optional" type="xs:int"/>
| <xs:attribute name="tcp-no-delay" use="optional" type="xs:boolean"/>
| <xs:attribute name="connect-timeout" use="optional" type="xs:int"/>
| <xs:attribute name="name" type="xs:string"/>
| </xs:complexType>
|
| <xs:complexType name="client">
| <xs:sequence minOccurs="1" maxOccurs="1">
| <xs:choice minOccurs="1" maxOccurs="1">
| <xs:element name="connector" minOccurs="1" maxOccurs="1" type="connector"/>
| <xs:element name="connector-bean" minOccurs="1" maxOccurs="1" type="bean"/>
| </xs:choice>
| <xs:sequence minOccurs="1" maxOccurs="unbounded">
| <xs:element name="connect-address" type="xs:string"/>
| </xs:sequence>
| </xs:sequence>
| <xs:attribute name="name" type="xs:string"/>
| </xs:complexType>
|
| <xs:complexType name="connection">
| <xs:sequence minOccurs="1" maxOccurs="1">
| <xs:element name="handler-bean" minOccurs="1" maxOccurs="1" type="bean"/>
| <xs:choice minOccurs="1" maxOccurs="1">
| <xs:element name="client" minOccurs="1" maxOccurs="1" type="client"/>
| <xs:element name="client-bean" minOccurs="1" maxOccurs="1" type="bean"/>
| </xs:choice>
| <xs:element name="scheduled-executor-bean" minOccurs="0" maxOccurs="1" type="bean"/>
| </xs:sequence>
| <xs:attribute name="name" type="xs:string"/>
| </xs:complexType>
|
| <xs:complexType name="bean">
| ???? what goes here ????
| </xs:complexType>
|
| <xs:element name="deployment" type="deployment"/>
| </xs:schema>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4149234#4149234
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4149234
17 years, 11 months
[EJB 3.0] - Re: Could not find new XAResource to use for recovering non-
by tmartindale123
"ejb3workshop" wrote : I was trying out some standard user transactions using EJB3 entities and persistent message queues. During my tests I encountered several application exceptions which were caused by my code, which I was able to resolved.
|
| However since then I am getting continous stream of messages on the console.
|
| Searching the forum revealed that I need to write a recovery module. Seeing that I was merely using EJB3 I am wondering if there is a standard recovery model.
|
| anonymous wrote :
| | [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] Could not find new XAResource to use for recovering non-serializable XAResource < 131075, 30, 28, 1--3f57fdc4:68f:46f90760:8c5d6-3f57fdc4:68
| |
|
| I'd be happy if I could get just rid of those messages as the cause of the problem has been resolved.
|
did you ever resolve this? I have the same problem
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4149228#4149228
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4149228
17 years, 11 months
[JBoss Tools (users)] - help - blasted deployment has stopped working from eclipse
by wiggy
help please
I have a seam EAR project that used to deploy - and has now stopped.
essentially its doing an exploded deploy (at least i cant find any .ear archive in the source tree.
the EarContent/META-INF/application.xml file in the eclipse workspace ear project, and all the code compiles.
when i start jboss in eclipse and tell it to deply the project - eclipse copies the ear project to the deploy directory - however it doesnt copy the application.xml for the jboss deploy directory META-INF directory!
it does copy the jboss-app.xml file though.
the deployer reader then fails with the error.
|
| 21:06:56,649 INFO [EARDeployer] Init J2EE application: file:/C:/jboss/jboss-4.2.2.GA/server/default/deploy/ForstersList-ear.ear/
| 21:06:56,649 ERROR [MainDeployer] Could not initialise deployment: file:/C:/jboss/jboss-4.2.2.GA/server/default/deploy/ForstersList-ear.ear/
| org.jboss.deployment.DeploymentException: No META-INF/application.xml found
| at org.jboss.deployment.EARDeployer.init(EARDeployer.java:146)
| 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.GeneratedMethodAccessor20.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:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy9.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$ScannerThread.loop(AbstractDeploymentScanner.java:274)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
|
|
worse i have another simple app (hello world) and that does deolpy the application.xml file - but i cant see what controls this. My real app just doesnt.
I have had other problems when you deploy and jboss tools doesnt deploy the seam jar files - however if i copy them in by hand - the deployer detects that and then completes the deploy -
cant understand that either.
get a problem un undeploy as well where is essentially reports a similar problem - whilst annoying this doesnt usually stop you redeploying.
whats going on - any ideas please i cant work like this its stopping me get on with the design
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4149227#4149227
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4149227
17 years, 11 months