November 2006 - jboss-user - Jboss List Archives

[JBoss Seam] - Re: Using seam-gen with JBoss IDE (Eclipse), where are all t

by rlhr

So I reinstalled the all-in-one bundled and set up the project again. I think I must have done something wrong configuring the project earlier, but I don't know why :) Now everything work great. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988684#3988684 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988684

19 years, 5 months

1
0
0 / 0

[EJB/JBoss] - SOLVED!!!: CommunicationException, local class incompatible:

by pavlikus

Hi all, If you get this exception in Intellij IDEA, then make sure there is no javaee.jar library on project class path. IDEA automatically adds this library to j2ee project/module and it's sure thing incompatible with jboss client libraries. Just in hope you wouldn't spend whole weekend battling with classloading and jar versions ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988683#3988683 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988683

19 years, 5 months

1
0
0 / 0

[JBoss Portal] - Re: Understanding architecture...

by ric1607

Thomas, Thank you for your answer, especially on a week-end! I hope I did not disturb your Saturday with my silly questions {:-) One solution I was thinking of was indeed to include the whole portal page in an iframe. My use case being for instance to include a forum frame or a CMS frame within our existing app. It sure looks odd (I confess), but it is according to my point of view a realistic use case: we have a complex existing webapp, with carefully crafted layout designed to use the top window with plenty of javascript everywhere -- and we cannot simply say "ok, let's put all that in a rectangle on the screen and add something beside". So the solution would be to rewrite all the main layouts under portal templates and this is a too steep slope. I'll try using the portal in an iframe and let you know about. Thank you very much Thomas! --Eric View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988681#3988681 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988681

19 years, 5 months

1
0
0 / 0

[Installation, Configuration & Deployment] - Re: Shutting down JBOSS

by weston.price＠jboss.com

Are you running in a cluster? Your original post did not mention this. The JNDI port is simply the port that your naming service is running on. Typically this is 1099 for each host. However, since you are running multiple instances on one machine it would be whatever JNDI naming port you configured for a particular instance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988680#3988680 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988680

19 years, 5 months

1
0
0 / 0

[Installation, Configuration & Deployment] - Re: Shutting down JBOSS

by kipper3d

Are you referring to this port number: 1400? Heres snippet for jb-user3 in the service-binding.xml file: <service-config name="jboss:service=HAJNDI" delegateClass="org.jboss.services.binding.AttributeMappingDelegate"> <delegate-config portName="Port" hostName="BindAddress"> 1401 </delegate-config> </service-config> Says it couldnt connect - so I have opened 1400 from the firewall - but still did not work. I'm gonna have to revisit this issue later - I appreciate your help! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988679#3988679 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988679

19 years, 5 months

1
0
0 / 0

[Installation, Configuration & Deployment] - Re: Shutting down JBOSS

by weston.price＠jboss.com

Hi, no problem. Try this ./shutdown.sh -s jnp://hostname:<jndi-naming-port> I can't remember if we removed the need for the 'jnp://' prefix or not. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988678#3988678 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988678

19 years, 5 months

1
0
0 / 0

[Installation, Configuration & Deployment] - Re: Shutting down JBOSS

by kipper3d

Uhm, its still running. Heres what i tried. Consider the following port information jb-user1 is 8180 jb-user2 is 8280 jb-user3 is 8380 jb-user4 is 8480 To shudown jb-user3: su - user3 for jb-user3 $JBOSS_HOME/bin/shutdown.sh -s localhost:8380 Error: Failed to retrieve stub from server localhost:8380 I'm assuming the port needs to be the http port. JNDI port doesnt work either - can't connect. I apologize if this is a relatively dumb question but I am new with this. Thanks! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988677#3988677 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988677

19 years, 5 months

1
0
0 / 0

[JBossWS] - Re: Using Axis SAAJ Implementation instead of JBossWS

by reinerka

Hi Thomas, it probably isn't the SAAJ implementation alone but as well the XML parsing components that cause more problem than they solve. Right now we've isolated those key items: 1. Chunked transfers 2. Encapsulation namespaces with single quotes Neither of them are against XML/HTTP rules, but they casue a large number of users of our services to fail due to interoperability issues (a key importance to us). 1. Chunked transfers We were able to remove this by adding a couple of additional classes to handle IO (which just shouldn't be needed). 2. Namesapces Using those specialiced classes we were able to resolve this issue as well. Overall a lot of our subscribers are running embedded systems that rely on minimal overhead for parsing XML and thus will sometimes choose a parser that is not 100% compliant but allows them to save memory footprint. Our objective is to make sure they work. SAAJ (and the required XML parser) were far more tolerant on receiving as well as providing a wider interoperability than what we now have. Regards, Reiner View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988676#3988676 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988676

19 years, 5 months

1
0
0 / 0

[JBoss Seam] - Re: Injection and disinjection control

by gavin.king＠jboss.com

There is a way, namely that you can use "configuration" instead of bijection. ie. <component name="b"> | <property name="var">#{a}</property> | </component> However, it sounds to me like you are trying to preoptimize. A few hundred calls of a setter method is totally insignificant compared to the other costs involved (database access, rendering the view, etc). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988675#3988675 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988675

19 years, 5 months

1
0
0 / 0

[JBoss Seam] - Re: Seam exception handling failing

by gavin.king＠jboss.com

It happens when the variable is first referenced. In this case, during the render phase. Note that if this is a GET request, or a redirect, there is no invoke application phase. Use a page action. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988674#3988674 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988674

19 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user November 2006