[Beginners Corner] - Looking at JBoss Developer Studio
by StormTAG
So, I'm in that nebulous middle ground of developer experience. I've put a few systems into production but I'm no guru. I've done enough work to appreciate the things that tools like Seam, Hibernate and the JBoss AS offer.
I've worked with the JBoss AS before. I've read a lot about Seam and played around with some of the tutorials. I desperately need an ORM solution beyond my home-rolled version at work (not that I'll ever get time to do it there!) Since JBoss Tools looks to be a full stack in one go it seems like a great starting point.
However, I know from experience that setting up a development environment is, well, a bitch. So I saw JBDS and figured that'd be a great point to start. Though, considering this would be out of my own pocket I'm not in a huge hurry to shell out $99.
So, my question to you guys is this: Given there's a brand new release of JBoss Tools and my relative inexperience would I be spending more than, say, 8 hours or so more trying to set up JBoss Tools on Eclipse than I would just buying a subscription to JBDS? Does JBDS have any other advantages over home rolling my own environment (besides picking and choosing my parts. I'm actually interested in almost all of the pieces of JBDS)? Is this even the right place for a post like this?!
I'm looking forward to getting started and I'd appreciate any help I can get!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223162#4223162
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223162
15 years, 9 months
[JBoss Tools (users)] - Seam Components Problem
by Kragoth
Hi all,
I'm having a rather large issue at the moment with JBoss Tools.
Basically what's happening is that it is not finding all my SEAM components. It only finds about 9 of my SEAM components and then stops.
I have well over 100 SEAM components and they just arn't showing up.
This means my auto complete in xhtml files is no longer working and SEAM validation is not working cause it doesn't find my other SEAM beans.
I tried completely rebuilding my workspace. I rechecked out my codebase... I've wasted a lot of time trying to get this working again. (Yes it was working)
Someone checked in a .project file with the SEAM builder disabled. Ever since then I've had this problem. Reverting to my old .project file did not fix this. I was able to trick it into finding my SEAM beans by renaming my root package (but this is not a solution I can use). After renaming the package it seemed to do a full scan and pick up my SEAM beans. HOWEVER, it still doesn't find the SEAM beans inside the SEAM libs.
I am using:
Eclipse 3.4.1
JBoss Tools 3.0.0.CR1-R200812191611
Here is my .project file
| <?xml version="1.0" encoding="UTF-8"?>
| <projectDescription>
| <name>gekko</name>
| <comment></comment>
| <projects>
| </projects>
| <buildSpec>
| <buildCommand>
| <name>org.eclipse.jdt.core.javabuilder</name>
| <arguments>
| </arguments>
| </buildCommand>
| <buildCommand>
| <name>org.eclipse.ui.externaltools.ExternalToolBuilder</name>
| <triggers>auto,full,incremental,</triggers>
| <arguments>
| <dictionary>
| <key>LaunchConfigHandle</key>
| <value><project>/.externalToolBuilders/CopyConfig.launch</value>
| </dictionary>
| </arguments>
| </buildCommand>
| <buildCommand>
| <name>org.jboss.tools.seam.core.seambuilder</name>
| <arguments>
| </arguments>
| </buildCommand>
| </buildSpec>
| <natures>
| <nature>org.eclipse.jdt.core.javanature</nature>
| <nature>com.atlassw.tools.eclipse.checkstyle.CheckstyleNature</nature>
| <nature>org.jboss.tools.seam.core.seamnature</nature>
| </natures>
| <linkedResources>
| <link>
| <name>gekko-build-exploded</name>
| <type>2</type>
| <locationURI>GEKKO_BUILD/exploded</locationURI>
| </link>
| <link>
| <name>gekko-build-services-classes-prod</name>
| <type>2</type>
| <locationURI>GEKKO_BUILD/gekko-services/classes/prod</locationURI>
| </link>
| <link>
| <name>gekko-build-services-classes-test</name>
| <type>2</type>
| <locationURI>GEKKO_BUILD/gekko-services/classes/test</locationURI>
| </link>
| <link>
| <name>gekko-build-web-classes-prod</name>
| <type>2</type>
| <locationURI>GEKKO_BUILD/gekko-web/classes/prod</locationURI>
| </link>
| <link>
| <name>gekko-build-web-classes-test</name>
| <type>2</type>
| <locationURI>GEKKO_BUILD/gekko-web/classes/test</locationURI>
| </link>
| </linkedResources>
| </projectDescription>
|
I also tried going back to an older version of Eclipse and JBoss tools and that worked.
Can someone tell me what I need to do to fix this? Otherwise I'm just probly gona switch to using InteliJ.
Thanks for any help.
Tim
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223160#4223160
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223160
15 years, 9 months
[Installation, Configuration & DEPLOYMENT] - Re: Large web service request, connection prematurely closed
by tinny4u
Well it would appear that after the appropriate number of restarts it works! Not sure what I did wrong, I must not have saved the server.xml file or something... Also this server is a vmware image so maybe it is something to do with the load on the host OS?
Anyway I will continue to monitor the situation.
Thanks for your help PeterJ!!!
For the record here are the settings that are working for me
| <Connector port="8080" address="${jboss.bind.address}"
| maxThreads="250" maxHttpHeaderSize="16384"
| emptySessionPath="true" protocol="HTTP/1.1"
| enableLookups="false" redirectPort="8443" acceptCount="100"
| maxPostSize="10240"
| bufferSize="10240"
| socketBuffer="10240"
| connectionTimeout="240000" disableUploadTimeout="true" />
|
| <!-- Define a SSL HTTP/1.1 Connector on port 8443
| This connector uses the JSSE configuration, when using APR, the
| connector should be using the OpenSSL style configuration
| described in the APR documentation -->
|
| <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true"
| maxThreads="150" scheme="https" secure="true"
| clientAuth="false" sslProtocol="TLS"
| connectionTimeout="240000"
| maxPostSize="10240"
| bufferSize="10240"
| socketBuffer="10240"
| maxSavePostSize="10240"
| maxHttpHeaderSize="16384"
| disableUploadTimeout="true"
| keystoreFile="${jboss.server.home.dir}/conf/.keystore"
| keystorePass="fact0ring" />
|
|
| <!-- Define an AJP 1.3 Connector on port 8009 -->
| <Connector port="8009" address="${jboss.bind.address}" protocol="AJP/1.3"
| emptySessionPath="true" enableLookups="false" redirectPort="8443" />
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223155#4223155
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223155
15 years, 9 months
[JBoss Messaging] - Re: Messaging blocked by long time-out again
by lanceliao1
We are using Jboss4.2.4 with JBM 1.4.2.GA-SP1 and jboss-remoting-2.2.2.SP11.jar.
| <invoker transport="bisocket">
| <attribute name="marshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
| <attribute name="unmarshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
| <attribute name="dataType" isParam="true">jms</attribute>
| <attribute name="socket.check_connection" isParam="true">false</attribute>
| <attribute name="timeout" isParam="true">0</attribute>
| <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
| <attribute name="serverBindPort">4557</attribute>
| <attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute>
| <attribute name="serverSocketClass">org.jboss.jms.server.remoting.ServerSocketWrapper</attribute>
| <attribute name="numberOfCallRetries" isParam="true">1</attribute>
| <attribute name="pingFrequency" isParam="true">214748364</attribute>
| <attribute name="pingWindowFactor" isParam="true">10</attribute>
| <attribute name="onewayThreadPool">org.jboss.jms.server.remoting.DirectThreadPool</attribute>
|
| <attribute name="clientLeasePeriod" isParam="true">10000</attribute>
| <attribute name="numberOfRetries" isParam="true">10</attribute>
| <attribute name="JBM_clientMaxPoolSize" isParam="true">200</attribute>
| <!-- The maximum time to wait before timing out on trying to write a message to socket for delivery -->
| <attribute name="callbackTimeout">10000</attribute>
| </invoker>
|
The remoting guys resolve the problem by setting TCP TTL.This is a ugly way.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223154#4223154
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223154
15 years, 9 months