Andrew Moko

You need to go back to your scjp notes. It's a whole topic that can't simply be explained in a sentence.

But, simply put you don't have to worry about implementing your own safety methods just so classes/ methods/ variables are EXCLUSIVE. This mainly achieved by synchronization, wait()/ notify() etc etc.

Unless you want to do something very specific with the 'unconsumed 'message, i'd replace the Topic with a Message Queue. Messages on the queue are redelivered on failured attempts/ timeouts

I don't see the Handler progressHandler in the MainActivity class being initialized. Learn to read and follow through the error stack messages.

at com.myapp.test.ProgressInputStream.sendLong(ProgressInputStream.java:76)

We need to view your code.

The java program doing the upload uses a set of libraries/ apis which OBVIOUSLY don't work in android.

Alternatively, fire-up another file upload app (with startActivity) and receive the response in your logic..

karthik kummar wrote:Hi Friends i am new to java beans. i am trying to implement Simple MDB using Netbean tool. but in client programming, i am getting error at JNDI lookup line. i am using JBOSS as server. my coding details are given below.

MDB code:

package model; import javax.ejb.MessageDrivenBean; import javax.ejb.MessageDrivenContext; import javax.jms.JMSException; import javax.jms.Message; import javax.jms.MessageListener; import javax.jms.TextMessage; public class SimpleMessageBean implements MessageDrivenBean, MessageListener { private MessageDrivenContext context; public void setMessageDrivenContext(MessageDrivenContext aContext) { context = aContext; } public void ejbCreate() { // TODO Add code to acquire and use other enterprise resources (DataSource, JMS, enterprise bean, Web services) } public void ejbRemove() { // See section 15.7.3 of the EJB 2.1 specification } public void onMessage(Message aMessage) { TextMessage msg = null; try { if (aMessage instanceof TextMessage) { msg = (TextMessage) aMessage; System.out.println ("MESSAGE BEAN: Message received: " + msg.getText()); } else { System.out.println ("Message of wrong type: " + aMessage.getClass().getName()); } } catch (JMSException e) { e.printStackTrace(); // mdc.setRollbackOnly(); } catch (Throwable te) { te.printStackTrace(); } } }

ejb-jar.xml:



<?xml version="1.0" encoding="UTF-8"?> <ejb-jar version="2.1" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd"> <display-name>SimpleMDB-ejb</display-name> <enterprise-beans> <message-driven> <display-name>SimpleMessageBeanMDB</display-name> <ejb-name>SimpleMessageBean</ejb-name> <ejb-class>model.SimpleMessageBean</ejb-class> <transaction-type>Container</transaction-type> <message-destination-type>javax.jms.Queue</message-destination-type> <message-destination-link>jms/MyQueue</message-destination-link> <activation-config> <activation-config-property> <activation-config-property-name>acknowledgeMode</activation-config-property-name> <activation-config-property-value>Auto-acknowledge</activation-config-property-value> </activation-config-property> <activation-config-property> <activation-config-property-name>destinationType</activation-config-property-name> <activation-config-property-value>javax.jms.Queue</activation-config-property-value> </activation-config-property> </activation-config> </message-driven> </enterprise-beans> <assembly-descriptor> <container-transaction> <method> <ejb-name>SimpleMessageBean</ejb-name> <method-name>*</method-name> </method> <trans-attribute>Required</trans-attribute> </container-transaction> <message-destination> <display-name>Destination for SimpleMessageBeanMDB</display-name> <message-destination-name>jms/MyQueue</message-destination-name> </message-destination> </assembly-descriptor> </ejb-jar>

jboss.xml:

<?xml version="1.0" encoding="UTF-8"?> <jboss> <enterprise-beans> <message-driven> <ejb-name>SimpleMessageBean</ejb-name> <destination-jndi-name>queue/jms/MyQueue</destination-jndi-name> </message-driven> </enterprise-beans> </jboss>


client code:

package view; import javax.jms.*; import javax.naming.Context; import javax.naming.InitialContext; public class SimpleMessageBeanClient { private static Queue queue = null; QueueConnectionFactory queueConnectionFactory = null; QueueConnection queueConnection = null; QueueSender queueSender = null; QueueSession queueSession = null; private TextMessage message=null; [b] Context jndiContext;[/b] public SimpleMessageBeanClient(){ try { //client creates the connection, session, and message sender: queueConnectionFactory = (QueueConnectionFactory)jndiContext.lookup("java:comp/env/jms/MyQueueConnectionFactory"); queue = (Queue)jndiContext.lookup("java:comp/env/jms/QueueName"); queueConnection = queueConnectionFactory.createQueueConnection(); queueSession =queueConnection.createQueueSession(false,Session.AUTO_ACKNOWLEDGE); queueSender = queueSession.createSender(queue); message = queueSession.createTextMessage(); for (int i = 0; i < 5; i++) { message.setText("This is message " + (i + 1)); System.out.println("Sending message: " + message.getText()); queueSender.send(message); } System.out.println("Sending message"); //session.close (); } catch (Exception e) { e.printStackTrace (); } } public static void main(String[] args) { SimpleMessageBeanClient sim = new SimpleMessageBeanClient(); } }



MDB is deploying without any error, but while run the client program 21st line searching for connection factory getting failed with error as null pointer exception whether i have to change in *.xml files. could you please advice on this.

It simply means You have a NPE AND You need to initialize the jndiContext and optionally pass in the environmental configuration variables to the constructor:

Context jndiContext = new InitialContext(); // use default environmental vars
or
jndiContext = new InitialContext(env); // env - configuration property file with env. variables.

I'm thinking of a fast algorithm to get kony off his hide holes,. any ideas??

Wendy Gibbons wrote:sorry a DOH moment, hashmaps DOH.

LOL

*off for my coffee break TGIF*

This is a jndi issue. I would navigate to the JNDI tree on the weblogic console and verify the bean interface mapped name

Wendy Gibbons wrote:

Andrew Moko wrote:

Wendy Gibbons wrote:I do, you can either have 20 small classes, or 1 enum each with it's own method

can you show me how you would do it with generics?

Sure. Here's my two centavos..

public class LocalizationDataModel{ private String language; public <T> void setLang(T language){ this.language = (String) language; } }

This method allows languages to be set dynamically without necessarily modifying the LocalizationDataModel class.

you haven't shown how you get the language class from the ID that is supplied, how you get rid of that big case statement?

public class LocalizationDataModel{ private Integer languageId; private String language; private final static HashMap<Integer, String> mapLang = new HashMap<Integer, String>(){ { put(1, "english"); put(2, "polish"); // etc } }; public <T> void setLang(T language){ // Language validations are implemented here... E.g if(languageId == mapLang.get((String)language){ this.language = (String) language; } } public void setLanguageId(){ // retrieve and set id from database/ flat file etc etc.. // e.g languageId = 1; } public Integer getLanguageId(){ return this.languageId; } }

I'm i missing out something??

Wendy Gibbons wrote:I do, you can either have 20 small classes, or 1 enum each with it's own method

can you show me how you would do it with generics?

Sure. Here's my two centavos..

public class LocalizationDataModel{ private String language; public <T> void setLang(T language){ this.language = (String) language; } }

This method allows languages to be set dynamically without necessarily modifying the LocalizationDataModel class.

Yes. You need an "ajax-push-server" technology to dynamically push data from server-client.

http://en.wikipedia.org/wiki/Comet_%28programming%29

Wendy Gibbons wrote:Have a look at enums (not enumerations)

here is a good page:
http://docs.oracle.com/javase/1.5.0/docs/guide/language/enums.html

I would make a method in ModelToCheck that took a language and s_TheTranslation, then this code could be inside model to check.

then inside model to check it could use the enum.

here is some psuedo code, because how to get the correct enum from the id is a bit of a learnt trick (it will not compile)
enum language{ ENGLISH(1), POLISH(2); public language(int magicNumberIdentifyingLanguage){ this.id = magicNumber; } public language getLanguageFromId(int id) { language list = language.getEnums; for(language item: list) { if(item.id == id) return item; } } // other stuff to actually do processing on the language }

Who uses enums, Wendy ;)

Proper use of generics brings out well-laid out, short understandable code and abstracts complexity. I'd create a generic method on modelToCheck that takes a language type. Inside the method check the language and call the appropriate method/ functions.

Looks like the OP wants his requirements fit the EJB technology. I still remember the hype that came with design patterns most developers would complicate a simple logic just to take advantage of the patterns.

Should you be binding or looking up the data source???