I took the seam jars from version 1.2.1 and put them in the lib directory of my
project and built the project but I still get the same error. What am I doing
wrong?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4069445#4069445
Reply to the post :
Simple question here: A user has to enter a series of serial numbers on a form.
We don't know in advance how many serial numbers the user will enter. It
could be five or fifty.
What would be cool is if a new text field would get added when the last empty
one is filled in.
I'm sure there's
Um, off hand I think you would have to use some DHTML to do this and not
necessarily use AJAX. I never tried doing that before with JSF components so I
don't know how that would work since the the DHTML is primarily all client side
and JSF requires the backing beans and in Seam's case EJB.
Thank you very much, PeterJ! I hava downloaded the documents about jboss4.0.2.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4069448#4069448
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4069448
Actually I mean DHTML, not AJAX.
Anyway, in this case, it might be better for me to have a scrollable panel that
opens up, and provide a couple hundred number fields, and be done with it.
Easy to implement, and if we need something more advanced later, I'll change it.
View the original post
Just confirmed this works for GWT 1.3.3, but not 1.4.10. I will open a JIRA
issue for this.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4069451#4069451
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4069451
I've got rid of some exceptions by improving beginCall()
| if (!Contexts.isConversationContextActive()) {
| Lifecycle.beginCall();
| }
| if (!Contexts.isPageContextActive()) {
| FacesLifecycle.resumePage();
|
JIRA issue created: http://jira.jboss.org/jira/browse/JBSEAM-1748
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4069452#4069452
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4069452
Your code looks fine to me, and is about as simple as the HelloWorld example,
which definitely works. I'm guessing there's some other issue which I can't
determine from the code you pasted, so I really need to have a deployable test
case that reproduces the issue. You can send it directly to
Are you setting Seam.Remoting.resourcePath? View the end of the source for the
interface.js that is generated within your Seam app to see how this is set.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4069457#4069457
Reply to the post :
Can you confirm whether the conversation ID actually exists in the SOAP
response? (in the actual XML)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4069458#4069458
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4069458
Will do, I'll send you my project and ear tomorrow when I'm back in the office.
It is being deployed in GlassFish V2 build 56
Thanks!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4069459#4069459
Reply to the post :
Thanks for all your help. I have used Karl's method and it is now working as I
would have liked.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4069460#4069460
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4069460
You currently can't specify a restriction on the * view like that (in fact
you should be using the login-required attribute anyway). There's an
outstanding JIRA issue to that effect:
http://jira.jboss.org/jira/browse/JBSEAM-1009
What happens when you move your restriction to a more specific
I've been using soapUI (http://www.soapui.org/) for some testing, though in my
limited experience I don't think it supports cookies. The web services test
page in the seambay example actually sends a web service request from the
browser, so it automatically gets cookie support (and therefore
samdoyle wrote : It is being deployed in GlassFish V2 build 56
Ah I missed this bit before. It is possible that this has something to do with
remoting not working, however go ahead and send me your test case and I can at
least try it with JBossAS. If it works there, then I may be able to get
Actually, SoapUI does support cookies. When you create a multi-step test case,
you can right click on the test case, select Options and then Maintain HTTP
Session. It can also be configured to support the Seam conversationId in SOAP
header. See:
Does Seam work with these top 4 AJAX frameworks (see the article)?
http://www.infoworld.com/article/06/11/27/48FEajax_1.html
Here are the links to their web sites
Backbase http://www.backbase.com/
JackBe http://www.jackbe.com/
Bindows http://www.bindows.net/
Tibco GI
What is the best way to generate XML documents (instead of html)
from Seam beans?
Thanks
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4069471#4069471
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4069471
I am working with jboss 4.0.1 and EJB and all my ejb modules work
but when I changed to jboss 4.0.5 I got the following error
the plataform where I installed jboss is windows 98
type Exception report
message
description The server encountered an
Port 1099 is used to locate the MBeanServerConnection, which needs to be
available to shut down the server using the shutdown script. Sending a kill
signal (in UNIX) or hitting ctrl-c also initiates clean shutdown.
Crashing or rebooting ... It could be OS, JVM as well as hardware related.
If the XML is to be a representation of the View then supply a different
renderer that produces XML from each UI component in the server side component
tree (JSF) and this will get called when JSF reaches the Render phase... or if
you just want to create XML then look at something like JDom
[EMAIL PROTECTED] wrote : samdoyle wrote : It is being deployed in
GlassFish V2 build 56
|
| Ah I missed this bit before. It is possible that this has something to do
with remoting not working, however go ahead and send me your test case and I
can at least try it with JBossAS. If it
I used SoapUI to issue the following request:
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:com=http://com.twocoast.tcsc.web.service;
|soapenv:Header/
|soapenv:Body
| com:isConfigurationChangePending
| serverNameQUATTRO/serverName
Open up the .war file, fix the web.xml file, redeploy.
Follow up with a patch and log it in JIRA.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4069485#4069485
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4069485
It looks like the interceptor isn't being hit, and I'm guessing it's a
packaging issue. Is your standard-jaxws-endpoint-config.xml inside the JAR
file containing your web services inside an EAR? Look at the packaging for the
seambay example to see how it should be.
View the original post :
Possibly, however I know that remoting doesn't work in standalone Tomcat
(there's a JIRA issue for it).
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4069488#4069488
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4069488
301 - 327 of 327 matches
Mail list logo
