Why are you writing code in the 'sun' package? I have a vague recollection that the
root classloader in Sun's VMs prevents you from loading classes into the 'sun'
package. If this is true it's likely to only be the beginning of your issue...
View the original post :
Just because other app servers allow something doesn't make it right!
When you say left up to the interpretation of the implementation, I assume you
haven't read section 18.1.1 of the EJB (2.0) spec?
View the original post :
Interesting. This does appear to be a bug in your parser. Have you tried the
parse(InputStream) method?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3844368#3844368
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3844368
The only valid transaction modes for MDBs are NotSupported and Required. Perhaps by
using an invalid mode, JBoss has defaulted to Required?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3844370#3844370
Reply to the post :
How is a bean using a class that uses threads different from the bean using threads
directly? You could bypass any of the spec requirements by simply saying, I didn't
violate the spec in the bean - only in one of the helper classes.
So, no.
View the original post :
Hmm... see when I talked about JNI method name mangling, and package names
(repeatedly?) And you also told me that your code wasn't in a package!
Oh well. Glad you got it sorted.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3841168#3841168
Reply to the post
Does the primary key class of the Warehouse bean override equals() in accordance with
section 9.2.9 of the EJB spec?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3840791#3840791
Reply to the post :
You haven't said what's wrong, but I suspect you're getting Naming exceptions saying
something like 'ejb not bound'. The global JNDI name of your bean will be something
like /ejb/rwTenantSearch. Beans are not bound under the java: namespace.
View the original post :
What is causing this is stated quite clearly in the first 3 lines of the stacktrace.
The call to setMessageListener() is not allowed.
If you want to receive messages asynchronously, you should write a message driven bean
(MDB).
View the original post :
Errr... what happens if the Servlet container throws away your servlet instance whilst
it's still registered to receive the messages? What happens once the specific servlet
call has returned? Does the servlet continue to receive JMS messages?
Seems a bit dicey to me...
View the original post :
Dunno. Probably something buried in a spec somewhere.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3840652#3840652
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3840652
A good solution to this would be to use SOAP/Web Services. Although, depending on
message volumes, the overhead might be too big.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3840447#3840447
Reply to the post :
For sending files I've successfully used Jakarta Commons-Net. However, I think this
starts a background thread. If so, it's not strictly spec compliant.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3840450#3840450
Reply to the post :
If you bothered to read the Javadoc for javax.naming.Context.bind(), you'd see it says
All intermediate contexts and the target context (that named by all but terminal
atomic component of the name) must already exist
That's what documentation's for, you know?
View the original post :
Or, instead of hacking config files, you could run 'shutdown.bat' (or 'shutdown.sh')
with no parameters and discover that there's a '-s' option which appears to solve the
problem.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3840156#3840156
Reply to the post
Errr... because fscontext doesn't obey the spec?! Sheesh!
Just because you've got away lucky with fscontext and Orion not obeying the spec,
doesn't mean you should JBoss to let you be so lax!
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3840163#3840163
Reply
Have you read the jTDS documentation? Your JDBC URL is invalid.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3839781#3839781
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3839781
Eeek. My bad. Sorry, it's fine - I thought IBCAMPAIGN was an instance name, but it's a
database name. Sorry.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3839782#3839782
Reply to the post :
What you are trying to do is disallowed by the J2EE spec. Having said that, JBoss does
nothing specific to prevent you from using JNI.
Have you managed to make this work outside the JBoss environment? i.e. write a simple
standalone Java program and try it. Note that the method name mangling
Are you sure this is right? This would imply a method called 1java in a class called
1crv1 in a package called ShowBondcrv1.aaBond. Neither the package name nor the class
name follow normal Java naming conventions, and the method name is simply illegal.
If your method name has _ characters in
If System.LoadLibrary returns without an exception, the library loaded OK (I think).
I can't conceive of any legal Java method signature which the JVM would map to the C
method signature you've quoted.
Tell me the full package name, class name and method name of the Java native method,
and
I guess that would map to a C method called Java_ShowBondcrv1_aaBond_crv1_java, except
that I'm not sure how the _ characters in the method name are handled. Looking at your
earlier example, it might turn _ into _1, which would leave the C method as
Java_ShowBondcrv1_aaBond_1crv1_1java, which
If you declare your XML as UTF8, it's usually best to make sure it actually is UTF8!
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3839539#3839539
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3839539
RTFM. Find out (with the help of the stacktrace and the JDK Javadoc) under what
circumstances a java.io.NotSerializableException can be thrown. Then figure out
(again, with the help of the stacktrace which pretty much gives you the answer) why a
NotSerializableException is being thrown in this
Yes. Read the release notes and better understand what version of JBoss IDE you have
downloaded.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3839079#3839079
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3839079
raagav already said he can't use the update manager (although it's unclear why that
won't work, but he can download the code directly)
Note, that you don't need JBoss IDE to debug your EJB's - you can just start JBoss in
debug mode (see run.bat) and connect the Eclipse debugger to it.
View
Java broadly divides exceptions into two types: checked and unchecked. Unchecked
exceptions derive from RuntimeException or Error. Everything else is a checked
exception. Checked exceptions are the ones that the compiler forces you to either
catch or else declare with a throws clause in your
OK. I assume it still doesn't work? Are you setting the PERSISTENT property CORRECTLY?
I vaguely recall there are two ways to do it. What works for me (although it appears
to contradict the Javadoc for QueueSender) is to set the property on the Message
immediatly before calling
Have you read the JMS spec? Have you read about delivery modes?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3838750#3838750
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3838750
Oh, and it also depends on whether your database supports transactions. I understand
that certain configuration of MySQL, for example, don't. Not sure about Hypersonic.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3838675#3838675
Reply to the post :
At the risk of sounding stupid, have you read the error message? Have you definied get
and set methods for the CMP fields mentioned? If so, show the bean's code (including
the interfaces, etc.)
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3838439#3838439
anonymous wrote : While the above code does work, I am a bit concerned about relying
on the implementation of the JBoss specific WrappedResultSet. Plus, the JDBC code is
no longer completely portable across app servers.
And you're not worried about relying on the implementation of the Sybase
Other options high on my list would be to beat Sybase into implementing the spec as
written and not doing a Microsoft and making it up as they go along.
Another option would be to consider a different driver. Try jTDS at
jtds.sourceforge.net
View the original post :
JDK1.5 includes JMX. JBoss does not currently run on JDK1.5 - and besides, JDK1.5 is
still a beta release. Use a 1.4 JDK.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3836228#3836228
Reply to the post :
If you want to use ant, why not just use the 'copy' task and copy your deployment into
the deploy directory? If you want to deploy to a remote machine, either use its UNC
name if it's Windows (\\machine\c$\...\server\default\deploy), or else for Unix use
rcp, NFS mount, etc.
View the original
Hi Simon,
The DTD does exist at that URL. Perhaps you need to go via a proxy to access the
Internet, which IE understands but ANT doesn't?
ANT will be trying to resolve the DTD externally because it won't have an
EnitityResolver configured which understands the public ID. Perhaps you can tell
Which bit of anonymous wrote : Goto the log4j site and read their documentation. did
you not understand?!
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3835196#3835196
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3835196
Resist, Adrian! Resist!!! :-)
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3834954#3834954
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3834954
---
This SF.Net email
It's not strange behaviour, it's the spec.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3833878#3833878
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3833878
---
This
Have you tried typing An error occurred at line: -1 in the jsp file: null into
Google? Or, in fact, doing any research at all?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3833881#3833881
Reply to the post :
Mr Smartass? Flattery indeed.
The solution was not at all obvious to me. I think the error message is very
misleading. My point was simply this:
You posted a message on the forum. The only reply you had in 12 hours was from me.
When I typed An error occurred at line: -1 in the jsp file: null
Firstly, don't put orb.jar in the lib directory, but it right at the top of the EAR.
Then, change your manifest class path to just orb.jar
A better approach (once you start having more JARs and complex dependencies between
them) is simply to define modules in your application.xml
View the
It never ceases to amaze me the amount of things people seem to guess and try and
then when it doesn't work they spend ages asking on mailing lists and waiting for
replies.
I spent 24 seconds (I timed it) going to the J2SE online documentation and looking for
Why do you think the jmsDeliveryMode 2 stands for NON_PERSISTENT? Instead of
guessing, I consulted the J2EE API documentation. This clearly states that
javax.jms.DeilveryMode.PERSISTENT = 2 (NON_PERSISTENT = 1)
View the original post :
Yep.
It's java:comp, not java:/comp
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3829413#3829413
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3829413
---
This SF.Net
Poking around in the JMS console shows that jboss.mq:service=InvocationLayer,type=JVM
has an attribute ConnectionFactoryJNDIRef which has a value java:/ConnectionFactory
This could well be the MBean you need to wait for
View the original post :
amlgroup - this sounds like it might be a transaction issue. Is your Session Bean
running in a transaction? Are you commiting the JMS transaction (which is different
from the CMT managed tx) after your send?
a
href=http://www.jboss.org/index.html?module=bbop=viewtopicp=3827019#3827019;View
The JAR file layout you quote appears to show AAAException.class in mycomp/ejb, not
mycomp/ejb/myejb. Perhaps this is the problem?
a
href=http://www.jboss.org/index.html?module=bbop=viewtopicp=3827021#3827021;View
the original post/a
a
Well, a tiny bit of logical thinking here...
If localhost doesn't work, but 127.0.0.1 does, that would suggest you have a
naming issue resolving localhost.
This is also bourne out by looking at the stack trace you have quoted. The most nested
exception says java.net.UnknownHostException:
You'd get a much faster answer you asked the same question 10 times instead of 4, just
in case. Using a language which the majority of readers won't understand would also
help.
a
href=http://www.jboss.org/index.html?module=bbop=viewtopicp=3824719#3824719;View
the original post/a
a
WHY WHY WHY do people insist on killing processes? They do it at here work and it
causes all sorts of problems. There's a perfectly good shutdown mechanism which will
ensure everything is shutdown cleanly. Try doing a kill -9 (or Windows equivalent) on
the Eclipse IDE and see where that gets
Errr... I suggest you re-read the document. The description you give applies to the
deploy directory.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3823793#3823793
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3823793
You're welcome.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3823809#3823809
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3823809
---
SF.Net is sponsored by: Speed
I think you misunderstand JMS. You can have many receivers all receiving messages from
the same queue. Each message will go to one receiver, and the spec states that the
decision about which receiver is random.
View the original post :
54 matches
Mail list logo
